The API Docs Podcast

In this episode, co-founders Boris and Geoff recap last month's feature releases.

Episode highlights:

• Custom CSS and JavaScript examples. A new guide shows how to add a branded header and a floating Ask AI button, with screenshots. You need a style.css, a script.js and a few lines of docs.json. The examples target stable hooks, not class names. They keep working when Jamdesk updates. CSS & JS Examples →
• One llms-full.txt per language. /fr/llms-full.txt now holds only the French pages of a multilingual site. /en/llms-full.txt holds the default language. The root /llms-full.txt still holds every language. The default language's index also answers at /en/llms.txt. Single-language sites are unchanged. llms.txt →
• Send readers straight to their own language. Set "localization": { "autoRedirect": true } in docs.json. First-time visitors land on their browser's language, such as /fr, instead of your default. The choice sticks for a year. Picking a language from the switcher overrides it. Only the site root redirects. Crawlers are never redirected. Your hreflang tags still decide what gets indexed. Requires two or more languages. Automatic language routing →
• Override the "last updated" date on a page. metadata.timestamp shows a "Last updated on …" line taken from the page's last Git commit. Add lastUpdatedDate: "2026-09-01" to a page's frontmatter to replace that date. The date also goes into your sitemap's and the page's structured-data dateModified, even when the footer line is off. Use it after you review a page, or when a formatting-only commit moved the date. Frontmatter →
• Turn off the copy button on a code block. Add nocopy to the code block's opening line. It works with a title and every other option. It applies per tab inside a . Use it for terminal transcripts, redacted examples, and "don't do this" snippets. Code Blocks →
• Sign readers in with your own login. Turn on auth.jwt in docs.json. Generate an Ed25519 signing key in Settings. Your backend signs a short-lived JWT at sign-in. Jamdesk verifies the token. Sessions last up to 30 days. Add groups: ["admin"] to a page to restrict it to tokens with that group. Other visitors get a 404. The page is hidden from their sidebar. Public paths, frontmatter public: true, and public navigation groups stay open to everyone. Pre-fill the API playground with credentials from the token. Included on every plan. Switch from password protection without downtime. JWT Authentication →
• The site root exports Markdown too. Fetch your docs root, or a language root such as /fr, with Accept: text/markdown or as /index.md. You get the first page in that navigation, the same page the HTML root shows. Sites without an index.mdx used to return a 404 here. That broke the first request most agents make. Markdown Source →
  
  

Learn more at jamdesk.com.

In this episode, co-founders Boris and Geoff recap last month's feature releases.

Episode highlights:

• Jamdesk translates your docs into 27 languages. Tick the languages you want, up to five per project, in Settings → Translations, and after every build the translated pages are committed to your GitHub repository. Later builds retranslate only the pages whose English source changed. Translations you already had, or edit by hand, are kept until you click Replace with AI translation. Included on every plan. AI Translation →
• Choose your own docs URL. Subpath hosting is no longer tied to /docs. Enter a single segment such as help or guide in the subpath field on the Custom Domain card and save. /docs keeps serving, canonicals move to the new path at once, and the previous custom subpath redirects to the new one for a single rename, so you can update your proxy at your own pace. Subpath Hosting →
• Fix with AI, now faster. Opening the fix preview from the build banner finishes sooner, including on large sites, and reopening it is close to instant because Jamdesk keeps the scan results until your docs change. The flow is unchanged: review each proposed edit, apply the ones you approve, and Jamdesk commits them and rebuilds. Fix with AI →
• A fourth theme: Halo. Set "theme": "halo" in docs.json for a warm, rounded look: Figtree type, a sand background with the content raised on a card, and the largest corner radii of any built-in theme. Custom colors, fonts, and CSS overrides work the same as on Jam, Nebula, and Pulsar. Theming →
• Serve your docs only from your own domain. Turn on Custom domain only in the Custom Domain card and a direct visit to YOUR_SLUG.jamdesk.app returns a 404, while your CNAME or proxy keeps working. Jamdesk checks your live domain before the toggle switches on, and if your DNS breaks the subdomain serves again until it recovers. This hides the subdomain from direct visitors but doesn't control who can read your docs; pair it with password protection for that. Custom domain only →

Learn more at jamdesk.com.

In this episode, co-founders Boris and Geoff recap last month's feature releases.

Episode highlights:

Edit your docs right in the dashboard. The web editor is now available to everyone and requires no setup. Open Editor in the sidebar to browse your connected repo, edit MDX with a live preview, and commit straight to your GitHub branch, which kicks off a build automatically. Web Editor →

Fix build warnings with AI, from the dashboard. When a build finishes with broken links or pages missing a description, a Fix with AI banner now appears on the build, showing how many issues can be repaired. Open it to preview each proposed edit (rewritten anchors and suggested page descriptions), then apply the ones you approve. Jamdesk commits them to your GitHub branch and starts a new build. Anything it can't resolve unambiguously is listed separately for you to fix by hand. Fix with AI →

Unlimited team members. Every project now includes unlimited team members on all plans, at no extra charge. The previous 10-member cap and per-seat pricing are gone — invite your whole team.

Let trusted bots publish your docs. Automation accounts like Dependabot, Renovate, or a CMS publishing bot aren't Jamdesk members, so their pushes don't trigger a build by default. Now when one is turned away, the build shows a one-click Authorize Bot Account button. Approve it, and that account's pushes publish to your live site, just like a team member's. Only project members can authorize an account, and you can review or revoke access anytime under Allowed automation accounts in your project's GitHub settings.

Your docs get an AI Score on every build. Jamdesk now scores how well AI agents can read your published docs — graded against the open AFDocs standard — automatically after every build, right in the dashboard. See your 0–100 score and letter grade, watch the trend across builds, and get a plain-language fix for every issue, each with a Copy prompt to fix button that hands the finding to your AI coding agent. Turn on Email team when score changes to hear about it when a build meaningfully moves your score. AI Score →

Learn more at jamdesk.com.

In this episode, co-founders Boris and Geoff recap last month's feature releases.

Episode highlights:

Fix broken links automatically. Broken internal-link warnings with an unambiguous target — typo'd anchors and cross-locale anchor drift — can now be fixed with one command. Run jamdesk fix --dry-run to preview planned changes, then jamdesk fix to apply them; only warnings where the correct anchor resolves to a real heading are touched, leaving ambiguous cases for manual review. CLI overview →

Announce anything with a banner. Add a banner to your docs.json and a message bar pins to the top of every page — above the header, in your theme's accent color. Use links, bold, and italic inline, and set dismissible: true to give readers a close button (it stays closed until you change the message). Banner →

Show when each page was last updated. Set metadata.timestamp: true in your docs.json and every page gets a "Last updated on June 15, 2026"-style line in its footer. The date comes from the last Git commit that changed the page, so it stays accurate automatically on each build — no manual dates to maintain. Page Metadata →

Style your navigation icons. Sidebar, group, tab, anchor, and search icons now honor the style on an icon object ({ "name": "rocket", "style": "duotone" }) or a style prefix (duotone/rocket) — light, thin, duotone, and the sharp family, not just solid. Icons →

Customize the search bar. Choose your own placeholder text with search.prompt, and curate the quick links visitors see in the empty search panel with search.popularPages — each with a title, a page slug, and a Font Awesome icon. Search configuration →

Collect email signups, no embed required. Connect Resend, Mailchimp, Kit, Loops, beehiiv, Brevo, or SendGrid in Settings → Email Signups, and a Jamdesk-hosted form adds readers straight to your own audience — your API key stays on our backend, never in your published site. Add the EmailSubscribe component to any page, or set placement: changelog to put a signup box on every changelog page automatically. Email Signups →

Gate analytics behind cookie consent. Add an integrations.cookies key to your docs.json and Jamdesk withholds every analytics and tracking script — Google Analytics, GTM, Plausible, Crisp, custom JavaScript, and its own built-in analytics — until a visitor consents, read from a localStorage flag your consent banner sets. Load an Osano or Termly banner straight from docs.json too; a short bridge snippet flips the flag the moment a reader accepts, and scripts load with no page reload. Cookie Consent →

llms.txt, organized. Every site's llms.txt now follows the llmstxt.org structure — your navigation tabs and groups become ## sections, so AI agents see your docs the way your sidebar organizes them. Multilingual sites get one index per language: the root file lists your default language and links each translated index (for example /fr/llms.txt), keeping each one small enough that no agent truncates it. llms.txt →

Agents find your docs faster. Every page now carries an invisible, screen-reader-silent directive pointing AI agents at llms.txt and the .md version of the page, and every Markdown export opens with a blockquote linking the index. Agents that fetch your HTML no longer have to guess that a Markdown path exists. AI Overview →

Embed your changelog anywhere. A "What's new?" launcher drops into your own app with one

In this episode, co-founders Boris and Geoff recap last month's feature releases.

Episode highlights:

• Ask AI straight from search. Start typing in search, then hand your question to the AI chat instead of opening a result — press ⌘/Ctrl+Enter or click Ask AI in the search footer. The question is appended to your chat conversation so you can keep a thread going, and plain Enter still jumps to the top result. AI Chat →
• Copy answers and transcripts. Every AI chat answer has a copy button that grabs the Markdown source, and a Copy transcript action in the chat header copies the whole conversation as role-labeled Markdown — handy for pasting into an issue or a doc. AI Chat →
• Smarter chat auto-scroll. The chat only follows a streaming answer when you're already at the bottom. Scroll up to re-read an earlier reply and it stays put instead of yanking you down; scroll back to the bottom and it re-pins.
• Custom CSS in local preview (CLI). jamdesk dev applies your custom CSS the same way the published build does, so you can check styling before deploying. Drop any .css file in your project root — style.css, or several combined alphabetically — and it loads on browser refresh. No docs.json entry needed, matching how Mintlify includes root stylesheets. Custom CSS →
• Custom social previews from frontmatter. Set any Open Graph or Twitter/X meta tag directly in a page's frontmatter — og:title, og:description, og:image, twitter:card, keywords, and the full metatag set. Use flat top-level keys or a nested seo: block; both work, and per-page values override your docs.json defaults. SEO →
• Hidden pages. Keep drafts, internal handbooks, or deprecated guides out of your sidebar and search results without deleting them. Add hidden: true to a page's frontmatter, or to a group or tab in docs.json. Hidden pages stay reachable by direct URL but disappear from navigation, sitemap, on-site search, and AI context — and pick up an automatic noindex tag. Need a hidden group whose pages still rank in search? Add searchable: true alongside hidden. Hidden pages →
• Grid and windows decorations. Two new background patterns join the Jam theme's gradient default. Set background.decoration to "grid" for a subtle 24px dot grid, or "windows" for two Windows 11–style frosted spots in the upper corners. The gradient and "none" flat fill still work as before — pick the look that fits your brand. Background →
• Background customization. A new background block in docs.json disables the Jam light-mode gradient, overrides the page color per mode, or tunes the gradient's color, size, position, and opacity. No custom CSS needed. Background →
• D2 Diagrams. A second diagram language joins Mermaid. Tag a fenced code block d2 and Jamdesk renders it as a build-time SVG, with light and dark themes baked in. Same workflow as Mermaid — pick whichever language fits the diagram you're drawing. D2 Diagrams →
• Grouped search results. Search no longer repeats the same page for every section match. Hits bucket under their parent page in the search modal, with up to three sections visible by default and an inline expander for the rest. Snippet highlighting stays put — you find the right section in fewer scans.
• Auto-detect docs.json on connect. Connecting a GitHub repo finds your docs.json wherever it lives. The connect flow scans the whole tree and flags a Mintlify mint.json if it stumbles on one instead. Monorepos and nested configs work with no manual setup. Connecting GitHub →
• docs.json location hints in the CLI. Misplaced configs are easier to spot. jamdesk validate, jamdesk dev, and jamdesk doctor report where your docs.json actually is — or where it should go — instead of a generic "not found" error. Fix it in seconds instead of decoding a stack trace. CLI overview →

Learn more about Jamdesk at jamdesk.com.

In this episode, co-founders Boris and Geoff recap last month's feature releases.

Episode highlights:

• PDF Export. Render your whole docs site to a single PDF from Settings → PDF Exports in the dashboard. Paid plans only. Multi-language projects pick a locale per export, results are cached per commit, and you get an email with a download link when rendering finishes.
• Multi-language OpenAPI Specs. Endpoint pages now render translated OpenAPI specs alongside translated MDX. Drop a .. file (e.g., openapi/api.fr.yaml) next to your source spec and Jamdesk picks it up on that language's URLs, falling back to the English spec when a language variant is missing. Operation summaries, parameter descriptions, response descriptions, and schema descriptions all localize. Setup: Translating OpenAPI Specs.
• Visibility Component. New component lets you carve out content for human readers or AI agents on the same page. Human-only blocks render in the browser but are stripped from .md exports and llms-full.txt; agent-only blocks do the reverse. Agents requesting Accept: text/markdown on canonical URLs automatically get the agent view.
• Password Protection, rebuilt. You can now lock your whole site behind a shared password, or gate just a handful of pages while the rest stay public. Set auth.password.enabled: true for whole-site mode, or mark individual pages with private: true in frontmatter (or list them under auth.password.private) for specific-pages mode. The Settings page in the dashboard walks you through setting, rotating, and revoking the password. Visitors hit a branded unlock screen with your site's logo, primary color, and an optional hint you define in docs.json. Setup guide: Password Protection.
• Automatic WebP Image Conversion. Jamdesk can convert your PNG and JPG images to WebP at build time. Converted files are usually 60-80% smaller than the originals with no visible quality loss, so your pages load faster without any manual image processing. Opt in via images.convertToWebp: true in docs.json. Favicons, og:image, and twitter:image stay in their original format for social crawler compatibility. A new Optimizing images step shows live progress in the dashboard and CLI during each build. Automatic Image Conversion →
• API Playground. Endpoint pages now have an interactive "Try it" button. Fill in parameters, watch code examples update in real time, and send live requests without leaving your docs. Enabled by default on all API pages. Works with both OpenAPI and MDX-authored endpoints.
• Claude Code Plugin. Install the Jamdesk plugin for Claude Code to give Claude deep knowledge of MDX components, docs.json configuration, navigation patterns, and CLI commands. Two-step install from the plugin marketplace. Pairs with CLAUDE.md and the MCP server for AI-assisted doc writing.
• Build Warnings for Missing Branding. Builds now warn when favicon or logo paths in docs.json reference files that don't exist in your project. Warnings appear in the dashboard build details and in the CLI via jamdesk dev and jamdesk validate. No email; the warning is informational only.
• YouTube Shorts. The component now supports vertical Shorts via the short prop, rendering a centered 9:16 player with no black bars. Use .

Learn more about Jamdesk at jamdesk.com.

In this episode, co-founders Boris and Geoff introduce Jamdesk.

Episode highlights:

• What Jamdesk is: An API docs platform where you write in MDX, push to GitHub, and your docs go live — priced at $29/month flat with everything included (analytics, white-labeling, custom domain, AI chat with no token fees, three themes: standard, Nebula, Pulsar).
• SEO & discoverability: Near-100 Google PageSpeed scores, automatic sitemap and llms.txt generation, IndexNow submissions to Bing/Yandex, and social metadata handling so your docs get found by both search engines and AI chatbots.
• CLI power: A command-line tool for local testing, broken link checks, and spell-checking — designed to plug into agentic coding workflows (Claude Code, Codex) so LLMs can edit, test, and publish docs autonomously.
• Two publishing paths: A GitHub app that auto-builds on push, or CLI-driven publishing from your AI coding agent.
• API Playground (newly launched): Lets users hit your test or production API directly from the docs, configurable via OpenAPI spec or manually in MDX.
• The pitch: 14-day free trial, founders use it themselves, aimed at API/software companies who nned a polished docs site without stitching one together.

Learn more about Jamdesk at jamdesk.com.