Whitepapper is a markdown-first content system built for developers who want full control over how their content is written, organized, published, and distributed without wrestling with bloated CMSes.

You write in Markdown. Whitepapper handles the rest: organizing your content into projects and collections, publishing public pages with proper SEO metadata, and exposing everything through a clean API you can call from your own frontend.

Who is Whitepapper for?

Whitepapper is built for developers who:

• Want to write and manage content in Markdown without a heavy CMS

• Need a structured way to organize content into projects and collections

• Want to publish content as public pages with SEO metadata they actually control

• Want to distribute the same content to platforms like Hashnode and Dev.to without rewriting

• Want to power their own frontend or app with a project-scoped API

What problems does it solve?

Writing and organizing content is fragmented. Most tools force you to either use a GUI you don't want, or roll your own CMS from scratch. Whitepapper gives you a structured content hierarchy without building anything.

SEO metadata is an afterthought everywhere else. Whitepapper makes metadata a first-class part of every paper. You can auto-generate it or fill it in yourself, and it maps directly to Open Graph, Twitter Card, JSON-LD, and standard meta tags on the public page.

Publishing to multiple platforms is tedious. You publish once on Whitepapper and distribute to Hashnode, Dev.to, or Medium from the same editor without copy-pasting.

Calling your content from a frontend requires a whole backend. Whitepapper's Dev API lets you fetch your project, collections, and papers with a single API key. No database, no extra service.

Content hierarchy

Whitepapper organizes content in this order:

User
├── Standalone papers
└── Projects
    ├── Project standalone papers
    └── Collections
        └── Collection papers

• A paper is a single Markdown document and the core unit of content.

• A collection is a group of related papers inside a project.

• A project is the top-level container. It has its own API key, its own public page, and its own visibility setting.

• Standalone papers live directly under your account, outside any project.