Publii VS tinacms

Those have complicated stacks that likely won't serve the person that can't grasp a CLI SSG.

https://getpublii.com has a simple GUI and is just a directory on your computer (inside the Dropbox directory for crude backup?).

Very nice! It looks a bit like Publii [0], but the editor part is cloud hosted instead of running as an app on your machine.

[0] https://getpublii.com/

Publii is one of the few competent attempts at a desktop CMS app.

https://getpublii.com/

They do a lot of things right.

Most SSGs, or if you want to have it easy: https://getpublii.com/ - generates static sites, can publish to github pages (among others), has themes.

I also consider https://getpublii.com interesting, but I have not yet had any personal experience with it.

I'd like to ask for some help regarding on how to "migrate" my website to my personal storage, more specifically how to do that while having everything made with Publii.

I haven't used it, but Publii[0] might be along the lines of what you're thinking of. I ran across it in a previous HN discussion, and it seems to be static site generator with a pretty user-friendly graphical interface.

[0]: https://getpublii.com/

> 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?