commit | 8bce55e655caa8a35b7c23c59690cf8032fb0f98 | [log] [tgz] |
---|---|---|
author | Dirk Pranke <dpranke@google.com> | Fri Oct 22 15:24:53 2021 |
committer | chromium-website-scoped@luci-project-accounts.iam.gserviceaccount.com <chromium-website-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Oct 22 20:55:22 2021 |
tree | 3eb7116e075fd4f918047770df266a755e99bedb | |
parent | 2381c9d8305fee4a2d02fab5cbee46d209f50483 [diff] |
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 builders. Bug: 1260171 Change-Id: Iac7cc49fe8fa433e6bbc6e9fa5cd01e8eb8c78c0 Reviewed-on: https://chromium-review.googlesource.com/c/experimental/website/+/3238585 Reviewed-by: Vadim Shtayura <vadimsh@chromium.org> Commit-Queue: Dirk Pranke <dpranke@google.com>
This Git repo contains the source content for www.chromium.org.
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/CONTRIBUTING.md if you wish to contribute to the site.