Notion as CMS is not always a good choice

We at Splitbee created an OSS library called react-notion [1] that helps you rendering Notion content in your React app.

This has many benefits such as the simplicity of the Notion Editor, simple layouts and ease of use.

While this works out for smaller blogs and content pieces across the website, it also has some drawbacks.

* No proper versioning/publishing feature. Depending on the implementation, the changes are visible on the website immediately or after the next deployment. * No i18n support. You would need to write content on 2 or more pages and link them somehow. * Can break at any time because we use Notion's Private API. (ing forward for the Public API)

We initially built our blog [2] & documentation [3] with react-notion but switched away with the Documentation to Sanity. We simply needed the versioning and publishing features.

Nevertheless, react-notion can be a great way for websites to display rich text content. The implementation is easy and it looks sleek out of the box.

[1] https://github.com/splitbee/react-notion [2] https://splitbee.io/blog/notion-as-cms-using-nextjs [3] https://splitbee.io/docs