firecms VS react-static

FireCMS is a free, open-source headless CMS based on Firebase, that both developers and content manager will love 🚀 #firebase #cms #content

firecms

May I introduce to you firecms.co

Been looking into fireCms.co an extendable gui for interacting with firebase Firestone and storage .

I like FireCMS. It requires a little bit of customization but it's very flexible.

We run firecms.co which is a React and Firebase-based CMS.

However, you can use Firebase for free. Firebase is a BaaS and offers a pretty generous free tier for hosting, database, etc. There are a few CMS options for Firebase. For my current portfolio, I use FireCMS to manage all the content on my site. After the content is updated in FireCMS, my frontend will retrieve the new data making it super easy to publish new content.

A quick google found me this: https://firecms.co/

You are now encouraged to make all your suggestions and ask questions in the Github discussion tab of the project: https://github.com/Camberi/firecms since it is more appropriate

React Static

Can you elaborate on why? What is the difference to Gatsby? Also, is the project still alive? Looking at the commit history, there doesn't seem to be that much going on since 2,5 years https://github.com/react-static/react-static/graphs/code-frequency

Django is still my go-to. Specifically [Django-REST-Framework](https://www.django-rest-framework.org/) with a front-end written with [react-static](https://github.com/react-static/react-static).

Django's ORM is so nice and the ecosystem around it rocks.

Its biggest downside is painful upgrades. They don't really follow [semantic versioning](https://semver.org/)

I still like react-static. Minimalism on react:

https://github.com/react-static/react-static

Link : https://github.com/react-static/react-static

react-static (https://github.com/react-static/react-static) is both good and enough. You don't need Gatsby/Next or anything else.