Skip to main content
The Pocketsflow documentation site is built with Mintlify. Every setting — navigation, theme, logo, footer — lives in a single docs.json file at the docs root (apps/docs/docs.json). This page documents the structure actually in use so contributors can add pages and adjust the site confidently.
This is a contributor reference for editing these docs, not a product feature. If you’re looking for your Pocketsflow account settings, see Account & security.

​
Where things live

​
Top-level keys

​
string
Points at the Mintlify schema for editor validation: https://mintlify.com/docs.json.
​
string
The Mintlify theme. This site uses mint.
​
string
required
The site name shown in the title. Here: Pocketsflow Docs.
​
object
required
Brand colors. The docs follow the marketing site (apps/landing-new): monochrome, black on white and #ededed on near-black.
Keep the docs monochrome to match www.pocketsflow.com. Don’t add a colour accent without a brand decision.
​
object
Page background per mode: #ffffff in light, #0a0a0a in dark (the same values as the marketing site).
​
object
Satoshi for headings and body, self-hosted from /fonts/satoshi-var.woff2 (the same file the marketing site serves). Code is set in Geist Mono by style.css.
​
string
Path to the favicon: /favicon.svg, the square “PF” monogram.
Light and dark logo paths:
Both are the “Pocketsflow” wordmark in Averia Serif Libre 700, converted to outlines so they render without loading a font. Regenerate them from apps/landing-new/public/brand/pf-logo-text.svg if the wordmark changes.
​
object
required
The site’s structure — tabs, groups, and pages. See Navigation below.
​
object
Top-bar links and the primary call-to-action button:
​
object
The “copy / open in AI tool” options on each page. This site enables: copy, view, chatgpt, claude, perplexity, mcp, cursor, vscode.
​
object
Footer socials, e.g. { "socials": { "x": "https://x.com/pocketsflow" } }.
Navigation is a set of tabs, each containing groups, each containing an ordered list of pages (paths relative to the docs root, without .mdx).
​
string
required
The tab label shown in the top navigation (e.g. Guides, Integrations, Resources).
​
string
required
A section heading within a tab’s sidebar (e.g. For buyers).
​
string[]
required
Ordered page paths relative to the docs root. buyers/overview → buyers/overview.mdx. Order here is the sidebar order.

​
Adding a page

1

Create the MDX file

Add your-section/your-page.mdx with valid frontmatter (see Writing pages).
2

Register it in docs.json

Add its path to the right group’s pages array, in the position you want it to appear.
3

Preview

Run the local preview and confirm it shows in the sidebar and renders.
A page that isn’t listed in any pages array is orphaned — reachable by direct URL but missing from the sidebar. Always register new pages.

​
Global anchors

navigation.global.anchors renders persistent links (with icons) across the whole site:

​
Page frontmatter

Every MDX page starts with YAML frontmatter:

​
Validating your changes

  • Preview locally with the Mintlify CLI: mint dev (installed via npm i -g mint), served at http://localhost:3000.
  • Check for broken links with mint broken-links.
  • Ensure docs.json remains valid JSON (a trailing comma will break the build).