Pagoti; A Markdown CMS for quick publishing
I built Pagoti as a lightweight alternative to traditional CMS platforms. The core idea was simple: most content workflows don't need complex admin interfaces or heavy database setups when all you're doing is writing and exposing content via API.
You can use Pagoti for:
- Sharing documents with private links (cleaner than Google Docs for one-off client shares)
- Managing content for Next.js or Nuxt projects without introducing Contentful or Sanity
- Give clients direct access to update content without touching the codebase
The workflow is straightforward: write in Markdown, publish, and access content through either API endpoints or consume on pagoti.com links.
Content is organized into projects and pages, with media assets that can be reused across different projects.
Custom themes support Google Fonts and various typographical controls for branded outputs.
Practical use cases
- Restaurant menus: Update pricing and menu items without redeploying, with QR code generation for in-venue access
- Client deliverables: Share proposals, project briefs, and documentation with expirable private links
- API documentation: Maintain technical docs that can be updated frequently without deployment cycles
- Campaign landing pages: Spin up simple pages without touching the main application codebase
- Internal documentation: Build team wikis where everyone works in Markdown instead of fighting with rich text editors
- Portfolio case studies: Expose project writeups via a single API across multiple sites
- Project context and notes: Keep searchable, linkable documentation that doesn't get lost in Notion or Google Docs
## What comes next?
I'm considering expanding the Stripe integration to support product catalogs and digital downloads. I've built ecommerce platforms that power UK retail brands before, and I keep seeing cases where existing solutions are unnecessarily complex for straightforward selling.
If there is demand I'd love to dive into multi cursor editing and sharing resources across teams on a per-project basis.
I'm also working on a CLI tool that uses Pagoti as persistent storage for Claude Code sessions—a place to maintain to-do lists, context, and notes that survive across different coding sessions and agents.
I'd appreciate feedback from other developers on whether this addresses a real gap in your workflow or if the problems I'm solving are too specific to my own use cases. Contact me if you have thoughts.