Skip to content
FEE
Frontend Engineering Essentials

[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) ​

RangeCategoryFocus
0-99FEE OverallPurpose, glossary, meta
100-199HTML & Semantic MarkupDocument structure, accessibility semantics, forms
200-299CSS & Layout SystemsBox model, flexbox, grid, responsive design
300-399JavaScript Core & RuntimeEvent loop, closures, prototypes, modules
400-499Browser APIs & Web PlatformDOM, fetch, storage, workers, intersection observer

Architecture & Patterns Layer (500-799) ​

RangeCategoryFocus
500-599Component Architecture & Design PatternsComposition, slots, reactivity, separation of concerns
600-699State ManagementLocal vs global state, derived state, sync patterns
700-799Rendering & PerformanceVirtual DOM, hydration, lazy loading, core web vitals

Tooling & Systems Layer (800-999) ​

RangeCategoryFocus
800-899Build Tooling & Module SystemsBundlers, tree-shaking, ESM, dev servers
900-999Design Systems & UI LibrariesTokens, theming, component libraries, documentation

Engineering Practices Layer (1000-1699) ​

RangeCategoryFocus
1000-1099Accessibility (a11y)ARIA, screen readers, keyboard navigation, color contrast
1100-1199Testing StrategiesUnit, integration, E2E, visual regression, accessibility testing
1200-1299SecurityXSS, CSP, CORS, subresource integrity, sanitization
1300-1399Progressive Web Apps & OfflineService workers, caching strategies, app manifest
1400-1499Observability & Error TrackingError boundaries, logging, RUM, source maps
1500-1599CI/CD & DeploymentBuild pipelines, preview deploys, CDN, cache busting
1600-1699Developer Experience & ToolingLinting, formatting, monorepos, dev servers, IDE integration
  • BEE -- Backend Engineering Essentials
  • ADE -- API Design Essentials
  • DEE -- Database Engineering Essentials

Article Metadata Fields ​

Each FEE article's frontmatter carries the following fields:

FieldValuesMeaning
idintegerUnique article number within the FEE numbering scheme
titlestringHuman-readable article title
statedraft, placeholderPublication state
overviewtrue (omitted if false)Marks category overview pages; these do not have a level field
levelentry, 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