sadanandpai/javascript-code-challenges

Vue 2, also known as Vue.js 2, is the earlier major version of the Vue JavaScript framework, hosted at vuejs/vue on GitHub under an MIT license. Per the repository's own README, Vue 2 hit End of Life on December 31, 2023, is no longer actively maintained, and the project now directs users toward vuejs/core (Vue 3) and an official migration guide, while leaving Vue 2 itself installable through CDNs, package managers, and GitHub.

App Ideas Collection is a GitHub repository maintained by Florin Pop and Jim Medlock that catalogs application ideas developers can build to practice their skills, organized into three difficulty tiers. Each entry defines an objective, user stories, optional bonus features, and resource links rather than a bare project name, and the repository is sponsored by CodeRabbit and licensed under MIT.

Front-End Checklist is a rule-by-rule audit checklist, not a linter. 385 rules. Eleven categories. Each rule has its own page with an explanation, a priority tag, and remediation steps — built for humans doing a manual pass and, more recently, for MCP-compatible agents doing the same audit automatically.

Strapi is a self-hosted headless CMS that auto-generates REST and GraphQL APIs from content model definitions you build visually with the Content-Type Builder — no code required on the API side. It ships with authentication, granular roles and permissions, a media library, i18n, and draft/publish workflows out of the box, and the request pipeline (Routes → Middlewares → Controllers → Services) is fully overridable at each layer. TypeScript is first-class and you can pair it with SQLite for local dev or PostgreSQL/MySQL/MariaDB in production. The plugin system and customizable admin panel are real extensibility points, not marketing. The tradeoff: there's no official Docker image (you roll your own from your project), and major version upgrades have been historically painful — the migration docs are thorough but the process still demands attention. Worth it if you need full control over your content infrastructure and don't mind owning the deployment; less ideal if you want something you can set and forget.