empty-site VS Publii

here is a barebones project I just created using nsm init .html on my machine using dev version of Nift (there's a few basic improvements to template/page.template and template/head.content from the released version). That hopefully gives a good idea of just how barebones a project can be. .nsm has config files and other stuff users don't really need to worry about (can configure projects through the command line), output is where the site is built to, template is where the template files for pages are stored, and content is where the files specific to building individual pages are stored (though there's nothing stopping one from putting files from either template/content directories in the other. Building a website is as simple as running nift build-updated or nift build-all similar to how you'd run git.

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/