Suggest starting spec-writing around the beginning of origin trials.

While features vary in when they should write their specs, the guidance to
finish the spec in the phase before origin trials was too early, and the
guidance lacked any instruction about when to start writing. Doing it too early
means that if the design changes, we have to rewrite an expensive spec instead
of the cheaper explainer.

I also renamed that phase to "Widen review", since "Evaluate readiness to ship"
was confusingly similar to "Prepare to ship", and the phase seems to be roughly
about getting wider reviews.

Change-Id: I15eef7476f7da8c0a04ac59a94cbf5b64c18e835
Reviewed-on: https://chromium-review.googlesource.com/c/website/+/4162680
Commit-Queue: Jeffrey Yasskin <jyasskin@google.com>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Auto-Submit: Jeffrey Yasskin <jyasskin@google.com>
1 file changed
tree: f785c76526d032cc68b862594e9db426bba15070
  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. DIR_METADATA
  15. node_modules.tar.gz.sha1
  16. npmw
  17. originals.tar.gz.sha1
  18. OWNERS
  19. package-lock.json
  20. package.json
  21. PRESUBMIT.cfg
  22. PRESUBMIT.py
  23. 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.