Attempt to fix `led` ACLs for testing recipe changes.

It looks like we need to grant some more permissions in order
to be able to run `led` and test recipe changes against our

Bug: 1260171
Change-Id: Iac7cc49fe8fa433e6bbc6e9fa5cd01e8eb8c78c0
Reviewed-by: Vadim Shtayura <>
Commit-Queue: Dirk Pranke <>
2 files changed
tree: 3eb7116e075fd4f918047770df266a755e99bedb
  1. docs/
  2. infra/
  3. scripts/
  4. site/
  5. third_party/
  6. .eleventy.js
  7. .firebaserc
  8. .gclient
  9. .gitignore
  10. .vpython3
  12. DEPS
  13. firebase.json
  14. node_modules.tar.gz.sha1
  15. npmw
  16. OWNERS
  17. package-lock.json
  18. package.json

Source code for

This Git repo contains the source content for

NOTE: 2021-10-19. This is not (yet) actually true. This is a work-in-progress repo that we plan to move to.

The website is implemented by serving static content (mostly Markdown files) that is translated / built ahead of time into HTML using the Eleventy static site generator (which is written in Node/JS) and deployed onto Firebase Cloud Hosting.

The Markdown is translated using a single extremely simple Nunjucks template and the site is served with a single basic Sass/SCSS stylesheet (using the Node/NPM library version of Sass).

Large objects (PDFs, big images, etc.) are stored in a Google Cloud Storage bucket, indexed by SHA-1 checksums that are committed into this repo.

See //docs/ if you wish to contribute to the site.