Fork docs/sync/ in docs/website/ (https://chromium.org)

We should keep these docs in a single place for simpler maintenance.
docs/website/ seems to be strictly better option, because besides
  * Appearing on code search
  * Being rendered by gittiles
like docs/sync/, it will also
  * Be rendered in chromium.org, which is often used by new
  contributors

For the moment we just copy the content to docs/website/ because the
directories are in different repositories. A second CL will follow
to delete docs/sync/.

Bug: 1006699
Change-Id: I55b6565c203686965e078bc42c63f918cd894436
Reviewed-on: https://chromium-review.googlesource.com/c/website/+/3401841
Reviewed-by: Dirk Pranke <dpranke@google.com>
Reviewed-by: Marc Treib <treib@chromium.org>
Commit-Queue: Victor Vianna <victorvianna@google.com>
11 files changed
tree: dbd3265e382b97f22e869139e2427bcc18a95fd9
  1. docs/
  2. infra/
  3. scripts/
  4. site/
  5. third_party/
  6. .eleventy.js
  7. .firebaserc
  8. .gclient
  9. .gitignore
  10. .vpython3
  11. AUTHORS
  12. CONTENT_OWNERS
  13. DEPS
  14. node_modules.tar.gz.sha1
  15. npmw
  16. originals.tar.gz.sha1
  17. OWNERS
  18. package-lock.json
  19. package.json
  20. PRESUBMIT.py
  21. README.md
README.md

Source code for www.chromium.org

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

NOTE: 2021-11-15. 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.

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