I keep trying to return to Zola but it seems I have to do much of the work there myself. It's kind of the other end of the spectrum for me: too much freedom! I wouldn't mind some convention-over-configuration there. Also the templating language isn't at all intuitive to me but it might be just me being stupid. But I also want multi-lingual articles and article revisions so maybe Zola is not for me. I absolutely love…
> I wouldn't mind some convention-over-configuration there. I strongly agree. I started some of that with my theme https://tildegit.org/southerntofu/zola-water and i'd be pleased to cooperate on "standard" conventions across themes so we can swap themes easily without having to reconfigure/reorganize everything. > But I also want multi-lingual articles and article revisions so maybe Zola is not for me. zola supports…
> Linking across revisions, as it is not supported by zola would require either an external component (eg. in an iframe) or a build script that rewrites output pages to be aware of their revisions.
Ah, I mean something much simpler than that. Imagine having a combo box at the top of the article, named "Versions" (or "Revisions") that has the value of "latest (2020-02-28)" at the top and currently selected and then has all others just as dates below. When you choose one, the page loads another HTML file. Extremely simple vanilla JS, likely 5-10 lines.
Or you can just have a limited list (say the last 5 revisions) with direct links -- again before the content starts. Clicking those would not even need any JS at all. It would be a plain old 2020-01-31 markup.
And if an article has no revisions (only has been written once) then the needs for such a combo-box or list of links disappears and they should just not be rendered at the article's page at all.