Requirement Engineering
A checklist of concerns to work through when starting a frontend project. Not every section applies to every engagement — scan the headers and focus on what's relevant to your project.
Design Systems
A design system is more than a component library. It's the combination of design tokens, reusable components, interaction patterns, usage guidelines, tooling, and governance that keeps a product's UI consistent as it scales. Done well, it accelerates development, creates a shared vocabulary between designers and developers, and bakes accessibility in from the start.
Estimation
1 item
Choosing a Rendering Architecture
This page helps you pick the right rendering strategy for your project. For detailed descriptions of each approach and their trade-offs, see Rendering Architectures.
Cookbooks
7 items
Evaluating npm Packages
Before adding a dependency, invest a few minutes evaluating it. Every package you adopt becomes a long-term commitment — it affects bundle size, maintenance burden, upgrade paths, and security surface. This page provides a structured evaluation workflow. For security-specific vetting (supply chain, typosquatting, install scripts), see the npm Security Checklist.
Microfrontends
Microfrontends are an architectural approach to building a web product from independently owned frontend parts. A composition layer brings those parts together into a user experience; each part may represent a business capability or a user-facing domain. The goal is to apply some of the organizational and delivery benefits of independently deployable services to the frontend.