Engineering / frontend
Frontend systems
The frontend is a reading instrument: it should make hierarchy, state, and the next useful action obvious.
Content has a shape
Editorial interfaces work when content is allowed to lead. A page header states the claim, metadata stays small, and a list or record gives the reader a stable rhythm instead of a wall of decorative containers.
- Use real headings and links before adding interaction.
- Keep loading and empty states useful rather than ornamental.
- Design for the narrow screen first because constraint clarifies hierarchy.
Edge-friendly rendering
Next.js on Pages should keep the runtime surface small: fetch content from the single API Worker, render stable pages at the edge, and avoid an image or server dependency that the deployment cannot provide.
A fast page is not just a low number. It is a page that gives the reader the right thing without waiting for a second guess.
Accessible by default
Labels, focus states, keyboard paths, contrast, reduced motion, and meaningful alt text are not polish. They are the interface for somebody whose browser or body does not match the designer's assumptions.