react-page VS tinacms

This is really slick! A really fluid and intuitive interface.

We use https://react-page.github.io/ (also MIT licensed) extensively at my startup; it attacks the same problem, and it's been incredibly effective (and hackable!).

Generally speaking, owning your own CMS data, in your own database, with a well-documented JSON data format, and adding the ability to take any React component you've written (that itself may interact with your own data) and make it not only reusable as part of a content editing system but also WYSIWIG, opens up a huge number of opportunities - including adding your own logic to transform content before display.

https://builder.io is another alternative that's very effective at the adapting-custom-components-to-WYSIWIG side of things, but does keep the data in its own cloud storage.

I'm really excited to see innovation in this space, and I'll be following Puck closely!

A few days ago someone posted a link in an answer to a similar library to https://react-page.github.io/.

https://github.com/react-page/react-page is fully open source with a simple JSON data model and multi-language support; we’ve built various utilities for auto-generating content. Invest a few days in customizing CSS and you have a world-class WYSIWYG for your own design language. Highly recommend.

I maintain https://react-page.github.io/

If its just some rich content you want to edit, you can also use https://github.com/react-page/react-page which is a rich content editor, that i am maintaining. You can use it to edit and display content. The data itself can be stored as a json string and can be saved in your api, your firebase or your headless cms. I also tried to pair it with strapi, where I would share ReactPage‘s config and cell plugins both with a nextjs frontend and strapi admin panel. This is extremly powerful and flexible.

I came across react-page[1] the other day, it seemed like a reasonably powerful block editor but was too much for our purpose so I haven't actually used it.

[1]: https://github.com/react-page/react-page

a quick search turned up React Page — can anyone vouch for this or recommend anything else?

> Why is are all static site generators (that I am aware of) are CLI? What prevent simplistic drag and drop GUI/WYSIWYG that generates those clean static files?

Check:

- Tina CMS: https://tina.io/

- Primo CMS: https://primocms.org/

Anyway, you seem to be holding the wrong end of the stick. Static generation is the easy part, what you're looking for is a subset that falls under the CMS umbrella, just search for `CMS+SSG` you'll find a diverse set of solutions.

You can also setup any generic Headless CMS to trigger generation for a static site. Why would someone build a full fledged CMS and limit it to a niche market inside a niche?

Tina CMS, formerly Forestry, is one of the best open source Git-based CMSs in terms of the provided feature set. It covers the basics, such as:

Try tina cms https://tina.io

Currently testing it with Docusaurus for our documentation site.

The next step in building this demo blog application is to set up TinaCMS, an open source headless CMS that supports the Markdown format.

Solutions like CloudCanon or TinaCMS use this approach.

With TinaCMS, all your content changes are committed directly to Git. This enables your team to create a variety of workflows for reviewing and merging content updates. By leaning on GitHub, you can integrate CI/CD into your content workflow.

Check out this license for example: https://github.com/tinacms/tinacms/blob/main/LICENSE

It's an Apache 2.0 license, but with adendums.

Would it be reasonable to say that I could fork their repo for own purposes, and argue in court that I was only familar with Apache 2.0, and not their modified terms?