Confidential  ·  Working Doc  ·  Scribe-X
Publishing Guide
How we publish on scribe-x.com

A faster lane for web pages, running right alongside our CMS.

We can now publish brand-new pages directly onto scribe-x.com, built with AI in minutes, without going through WordPress or HubSpot. Both keep doing everything they do today, and HubSpot stays wired in as our CRM, forms, and tracking. This adds a lane, it doesn't replace the ones you have.

This is a working doc for the Scribe-X team. It explains what changed, what stays the same, and the step-by-step for publishing a page. Read it, poke holes in it, and we'll refine it together.

What changed

One small addition at the front door of our site. Nothing removed.

Until now, every new page had to be hand-built inside WordPress (or HubSpot), in a template, through the usual queue. That's fine for a lot of work, and it isn't going anywhere. But it's slow when you want to ship something now.

We added a second way to publish. New pages can be built as code (with AI), hosted on modern infrastructure, and served on your real domain at your real URLs. The old site and the new pages live side by side. You choose, page by page, which lane to use.

Our two lanes

Same website, same domain, two ways to put a page on it.

The CMS Lane
WordPress + HubSpot
  • Everything you publish today (WP pages, the blog, HubSpot landing pages)
  • Edited by the team in those tools, as always
  • HubSpot stays our CRM, forms, and tracking
  • Unchanged. Nothing moves.
The AI-Speed Lane
AI-Speed Publishing
  • New code-built pages, made with AI in minutes
  • Answer pages, blogs, FAQ pages, lead magnets
  • Live on scribe-x.com, with tracking built in
  • Published by you or Oliver, on demand

What the AI-Speed Lane is really for

Speed and volume, pointed at one goal: owning the answer in our category.

This lane isn't just a faster way to make a page. It's how we publish an army of answers, and use them to control the narrative in our industry.

When a buyer (or an AI search engine) asks a question about AI medical scribes, someone's page becomes the answer. Right now most of those answers are unclaimed. The company that publishes them first, fastest, and on a domain that already carries trust wins the category's narrative. That's the game we're playing.

Built to publish, at a much faster clip
  • Answer pages ... one for every real question buyers and AI ask, so we become the answer instead of a competitor.
  • Blog posts ... ship thought leadership on a cadence the old queue could never keep up with.
  • FAQ pages ... fast, focused, and tracked.
  • Lead magnets ... scorecards, guides, and tools (like the 5 Shifts guide) that capture demand.

This is just truth: AI made content nearly free, so volume alone is no longer the moat. Speed to the right answer is. This lane is how we move at that speed.

How the AI-Speed Lane works

A small rule at the front door. Engineers call it a "strangler-fig" setup, a reverse proxy.

Every visitor to scribe-x.com already passes through a "front door" (Cloudflare, already in front of our site). We added one rule there. On every request, it checks a single thing:

1
A visitor opens a scribe-x.com pageSame domain, same URLs as always.
2
The front door asks: do we have a new version of this page?A check that takes a millisecond.
3
Yes: it serves the new AI-built pageFrom the AI-Speed Lane, on our real domain.
4
No: it passes straight through to WordPressExactly like today. Nothing changes for every other page.

New pages grow around the old site, one at a time, like a vine growing around a tree while the tree keeps standing. You replace as much or as little as you want, whenever you want.

What we're NOT changing

Promises
  • WordPress and HubSpot stay. Our existing pages, the blog, HubSpot landing pages, forms, and automations keep running exactly as they do now.
  • Nothing gets deleted. New pages sit in front of the old ones; the old ones stay behind them.
  • Email is untouched. This is about web pages only. Our email runs on its own system.
  • Tracking comes along. Google Analytics (through Google Tag Manager) and HubSpot are built into every new page, so our analytics and CRM keep working.
  • There's a kill switch. Any new page can be turned off in seconds, and that path instantly returns to the old site.

Who publishes, and who approves

A small, controlled circle today. It scales later, on purpose.

Today
  • Publishers: Greg and Oliver only. They are the two people set up to publish on the AI-Speed Lane right now.
  • Approver: Jason, and only Jason. No page goes live on scribe-x.com without Jason's approval.
  • Every page is documented as approved before it's published, so there's a clear record of what went live, when, and that Jason signed off (logged in the approval log).

Scaling it later

Over time we can let anyone authorized on the Scribe-X team publish on the AI-Speed Lane, as long as they're set up. The approval step stays exactly the same: Jason's documented sign-off, every time. Here's what a new publisher needs:

Setup for a new publisher
  • An AI coding tool that runs in the terminal (edits files and runs commands). Claude Code or OpenAI Codex CLI both qualify ... pick one and sign into its account. It's the operator that builds and ships the pages.
  • Claude Code connected to Cloudflare, with the right access to the scribe-x.com setup. A one-time login that grants permission to publish through the front door and to the page hosting.
  • The shared project files (the folder or repo where the pages live).

With that in place, a new team member runs the same simple steps below. And still, nothing goes live without Jason's documented approval.

How to publish a page (step by step)

You drive an AI coding tool, and it does the technical work. You and Oliver can each do this independently, with whichever tool you prefer.

The AI is swappable

The AI tool is just the operator. The real system is the page-source files in the project folder plus the Cloudflare access, both of which live on the machine, not inside any AI. Any local terminal coding agent ... Claude Code or OpenAI Codex CLI ... can run the same edit-then-publish loop, so we're never locked to one vendor.

Update an existing page (e.g. the 5 Shifts page)
About a minute. No routing changes needed.
  1. Open Claude Code in the Scribe-X project folder.
  2. Say: "Update the 5 Shifts page: [your change]." It edits the page and redeploys it.
  3. Check it live at www.scribe-x.com/the-5-shifts (refresh, give it ~30 seconds).
Publish a brand-new page
A few minutes of building, then your review before it goes live.
  1. Open Claude Code in the Scribe-X project folder.
  2. Say: "Publish a new page at www.scribe-x.com/[slug]. Content: [paste it or point to an AI draft]." It builds the page, bakes in tracking, and gives you a private preview link.
  3. Review the preview and get Jason's documented approval (see "Who publishes, and who approves," above). Then say "approved, make it live."
  4. Confirm it's live at www.scribe-x.com/[slug].

The rules

Keep these in mind
  • Always use www. Pages answer on www.scribe-x.com/... (a quirk of how this zone runs the front-door code). Share and link the www version.
  • Every new page MUST carry the right tags. Google Analytics (via Google Tag Manager) and HubSpot tracking go on every page, no exceptions ... a page without them is a blind spot for our analytics and our CRM.
  • Approval gate. Nothing goes live on scribe-x.com without sign-off. New pages get reviewed on a private link first, then published.
  • Kill switch. To pull any page instantly, turn off its rule in Cloudflare. That path reverts to the old site at once.

When to use which lane

Use the CMS Lane for
  • The existing blog archive and editorial the team manages in WordPress
  • Pages the team already edits comfortably in those tools
  • HubSpot campaign landing pages tied to existing workflows
Use the AI-Speed Lane for
  • Answer pages to own the category's AI narrative ... the army of answers
  • New blog posts, at a much faster clip
  • FAQ pages and lead magnets (scorecards, guides, tools)
  • Anything you want live today, not in three weeks

Changing or replacing existing pages

Edits stay where they are. Replacements can move to the AI-Speed Lane, over time.

Editing an existing page

If the page lives in WordPress or HubSpot, keep editing it there. Same process, same tools, nothing changes. The CMS Lane stays the CMS Lane.

Replacing an existing page

When we want a faster, better version, we rebuild the page on the AI-Speed Lane. The front-door rule serves the new page at the same URL, the old one stays safely behind it, and the kill switch reverts it instantly if needed.

The long game

Page by page, we can migrate as much of the site as we want onto the AI-Speed Lane, refreshing design and copy at the speed of AI instead of the speed of the old queue. Nothing has to move until we choose to move it. The new grows around the old.

What's live now

The first page on the AI-Speed Lane is already up: the 5 Shifts guide at www.scribe-x.com/the-5-shifts. It was built as code, published on the real domain, around WordPress, with a kill switch and zero disruption to the rest of the site. That's the proof this works.

Next, together

Let's talk through which pages make sense for the AI-Speed Lane, agree on the review-and-approve flow, and line up the first batch. This doc will grow as we settle the process.