Standards-first, not framework-first
A framework is a means, not an end. The thing you actually ship is HTML, CSS and (ideally very little) JavaScript. This starter treats the standards as the product and the framework as the build tool.
The checklist this site holds itself to
- Valid HTML per the W3C validator — zero errors.
- One
<h1>per page, logical heading order, real landmarks. - Canonical URLs, Open Graph, sitemap, RSS, robots.txt.
- A+ on securityheaders.com and Mozilla Observatory.
- WCAG 2.2 AA: skip link, visible focus, contrast, reduced-motion.
- Lighthouse 95+/100/100/100 across Performance, Accessibility, Best-Practices, SEO.
Why it lasts
Frameworks churn. Standards don’t. A site built on valid semantic HTML and a small stylesheet will still render, rank and be readable years from now — by browsers, by search engines, and by whatever reads the web next.