Choose the review workflow for the artifact your team is shipping.
Route docs, static HTML, decisions, knowledge bases, generated specs, and launch previews into the Commentary surface that keeps the work readable before it ships.
Every solution starts from the product surface reviewers actually use: rendered Markdown, HTML Review, Knowledge Brain, draft review, developer handoff, or opted-in live preview feedback.
- Docs pages
- HTML pages
- Knowledge bases
- Launch previews
Start from the team, then show the surface.
Each solution page names the promise, shows the concrete product surface, and points to the next product or developer step.
Documentation teams
Open Git-backed Markdown, MDX, static HTML, and review-hosted Forms as readable pages, then check every section for accuracy, structure, completeness, and release readiness.
Engineering
Give ADRs, design docs, rollout plans, operational guidance, project knowledge bases, and acceptance-gate forms a readable review surface before teams or agents depend on them.
Agentic development
Review AI-drafted specs, plans, docs, maintained knowledge bases, and agent-created review forms as readable artifacts, then give agents structured comments and answers they can act on without guessing.
Product and design
Review product specs, launch narratives, GTM content, static HTML pages, beta feedback forms, and opted-in live previews with cross-functional context in one workspace.
Start with the document workflow.
Open a focused product page or use the developer surface when review feedback needs to flow back to agents and tools.