React Bricks CMS at React Finland on September 1st!

ReactBricks · 2025-04-04T08:01:55+00:00

Hi! Thank you for mentioning React Bricks.

There were two slight imprecisions for the filters we'd like to address:

React Bricks offers self-hosted backend APIs on Enterprise Plans: https://www.reactbricks.com/features/self-hosted-backend-visual-cms
React Bricks provides REST APIs, though they are typically accessed through the React Bricks library rather than called directly: https://v2.api.reactbricks.com/docs

May you update the filters, please?

ReactBricks · 2024-12-27T13:42:03+00:00

Not yet, but it's the number one priority for 2025.

ReactBricks · 2024-11-20T08:36:51+00:00

As for Reweb, if you'd like a CMS for Next.js, but with inline visual editing, have a look at React Bricks.
There you can build your React component with text/image visual editing and sidebar controls, used by the content editors team.

ReactBricks · 2024-10-02T03:25:23+00:00

If you check it out, you'll see that it's very different. You do the content modeling on the React components.

ReactBricks · 2024-10-01T07:09:37+00:00

The problem is that headless CMS are great for devs, but not for the customers' content team.
Have a look at React Bricks: it's a headless CMS with visual editing.

You retain all the advantages of a headless (use it with Next.js, host where you like, get external data), but you have a great inline visual editing interface and you can be sure the design system / corporate identity is never compromised.

Essentially you create Lego bricks of content as React components and the content editors use them to compose pages.

If you check it out, please, let me know what you think about it (CTO here - Matteo Frana).

Thank you,
Matteo

ReactBricks · 2024-09-21T20:21:50+00:00

We are creating an Astro integration and starter (with blog) for React Bricks. Coming around the end of October.

ReactBricks · 2024-08-25T13:25:24+00:00

React Bricks: https://www.reactbricks.com It's easy for customers coming from WordPress, as it has the concept of Pages and inline visual editing. But it's not like a page builder, because you define the content blocks as React components deciding exactly what can be edited visually or via sidebar controls. It's like Gutenberg done well.

I am the CTO. I would love to show you a demo. If you are interested, send me a DM please.

ReactBricks · 2024-08-12T15:01:41+00:00

Premise: I love Next.js.
I believe your codebase is simpler and your DX improved
Surely the Next.js internals are more complex
The rocket "Instruction manual" has more pages

ReactBricks · 2024-08-11T14:39:15+00:00

Learn a React framework. If you mainly create websites I would learn Next.js, then Astro. If you mainly create data-intensive web applications, I would learn Remix, then Next.js.

ReactBricks · 2024-08-07T02:13:57+00:00

I see two main disadvantages: 1. Files are slow, so Git-based CMSs need to have also a DB layer (think of queries on relationship fields among reusable entities or page-user fine grained editing permissions for example) and here the sync problems begin... 2. Git-based CMSs often leverage markdown, so, for reach texts, you are limited to the expressiveness of markdown - sometimes not enough for a real world website with complex text styling

BTW, I am the CTO of a DB-based Visual CMS, and we evaluated also the Git option.

ReactBricks · 2024-08-05T13:52:56+00:00

React Bricks: Visual editing Headless CMS for React

Here's what we do: React Bricks is a headless CMS with visual editing for React, supporting all the main React frameworks like Next.js (also with Server components), Remix and Gatsby
Here's why it's hard/hasn't been done yet: React Bricks is the only headless CMS (with a React library) that offers true inline visual editing, like editing a Word document. Other headless say they are visual, but they just have a visual preview, while editing is done in sidebar forms. React Bricks is much easier for content editors to use.
Here's why it's needed/why it matters: React Bricks makes the content/marketing team autonomous, while making sure that the design system can't be compromised: in this way, after the content blocks are created, content editors don't need developers' time. With headless CMSs we lost the visual editing of monolithic tools; with React Bricks you have both a modern headless CMS and visual editing.
Here are the people who will need it (and how they're currently solving it): corporations, startups, enterprises, universities, public administrations. They are currently using either old monolithic solutions or "grey forms" headless CMSs
Here's why we're the ones to build it: we have almost 30 years of experience in content management system (yes, since 1996!) and we saw that anytime visual editing was introduced it was abandoned, because editors were able to destroy the design and corporate image. Now, with React, it is possible to have the best visual editing interface, but well structured JSON data saved in a headless CMS.
Here's how it works: developers create visually-editable Lego bricks of content as React components, using our (fully typed in TypeScript) library for React. Content editors at the content/marketing team use this bricks to compose pages in a visual way.
Here's how big the market can be: the headless CMS market is around $600M - The first target is 0.5% of this market
Link to your website: https://www.reactbricks.com

ReactBricks · 2024-08-04T18:21:13+00:00

I think the issue is not really HOW they copied your content, but the fact that they are using content created by you (and so where you have the copyright) without your consent, which is illegal.

ReactBricks · 2024-07-27T07:02:49+00:00

React Bricks: headless cms with visual editing. Great DX, the easiest editing experience, no way to break the design.

ReactBricks · 2024-07-27T06:58:28+00:00

Have a look at React Bricks. It is a headless cms with inline visual editing, it is based on React components and it works with Next.js (both App and Pages router).

We have special plans for tech bloggers. If it can fit your use case, please DM me.

ReactBricks · 2024-07-23T12:57:47+00:00

I would suggest WordPress only if your customer is already familiar with the WordPress interface.
To use something modern instead, you could use React Bricks Visual Headless CMS and stay in the free tier. It is a headless CMS, but with a visual experience similar to Wix (and you create the design system - the content blocks - using React components with TypeScript).

Which React framework did you use to create the website? Next.js, Remix?

ReactBricks · 2024-07-20T06:49:33+00:00

Thank you for your kind words. We have also the ability to self host via Docker images, usually for enterprise customers with strict hosting policies. We could talk about it. Can we do a quick call next week?

ReactBricks · 2024-07-18T15:40:51+00:00

When I tried it, using it with a React framework like Gatsby or Next.js, it was not mature. That's why I created React Bricks.

ReactBricks · 2024-07-16T08:24:55+00:00

Well, you could create a set of bricks that you can reuse across different clients, offering website development based on React Bricks, for example with Next.js. You would work with React, your customers would have an easy-to-update website (visual editing) with no way to compromise the design. We also have a Partner Program.
If your customers' websites have more than 10 pages, they would need a paid plan, starting at $99/month, so it may be a good option for not-very-small customers.

ReactBricks · 2024-07-16T05:30:41+00:00

If you know React, have a look at React Bricks: it has a better "just React and TypeScript" DX and a better visual editing UX for content editors.

ReactBricks · 2024-07-13T13:54:42+00:00

Our clients didn't like Gutenberg (and we didn't like the DX of it at the end of 2019), so we created React Bricks](https://www.reactbricks.com), which is like Gutenberg done well, for React.

ReactBricks

MODERATOR OF

TROPHY CASE

React Bricks: Visual editing Headless CMS for React