AI-native documentation for WordPress

One source for readers, search, and agents.

Keep Markdown beside your code. DocsPress publishes native Gutenberg Pages, exposes exact .md twins and /llms.txt, and carries WordPress edits back to GitHub as reviewable pull requests.

github.com/repo
docs/
index.mdquickstart.mdapi.md
Octocat and Wapuu high-five beside the DocsPress workflow.
DocsPresskeeps one source
For readersWordPress PagesNative Gutenberg
For agents/llms.txtExact page.md routes
Reviewable pull requestWordPress edits return to GitHub

/llms.txt

Agent discovery

A small index points to every published, source-backed Markdown page.

page.md

Exact source twins

Agents fetch reviewed Markdown directly—never reconstructed or scraped HTML.

GitHub ↔ WordPress

Reviewable sync

Commits publish Pages; Gutenberg edits return to the repository as pull requests.


Site Editor

Fully customizable

Change templates, navigation, styles, and every DocsPress block with native WordPress controls.

v1 → v2 → v3

API versioning

Publish current and historical releases with version-aware URLs, switching, and notices.

Threaded replies

Built-in discussions

Open comments where feedback helps, with moderation and spam controls provided by WordPress.

Built for the agentic web

HTML for people. Markdown for machines. No parallel docs stack.

Every published source-backed Page has two deliberate surfaces. People get the complete WordPress reading experience; agents and retrieval tools get stable Markdown with a predictable content type.

See how AI discovery and Markdown routes work →

markdown /llms.txt
# Product documentation> Guides and API reference.## Documentation- [Quickstart](https://docs.example.com/docs/quickstart.md)- [API reference](https://docs.example.com/docs/reference/api.md)- [Continuous sync](https://docs.example.com/docs/guides/continuous-sync.md)
A small discovery index points agents to exact, reviewed Markdown pages.

GitHub stays authoritative

Markdown moves both ways without losing review.

DocsPress keeps documentation beside the product it explains, while WordPress remains a first-class editorial and publishing surface.

Follow the continuous synchronization guide →

  1. Edit Markdown with the code

    Authors and coding agents work in the repository they already review.

  2. Publish through GitHub Actions

    DocsPress converts the tree into native Gutenberg Pages and stores the exact source beside each Page.

  3. Edit in WordPress when it helps

    Editors can improve managed Pages with familiar blocks instead of learning a separate docs frontend.

  4. Review the change back in GitHub

    WordPress-only edits become a focused pull request. Two-sided changes stop as explicit conflicts.

Success
One reviewed documentation corpus

The WordPress experience, /llms.txt index, and page-level .md routes stay aligned with the same source-owned Markdown.

Markdown → Gutenberg → Markdown

Installable WordPress packages

Two packages. One native documentation system.

Install through the normal WordPress upload screens. No separate frontend, build service, or proprietary runtime required.

Site experienceLatest theme

Download Theme

A Site Editor-first documentation shell with editable templates, navigation, search, reading tools, and complete visual style families.

  • Site Editor
  • 10 visual systems
  • Docs navigation

WordPress 6.6+ · PHP 7.4+ · GPL-2.0-or-later

Authoring toolkitLatest blocks

Download Blocks

Add the Gutenberg blocks demonstrated in Kitchen Sink: API requests, code tabs, file trees, diagrams, prompts, flows, results, and more.

  • 15 docs blocks
  • Native controls
  • Theme-aware

WordPress 6.6+ · PHP 7.4+ · GPL-2.0-or-later

Start with the repository you have

Bring Markdown, or generate it from source.

Both paths end with reviewed documentation owned by your GitHub repository.

From the site

Latest updates