Jahia Collaborative Content Review Panel
Jahia Collaborative Content Review Panel
In-context review comments and task assignment for jContent — collaborate on any page without leaving the editor.
Add a collaborative review sidebar to jContent. Your team leaves threaded comments directly on any page or content item, pins each one to the exact component it's about, resolves them together, and turns follow-ups into native Jahia tasks — all in edit mode, and none of it is ever published to your live site.
Overview
Content Review Panel makes editorial review a conversation that happens right where the work is. Instead of scattering feedback across email, chat threads, and spreadsheets, reviewers comment on the page itself inside jContent — and every comment stays private to the back office.
Open the Review comments panel from the page toolbar and you get a chat-style thread attached to the content you're looking at. Comments show who wrote them and when, can be replied to, resolved, reopened, and assigned — giving editors, reviewers, and stakeholders a single shared place to sign off on content before it goes live.
Key features
- In-context comment drawer on any page (jnt:page) or content item (jmix:mainResource), opened straight from the jContent toolbar.
- Threaded discussion — reply to a comment, keep the conversation together, with author and timestamp on every entry.
- Pin a comment to a component — point-and-click directly on the Page Builder canvas to anchor a comment to the exact element it's about; click the pin later to jump back to it.
- Resolve, reopen, and "resolve all" — track what's been addressed and filter open vs. resolved at a glance.
- Assign to a teammate — turn a comment into a standard Jahia task that appears in the assignee's Dashboard → My Tasks, with a one-click link back to the reviewed page.
- Private by design — comments are stored as hidden, non-published nodes; publishing the page never pushes review chatter to your live audience, and they never appear in pickers or the content tree.
- Bilingual out of the box — full English and French UI.
Why teams use it
- Feedback lives with the content, not in a separate tool — no copy-pasting URLs or screenshots.
- Nothing leaks to production — review notes are back-office-only, guaranteed.
- No new system to learn — assignments use Jahia's own task dashboard; comments use jContent you already know.
- Zero configuration — install, enable on a site, and start commenting.
Requirements
- Jahia 8.2 or later.
- Enable the module on your site (Site settings → Modules), then open any page in jContent.
Vidéo
Captures d'écran
Comment installer
From the Jahia Store (recommended)
- In Jahia Administration → Modules (or the Store), find Content Review Panel and install it.
- Open your site's Site Settings → Modules and enable Content Review Panel for the site.
- Open any page in jContent — the Review comments button appears in the page toolbar.
Manually, from the release .jar
- Download content-review-<version>.jar from the GitHub releases.
- Deploy it in Administration → Modules → Upload a module (or via the Module Manager / Provisioning API).
- Enable it on your site as above.
From source
git clone https://github.com/smonier/content-review.git
cd content-review
export JAVA_HOME=$(/usr/libexec/java_home -v 17) # Java 17
mvn clean install
# then deploy target/content-review-*.jar as above
No configuration files, no server settings — once enabled on a site, it works.
FAQ
Where are review comments stored, and can site visitors see them? Comments are stored as hidden nodes directly under the page or content item being reviewed, and they are non-publishable. Publishing the page never pushes them to the live site, and they never appear to visitors, in content pickers, or in the Page Builder canvas — they live only in the editing workspace.
Who can read and leave comments? Anyone with edit access to the content. Because comments live under the content node, the same permissions that let someone edit a page let them read and add review comments on it.
Does it work on content items, or only pages? Both — any page (jnt:page) and any main-resource content item (jmix:mainResource, e.g. articles, news, press releases).
Can I pin a comment to a specific part of the page? Yes. Click Attach component, then click the element on the page; the comment is anchored to it, and you can jump back to it anytime by clicking its pin. On views with no page canvas you get a content picker instead.
What happens when I assign a comment? It creates a standard Jahia task in the assignee's Dashboard → My Tasks, titled from the comment and linking back to the reviewed page. Resolving the comment marks the task finished; reopening it reactivates the task.
I assigned a comment but the person doesn't see the task — why? Check, in order: (1) they need to look under Dashboard → My Tasks; (2) resolved comments' tasks are finished and drop off the default active-tasks view; (3) if you're testing as root, note that root sees all tasks regardless of assignee, so verify with the actual assignee's account; (4) after updating the module, reload the jContent tab so it runs the latest version before assigning.
Does it send email notifications? Not in this version. Assignees are notified through the standard Jahia task dashboard, and reviewers get an in-app toast when new comments arrive while the panel is open.
Can I delete or resolve someone else's comment? Anyone with edit access to the page can resolve or reopen any comment. You can delete your own comments; a comment that already has replies is kept so the thread stays intact.
The "Review comments" button doesn't appear. Make sure (1) the module is enabled on the current site, (2) you've selected a page or a main-resource content item (it doesn't show on folders or other node types), and (3) you've reloaded jContent since installing.
What languages are supported? English and French, chosen automatically from the jContent UI language.
Has it been security-reviewed? Yes. It was swept against Jahia's internal security-scan taxonomy: all actions run as the signed-in editor through Jahia's own APIs (no elevated sessions, no custom endpoints), displayed author identity comes from the server (not client input), comment text is neutralized before it reaches a task, and review data never reaches the public site.
MIT