Publii VS Lektor

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/

Guess I'm one of the annoying users who complained when armin's Lektor (https://github.com/lektor/lektor) started going dormant back when, but I loved it for a while. I'm on Astro now, but a big thanks for helping a younger version for me.

Lektor is a modern and flexible static content management system that utilizes Python as its core language. It comes with an intuitive web-based admin interface, making it easy for content creators to manage and update the site. Lektor supports a variety of content types and has an active community that contributes to its continuous improvement.

Lektor CMS is sort of a prototype-ish thing doing this: https://www.getlektor.com/

It has (used to have? Can't find them on the site now) pre-packaged binaries that you would drop into a folder structure generated by the technically-minded person, and the content editor can simply click on that binary, which opens the backend of the CMS in the web browser, make changes and click deploy.

There have been several Flask-based CMS's but I don't remember most of them. IIRC Lektor is based on Flask.

Static hosting could be enough for many sites and one could combine the technical and UX advantages of your dynamic interface with the advantages of static sites for security and distribution.

I found that useful when i worked with https://www.getlektor.com/ years ago. In lektor the dynamic part runs on a users desktop machine, but it of course wouldn't need to.

Lektor is Python based and Just Works, but it is far off the beaten track… https://www.getlektor.com/