Update recipe configuration.

It turns out that we need to set up recipe builders to automatically
pick up changes to recipes in a repo and build CIPD bundles for
them to be used on the bots. This means that there is some amount
of overhead to having the recipes be in the source repo, as opposed
to an existing repo that already has builders.

I've moved the chromium_website recipe to the tools/build repo as
a result; later I'll see if I can update things to move the recipe
back here.

Also, this CL fixes the cipd package name for the recipe bundle,
which was set incorrectly before.

Bug: 1260171
4 files changed
tree: a4a6a19f499e423ea5b16ad97b78267a8a3b81af
  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
  19. PRESUBMIT.py
  20. README.md

Source code for www.chromium.org

This Git repo contains the source content for www.chromium.org.

NOTE: 2021-10-13. 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.