Understand
Build the mental model through structured, first-principles explanations.
03 / Knowledge product
Frontend Engineering Wiki
A growing map of frontend engineering connecting first-principles explanations, interview reasoning, quick references, and deliberate practice.
- Role
- Creator and engineer
- Period
- 2026 — ongoing
- Scale
- 10 chapters · 224 answers · 12 tracks
- Status
- Growing
01 / The problem
Frontend knowledge is abundant. Finding the right explanation is difficult.
Documentation, articles, interview lists, and courses each solve a different part of learning. The Wiki connects them into a route from first understanding to confident application.
ConnectedMental model
02 / The learning loop
One topic. Four useful ways to engage with it.
Take debounce: understand why calls are delayed, explain how it differs from throttling, recall the meaning of cancel and flush, then implement those behaviors. The goal is to connect a definition to a decision an engineer can make in a real interface.
Explain
Turn understanding into concise answers for interviews, reviews, and technical conversations.
Recall
Retrieve important distinctions, rules, and terminology through compact references.
Apply
Reinforce the concept through exercises, debugging scenarios, and implementation prompts.
03 / Information architecture
The structure grows without becoming a content dump.
Readers can navigate by goal, topic, or depth without losing their position in the wider system.
Tracks provide a route
Twelve learning tracks group related ideas into navigable paths without preventing exploration of individual topics.
Links expose the system
Explanations connect prerequisites, adjacent concepts, practical consequences, and deeper material.
Content modes stay distinct
Long explanations, compact answers, references, and exercises each keep the shape appropriate to their purpose.
04 / Editorial decisions
Content is designed as deliberately as an interface.
Depth should be intentional
- Pressure
- One reader may need a five-minute reminder; another needs the complete mental model.
- Decision
- Separate quick answers from deep explanations and link them in both directions.
Navigation should teach
- Pressure
- A flat article list hides how frontend concepts depend on one another.
- Decision
- Organize material into tracks and expose relationships between topics.
Practice should follow reasoning
- Pressure
- Passive reading can feel clear without producing durable understanding.
- Decision
- Connect explanations to recall prompts, questions, and practical exercises.
Growth should remain visible
- Pressure
- An evolving curriculum will always contain unfinished areas.
- Decision
- Show roadmap and coverage states instead of pretending the collection is complete.
05 / Shape of the system
A curriculum built for explanation and practice
Subject areas forming the curriculum backbone
Focused answers connected to broader mental models
Guided paths through related engineering concepts
Different interfaces for understanding and practice
06 / Outcome