Markdown compatibility2 detected · 0 enabled · 0 missing assets · mkdocs docs · 2 warnings
- HomeREADME.md
- Getting starteddocs/getting-started.md
- Core conceptsdocs/core-concepts.md
- Demo walkthroughdocs/demo-walkthrough.md
- Review pull requestsdocs/review-pull-requests.md
- Review repository branchesdocs/review-repository-branches.md
- Draft reviewsdocs/draft-reviews.md
- Brainstorming Reviewsdocs/brainstorming-reviews.md
- Live Preview Reviewsdocs/web-app-reviews.md
- Commentary Formsdocs/commentary-forms.md
- Review progressdocs/review-progress.md
- Review modesdocs/review-modes.md
- Workspacedocs/workspace.md
- Markdown renderingdocs/markdown-rendering.md
- Markdown extensionsdocs/markdown-extensions.md
- Static HTML reviewCurrent page
- Knowledge Braindocs/knowledge-brain.md
- Access and authenticationdocs/access-and-authentication.md
- Developer accessdocs/developer-access.md
- Generate a GitHub PATdocs/generate-a-github-pat.md
- Azure DevOpsdocs/azure-devops.md
- Commentary CLIdocs/commentary-cli.md
- Agent skillsdocs/agent-skills.md
- API and MCPdocs/api-and-mcp.md
- API referencedocs/api/reference.md
- MCP toolsdocs/api/mcp-tools.md
- Blogdocs/blog.md
- Troubleshooting and FAQdocs/troubleshooting-and-faq.md
- MkDocsMkDocs is a Pro Markdown feature that is not enabled for this viewer. MkDocs-specific syntax remains visible as ordinary Markdown when compatibility rendering is unavailable.
- Repository link validationPro can validate links across this repo. Links still render with standard repository-aware rewriting.
Static HTML Review
Commentary can review static .html and .htm files in the same document-first workspace as Markdown.
What Works
Static HTML files open with:
- rendered
Previewmode Rawsource mode- file navigation across changed or branch files
- outline navigation for headings and meaningful sections
- semantic comment anchors for headings, sections, rows, cards, figures, and other stable blocks
- app-native comments and replies
- sanitized Commentary Forms bindings when the HTML declares compatible form controls
HTML authors do not need to add Commentary IDs, custom tags, or data-commentary-* attributes for ordinary review anchors. Commentary uses ordinary structural and content signals such as element type, headings, nearby text, IDs, classes, ARIA labels, titles, alt text, links, table labels, figure captions, and sibling context.
Forms In Static HTML
Static HTML can bind controls to a Form Contract with declarative data-commentary-field metadata. Commentary validates values against the contract, reports binding diagnostics, and submits through the same server-side Forms validation path as native Forms.
HTML bindings do not trust form action, inline handlers, customer scripts, or unsafe page behavior. See Commentary Forms.
Safety Model
HTML preview is sandboxed. Commentary strips or blocks active behavior that would make review unsafe or misleading:
- scripts do not run
- event handlers are removed
- dangerous URLs are removed
- active embeds are blocked
- unsafe stylesheet behavior is restricted
When restrictions affect a file, the review shell shows a compact status summary so reviewers know the preview is intentionally safer than a full browser page.
Current Boundaries
Static HTML review is for document-like artifacts, generated reports, and static pages. It is not a live deployment preview. JavaScript execution, multi-page crawling, full browser fidelity, and visual HTML diff are outside the current review surface.
Provider sync for rendered HTML comments is best effort. When Commentary cannot map a rendered HTML comment to reliable provider source lines, the thread stays app-native or syncs with file-level context.