Skip to content
Blume
Esc
↑↓navigate↵open⌘Jpreview
Customer stories

Ordinal moved to Blume while walking the dog.

Ordinal, the social media platform for B2B teams, moved its docs to Blume in an evening, and a Claude Code routine now keeps them current.

Hands-on time; Claude Code did the rest
20 min
Guide URLs changed in the move
0
Francisco, right, and a colleague smiling over lunch at a sidewalk café table

Ordinal is a social media management platform for B2B teams. It's built around LinkedIn: teams draft and schedule posts for executives, company pages, and employees, route them through approvals, coordinate likes, comments, and reposts with Team Engagements, and track performance in one analytics view. Ordinal also publishes to X, Instagram, Threads, Facebook, TikTok, YouTube Shorts, Webflow, Slack, and Discord. For developers and AI assistants, it offers a REST API, an MCP server, and webhooks.

Its docs cover all of it: a guide for every feature, references for two APIs, and a page for every webhook event.

The challenge

Ordinal's docs had been MDX in their own repository from the start, and every change went through GitHub. The team wanted a docs site that worked the same way, and docs that kept up with the product as it changed.

The move

Francisco had had his eye on Blume for a few months. One evening in September 2026, he handed the migration to Claude Code with Blume's migration playbook. It rewrote the frontmatter and icons on 68 pages in one pass, then worked through the rest unattended while Francisco walked the dog.

The content moved almost one to one. Cards (about 250 of them), Steps, Tabs, Accordions, Expandables, CodeGroups, and Frames all have Blume equivalents with nothing to import, and callouts became ::: directives. The 273 response fields on the 22 webhook event pages became type tables.

The real work was keeping URLs. The old sidebar groups lived only in a config file, so Claude rebuilt them as group folders like (calendar-and-posts)/, which add no segment to the URL, and gave pages that changed folders a slug that kept their old address. The Guides tab sits at the site root, so nothing had to move under a new prefix. Not one guide URL changed.

The API reference came for free: pointing openapi() at Ordinal's two existing specs built 72 endpoint pages with schemas, code samples, and a Try it panel. Blume names endpoint pages by their operation ID, where the old site used each one's summary, so 72 of the site's 79 redirects send old endpoint URLs to their new pages. On Vercel, they're real 301s.

Before cutover, blume validate checked every link and redirect. Its first run flagged 52 broken links, which exposed 19 pages a content glob had silently left out of the build. With those back, the site went live on Vercel the next day.

Everything else was a line or two in blume.config.ts: llms.txt, a Markdown version of every page, a docs MCP server beside Ordinal's own product MCP server, the assistant, PostHog analytics, and Edit on GitHub links.

“I started the migration and went to walk the dog. About 20 minutes of my time, and every URL still worked.”

FranciscoCo-founder, Ordinal

Docs that keep themselves current

To keep the docs current, Ordinal set up a scheduled Claude Code routine. Every weekday at 5pm Chicago time, a cloud Claude Code session checks out both the product and the docs repositories, then:

  1. Lists the product pull requests merged in the last seven days, skipping any that a docs pull request already references, so it never documents the same change twice.
  2. Reads each one's description and diff and decides whether customers would notice. Bug fixes, refactors, backfills, internal automations, and work behind feature flags are skipped.
  3. Writes the docs change following the repository's CLAUDE.md, which spells out Blume's syntax and conventions.
  4. Runs npm run build and npm run validate, and goes on only if both pass with no errors.
  5. Opens one pull request per change for a person to review and merge.

The routine needs only git, the GitHub CLI, and npm, so it runs with no connectors attached. It reads pull request text that other people wrote, and keeping email, Slack, and payments out of its reach limits what an injected instruction could do.

The results

Every guide URL survived the move, and the docs now keep up with the product on their own, one reviewed pull request at a time.

WhatNumber
Hand-written pages80, across 5 header tabs
API reference pages72, from 2 OpenAPI specs
Redirects79, 72 of them for endpoints
Guide URLs changed0
Webhook fields converted273, on 22 event pages
Francisco's hands-on timeAbout 20 minutes

The whole move was one pull request, and the new docs are live at docs.tryordinal.com.

To move your own docs, read Migrate to Blume.

Read another story.Or see every team on Blume.

Upgrade your docs with Blume.

Install today and ship a production-grade docs site in minutes. Free and open source, forever.

npx blume init