Site launch checklist

Open
#51 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
css, html, typescript
Domain
accessibility, full-stack, release

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.

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
Dominant language
TypeScript
Stars
1
Forks
3
Avg merge
1d 8h
Merged PRs (30d)
8

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ietf-tools/queue

All issues in ietf-tools/queue

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.