Lektor VS zim-desktop-wiki

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/

I'll slightly modify your argument; because Pure HTML does suck:

Why don't people make static sites with a simple "Markdown-or-Similar to HTML" converter, CSS, and vanilla JS...etc?

(This is what I do, btw -- http://zim-wiki.org + a template)

You should add Zim [1] to the "Personal Knowledge Management" section :)

[1] https://zim-wiki.org

https://meyerweb.com/eric/tools/s5/

And I just tweaked the CSS and added a bit of logic to included the possibility of one image per slide; as well as editing slides not with raw HTML but with https://zim-wiki.org (because that's what I'm really used to, I'm sure any Markdown thing would work just as well).

Absolutely; recently I realize I wish I'd never learned vim. I use too many other programs that are at least CUA-ish ( http://zim-wiki.org is the most important app I use ) and now I kind of want out. I haven't yet tried Modeless Vim, but that looks like my next experiment.

https://github.com/SebastianMuskalla/ModelessVim

It is so hard not to feel REALLY SMUG reading stuff like this, as someone who has run my own website as the working primary source for my college instruction for the past 15 years or so using https://zim-wiki.org. (before Markdown was much of a thing!)

It's borderline bizarre to have watched this method of doing things kind of die out, and then also come back in the form of "static site generators" -- which, frankly, are still way clunkier than this.

Write in Zim, export to html, rsync to site. Easy.

FWIW, I've been using http://zim-wiki.org for YEARS. (Sites a little messy and I need to clean it up, but it's extremely functional,) I host my college classes websites from it, to the point that I forced myself to learn the Canvas API, to just clone the page from this site to the front page of Canvas and change the links so they come back here.

jrm4.com