Skip to content
FEE
Frontend Engineering Essentials

Frequently Asked Questions ​

General Questions ​

What is FEE? ​

FEE (Frontend Engineering Essentials) is a numbered collection of frontend engineering guidelines. See FEE-0 for the full overview.

Who is FEE for? ​

Frontend engineers at all levels -- from those learning fundamentals to senior engineers deepening their architecture skills. FEE builds conceptual foundations, not vendor-specific tutorials.

Is FEE specific to a particular framework? ​

No. FEE principles are vendor-agnostic and framework-agnostic. When a concept is best illustrated with a specific technology, it is clearly noted as an example, not a recommendation.

How does FEE relate to BEE, ADE, and DEE? ​

FEE covers frontend engineering broadly. BEE (Backend Engineering Essentials) covers backend. ADE (API Design Essentials) goes deep on API design. DEE (Database Engineering Essentials) goes deep on database design. They cross-reference each other where topics overlap.

Can I propose a new FEE? ​

Yes. Follow the structure described in FEE-0 and submit a pull request.

Content Questions ​

Why RFC 2119 keywords (MUST, SHOULD, MAY)? ​

These keywords provide precise guidance levels. MUST means the principle is non-negotiable. SHOULD means follow it unless you have a documented reason not to. MAY means it is optional.

How are FEE numbers assigned? ​

FEEs are numbered by category range with 100 per category. See the category table in FEE-0 for the full mapping.

What if my situation requires deviating from a FEE? ​

Document the reason. FEEs are guidelines, not laws. The goal is to make informed decisions, not to blindly follow rules.