The customer-facing documentation site for Molecule AI, deployed at doc.moleculesai.app.
Built with Fumadocs + Next.js 15 (App Router) + Tailwind v4 + MDX.
- Open source (MIT) — we self-host on our own domain, no vendor lock-in
- Next.js 15 native — matches the canvas stack already in the platform monorepo
- Flexible — can grow into custom doc components for our agent canvas flows, embedded mini-canvases in docs, etc.
- Modern aesthetic — Shiki code highlighting, full-text search, dark mode, all out of the box
npm install
npm run devVisit http://localhost:3000.
- Create a new
.mdxfile undercontent/docs/. - Add an entry to
content/docs/meta.jsonto control sidebar ordering. - Frontmatter:
titleanddescriptionare required.
---
title: My new page
description: One-line summary used in nav + meta tags.
---
Content goes here..
├── app/ # Next.js App Router routes
│ ├── (home)/ # marketing landing
│ ├── docs/[[...slug]]/ # docs dynamic route
│ ├── api/search/ # built-in full-text search
│ ├── layout.tsx # root layout + RootProvider
│ └── layout.config.tsx # nav links shared by home + docs
├── content/docs/ # MDX source — the actual documentation
│ ├── meta.json # sidebar order
│ ├── index.mdx # docs landing
│ └── *.mdx # one file per page
├── lib/source.ts # Fumadocs loader bound to the MDX source
├── mdx-components.tsx # default + custom MDX renderers
├── source.config.ts # MDX compile config (remark/rehype plugins)
├── next.config.mjs # Next config wrapped with createMDX
├── postcss.config.mjs # Tailwind v4 postcss plugin
└── package.json
The Documentation Specialist agent in our molecule-dev org template
owns this repo end-to-end. It runs on a schedule, watches PRs landing in the
platform monorepo, and
opens docs PRs here whenever:
- A new public API endpoint lands
- A new template / plugin / channel is added
- A user-facing concept changes
- An ecosystem-watch entry needs publishing
Manual edits welcome. The agent picks up changes on its next cron tick.
This site is deployed to doc.moleculesai.app via Vercel (TBD — once the
domain is configured). PRs to main ship to preview URLs automatically.
Open a PR. The Documentation Specialist + a human reviewer will look at it within one cron tick (currently daily).