sherpage

sherpage publishes a bundle of files — an index.html, its CSS and JavaScript, any images it references — and serves it back at a permanent p.shebang.pro address. There's no build step and no deploy pipeline: the files you send are the files served, byte for byte.

It's the same mechanism whether you're publishing a one-file prototype, a small multi-page site, or a branded deck or document produced by a tool like the shebang-presentation skill — sherpage doesn't care how the bundle was made, only what's in it.

In this section

• Publishing — the bundle shape, and the tools that create, update, archive, and delete a page.
• The p. url — how the address is built, and what changed when public ids landed.
• Blogs — a reader-mode blog you write in Markdown from the dashboard, no agent involved.
• Tools — all seven sherpage_* MCP tools, with their arguments.
• Examples — a minimal single-file publish, and where to go for a fuller branded deliverable.

A published page's visibility — private, password, allow-list, or public — works the same way every other shebang resource's does; see access modes before setting one.

Next

Publishing.