Publii limitations (as of 0.38.1)

Publii editor

Very Basic editor

We’re going to use Publii to migrate to Static Sites from WordPress, the functionality and feel of the post editors are very lacking. Only the basic stuff is in, thankfully I can put posts in as HTML to get around most of the issues.
Really to make me happy to use it, it needs more features. Either caught up to current TinyMCE levels or how WordPress’s post editor is.
The Block editor is not much better and lacks even more.

Does not like using Network drives

I have folders and folders of stock images for blogs on my network drive/NAS, and Publii really does not like to pull them into the app.
adding them in the post editor (TinyMCE area), it’ll upload/link it in it’ll work.
Adding the network drive as a mapped drive seems to help it, so the app must be trying to link it in.
Also, while the app itself can see and import files with uppercase letters in its name, the copying/processing system it uses doesn’t seem to cope with them.

No Media Library

There is no system to show you that you’ve already used that image, or whether its available already on your site structure. This might be due to the way each posts handles its own images rather than a source folder for all images. I’ve also found a bug converting a clients site where particular images are deleted on each render on a specific post.

Lack of class settings on elements

Again, both the WYSIWYG and Block Editors are basic compared to WordPress’s old one and Gutenberg. When writing HTML elements (which the majority of it is going to be) there is no way of setting classes easily from Editor, unless you get into HTML mode, which is another mess.

Lack of layout tools

Despite what I just said about classes, Publii seems to imply that layouts and extra columns can be controlled via extra options programmed in to set up elements with classes when selected. I don’t really agree with this, but it has given me some ideas on how to get around some of the issues.

So what is good about Publii

Well, with no online dashboarding or logins. It means those 50,000 bots who hit my sites daily won’t get anywhere. Not that they got anywhere anyway except noted in log files. The bots expecting some PHP responses or files which they can interact with will get nothing. I can even set up repeat offenders to be stuck in loops and get even more broken.

Why not something node based like Gatsby? Jekyll? Hugo? etc

I tried a deployment of Gatsby on local dev, and it only worked once and then complained about a module that is only available on Mac/UNIX installs.
Eleven.ty wasn’t much better.
These frameworks appear to need to be running to serve the site. therefore tying up more resources. Then if it crashes, it’ll be down until I cross at least 3 2fa’s to log in and start it again. Whereas Publii creates all the HTML, checks for linking and tags and formats it in the client and uploads to the server.