[FEE-0] FEE Overview
INFO
FEE (Frontend Engineering Essentials) is a collection of vendor-agnostic guidelines and best practices for frontend engineering.
Context
Frontend engineering spans a vast landscape -- from HTML semantics and CSS layout to component architecture, state management, and build tooling. Engineers often learn these concepts piecemeal, through scattered blog posts, framework-specific tutorials, or painful production debugging. FEE provides a structured, numbered set of principles that build a coherent mental model of frontend engineering.
Purpose
- Establish shared vocabulary for frontend engineering discussions
- Provide actionable, vendor-neutral guidance for common frontend decisions
- Serve as an onboarding resource for engineers at all levels
- Bridge the gap between "I know the framework" and "I understand the platform"
How to Read FEEs
Each FEE follows a consistent structure:
- Context -- Why this principle matters
- Scenario (100–400 series only) — A concrete product situation showing when this API or feature is the right tool.
- Design Thinking -- The mental model and reasoning behind the principle
- Best Practices -- Actionable rules (MUST / SHOULD / AVOID)
- Visual -- Diagrams where they aid understanding
- Example -- Concrete, vendor-agnostic examples
- Common Mistakes -- Anti-patterns to avoid
- Related FEEs -- Cross-references to other principles
- References -- External resources for deeper learning
Categories
Foundation Layer (0-499)
| Range | Category | Focus |
|---|---|---|
| 0-99 | FEE Overall | Purpose, glossary, meta |
| 100-199 | HTML & Semantic Markup | Document structure, accessibility semantics, forms |
| 200-299 | CSS & Layout Systems | Box model, flexbox, grid, responsive design |
| 300-399 | JavaScript Core & Runtime | Event loop, closures, prototypes, modules |
| 400-499 | Browser APIs & Web Platform | DOM, fetch, storage, workers, intersection observer |
Architecture & Patterns Layer (500-799)
| Range | Category | Focus |
|---|---|---|
| 500-599 | Component Architecture & Design Patterns | Composition, slots, reactivity, separation of concerns |
| 600-699 | State Management | Local vs global state, derived state, sync patterns |
| 700-799 | Rendering & Performance | Virtual DOM, hydration, lazy loading, core web vitals |
Tooling & Systems Layer (800-999)
| Range | Category | Focus |
|---|---|---|
| 800-899 | Build Tooling & Module Systems | Bundlers, tree-shaking, ESM, dev servers |
| 900-999 | Design Systems & UI Libraries | Tokens, theming, component libraries, documentation |
Engineering Practices Layer (1000-1699)
| Range | Category | Focus |
|---|---|---|
| 1000-1099 | Accessibility (a11y) | ARIA, screen readers, keyboard navigation, color contrast |
| 1100-1199 | Testing Strategies | Unit, integration, E2E, visual regression, accessibility testing |
| 1200-1299 | Security | XSS, CSP, CORS, subresource integrity, sanitization |
| 1300-1399 | Progressive Web Apps & Offline | Service workers, caching strategies, app manifest |
| 1400-1499 | Observability & Error Tracking | Error boundaries, logging, RUM, source maps |
| 1500-1599 | CI/CD & Deployment | Build pipelines, preview deploys, CDN, cache busting |
| 1600-1699 | Developer Experience & Tooling | Linting, formatting, monorepos, dev servers, IDE integration |
Related Resources
- BEE -- Backend Engineering Essentials
- ADE -- API Design Essentials
- DEE -- Database Engineering Essentials
Article Metadata Fields
Each FEE article's frontmatter carries the following fields:
| Field | Values | Meaning |
|---|---|---|
id | integer | Unique article number within the FEE numbering scheme |
title | string | Human-readable article title |
state | draft, placeholder | Publication state |
overview | true (omitted if false) | Marks category overview pages; these do not have a level field |
level | entry, mid, senior, ??? | Intended audience difficulty. entry = suitable for juniors; mid = assumes solid fundamentals; senior = advanced depth. ??? = pending manual review. |
Maintainer
Alive Kuo -- alegnadise@gmail.com