This repository is the Front End Interview Handbook, a comprehensive collection of front-end interview questions and answers covering HTML, CSS, JavaScript, system design, behavioral topics, and company-specific experiences. It is built as a static documentation site using Docusaurus 3, with a custom theme that includes sidebar advertisements and a modified table of contents. The site supports 10 languages through i18n and is deployed at frontendinterviewhandbook.com. While primarily a content repository, it demonstrates solid software engineering practices in its Docusaurus configuration, custom theme components, and multilingual setup. The content is curated from the h5bp/Front-end-Developer-Interview-Questions repository and community contributions, with references to authoritative sources. The repository also includes blog posts and success stories. It is not a traditional application or data pipeline but a hybrid of a documentation site and a curated knowledge base.
This repository is a curated collection of front-end developer interview questions, organized by topic (General, HTML, CSS, JavaScript, Testing, Performance, Network, Coding, Fun) and translated into 30+ languages. It is built as a static website using the Eleventy (11ty) static site generator, with Nunjucks templates, Markdown content files, and a modest CSS/JS asset pipeline. The core value is entirely in the question content and its community translations; the application layer is a thin publishing wrapper. There are no reusable software components of note — the Eleventy config, CSS, and JS are all straightforward boilerplate for a documentation-style static site. The project's influence stems from its content curation and community adoption, not from any technical craftsmanship in the codebase.
This repository is not a software application or data pipeline. It is a curated index of backend coding challenges sourced from real job postings by various companies. The only substantive content is a single README.md file containing a table of company names, countries, required stacks, and hyperlinks to external challenge repositories. The sole automated component is a GitHub Actions workflow that periodically checks the validity of those links and creates issues for broken ones. There is no source code, no application architecture, no data transformations, and no reusable software components. The repository serves as a reference directory for developers seeking practice challenges, but it provides no functional tooling or infrastructure.