Current feature
Answer first. Current behavior only.
Give readers a documentation portal, not a folder of disconnected files
Each published WeWrote space resolves into a clean reader with a document tree, path-aware navigation, breadcrumbs, rendered Markdown, and fast search over published text. Drafts and private spaces remain protected. Search provides instant, highlighted passages without mandatory AI complexity.
Navigation follows the document paths
Document slugs can contain slash-delimited paths such as setup/getting-started. WeWrote turns those paths into nested reader navigation and resolves parent documents for breadcrumbs.
The folder model is intentionally lightweight. Folders are path prefixes rather than complex databases with administrative overhead.
Search returns passages from published documentation
Search indexes document text and returns ranked results with short highlighted passages. Queries can be scoped to a path prefix within the current space.
Search is fast, dependable full-text search designed to find exact procedures, terms, and policies quickly.
Machine-readable discovery endpoints
Published spaces automatically expose sitemap and llms.txt endpoints so external search engines and machine readers can discover and index company documentation cleanly.