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! :)
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