Use case
Answer first. Current behavior only.
Publish Markdown documentation without operating another build pipeline
WeWrote stores document bodies with Markdown portability and lets you publish them from a dashboard. A published space becomes a fast reader with navigation, breadcrumbs, and full-text search, so routine documentation updates do not require rebuilding and deploying a separate docs repository.
Use a managed portal when deployment work is the wrong work
A static documentation framework is a strong choice when the docs need custom components, versioned releases, or localization. It can be excessive for a team maintaining SOPs, a consultant with client handoffs, or a founder publishing operating procedures.
WeWrote narrows the workflow to authoring, organization, publication, and reading. We stopped at the knowledge base so you don't have to operate another build pipeline.
The publishing path
- 01Create and edit a document through the clean web editor.
- 02Content is stored with Markdown portability while metadata and searchable text are indexed cleanly.
- 03Switch the document from draft to published.
- 04The document appears under its path in the public space reader.
- 05Readers navigate or search the published set without needing an account.
Automation and agent integration
WeWrote is designed to work with AI coding agents via open REST APIs and native MCP servers, allowing agents to push documentation and receive live share links directly.