@nomiedge/templates

Three production-shaped Next.js App Router templates — marketing, docs, app-shell — composed entirely from @nomiedge/*. Never consumed as a runtime dependency: nomiedge init --template=<name> copies the template's real source files straight into your project (the same vendoring model nomiedge add --mode=source uses for individual components).

Templates

• marketing — a landing page: hero, feature grid, footer.
• docs — a documentation site: MDX content, nav, ⌘K search.
• app-shell — a dashboard shell: responsive sidebar, themed content area.

Adding a template

1. Add a new directory under src/<name>/ with a real layout.tsx/page.tsx.
2. Compose it from @nomiedge/* only — no re-implemented component, no copied token value.
3. Register it in src/manifest.ts with its registryDeps (every @nomiedge/* component name it uses) — the CLI validates these against the real registry before scaffolding.

Why next/next-themes are devDependencies

Template source imports them (src/shared/theme-provider.tsx, src/shared/metadata.ts), so this package's own pnpm typecheck needs their real types available — but this package never ships as a runtime dependency of anything (see above), so these are devDependencies only, purely for this package's own tooling. nomiedge init --template=<name> merges its own real, separately-versioned next/next-themes into the target project (see @nomiedge/cli's scaffoldTemplate.ts), not these.