Go to file
molecule-ai[bot] dadb6d41cd
Merge pull request #6 from Molecule-AI/docs/fix-auth-701
docs(api-ref): PATCH auth + templates AdminAuth + validation — PR #701 breaking changes
2026-04-17 12:48:54 +00:00
app feat: add External Agents, Token Management, MCP Server docs 2026-04-16 09:14:45 -07:00
content/docs docs(api-ref): auth + validation breaking changes from PR #701 2026-04-17 12:44:10 +00:00
lib feat: add External Agents, Token Management, MCP Server docs 2026-04-16 09:14:45 -07:00
.gitignore chore: gitignore credentials for docs 2026-04-16 09:19:24 -07:00
mdx-components.tsx init: scaffold doc.moleculesai.app with Fumadocs + Next.js 15 2026-04-14 21:01:17 -07:00
next.config.mjs init: scaffold doc.moleculesai.app with Fumadocs + Next.js 15 2026-04-14 21:01:17 -07:00
package-lock.json feat: add External Agents, Token Management, MCP Server docs 2026-04-16 09:14:45 -07:00
package.json feat: add External Agents, Token Management, MCP Server docs 2026-04-16 09:14:45 -07:00
postcss.config.mjs init: scaffold doc.moleculesai.app with Fumadocs + Next.js 15 2026-04-14 21:01:17 -07:00
README.md init: scaffold doc.moleculesai.app with Fumadocs + Next.js 15 2026-04-14 21:01:17 -07:00
source.config.ts init: scaffold doc.moleculesai.app with Fumadocs + Next.js 15 2026-04-14 21:01:17 -07:00
tsconfig.json feat: add External Agents, Token Management, MCP Server docs 2026-04-16 09:14:45 -07:00

Molecule AI Documentation

The customer-facing documentation site for Molecule AI, deployed at doc.moleculesai.app.

Built with Fumadocs + Next.js 15 (App Router) + Tailwind v4 + MDX.

Why Fumadocs

  • 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

Local development

npm install
npm run dev

Visit http://localhost:3000.

Adding pages

  1. Create a new .mdx file under content/docs/.
  2. Add an entry to content/docs/meta.json to control sidebar ordering.
  3. Frontmatter: title and description are required.
---
title: My new page
description: One-line summary used in nav + meta tags.
---

Content goes here.

Repository layout

.
├── 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

Who maintains this

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.

Deployment

This site is deployed to doc.moleculesai.app via Vercel (TBD — once the domain is configured). PRs to main ship to preview URLs automatically.

Contributing

Open a PR. The Documentation Specialist + a human reviewer will look at it within one cron tick (currently daily).