Site launch checklist
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 3
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 8
Description
Before launch
- Review the approach to redirects ie 301 vs 302
- Address FIXMEs in the code
- Validate W3C compliance of HTML, CSS
- server rendered HTML is compliant per validator.w3.org
- server rendered CSS is compliant per validator.w3.org except for not knowing some modern CSS like container properties.
- Test accessibility further (Lighthouse, manual testing)
- test every markdown page
- test index pages
- Analytics (Matomo)
- should it use the same site id as Red?
- ensure prod uses prod Matomo envs
-
JSON-LD? - Health check route
Contributor guide
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
Start by separating the unchecked checklist items into concrete tasks, then inspect the redirect handling, FIXME locations, CSS validation, Markdown and index pages, and health check route. Use Lighthouse, manual accessibility testing, and the W3C validator where named. Done requires each remaining launch item to be resolved or tracked in a focused issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, html, typescript
- Domain
- accessibility, full-stack, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100