Just checked my email, can confirm they didn't say it was ending... I really didn't notice on the page here but that I cannot guarantee. Many deals are ending tomorrow.
Please, ask AppSumo about this: we are not responsible for AppSumo communications or missing ones. If there is a way you can still buy the deal in some way, they will know how to do. Let me know.
Q: Hi Matteo / team,
Welcome to AppSump and great work with React Bricks!
I've full-stacked to the highest tier, but noticed that the entirety of the plan limits are applied to one 'app' in React Bricks.
I'm thinking I might like to purchase an additional app at License Tier 3. I could probably achieve this by creating another account (although I'm not sure if that's allowed, seen as the the deal is for new customers only).
Alternatively, is there any supported way to purchase an additional app with the same limits? Either right now during the AppSumo deal period, of after the deal has ended as an in-app purchase?
I have purchased another 3 plans, and I am toying with the idea of purchasing a few more. The only snag is I'm not sure how much I love the idea of using 7 different accounts to manage all of these apps.
Is it possible that if I contacted customer service they could consolidate these apps into one account?
Hi J, if, after the purchase of all the plans you can send me (by email) all the APP_IDs and the email of the account you'd like to use, we could migrate those app to that account.
Thank you, Matteo
Q: Hi.
I'm kind of confused.. this is a website builder? Yes? But it doesn't host the website it just builds it and then exports it? Correct? To what? A zip file to be uploaded at my host? And the limitations that exist are really regarding "builds" and nothing to do with visitors? Nope,..,I'm still confused 🤷🏻
A: Hi! React Bricks is 2 things that work together: - A headless CMS - A React library to create visually editable content blocks as React components
So the APIs are hosted by us, but you create a React-based website (with Next.js or Gatsby) and you host it wherever you want (Vercel, Netlify, AWS Amplify...), together with the Admin interface. The website is built using the Next.js or Gatsby build process as a static website. The number of API calls depends only on the number of calls Next or Gatsby do during the builds (and the calls you do to edit content).
Q: Hi, can you please explain how are the API count calculated?
Lets say I have a page where I embedded a section using react-bricks, the section has 10 objects. each time a user visits that page, I'm using 10 API's ? or is there one API usage for the 'section' ?
Also, does the whole page have to be designed using react-bricks, or can I use it to embed certain sections on existing pages? How will objects/APIs work and how do i provision for the design when buying codes?
A: Hi gnilomus, We count the number of API calls. Usually they don’t depend at all on the number of visits to your website, as most of our customers use static site generation (SSG), so our APIs are called only: - At build time (calls to get the content) - When you edit content (calls to get/store the content)
As for Storyblok, we are completely different products: with Storyblok you edit using forms that appear on a sidebar, while with React Bricks you directly edit over the content as in Word or Pages. For content editors this is much easier. You are right that our free plan is quite limited, but we need to create a sustainable business. And with AppSumo you have great one-time Deals! :)
Also, this is marked as alternative to storyblok but the limits in storyblock Free plan (community version) seem to be much more generous than these paid plans.
Can you please explain what makes this paid offering more attractive?
Hi gnilomus, no, maybe I wasn't clear enough. If you create a static website, the number of API calls is completely independent from the visits you receive. For example, if you have a website with 10 pages and you rebuild it once per month, you will have just 10 GET API calls + the calls that you do to edit the content, far from the 10,000 calls you have in the plan. If this websites receives a million visits per day, it will never hit our APIs as the content is statically generated at build time.
The calculation is easy: anytime you call our APIs we count 1, but you call the APIs only when you save the content or re-build the static website, not when your users visit it. This is how SSG works. We have examples of websites with literally millions of visits per month (like casavo.com, the biggest real estate in Italy), which don't generate very high API calls. Everything is "cached" by the static generation.
A: Hi Said_PeakProductivityBooks, unfortunately not. It's very easy to reuse the UI of a website created with React components, like a Next.js or Gatsby website, not an Elementor website, I'm sorry.
A: Hi cientiros, no, that's not a use case for React Bricks. It is like an headless CMS but with visual editing, so that it has a great visual interface for editors, but you control everything in code. It is not meant to export a CRUD application, I'm sorry.
A: Hi David, the APIs are hosted by us, but the front-end website is hosted by you wherever you want. We don't have any "backdoor" in your frontend, but of course you need our APIs to save the content. It's like any other headless CMS. The data are saved on our backend >> the static build on your hosting provider uses the data from our APIs >> the static website is hosted on your hosting provider.
The point of hosting the Admin interface with the frontend project is that this is the only way you can have true visual editing over the content, because both the frontend and the admin interface can import your React content blocks ("bricks").
Q: Can I use React Bricks with Flotiq, a CMS currently on AppSumo?
Can I host my website made by React Bricks, on Netlify?
A: Hi Diane, surely, you can host your website on Netlify, or Vercel or any other provider which runs Node.js for the build process. As for Flotiq, really I think you should choose which platform you prefer to create content. It's true that you can also get data from any headless CMS and use it in React Bricks, but for a new project it's much better to choose just one CMS not to add too much complexity.
A: Hi! We provide a set of pre-made content blocks that you can use and which are open source (React Bricks UI project). Usually you get the most from React Bricks if you create your own blocks (maybe getting inspiration from the pre-made ones), so that you can have your own corporate image. There is no automatic way to import an HTML template: you need to create your content blocks in React code. You can use data from any external data source like Airtable in React Bricks.
A: Hi SumoDavid, you need a NodeJs capable hosting, like Vercel, or a simple static hosting which can run a Node.js build like Netlify. I suggest one of these two services, because: - they integrate with GitHub or BitBucket to rebuild as you push code on the repository - they provide build hook to rebuild from React Bricks when your editors click the "Deploy" button - usually you can stay in the free tier
A: Hi Virally, with React Bricks you host the frontend project wherever you like and, using Next.js or Gatsby you can leverage Static Site Generation (SSG) to create a static website that can be hosted on a simple CDN. React Bricks hosts just the APIs where the content is stored, but than pages are generated by Gatsby or Next.js (if you use getStaticProps). The Next.js or Gatsby site, together with the admin interface, can be hosted by you on a simple web server, a CDN, or a host like Netlify or Vercel.
I'm looking forward to seeing what you create with React Bricks! :)
Hi Virally, no, I mean that a React Bricks project really is a Gatsby, Remix or Next.js project, using the React Bricks library. Gatsby, Remix and Next.js are React Framework to create websites, either using Static site generation (like Gatsby and Next.js) or Server-side rendering (like Remix and Next.js which can do both). So, if you use SSG with Gatsby or Next.js you are generating a static site, but the generation process calls the React Bricks APIs to generate all the pages. So you need React Bricks to edit the content and generate the static site. Anyway, this has nothing to do with limits: you have limits on React Bricks CMS APIs. If you have 300 pages, you can just create 300 pages. I suggest you to purchase the deal, start the CLI (npx create-reactbricks-app) and see how it works: you have 30 days to request a refund if it's not what you need. In this way you will see that when you scaffold a project with the CLI you will choose the React framework and you will have a complete project set up for you, ready with static site generation.
Do you only host the APIs and thats it? I thought I read in another question that you host images and videos also. And if you do host the images, videos etc, and we're already using a headless CMS, then what would get stored on netlify?
We host the content through our APIs and also the assets that are uploaded using our <Image> and <File> components. Why do you need another headless CMS, instead of just using React Bricks?
Thank you, Matteo
Q: Does it support filtering, or even advanced filtering?
e.g. I'd like to filter blog posts by category, author, topics and other attributes simultaneously.
A: Hi Gaspard, 40,000 API calls means that the number of calls to our HTTP REST APIs during one month must be below 40,000. Every time you GET the content of a page or SAVE a page you trigger an API call. If you use Static Site Generation you will trigger API calls just at build time (1 for each page every time you rebuild) and when you edit content, so it is very difficult to reach that limit.
500 MB of disc space is the space you have to save images (we count the space on our backend server, not the space on the CDN - which means you have 500 MB on our server + 500 MB on the global CDN).
50 GB of bandwidth means that the CDN bandwidth you have in one month must be less than 50 GB. For example, if you have 100 images of 50 KB each (5 MB total) you can have them downloaded 10.000 times each.
On the lifetime deals the limits are hard limits, so when you reach them you should upgrade to another plan. Really I think it's very unlikely that you will reach them unless you have a very high traffic website.
A: Dear CluelessClay, thank you for your question. I don't know TeleportHQ well. From what I can see on TeleportHQ websites, it seems more a tool like WebFlow: in particular, I think your editors will be able to change margins, paddings, text size etc. using the sidebar menus. With React Bricks the sidebar controls are just the ones that you define in code, so, if font size for a content block should not be changed by content editors (because it's part of the design system), they will not have the possibility to change it.
Another difference is that they host the website and set limits on bandwidth, so that, if you site has success, you need to pay more. With React Bricks you host the website yourself wherever you like, while we just host the content data and the images (on a global CDN).
A: You can start your blog right now with the Tier 3. I think it will take you some time to reach 300 articles for your blog. When you reach 300 articles you should consider a React Bricks monthly plan instead of the lifetime deal to overcome the (already high) limit.
Q: I plan to use Swell, which is a headless ecommerce CMS (backend).
I need a frontend, and they recommend builder.io, but I saw this and I'm interested.
Would ReactBricks work as a page builder and editor for Swell? I ask because you call this a headless CMS, but I already have a backend headless CMS, so I find that a little confusing.
My second question is, regarding your blog function. I saw your blog video on youtube and it looks great. However, Swell doesn't support a blog in their CMS. Would I be able to use Swell as the backend ecommerce CMS, but then also use ReactBricks blog functionality, all in the same site?
A: Dear platt80, there is no Swell starter ready for React Bricks. I think the best thing would be to create the store with Next.js and Swell and then add React Bricks just for the products' landing page editing. This will be much simpler in a couple of months when we'll create a new way to add easily React Bricks to an existing project, thinking in particular of React e-commerce stores created with a headless e-commerce like Swell or Shopify. Meanwhile you could create your store using React. I don't know what you would have already done for you in the Builder.io starter: maybe you could also try it to see if it has already everything you need and saves you the dev time to create the frontend.
A: Hi! Stories are another thing: they are cookie-cutter props for content blocks. Suppose you have a hero unit block. You can edit it to have a certain text and background color and save it as a story. In another page you can then create another identical block, but story are not single source of truth: if you change the content in a page, it doesn't change everywhere.
For an e-commerce you can create a pageType "product" and create pages inside this pageType. We are publishing today v3.3.0 where you can also define that a pageType is more an abstract entity than a page (for example "category") and you can create a relationship custom field "category" on the product that maps to the category entities.
When you set up a project for the e-commerce (I suggest choosing Next.js for this use case) I am happy to have a call with you to do a custom demo.
Q: I've been watching your tutorials and trying to figure out how the content created in your CMS (once the ...
content editors have completed doing that) can be consumed by a frontend developer to build a NextJS site. Do you have any documentation on this? Your starter tutorials do not cover this part at the moment. Is there a REST API that a frontend developer can use your CMS to pull content onto the frontend (aka data fetching). For instance, in Strapi, you've created a schema and then add content in a "Collection". Then a frontend developer would use the Strapi APIs to fetch the data and render onto the frontend. How would you do this with React Bricks CMS?
A: Hi! with React Bricks you have helper functions to call our APIs, so that you don't have to call them yourselves. In particular, you find in the documentation the `fetchPages` and `fetchPage` methods. I suggest that you try React Bricks and scaffold a Next.js project using the CLI: npx create-reactbricks-app@latest So that you see the structure of the starter project and how it works.
Im aiming for Tier 3, but wanted to ask one question first.
For my future website im willing to import React design blocks from https://saasblocks.app/ to React Bricks via JS code import. I assume thats possible with your app.
For CSS they use Tailwind. But besides Tailwind CSS they also use some custom CSS for the colors of their blocks.
Will i be able to import this custom CSS config file into React Bricks somehow so everything works smoothly?
A: Hi Anton, yes, you can use any HTML/CSS block and turn into a React component, adding the React Bricks wysiwyg components where you want the texts and images to be directly editable and setting the `schema` property to define the sidebar controls you could need to let users change things like the background color. React Bricks works with any CSS framework.
A: Hi Cientiros, React Bricks and Divjoy are two completely different products: Divjoy creates React code for you for different needs you may have (CSS framework, integrations, template). React Bricks instead is a CMS where you create content blocks in React, but then you can invite editors who use these content block to compose pages, whose content is saved on our APIs (like a headless) while you can host the frontend wherever you want. It may seem similar because also React Bricks scaffolds a React project, but it is a React project connected with our CMS APIs, so that you can invite editors that can enter the admin and manage the content using a no-code tool, but based on the pixel-perfect design you (or your developers) can create, with the ability to change just what you decide that can be changed. DivJoy is like a shortcut to create a React project. React Bricks is like a headless CMS but with visual editing powered by React components.
Q: Was deciding about buying T3 or not but the sale ended without notice?
Matteo_ReactBricks
May 14, 2024A: Hi PUAV,
I think the end of the sale was scheduled by AppSumo and announced in some way.
Could you please contact the AppSumo support?
Thank you,
Matteo
Share React Bricks
Hello Matteo,
Just checked my email, can confirm they didn't say it was ending... I really didn't notice on the page here but that I cannot guarantee. Many deals are ending tomorrow.
I can confirm you that ther was no notice about it :(
I would like to try it and buy it... how can I do? PLEASE
Verified purchaser
Please, ask AppSumo about this: we are not responsible for AppSumo communications or missing ones.
If there is a way you can still buy the deal in some way, they will know how to do.
Let me know.
Q: Hi Matteo / team, Welcome to AppSump and great work with React Bricks!
I've full-stacked to the highest tier, but noticed that the entirety of the plan limits are applied to one 'app' in React Bricks.
I'm thinking I might like to purchase an additional app at License Tier 3. I could probably achieve this by creating another account (although I'm not sure if that's allowed, seen as the the deal is for new customers only).
Alternatively, is there any supported way to purchase an additional app with the same limits? Either right now during the AppSumo deal period, of after the deal has ended as an in-app purchase?
Thanks,
J
Matteo_ReactBricks
May 14, 2024A: Hi J,
you can purchase a new deal with the same account, but when you activate it on our side, you need to provide a new e-mail address.
BTW, thank you for the great review! 😍
Share React Bricks
Verified purchaser
Hi Matteo!
I have purchased another 3 plans, and I am toying with the idea of purchasing a few more. The only snag is I'm not sure how much I love the idea of using 7 different accounts to manage all of these apps.
Is it possible that if I contacted customer service they could consolidate these apps into one account?
Thanks,
J
Verified purchaser
Hi J,
if, after the purchase of all the plans you can send me (by email) all the APP_IDs and the email of the account you'd like to use, we could migrate those app to that account.
Thank you,
Matteo
Q: Hi.
I'm kind of confused.. this is a website builder? Yes? But it doesn't host the website it just builds it and then exports it? Correct? To what? A zip file to be uploaded at my host? And the limitations that exist are really regarding "builds" and nothing to do with visitors? Nope,..,I'm still confused 🤷🏻
Matteo_ReactBricks
May 14, 2024A: Hi!
React Bricks is 2 things that work together:
- A headless CMS
- A React library to create visually editable content blocks as React components
So the APIs are hosted by us, but you create a React-based website (with Next.js or Gatsby) and you host it wherever you want (Vercel, Netlify, AWS Amplify...), together with the Admin interface.
The website is built using the Next.js or Gatsby build process as a static website.
The number of API calls depends only on the number of calls Next or Gatsby do during the builds (and the calls you do to edit content).
Share React Bricks
Q: Hi, can you please explain how are the API count calculated?
Lets say I have a page where I embedded a section using react-bricks, the section has 10 objects. each time a user visits that page, I'm using 10 API's ? or is there one API usage for the 'section' ?
Also, does the whole page have to be designed using react-bricks, or can I use it to embed certain sections on existing pages? How will objects/APIs work and how do i provision for the design when buying codes?
Matteo_ReactBricks
May 14, 2024A: Hi gnilomus,
We count the number of API calls.
Usually they don’t depend at all on the number of visits to your website, as most of our customers use static site generation (SSG), so our APIs are called only:
- At build time (calls to get the content)
- When you edit content (calls to get/store the content)
As for Storyblok, we are completely different products: with Storyblok you edit using forms that appear on a sidebar, while with React Bricks you directly edit over the content as in Word or Pages. For content editors this is much easier.
You are right that our free plan is quite limited, but we need to create a sustainable business. And with AppSumo you have great one-time Deals! :)
Share React Bricks
Also, this is marked as alternative to storyblok but the limits in storyblock Free plan (community version) seem to be much more generous than these paid plans.
Can you please explain what makes this paid offering more attractive?
Verified purchaser
Hi gnilomus,
no, maybe I wasn't clear enough.
If you create a static website, the number of API calls is completely independent from the visits you receive.
For example, if you have a website with 10 pages and you rebuild it once per month, you will have just 10 GET API calls + the calls that you do to edit the content, far from the 10,000 calls you have in the plan.
If this websites receives a million visits per day, it will never hit our APIs as the content is statically generated at build time.
The calculation is easy: anytime you call our APIs we count 1, but you call the APIs only when you save the content or re-build the static website, not when your users visit it. This is how SSG works.
We have examples of websites with literally millions of visits per month (like casavo.com, the biggest real estate in Italy), which don't generate very high API calls. Everything is "cached" by the static generation.
so if i'm in plan 1
and design 5 sections of my site using react-bricks (which is a low estimation)
A user comes and loads those 5 sections, ie uses 5 API calls.
So, I can only serve 2000 users a month?
That seems very low limits.
If thats not how it works, Are there some docs with calculation examples?
Thanks
Q: Hi Matteo, Is there a possibility to convert a WordPress site (built with elementor) into ReactBrick without having to redo from scratch?
Especially the UI portion.
Thanks.
Matteo_ReactBricks
May 14, 2024A: Hi Said_PeakProductivityBooks,
unfortunately not. It's very easy to reuse the UI of a website created with React components, like a Next.js or Gatsby website, not an Elementor website, I'm sorry.
Matteo
Share React Bricks
I see. Thanks Matteo. I will give ReactBrick a try.
Q: Can I export React to a working CRUD app with server endpoints and react-query for fetching/caching data on the client-side?
Matteo_ReactBricks
May 14, 2024A: Hi cientiros,
no, that's not a use case for React Bricks.
It is like an headless CMS but with visual editing, so that it has a great visual interface for editors, but you control everything in code. It is not meant to export a CRUD application, I'm sorry.
Share React Bricks
Q: You said we can host the website and the admin interface wherever we want.
Is this for real? 100% hosted or are there some for of backdoors in the system where you still have access to our system?
Or are we in some way still dependent on you even after doing this?
Matteo_ReactBricks
May 14, 2024A: Hi David,
the APIs are hosted by us, but the front-end website is hosted by you wherever you want. We don't have any "backdoor" in your frontend, but of course you need our APIs to save the content. It's like any other headless CMS. The data are saved on our backend >> the static build on your hosting provider uses the data from our APIs >> the static website is hosted on your hosting provider.
I hope it is more clear now.
Matteo
Share React Bricks
So what's the point of hosting the admin interface on our servers?
Verified purchaser
The point of hosting the Admin interface with the frontend project is that this is the only way you can have true visual editing over the content, because both the frontend and the admin interface can import your React content blocks ("bricks").
Q: Can I use React Bricks with Flotiq, a CMS currently on AppSumo?
Can I host my website made by React Bricks, on Netlify?
Best,
Diane
Matteo_ReactBricks
May 14, 2024A: Hi Diane,
surely, you can host your website on Netlify, or Vercel or any other provider which runs Node.js for the build process.
As for Flotiq, really I think you should choose which platform you prefer to create content. It's true that you can also get data from any headless CMS and use it in React Bricks, but for a new project it's much better to choose just one CMS not to add too much complexity.
Share React Bricks
Q: Does this come with any templates, or does a user have to start from scratch with a blank canvas?
Is there a feature to import html templates?
Is there a way to dynamically create pages from Airtable data, similar to how softr.io and duda work?
Matteo_ReactBricks
May 14, 2024A: Hi!
We provide a set of pre-made content blocks that you can use and which are open source (React Bricks UI project).
Usually you get the most from React Bricks if you create your own blocks (maybe getting inspiration from the pre-made ones), so that you can have your own corporate image.
There is no automatic way to import an HTML template: you need to create your content blocks in React code.
You can use data from any external data source like Airtable in React Bricks.
Matteo
Share React Bricks
Q: Another question, can we host this on a normal shared hosting providing.
You know, the typical hosting that has PHP, Python etc but not really a dedicated server.
Matteo_ReactBricks
May 14, 2024A: Hi SumoDavid,
you need a NodeJs capable hosting, like Vercel, or a simple static hosting which can run a Node.js build like Netlify. I suggest one of these two services, because:
- they integrate with GitHub or BitBucket to rebuild as you push code on the repository
- they provide build hook to rebuild from React Bricks when your editors click the "Deploy" button
- usually you can stay in the free tier
Thank you,
Matteo
Share React Bricks
Q: Is it possible to export landing pages as static files that I create using ReactBricks and host it on my own server?
Matteo_ReactBricks
May 14, 2024A: Hi Virally,
with React Bricks you host the frontend project wherever you like and, using Next.js or Gatsby you can leverage Static Site Generation (SSG) to create a static website that can be hosted on a simple CDN.
React Bricks hosts just the APIs where the content is stored, but than pages are generated by Gatsby or Next.js (if you use getStaticProps).
The Next.js or Gatsby site, together with the admin interface, can be hosted by you on a simple web server, a CDN, or a host like Netlify or Vercel.
I'm looking forward to seeing what you create with React Bricks! :)
Share React Bricks
So you mean, we can build templates/themes pages which we can export and use them with Remix and Gatsby CMS?
Verified purchaser
Hi Virally,
no, I mean that a React Bricks project really is a Gatsby, Remix or Next.js project, using the React Bricks library.
Gatsby, Remix and Next.js are React Framework to create websites, either using Static site generation (like Gatsby and Next.js) or Server-side rendering (like Remix and Next.js which can do both).
So, if you use SSG with Gatsby or Next.js you are generating a static site, but the generation process calls the React Bricks APIs to generate all the pages. So you need React Bricks to edit the content and generate the static site. Anyway, this has nothing to do with limits: you have limits on React Bricks CMS APIs. If you have 300 pages, you can just create 300 pages.
I suggest you to purchase the deal, start the CLI (npx create-reactbricks-app) and see how it works: you have 30 days to request a refund if it's not what you need.
In this way you will see that when you scaffold a project with the CLI you will choose the React framework and you will have a complete project set up for you, ready with static site generation.
Verified purchaser
Do you only host the APIs and thats it? I thought I read in another question that you host images and videos also. And if you do host the images, videos etc, and we're already using a headless CMS, then what would get stored on netlify?
I'm referring to static site by the way.
Verified purchaser
We host the content through our APIs and also the assets that are uploaded using our <Image> and <File> components.
Why do you need another headless CMS, instead of just using React Bricks?
Thank you,
Matteo
Q: Does it support filtering, or even advanced filtering?
e.g. I'd like to filter blog posts by category, author, topics and other attributes simultaneously.
Matteo_ReactBricks
May 14, 2024A: Hi ah_quan,
you can filter pages by pageType, tags, language and any custom field. The condition are in logical AND.
Thank you,
Matteo
Share React Bricks
Q: Hello, is it possible to have more explanations on what exactly are these points : 40,000 API calls per ...
month
500 MB total disk space for assets
50 GB of bandwidth per account
and what happen after reaching the limit ?
thanks 🙏
Matteo_ReactBricks
May 14, 2024A: Hi Gaspard,
40,000 API calls means that the number of calls to our HTTP REST APIs during one month must be below 40,000. Every time you GET the content of a page or SAVE a page you trigger an API call. If you use Static Site Generation you will trigger API calls just at build time (1 for each page every time you rebuild) and when you edit content, so it is very difficult to reach that limit.
500 MB of disc space is the space you have to save images (we count the space on our backend server, not the space on the CDN - which means you have 500 MB on our server + 500 MB on the global CDN).
50 GB of bandwidth means that the CDN bandwidth you have in one month must be less than 50 GB. For example, if you have 100 images of 50 KB each (5 MB total) you can have them downloaded 10.000 times each.
On the lifetime deals the limits are hard limits, so when you reach them you should upgrade to another plan. Really I think it's very unlikely that you will reach them unless you have a very high traffic website.
Share React Bricks
Q: How would you compare ReactBricks with a similar saas currently on appsumo, TeleportHQ ?
Matteo_ReactBricks
May 14, 2024A: Dear CluelessClay,
thank you for your question. I don't know TeleportHQ well.
From what I can see on TeleportHQ websites, it seems more a tool like WebFlow: in particular, I think your editors will be able to change margins, paddings, text size etc. using the sidebar menus.
With React Bricks the sidebar controls are just the ones that you define in code, so, if font size for a content block should not be changed by content editors (because it's part of the design system), they will not have the possibility to change it.
Another difference is that they host the website and set limits on bandwidth, so that, if you site has success, you need to pay more.
With React Bricks you host the website yourself wherever you like, while we just host the content data and the images (on a global CDN).
Share React Bricks
Q: Can I use React Bricks to build a large blog site with 500 pages, as the highest tier is capped at 300?
Matteo_ReactBricks
May 14, 2024A: You can start your blog right now with the Tier 3. I think it will take you some time to reach 300 articles for your blog.
When you reach 300 articles you should consider a React Bricks monthly plan instead of the lifetime deal to overcome the (already high) limit.
Share React Bricks
Q: I plan to use Swell, which is a headless ecommerce CMS (backend).
I need a frontend, and they recommend builder.io, but I saw this and I'm interested.
Would ReactBricks work as a page builder and editor for Swell? I ask because you call this a headless CMS, but I already have a backend headless CMS, so I find that a little confusing.
My second question is, regarding your blog function. I saw your blog video on youtube and it looks great. However, Swell doesn't support a blog in their CMS. Would I be able to use Swell as the backend ecommerce CMS, but then also use ReactBricks blog functionality, all in the same site?
Matteo_ReactBricks
May 14, 2024A: Dear platt80,
there is no Swell starter ready for React Bricks.
I think the best thing would be to create the store with Next.js and Swell and then add React Bricks just for the products' landing page editing.
This will be much simpler in a couple of months when we'll create a new way to add easily React Bricks to an existing project, thinking in particular of React e-commerce stores created with a headless e-commerce like Swell or Shopify.
Meanwhile you could create your store using React. I don't know what you would have already done for you in the Builder.io starter: maybe you could also try it to see if it has already everything you need and saves you the dev time to create the frontend.
Share React Bricks
Q: If using this for eCommerce, can things like products or collections be saved as Stories so they can easily be pulled into a page?
Or are stories for a different function?
Matteo_ReactBricks
May 14, 2024A: Hi!
Stories are another thing: they are cookie-cutter props for content blocks.
Suppose you have a hero unit block. You can edit it to have a certain text and background color and save it as a story. In another page you can then create another identical block, but story are not single source of truth: if you change the content in a page, it doesn't change everywhere.
For an e-commerce you can create a pageType "product" and create pages inside this pageType. We are publishing today v3.3.0 where you can also define that a pageType is more an abstract entity than a page (for example "category") and you can create a relationship custom field "category" on the product that maps to the category entities.
When you set up a project for the e-commerce (I suggest choosing Next.js for this use case) I am happy to have a call with you to do a custom demo.
Thank you,
Matteo
Share React Bricks
Q: I've been watching your tutorials and trying to figure out how the content created in your CMS (once the ...
content editors have completed doing that) can be consumed by a frontend developer to build a NextJS site. Do you have any documentation on this? Your starter tutorials do not cover this part at the moment. Is there a REST API that a frontend developer can use your CMS to pull content onto the frontend (aka data fetching). For instance, in Strapi, you've created a schema and then add content in a "Collection". Then a frontend developer would use the Strapi APIs to fetch the data and render onto the frontend. How would you do this with React Bricks CMS?
Matteo_ReactBricks
May 14, 2024A: Hi!
with React Bricks you have helper functions to call our APIs, so that you don't have to call them yourselves. In particular, you find in the documentation the `fetchPages` and `fetchPage` methods.
I suggest that you try React Bricks and scaffold a Next.js project using the CLI:
npx create-reactbricks-app@latest
So that you see the structure of the starter project and how it works.
Thank you!
Matteo
Share React Bricks
Q: Hello!
Im aiming for Tier 3, but wanted to ask one question first.
For my future website im willing to import React design blocks from https://saasblocks.app/ to React Bricks via JS code import. I assume thats possible with your app.
For CSS they use Tailwind. But besides Tailwind CSS they also use some custom CSS for the colors of their blocks.
Will i be able to import this custom CSS config file into React Bricks somehow so everything works smoothly?
Thanks.
Matteo_ReactBricks
May 14, 2024A: Hi Anton,
yes, you can use any HTML/CSS block and turn into a React component, adding the React Bricks wysiwyg components where you want the texts and images to be directly editable and setting the `schema` property to define the sidebar controls you could need to let users change things like the background color.
React Bricks works with any CSS framework.
Thank you,
Matteo
Share React Bricks
Q: How is this different from Divjoy?
Matteo_ReactBricks
May 14, 2024A: Hi Cientiros,
React Bricks and Divjoy are two completely different products: Divjoy creates React code for you for different needs you may have (CSS framework, integrations, template).
React Bricks instead is a CMS where you create content blocks in React, but then you can invite editors who use these content block to compose pages, whose content is saved on our APIs (like a headless) while you can host the frontend wherever you want.
It may seem similar because also React Bricks scaffolds a React project, but it is a React project connected with our CMS APIs, so that you can invite editors that can enter the admin and manage the content using a no-code tool, but based on the pixel-perfect design you (or your developers) can create, with the ability to change just what you decide that can be changed.
DivJoy is like a shortcut to create a React project.
React Bricks is like a headless CMS but with visual editing powered by React components.
I hope this is more clear now :)
Share React Bricks