AdapterHub

Repo architecture

Monorepo layout, apps, and CI/CD for PackageHub.

Repository architecture

PackageHub is a pnpm workspace monorepo with two applications and shared tooling.

Top-level layout

PathPurpose
apps/webSolidStart app — main product (dashboard, GitHub/registry connections)
apps/docsFumadocs (Next.js) — documentation site (MDX in content/docs/)
scripts/One-off scripts (e.g. create-docs scaffold)
README.adocProject overview and quick links
install.adocInstallation steps
running.adocHow to run and build locally
repo-architecture.adocThis file (Asciidoc at repo root)

Web app (apps/web)

  • Stack: SolidStart (Vite 7, Solid 1.9, Nitro).
  • Entry: src/entry-client.tsx, src/entry-server.tsx, src/app.tsx.
  • Routes: File-based under src/routes/ (e.g. index.tsx, dashboard.tsx, registries.tsx).
  • Config: vite.config.ts, tsconfig.json.

Docs app (apps/docs)

  • Stack: Next.js 16, Fumadocs UI, Fumadocs MDX, Tailwind 4.
  • Content: content/docs/*.mdx; sidebar order in content/docs/meta.json.
  • Source config: source.config.ts; Fumadocs loader in lib/source.ts.
  • CI: GitHub Actions build and deploy the docs (e.g. GitHub Pages).

CI/CD

  • .github/workflows/ — GitHub Actions:
    • docs.yml — build and deploy the Fumadocs site (e.g. to GitHub Pages).

Dependencies

  • Root package.json: workspace scripts only.
  • Each app has its own package.json; lockfile is at repo root (pnpm-lock.yaml).

On this page