About five minutes. The site's page in Settings walks the same steps and ticks them off.
https://example.com.</body> on every page,
and publish. Nobody you have not invited sees anything.Send reviewers your site's login first, then turn on Sign-in on the site's page.
Add these, or the browser will block the tag without saying so:
script-src https://mend.page connect-src https://mend.page wss://mend.page img-src blob: data: https://mend.page style-src 'unsafe-inline' (or put your nonce on the tag as data-csp-nonce) frame-src https://mend.page (the bot check, where visitors join or ask)
Turn on Guests on the site's page: visitors leave notes with a first name, for 24 hours, and see only their own. Show pins to visitors shows people who have not joined where notes are, never what they say.
Add the site's own labels under Labels, such as Tree work. Anybody who can read a note can label it, and readers filter the pins by label.
| Content Reviewer | Leaves notes that wait for the client’s approval before anything changes. Closes only their own. |
|---|---|
| Reviewer | Leaves notes. Never sees the console. |
| Triager | Fixes and sorts notes. The role for a developer. |
| Site owner | Runs the sites you give them: settings, reviewers and notes. Doesn’t see what agents do unless you switch it on. |
| Maintainer | Every site, plus addresses, people, repositories and runner tokens. |
| Owner | All of that, and can permanently remove a person's words. |
data-review-anchor="hero-cta" keeps notes on an element attached when
the page is rebuilt.data-review-redact covers an element in every picture.<meta name="review:release" content="…"> with your build's commit
lets reviewers be asked "does it look fixed?" after you deploy.Also: Leaving notes, for reviewers · Setting up a site · Fixing notes