Mezzanine is a CMS
Seeing as it's not well maintained (hypothetical vulnerability in old Django it uses, outdated Bootstrap) and especially that all users of the backend of the site are developers, I wonder if it's even worth having a CMS? For me, it seems like it would be easier to plop a Markdown file in `page_contents`, add it to a site map or whatever and then commit to Git.
Then we have to implement much more ourselves like the menu, the dynamically created sitemap (`/sitemap.xml`) and more. At some point, I checked available static site generators but I didn't find a single one which was usable. So I went the way with Mezzanine which is an awesome and simple CMS, IMO. Furthermore, I consider the currently outdated state as tolerable and I assume development will continue at some point in the future.
Do no touch any of the markdown to include HTML, please.
So how would one make the individual pages look less like they're rendered from a text file (ie. more "designed" like the home page)? To give a concrete example, I was thinking of putting each of the mailing lists in cards in a grid, each with a little search form (to send [a search query to the archives](https://www.mail-archive.com/search?q=version&l=users%40lists.geany.org)), a "subscribe" button, and maybe and icon representing each list in the card.
This is not possible currently, except putting HTML into the Markdown text. Given the fact that there was not much interest in the website in the last years and that we like to focus more on Geany itself (obviously and what is good) I thought to keep maintaing the website content as easy as possible and Markdown is something each of us can write easily. So it seemed meaningful to me to have as much as possible of the page contents as Markdown.
After all, if we want to change the backend of the website and/or replace it by something static or generated, let's do.