A React Bricks application, being it a Next.js, Remix, or Gatsby project, consists of:
The code for an app resides in your repository, and we never have access to your code.
The React Bricks library, operating within your project, fetches the JSON content for each page from the React Bricks APIs. Each page's content consists of an array of blocks, each with their type and properties. The library renders the appropriate React component for each content block, providing it with all the required properties from the APIs.
React Bricks is highly optimized. The code related to visual editing is never included in the front-end bundle. Therefore, React Bricks has minimal or no impact on the native performance of the underlying React frameworks, whether it's Next.js, Remix, or Gatsby.
For enhanced performance, React Bricks was the first visual headless CMS to support React Server Components with the Next.js App Router.
React Bricks is designed to provide developers with flexibility.
For example, you can create custom sidebar controls, develop custom rich-text plugins, define custom fields on pages, and use content from external APIs. It also allows you to use any CSS framework and host the front-end website wherever you prefer.
You can have a custom CDN domain for assets, customize user roles, and more. Learn more about React Bricks flexibility.
React Bricks stands out as the top CMS for React Developers . It leverages React and TypeScript expertise, it makes content editors autonomous, and offers excellent learning resources. It is easy to start using the CLI and offers great flexibility.
For content editors, it provides all necessary features such as Localization, Scheduled Publishing, Digital Asset Management, SEO, Collaboration, Image Optimization, and more.
As an enterprise-grade solution, it includes Content Versioning, Approval Workflows, Custom Roles, Single Sign-On (SSO), Multiple Environments, Fine-Grained Permissions, Scheduled Backups, and the ability to self-host the backend.