Discofork
Repository brief

h5bp/Front-end-Developer-Interview-Questions

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T12:04:36.757Z
3mo ago

h5bp/Front-end-Developer-Interview-Questions

A large, actively maintained H5BP repository of front-end interview questions. It is primarily a content site with markdown question lists and Eleventy-based build scripts, and it has very high adoption: 60,813 stars and 11,062 forks.

GitHub
Loading tags...
Stars60,813
Forks11,062
Default branchmain
Last pushed2026-03-28T04:27:12Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork if your priority is translated, localized interview content. Choose upstream if you want current maintenance, newer question updates, and the latest build/security workflow.

Prefer this fork if you want interview prep with answers and translated material. Prefer upstream if you want the actively maintained, lower-risk canonical question set.

Prefer upstream for almost any active use. Choose this fork only if you explicitly want a legacy, frozen copy and are prepared to own the missing updates and divergence.

Choose the fork only if you specifically want its localized/translated variant. For most adopters, upstream is the better default because it is actively maintained, far more complete, and much less risky to rely on.

Choose this fork only if you want an old, simplified, translation-oriented snapshot. For most adopters, upstream is the better base because it is actively maintained, broader in scope, and much easier to keep current.

Choose upstream if you want current content and active maintenance. Choose this fork only if you specifically want an older, trimmed, localization-heavy base and are prepared to manage missing updates yourself.

Choose the fork only if you want an older, simplified, more self-contained interview-question set. Choose upstream if you want current maintenance, broader content coverage, and newer tooling.

Prefer upstream unless you explicitly want an unmaintained snapshot; this fork adds no visible functionality and is materially behind.

Prefer upstream unless you specifically want this fork's older localized/customized snapshot. It looks materially stale and missing a large amount of upstream content and maintenance, so adoption is only sensible for archival or narrow legacy reuse.

Prefer this fork if you want a static, personal answer set for self-study. Prefer upstream if you want the current, maintained interview-question repository with ongoing updates and community workflow.