Preview-driven
References should be scannable visually before an engineer has to inspect code or notes.
A reference library built for engineering decisions, not just inspiration.
Frontend Reference is the first reference track inside Featlas: a working library for frontend teams to compare UI patterns, inspect implementation details, and keep reusable decisions in one system.
Code-backed
Each item includes implementation snippets that are strong enough to serve as a real baseline.
Context-aware
States, accessibility, and responsive behavior stay attached to the same item instead of being scattered across docs.
What it should feel like
- A clean docs-style reading flow with navigation on the left and focused content in the center.
- A content model that scales from small primitives to larger sections without collapsing taxonomy.
- A practical editorial standard so new references stay consistent as the library grows.
Why this structure matters
A large UI gallery becomes noisy quickly when previews, code, states, and writing standards are separated. This project keeps them together so the browsing experience still scales when the item count grows.
The result should feel closer to a frontend handbook than a loose screenshot collection: opinionated enough to guide choices, but still practical enough to support daily implementation work.