reviewer_notes

In‑context page annotations for content reviews

Reviewer Notes adds a lightweight overlay that lets editors and stakeholders leave in‑context notes anywhere on a page, tag them for easy filtering, track status (Open/Resolved), and collaborate via logs and per‑note comments.
It also includes an admin report to browse and export notes site‑wide.

Why use this module?

• Speeds up editorial review cycles with in‑context feedback
• Clear audit trail via logs and comments
• Flexible tag-based triage for large review sets

Key Highlights

• Two note types: Annotated element (anchors to an HTML element) and Quick note (page‑level)
• Tag filtering with OR logic; click a tag to add it to the filter
• Status workflow: Open ↔ Resolved with live UI updates
• Activity logs and per‑note comments (with user and UID)
• “Go to” scrolls to the anchored element (selector fallback)
• Admin report (filter by path/tags) and CSV export
• URL rules (supports wildcards) to control where the overlay appears
• CSRF protection for all POST endpoints (Configurable)
• Works with both URL aliases and system paths

Reviewer Note's interface

A few use cases

• Editorial review: Editors leave in-context feedback on headings, body copy, media, or CTAs; tag by section (hero, footer) or topic (tone, legal).
• Stakeholder sign-off: PMs/clients annotate specific components for approval or changes; track Open/Resolved for sign‑off history.
• QA/UAT: Testers flag broken links, layout glitches, or interactive issues on the exact element; devs “Go to” and resolve.
• Accessibility review: Auditors mark elements needing alt text, color contrast fixes, or ARIA roles, with tags like a11y/contrast/keyboard.
• SEO/content ops: Specialists note missing H1s, metadata, internal links; tag by priority or optimization task.
• Design review: Designers annotate spacing/typography/component fidelity against Figma; tags map to design tokens/components.
• Localization: Translators flag truncations, RTL issues, or hard‑coded strings on the exact element; tag by locale.
• Release readiness: Product owners collect page‑level “quick notes” for launch checklists and track resolution.
• Governance/compliance: Legal/compliance teams mark disclaimers, consent text, or policy updates to specific sections.
• Training/onboarding: Senior editors leave guidance notes tied to elements as living documentation.
• Regression tracking: During sprints, testers reopen resolved notes if regressions appear; logs give full history.
• Multi‑site oversight: Central team filters notes across paths/tags to spot systemic issues (e.g., footer links) and export CSV.
• Migration validation: Content teams annotate mismatches between legacy and migrated pages for targeted fixes.

Flow chart