React Bricks is itself a headless CMS in the sense that it has APIs as a service, but:
These two features together make it unique, and allows magic that cannot be done with a "normal" headless CMS: the magic of direct Visual editing.
Once there were the monolithic CMSs, like Worpress and Drupal (and they are still there). Then came APIs and the separation of concern between the server APIs and the frontend website. Developers want to do the frontend part, creating websites using React (with Next.js, Gatsby or Remix). And so came headless CMSs, the server part of a monolithic CMS as a service (admin interface and APIs).
But headless CMSs don't know how the content is presented on the frontend (they are decoupled from the frontend, which developers like), and so you cannot have visual editing any more.With headless CMSs, we lost the direct visual editing of content, which was replaced by gray forms.
Visual editing is a much better UX for content creators, because they can see how the content looks as they create it.
The best headless CMSs try to fill this gap providing an instant preview: you edit the code on a form which lays on a sidebar and you see the result on the page.
Unfortunately that is not direct visual editing. Writing in one place and looking for result in another place causes a much higher cognitive load. Developers are used to this: edit code in your IDE and see the result in the browser. Content creators are used to the much better experience of Word or Pages: you just click on the text that you want to change and write.
React Bricks combines all the advantages of a headless CMS and a visual site builder, improving on both: it is better than a headless for developers and better than a visual builder for marketing and content creators. Let's see why!
You get all the advantages of a Headless CMS:
and much more:
You get all the advantages of a Visual builder like Wix or WebFlow:
and much more:
Be the first to discover our latest news. No spam, promise.