commit | b345e171afe4551a19f9954ed04054c28d89d6f7 | [log] [tgz] |
---|---|---|
author | Dirk Pranke <dpranke@google.com> | Wed Oct 20 16:01:43 2021 |
committer | chromium-website-scoped@luci-project-accounts.iam.gserviceaccount.com <chromium-website-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Oct 20 16:30:30 2021 |
tree | a247808da6818a6ac99609d3860194b01d3152db | |
parent | 141fe73318eb87c1f660fa1c2170844fbd9e8674 [diff] |
Add gatong@ and sshrimp@ to OWNERS for more redundancy. Until we get a better list of top-level OWNERS, we should have at least a few more people to avoid singletons. Change-Id: I9036d8130c75b156ae3ff653d7a4edb1a7a03aa9 Reviewed-on: https://chromium-review.googlesource.com/c/experimental/website/+/3234017 Reviewed-by: Struan Shrimpton <sshrimp@google.com> 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.