yangshun/front-end-interview-handbook
Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.
yangshun/front-end-interview-handbook
A large, active front-end interview preparation repository with documentation-heavy content covering interview formats, front-end system design, trivia, coding questions, and company-specific interview questions. It is popular and widely forked, and the repo was recently updated in March 2026.
Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.
Choose a fork to inspect
Prefer upstream unless you specifically want this fork's translated/static snapshot. The fork adds localized study material, but it is materially stale and diverged enough that it is a poor starting point for anyone wanting current interview prep content.
Prefer this fork only if you specifically want a frozen, multilingual interview-question corpus to adapt. If you want current front-end interview prep content and an actively maintained docs site, upstream is the better choice.
Adopt this fork only if you specifically want the older translated content and do not need current upstream maintenance or tooling. For most users, upstream is the better base.
Choose upstream unless you specifically need this older fork’s snapshot or plan to own maintenance yourself. For most adopters, the fork is too stale and too far from upstream to be a better default.
Prefer the upstream unless you explicitly want a small, stale, highly customized baseline. This fork is better as a lightweight archive or translation seed than as a current interview-prep resource.
Prefer this fork only if you want an older, highly customizable content base. For most adopters, upstream is the better choice because it is actively maintained and updated for 2026.
Choose this fork only if you want an old, translation-heavy snapshot for local study or adaptation. If you want the current handbook, modern site, and up-to-date interview guidance, upstream is the better choice.
Prefer this fork only if you want a mostly static, translation-heavy interview study repo. If you want current coverage, modern tooling, or the latest handbook content, upstream is the better choice.