Frontend Project Shell Taxonomy

This taxonomy groups captured frontend repositories by reusable project role rather than popularity alone. Its first question is: can this help start or migrate a future frontend project?

Shell Score Guide

  • 10: complete project shell with docs, routing/content conventions, examples, and clear deployment path.
  • 8-9: strong app/site shell, sometimes with a narrower ecosystem or more evolving API.
  • 6-7: important tooling or partial shell; useful when composing a custom project.
  • 4-5: dependency substrate/runtime; pair with a framework shell before starting a project.

app-framework

build-tooling

docs-framework

knowledge-site-framework

site-framework

ui-runtime

Counterpoints And Gaps

  • AMBIGUOUS: Ecosystem roles are registry-level project-reuse labels; some repos legitimately span docs, app, and runtime layers.
  • INFERRED: Role grouping is for project selection and retrieval, not a definitive taxonomy of each framework’s architecture.