Editorial Review Threads

Editorial Review Threads lets reviewers pin comment threads to individual fields on the content edit form. Editors reply, mention colleagues and resolve threads, and content cannot be published while threads are still open.

Reviewing content in Drupal usually happens outside Drupal: in email, chat or a shared document, with comments like "the second paragraph of the body" that editors then have to find. This module keeps the review on the edit form itself, next to the exact field it is about, and makes sure nothing is published before the review is done.

Features

• Threads on fields. A comment button next to each field label shows how many threads are open on that field. A side panel lists the threads and lets reviewers start new ones, reply, and resolve or reopen them.
• Publish gate. A validation constraint stops content from being saved as published while it has open threads. It works with or without Content Moderation, and applies to every validated save: forms, JSON:API and REST. A permission lets trusted users bypass it, and the gate can be turned off.
• @mentions. Type @ in a message to pick a colleague. Mentioned users get an email with a link straight to the thread. Only people who can see the thread are suggested, so nobody is notified about content they cannot open.
• Built for multilingual sites. Each translation is reviewed and published on its own: a comment on the English title does not block the Arabic version. Threads on untranslatable fields are shared by every language. The edit form links to open threads in other languages, and right-to-left languages are fully supported.
• Per-field control. Turn threads off for any field with an "Allow review threads" checkbox in Manage form display.
• Overview. Content » Review threads lists every open thread on content you can edit, with its field and language, linking straight to the thread on the edit form.
• Plain Drupal underneath. Threads and messages are content entities with Views integration, so you can build your own dashboards. Threads are deleted with the content, or the translation, they belong to.
• Accessible. Keyboard navigation, screen reader announcements and labelled controls throughout.

Post-Installation

1. Go to Administration » Configuration » Content authoring » Editorial review threads (/admin/config/content/editorial-review) and choose the content types that use review threads.
2. Decide whether open threads block publishing, and whether mentioned users are emailed. Both are on by default.
3. Grant the permissions at Administration » People » Permissions: View review threads, Create review threads and replies, Resolve review threads, Bypass the review publish gate and Administer editorial review. Users also need permission to edit the content itself.
4. Optionally, turn threads off for some fields: in the content type's Manage form display, open a field's widget settings and uncheck "Allow review threads".

Threads can be started on saved content. The language selector and the fields in the form sidebar (authoring information, URL alias, publishing options) never get threads.

Additional Requirements

Drupal 11.1 or later and the core Node module. No other modules or libraries are needed.

Recommended modules/libraries

• Content Translation (core), to review each translation on its own.
• Content Moderation (core). The publish gate reads the moderation state, so a transition to a published state is blocked while threads are open.
• Views (core), to build your own lists of threads and messages.

Similar projects

Core's Comment module adds public discussion to published content for site visitors. Editorial Review Threads is for the editorial team instead: its threads live on the edit form, are pinned to a single field, are never shown to visitors, and take part in the publishing workflow.

Supporting this Module

Bug reports, feature requests and patches are welcome in the issue queue. Translations can be contributed on localize.drupal.org.