Skip to main content
All guides
Collaboration

Feedback right where the words live

Website feedback usually lives everywhere except the website: in chat threads, email chains, and screenshots with red circles. The Root.js CMS brings the conversation into the editor, next to the exact field it is about.

A comment thread pinned to a field in the Root.js CMS editor, with teammates discussing a headline and an @mention.

Comments on the field, not in the chat

Anyone can start a comment thread on a specific field, such as a headline, an image, or a call to action. Mention a teammate with @ and they are notified. Threads can be resolved when the change is made, and important ones can be pinned to the top of the doc, so decisions stay attached to the content they shaped.

See who is working on what

Avatars at the top of each doc show who else is viewing it right now, so two people do not rewrite the same page at the same time. The doc’s status shows when it was last saved, and by whom.

Track content work with tasks

The task manager (currently an experimental feature) tracks the work behind a launch: writing copy, reviewing translations, replacing images. Tasks link to the docs they are about and have assignees, statuses, and due dates, so the whole team can see what is left before a release.

The Root.js CMS task board, with content tasks like writing alt text and reviewing German translations moving from new to in progress to in review, each with a priority, an assignee, and a target launch date.
Tasks for a spring launch, each linked to a doc and assigned to a teammate.

Notifications

The CMS can notify people by email when they are mentioned in a comment, or tell admins when content is published. Developers can connect other notification channels, such as your team chat.

Frequently asked questions

Where does review feedback live?
On the field it is about, as a comment thread with @mentions, resolved when the change is made.
How do we avoid overwriting each other’s work?
Live presence shows who is viewing each doc, and every save is kept in the version history if something needs to be recovered.
Can we track a launch checklist in the CMS?
Yes, with tasks that link to docs and have assignees and due dates.
Next guideRoles, permissions, and governance
1
2
3
4
5
6
7
8
9
10
11
12
Breakpoint: