HTML review
Review the rendered HTML, not a screenshot of it.
HTML review often gets split across a browser tab, screenshots, Slack messages, and a source-code diff. HTML Docs puts the feedback layer on the actual artifact. Reviewers keep the layout and interactions in view while comments stay connected to the content being discussed.
Vague feedback creates avoidable revision cycles.
“The section near the bottom feels off” forces the author to reconstruct what the reviewer saw. A comment anchored to the relevant region carries more context and can be read by both a human editor and an agent. Threaded replies keep clarification with the original issue.
How it works
From local output to a reviewed artifact.
Publish the page
Create a live version that preserves the original HTML experience.
Invite the reviewer
Send a browser link instead of an attachment or screenshot set.
Discuss in context
Use comments and replies around the relevant region of the page.
Revise and resolve
Update the page, explain the change, and close the completed thread.
What changes when review is built into the page
Fewer translation errors
The reviewer and author look at the same rendered state.
Actionable context
Feedback carries the page region and selected text when available.
Review history
Versions and threads show how the artifact reached its current state.
HTML Docs vs. Screenshot feedback
Choose for the job you actually need to finish. This comparison focuses on workflow, not a blanket claim that one tool replaces another.
| Criterion | HTML Docs | Screenshot feedback |
|---|---|---|
| Interactivity | Review the functioning page | Static representation only |
| Comment context | Connected to document regions | Pins or prose on an image |
| Revisions | Update the same artifact | Capture and resend new screenshots |
Frequently asked questions
Can reviewers comment without editing the HTML?
Yes. Reviewers can focus on reading and feedback while editors control content changes.
Are comments threaded?
Yes. A comment can have replies and can be resolved or reopened as the review progresses.
Can an AI agent act on the comments?
Yes. Comments and editable regions are available through the collaboration API.
Does HTML Docs replace code review?
No. Use code review for implementation quality. Use HTML Docs when stakeholders need to review the rendered artifact and its meaning.
Publish the next artifact from where it was created.
npx @html-docs/cli publish page.html