Review HTML mockups with pinned comments
A design review breaks down when nobody can tell what "the button" refers to. In Ollav every comment is pinned to an element of the live mockup, so the conversation sits on the thing it's about.
Leaving a comment
- Open the shared link.
- Click the element you mean: a heading, a button, a table cell.
- Write the comment. You can paste a screenshot into it.
The pin stays attached to that element after reloads and most re-renders. Ollav anchors to stable attributes (data-*, ARIA roles, text) rather than generated class names, and falls back to matching the element's text.
State matters. If the element only appears after a few clicks (a modal, step 3 of a wizard), Ollav records the clicks that got you there, and you can add a short note like "Open the pricing modal first". Reviewers and agents can then reproduce the state.
Reacting instead of replying
Use reactions to show agreement or progress without adding noise. Every comment has a default bar, and the + opens a searchable picker with every emoji (your recent ones first):
- 👍 agree
- ❤️ love it
- 🎉 nice
- 👀 looking at it
- ✅ done
You can also mark an element with an emoji alone. When you place a mark, pick its look: the numbered pin, a quick 👍 👎 ❤️ ❓ 💡, or any emoji. Then add a comment or leave it as a reaction. The emoji is what shows on the page.
Resolving
When a thread is dealt with, resolve it. Resolved threads turn grey and drop out of the agent's default view (get_review returns open threads only). Reopen one if the fix didn't hold.
Versions
Publishing a new version keeps the same link. Comments from earlier versions stay, marked as made on an earlier version, because their element may have changed. Review rounds then look like this:
| Round | What happens |
|---|---|
| v1 | Reviewers pin comments and react |
| v2 | Designer or agent fixes the top threads, resolves them and replies "fixed in v2" |
| v3 | Remaining threads, then sign-off |
Running a good review round
- Set a scope. "Comment on the onboarding flow only" keeps feedback relevant.
- Set a deadline. The link is always live, so tell people when you'll ship the next version.
- One thread per issue. Reply in the thread rather than starting a new pin on the same element.
- Let the agent do the busywork. If an agent built the mockup, it can read the open threads, make the edits and resolve them. See the agent feedback loop.