Your tools, inside the CMS
Developers can add custom tools to the CMS sidebar, such as a launch checklist, an SEO dashboard, or an internal reporting page, so editors do not have to leave the CMS to use them.
Plug into your workflow
-
Publishing checks enforce your own rules before content goes live.
-
Notifications send updates to email or your team chat.
-
Action hooks trigger other systems, such as analytics or a search index, when content changes.
-
Themes adjust the look of the CMS to suit your team.
Bring your own providers
Root.js connects to the services your organization already uses and approves: AI models from several providers, translation services such as Crowdin and DeepL, and data from Google Sheets or any API.
Content structure as code
The structure of your content is defined in code alongside the website. Changes to it are reviewed, tested, and versioned like any other change, and developers get type checking that catches mistakes before they reach editors. The editor can also be embedded in other internal apps.
No lock-in
Root.js, including the CMS, is open source under the MIT license. Content is stored in your own cloud project and can be exported at any time, and the code that renders your website is yours.
Frequently asked questions
- Can we add our own internal tools to the CMS?
- Yes. Developers can add custom pages to the CMS sidebar, and custom publishing checks, notifications, and hooks.
- What if we want to move off Root.js later?
- Your content is in your own database and can be exported, and the software is open source.
- Does it work with our existing providers?
- Root.js supports several AI, translation, and data providers out of the box, and developers can add others.