What this example shows
A fictional neighborhood association publishes an HTML survey report, collects two precise comments, and publishes a second version that answers them. Every name and number on this page is fictional. The two versions stand next to each other below: version 1 with its comments, and the revised version 2.
This is the workflow behind collecting feedback on an interactive research report: one self-contained file, comments attached to the exact text or point they mean, and a next revision with the earlier version still in history.
The report, before and after
survey results.
Most respondents prefer weekend workshops. Attendance held steady through the spring.
Marks the Q3 bar in the chart above.
This bar carries no value label. Readers cannot tell 40 from 60 or check whether attendance held steady, so label every bar.
On version 1lead by a clear margin.
Of 42 fictional respondents surveyed in March, 31 prefer weekend workshops. Attendance rose from Q1 to Q3, then fell in Q4.
Every bar carries its fictional value. Sample: 42 fictional respondents.
In short: version 1 claims that most respondents prefer weekend workshops, says attendance held steady through the spring, and shows an attendance chart without values. Mara comments on the claim and asks who was surveyed. Jon comments on the Q3 bar, which carries no value label. Version 2 states the sample, 31 of 42 fictional respondents, labels every bar (Q1 30, Q2 45, Q3 52, Q4 38), and says attendance rose from Q1 to Q3, then fell in Q4. Both comments stay on version 1.
Why each comment names its version
Reviewers need to know which document version a comment refers to. In Jotzu every comment carries its revision: the two comments above sit on version 1, and they stay on version 1 after version 2 is published. Opening an earlier revision shows the comments written against it, so the history keeps its meaning. A guest link is pinned to the revision it names and does not follow the newest version.
Compare the revisions without a diff tool
To compare the report before and after feedback, open version 1 and the current revision from the revision history and read them next to each other, as on this page. Jotzu keeps every revision and its comments; it does not generate a semantic or pixel-level comparison between versions. Publishing a revision and resolving a comment are separate actions, so an open comment stays open until someone resolves it.
The chart is drawn by the page, not a screenshot
This review never flattens the chart into a screenshot. The report is one self-contained file: its chart is inline SVG drawn by the page itself, so it stays sharp at any size, with no library loaded from another website and no outside fonts. Scripts and fonts from other websites do not load in the preview, so a report that depends on them will not render as its author saw it. Upload one self-contained HTML, Markdown, or PDF file, up to 10 MiB, and the interactive parts of a real report keep working in Jotzu while reviewers comment. Export gives back the original file or a rendered PDF.
Start your own review
To walk through the whole flow, share an HTML file for feedback. For the full workflow, see how Jotzu works. Straight answers to common questions are in the FAQ.
Who did we ask? State the sample before the claim, or readers cannot judge it.
On version 1