laywill / laywill/laywill.github.io
Cutover: launch v2.0.0
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 0
- Forks
- 0
- Avg merge
- 8h 17m
- Merged PRs (30d)
- 58
Description
Execute the runbook in architecture.md: rc-tag pre-flight → DNS confirmed → default branch flipped to main → master workflow disabled → push v2.0.0 → verify www/apex/HTTPS/redirect stubs → re-verify Search Console + submit sitemap → Lighthouse ≥95 perf/a11y/SEO → delete stale branches.
William: final go/no-go before the tag is pushed.
Depends on: every other epic.
Acceptance criteria
- All runbook steps checked off in order
- Rollback path verified as documented before starting
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the cutover runbook in docs/overhaul/architecture.md at the linked section, then follow its rc-tag pre-flight and dependency checks. Complete the DNS, branch, workflow, v2.0.0, site, Search Console, sitemap, Lighthouse, and stale-branch steps in order; done means every acceptance criterion is checked and the documented rollback path is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- ci-cd, cloud, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100