Why We Built GetPagemark

The Problem

We tried every documentation tool out there. Here's what we found:

• GitBook — raised their prices and locked features behind enterprise plans
• ReadMe — great for API reference generation, but overkill for a simple docs site
• Docusaurus — requires a full React project
• MkDocs — needs Python

Even the "simple" options come with a build step, config files, and deployment pipelines.

All we wanted was to push a folder of markdown files and get a clean, searchable documentation site with a sidebar. That's it.

So We Built GetPagemark

The entire flow is three steps:

1. Connect a GitHub repo
2. Pick a branch
3. Choose a slug

Done. Your site is live at slug.getpagemark.com with:

• Auto-generated navigation from your folder structure
• Full-text search
• Dark mode
• A clean default theme

Read More

• Markdown Is Enough — why we bet on plain markdown instead of custom component systems
• Private Repos Are Now Supported — connect private GitHub repos and build docs securely

Zero Configuration Deploys

Every push to your branch triggers a rebuild. No CI/CD to configure. No YAML. No build commands. Just git push and your docs are updated.

Simple, Fair Pricing

We charge $3/month per additional site after your first free one. That's the whole pricing model.

• No per-seat pricing
• No feature gates on the free tier (except custom domains and metadata customization)
• The free tier is genuinely useful — it's not a trial

---

If you're tired of fighting your documentation tooling instead of writing documentation, give GetPagemark a try.