vipin wiki

Frontend Frameworks Public Corpus

8 min read

Frontend Frameworks Public Corpus

This hub tracks reusable frontend project frameworks: knowledge-site shells, documentation frameworks, app frameworks, build substrates, and lower-level UI runtimes. The goal is project reuse: when a future project needs a frontend, a human or agent should be able to click through from use case to framework, repository, docs, demo, and release ideas.

The current vipin wiki publishing layer uses Quartz v4 through the local site/ adapter and .wiki-tmp/quartz build flow.

Choose By Project Need

I Need A Personal Wiki Or Knowledge Site

FrameworkRoleShell scoreCaptured reposDocsDemo/showcase
Quartzknowledge-site-framework101https://quartz.jzhao.xyzhttps://quartz.jzhao.xyz

I Need Documentation Or Developer Docs

FrameworkRoleShell scoreCaptured reposDocsDemo/showcase
Docusaurusdocs-framework101https://docusaurus.io/docshttps://docusaurus.io/showcase
Fumadocsdocs-framework91https://fumadocs.dev/docshttps://fumadocs.dev
Nextradocs-framework91https://nextra.site/docshttps://nextra.site
Starlightdocs-framework91https://starlight.astro.build/getting-started/https://starlight.astro.build
VitePressdocs-framework91https://vitepress.dev/guide/getting-startedhttps://vitepress.dev

I Need A Website Or App Shell

FrameworkRoleShell scoreCaptured reposDocsDemo/showcase
Next.jsapp-framework101https://nextjs.org/docshttps://nextjs.org/showcase
Nuxtapp-framework104https://nuxt.com/docshttps://nuxt.com/templates
Astrosite-framework93https://docs.astro.buildhttps://astro.build/themes/
React Routerapp-framework92https://reactrouter.comhttps://remix.run
SvelteKitapp-framework91https://svelte.dev/docs/kithttps://svelte.dev
Angularapp-framework83https://angular.dev/overviewhttps://angular.dev
Qwikapp-framework81https://qwik.dev/docs/https://qwik.dev/examples/
TanStack Startapp-framework81https://tanstack.com/start/latesthttps://tanstack.com/start

I Need Build Or Server Tooling

FrameworkRoleShell scoreCaptured reposDocsDemo/showcase
Vitebuild-tooling72https://vite.dev/guide/https://vite.dev
Nitrobuild-tooling61https://nitro.build/guidehttps://nitro.build

I Need A UI Runtime Or Dependency Substrate

These are important, but usually not enough by themselves for a complete project shell.

FrameworkRoleShell scoreCaptured reposDocsDemo/showcase
Solidui-runtime63https://docs.solidjs.comhttps://playground.solidjs.com
Svelteui-runtime53https://svelte.dev/docshttps://svelte.dev/playground
Reactui-runtime42https://react.devhttps://react.dev
Vueui-runtime45https://vuejs.org/guide/https://play.vuejs.org

Full Matrix

FrameworkRoleCaptured reposHomepage
Angularapp-framework3https://angular.dev
Astrosite-framework3https://astro.build
Docusaurusdocs-framework1https://docusaurus.io
Fumadocsdocs-framework1https://fumadocs.dev
Next.jsapp-framework1https://nextjs.org
Nextradocs-framework1https://nextra.site
Nitrobuild-tooling1https://nitro.build
Nuxtapp-framework4https://nuxt.com
Quartzknowledge-site-framework1https://quartz.jzhao.xyz
Qwikapp-framework1https://qwik.dev
Reactui-runtime2https://react.dev
React Routerapp-framework2https://reactrouter.com
Solidui-runtime3https://www.solidjs.com
Starlightdocs-framework1https://starlight.astro.build
Svelteui-runtime3https://svelte.dev
SvelteKitapp-framework1https://svelte.dev/docs/kit
TanStack Startapp-framework1https://tanstack.com/start
Vitebuild-tooling2https://vite.dev
VitePressdocs-framework1https://vitepress.dev
Vueui-runtime5https://vuejs.org

Entry Points

  • frontend-project-shell-taxonomy - Browse frameworks by reusable project-shell role.
  • frontend-framework-reuse-map - Decide which framework to migrate into a future project.
  • raw/frontend-frameworks-public/manifest.json - Local manifest with stable IDs, hashes, candidate records, and provenance.

Languages

Needs Review

Maintenance Rules

  • Stable IDs are mandatory: framework:<slug>, github:<owner>/<repo>, github-release:<owner>/<repo>:<tag_name>, and github-candidate:<owner>/<repo>.
  • Do not promote candidates into public repo pages until raw/frontend-frameworks-public/registry.json explicitly includes them.
  • Public pages contain metadata, summaries, hashes, and links only.
  • Re-run scripts/ingest-frontend-frameworks-public.ps1 before making current claims about stars, releases, or repo structure.
  • Treat ui-runtime entries as dependency substrates unless their registry notes explicitly identify a complete project shell.

Counterpoints And Gaps

  • AMBIGUOUS: The corpus is complete only inside the curated project-framework registry boundary, not across every repo in each owner organization.
  • AMBIGUOUS: Candidate discovery is keyword-based and may miss official repos whose descriptions/topics do not match project-shell keywords.
  • INFERRED: Stars, file profiles, and release ordering are crawl-time signals and should not be treated as stable quality rankings.

Graph View

Backlinks