Project category

Content & Directory tech stacks

Curated resources, catalogs, blogs, and content-first sites. 7 production examples.

Production Content & Directory projects

Next.js-Native Headless CMS & App Framework Hybrid Payload CMS A pnpm and Turborepo monorepo lets one core package share a common database-adapter export shape across MongoDB, Postgres, SQLite, and D1, while GraphQL, storage providers, and deployment templates stay in separate packages so a project only pulls in the pieces its target host and database actually need.
Q&A & Developer Knowledge Community Classic Apache Answer A statically linked Go binary that embeds its React UI and supports SQLite, MySQL or PostgreSQL keeps deployment to one container, while typed plugin interfaces extend auth, storage, search and AI without forking.
Content Directory & Showcase Hybrid Stack It Fast Choose your stack based on real projects, not guesswork. Context: Launch this week as fast as possible driver. Survey verified stack.
Headless CMS Classic Strapi Declarative content modeling paired with a customizable React admin dashboard gives engineering teams full control over content structures and delivery APIs.
Headless CMS Classic Directus A Knex-based query layer and adapter packages for storage keep the same API and Studio working across many SQL vendors and object stores, while extension code runs inside an isolated-vm sandbox so third-party hooks cannot destabilize the main API process.
Documentation Portal Classic Starlight Leveraging Astro static rendering delivers 100/100 Lighthouse performance with zero JavaScript by default and built-in client-side WebAssembly search.
Content Platform Classic Ghost Ghost runs its core server, a React admin app that is replacing a legacy Ember admin in place, and every public-facing widget as separately Vite-built packages inside one pnpm/Nx monorepo, so the publishing surface, the editor and each embeddable script can evolve and ship on their own schedule.

Every rule ships as files

AGENTS.md rules and agent skills for Content & Directory

astro-static-content/AGENTS.mdAstro Static Site + Content Collections + TailwindRules for a fully static Astro 7 site: content collections with Zod schemas, zero-JS pages with rare islands, build-time sitemap and OG images, and static hosting on Cloudflare. starter astro-tailwind-cloudflare/AGENTS.mdAstro SSR + Tailwind CSS + CloudflareArchitecture rules for Astro server-side rendering, React client islands, Tailwind CSS, and Cloudflare Pages/Workers edge deployment. intermediate rust-axum-htmx-askama/AGENTS.mdRust + Axum + htmx + Askama (Server-Rendered Web App)Server-rendered Rust web app rules: Axum 0.8, compile-time Askama templates, htmx partials, sqlx 0.9 + PostgreSQL, and a cargo check loop for AI agents. intermediate

Questions about Content & Directory stacks

How many Content & Directory tech stacks are in the directory?

7 verified production Content & Directory projects are currently indexed, each with a full architecture breakdown and copy-paste AI scaffolding prompt.

What AGENTS.md rules or agent skills apply to Content & Directory projects?

Astro Static Site + Content Collections + Tailwind, Astro SSR + Tailwind CSS + Cloudflare, Rust + Axum + htmx + Askama (Server-Rendered Web App) are battle-tested architecture rules for this category, each with a full AGENTS.md, CLAUDE.md, Cursor .mdc file and a Claude Code SKILL.md.

How do I get a custom stack recommendation for a Content & Directory project?

Take the STACK IT FAST architecture survey and select "Content Directory & Showcase" as your project type to get a ranked rule recommendation and an instant AI scaffolding prompt tailored to a "Content & Directory" project.