FT
Featlas
Frontend Reference
Guidelines

Standards for keeping the library useful as it grows.

A reference library only stays valuable if new items are added with discipline. These guidelines define the minimum bar for content quality, accessibility, naming, and implementation readiness.

Content quality

  • The preview should match the source code closely enough that engineers can trust what they see.
  • Titles must be specific and easy to scan in sidebar, cards, and search results.
  • A new item should introduce a clear variation, not a barely different duplicate.

Accessibility baseline

  • Interactive states should remain usable by keyboard, not only by pointer.
  • Visible focus treatment should never disappear in the final implementation.
  • ARIA notes should be included when a component needs specific behavior beyond plain HTML.

Naming and taxonomy

  • Domain, category, and item slug should stay explicit and predictable.
  • A reference belongs to one primary category to keep navigation clean.
  • Preview components must remain separate from the shell used to present the website itself.

Definition of done

  • Every item should include preview, source code, explanation notes, and state coverage.
  • Responsive and accessibility notes should be written as practical guidance, not generic filler.
  • Before publishing, the item should be reviewed in the context of neighboring references so the collection stays coherent.