Blog

How to share a Markdown file as a web page only your team can see

A runbook, a handbook, meeting notes your agent wrote. Markdown is easy to write and awkward to share with people who don't live in a code editor. The usual ways to turn it into a page, what each is good at, and the one-command version behind sign-in.

Coding agents write a lot of Markdown. Ask one to document how to restart the billing job and you get a runbook in runbook.md. Ask it to summarise a planning meeting and you get notes.md. Ask it to turn a pile of onboarding emails into something coherent and you get a handbook with headings, tables and checklists.

In your editor, that file is perfect. Then you need to send it to the support team, or the new starter, or a client, and it turns out most people don't want a .md attachment. They want a link that opens a page they can read on their phone.

This article is about turning one Markdown file into that page, for your team and nobody else. We make Spryloom, and the last option below is ours, so read it knowing who wrote it. The others are real choices, described as fairly as we can.

What "only my team" means for a document

A runbook can name internal systems. Meeting notes name clients and numbers. A handbook has the salary bands. So a link that opens for anyone who has it isn't good enough, and neither is a document anyone in the company can find by searching.

What you want is short:

  • A readable page. Headings, tables and code that look right on a laptop and a phone.
  • Sign-in before anything is sent, by people you name, with their own email.
  • A shared password. Not good enough.
  • One address that stays the same when you update the file.
  • A way to take someone off the list without changing it for everyone else.

Option 1: a GitHub Gist or a repository

A gist renders Markdown well, and a file in a GitHub repository does too. If your readers are engineers who already have GitHub accounts, this is often the easiest answer, and a private repository gives you real access control.

The trade-offs are about who's reading. A "secret" gist isn't private: it's unlisted, and anyone with the link can open it. A private repository needs every reader to have a GitHub account with access to it, which is a big ask for someone in finance or a client.

Option 2: paste it into Notion or Google Docs

Both are excellent for documents people will keep editing together. Comments, suggestions, version history and sharing controls that most people already understand. If the document is going to be edited by several people from here on, this is probably the right home.

The cost is that the document leaves the place it was written. Paste a Markdown file in and the formatting mostly survives, but the next time your agent updates runbook.md, someone has to paste it again, and the copy in the doc drifts from the file in your project. Readers also need an account with that tool, or a link setting that's more open than you wanted.

Option 3: a static site host

Netlify, Vercel, Cloudflare Pages and GitHub Pages can all publish Markdown, usually through a static site generator that turns it into HTML. If you're publishing many documents, a docs site with navigation and search is worth building.

For one file, it's a lot: a generator, a build step, a project on the host. And these hosts publish openly by default. Putting a login in front is a separate feature or product, with its own setup. How to put a login in front of an HTML page compares those options in detail.

Option 4: publish the file as a page

Spryloom publishes a single Markdown file as a readable page, behind sign-in that happens before the page is sent.

# Runbook ## Restart runbook.md sign-in Runbook
One file becomes one page. Invited people sign in and read it; anyone else gets nothing.

Spryloom turns the Markdown into a plain, readable page: one column, your device's system fonts, light or dark to match it, and tables and code blocks that scroll rather than overflow. It understands the GitHub flavour of Markdown, so tables, task lists and fenced code blocks come out as you'd expect. The page takes its title from the file's first # heading. Nothing is written next to your file, there's no server, and the page is live in seconds.

runbook
spry publish runbook.md --visibility invited
# then invite the team
spry invite runbook --email sam@yourcompany.com --email alex@yourcompany.com

--visibility invited means people you invite can open it. Without it, a new page opens only for you, which is the right state while you check it. Each person gets an email naming the page and who shared it, with an Open button that signs them in. It works once, for seven days; after that they ask for a sign-in link at the page's address. Nobody creates an account or chooses a password. Someone who wasn't invited reaches the sign-in page and no further, and the page is never sent to them.

If everyone who should read it is at your company, and you signed in with a work address whose mail runs on a service such as Google Workspace or Microsoft 365, you can let the whole company in instead:

spry publish handbook.md --visibility company --domain yourcompany.com

Keeping it up to date

Publish again with the same --visibility. Leave the flag off and the page goes back to opening only for you.

The address stays the same, the people you invited stay on the list, and the version number goes up. If the new version is wrong, spry rollback runbook puts the previous one back.

To take someone off the list:

spry uninvite runbook --email alex@yourcompany.com

From your agent

You don't have to leave the conversation. In Claude Code or Codex with Spryloom connected, "publish the runbook for the support team and invite sam@yourcompany.com" does the same thing. The agent asks who it's for before it publishes.

What it doesn't do

  • One file, one page. A Markdown file links to images on your computer that a single file can't bring along, and Spryloom tells you so when you publish. For a document with images, ask your agent to make a folder with an index.html and the images beside it, and publish the folder.
  • No navigation between documents. Several Markdown files are several pages, each at its own address. For a whole docs site with a sidebar and search, a static site generator is the better tool.
  • No editing in the browser, and no comments. Readers read. Changes come from the file, through you or your agent. If several people will keep editing the text, Notion or Google Docs is a better home.
  • Everyone invited sees all of it. It's a login, not a redaction. Keep what some readers shouldn't see out of the file.
  • For people you know. Everyone who opens it signs in with an emailed link. A page anyone can open without signing in isn't something Spryloom offers.
  • The badge. Pages carry a small "Built with Spryloom" badge. Publish with --no-badge to leave it off.

Which one to pick

Readers are engineers with GitHub access→A private repository
Several people will keep editing it→Notion or Google Docs
Many documents, with navigation and search→A static site generator and host
One file, now, for people you'll invite by email→A Spryloom page

Start here

From a terminal, in the folder with the file:

npx -y spryloom publish runbook.md --visibility invited

In Claude Code, add the plugin once, then ask your agent to publish the file:

/plugin marketplace add spryloom/claude-plugin
/plugin install spryloom@spryloom

Before you send the link, open it in a private browser window, where you're signed in to nothing. You should see a sign-in page, not your runbook.

Spryloom publishes apps and pages built with a coding agent behind sign-in, for the people you invite. This article was written by the people building it.

Get started free