While it's not a static site generator, PicoCMS is a PHP-based static site CMS that uses Markdown for content management & Twig templating engine for layout. There is more information here - PicoCMS.
Currently using it on a client's build & it's been super simple to dev for. Hope this helps 😀
is exactly what you want:
But a CMS is not a blog engine by itself. You could extend it for comments, social network integration, timestamps etc.
Wordpress seems a little "overkill" for just creating a few pages to embed grafana graphs in. Maybe something like this might be better: http://picocms.org/
I've had no experience with it, but it seems like it should do the trick and everything is stored in flat files (no databases).
> Next you need a database, MySQL, Postgress, MongoDB, anyone will do.
To be fair, you don't even need a database for them. PicoCMS exists without any sort of database at all, and relies on Markdown files to operate, along with FTP
All I ways saying is that the docs are identical. Look at the docs for URL structure and tell me they aren't copied verbatim. That is all I was wondering. :)
Building your own mini CMS, that gives the user some simple forms to edit page info and so on is always possible, and once done could be reused between projects. BUT unless you really know what you're doing, there's a lot of things to consider, and a lot of things that can go wrong.
It might be better to look into a "micro" CMS, for example Pico CMS and similar, which don't need a database to run. You'll get a lot more freedom with the templates, and there's usually an admin editing plugin that clients could use.
There are a lot of git powered static site generators like https://www.mkdocs.org/, but if you just want a blog platform with markdown syntax, which is similar to Wordpress https://ghost.org/
Both can be self hosted quite easily. For a even more purists cms, you may have a look at http://picocms.org/
I've installed all of these and for my use case, none were satisfactory, but found them interesting as a flat file CMS . Grav was my favorite, but others seem to be decent as well:
In the end, hard to beat WYSIWYG because by the time you add markdown, a curly brace for this, a double curly brace for that, forget what the weirds tabs accomplish and about the time you have it figured out the upgrade introduces YAML. Oh, and it looks stale too because no one creates modern themes any longer.
Now you long for WYSIWYG and good ole WordPress/Drupal
I have! I made a couple off the TP-Link MR3040 which is nice as the internal battery lets you carry it around to events and things or host without power. I started with a pirate box, but soon moved over to making library boxes (fork of pirate box) as they run PHP out of the box, mesh and sync, and are little less in your face than the whole PIRATE thing (which I know you can change).
I've been serving various left and banned epubs/pdfs/mobis and videos. With that said, almost no one has ever connected and I think the UI/UX and connection experience is part of that. The ugly file listing is also a pain to find anything interesting (even if you skin it with better CSS via lighttpd hacks).
Currently looking at repurposing one of those flat file PHP CMS's like Pico to use as an autogenerating library. The way those types of CMS work is that you just upload your markdown files and the engine generates the page, links, and search queries to it on the fly. I figure I can just add some similar code that will take a PDF/ePub/mobi, a markdown file with the same file name and description/tags/author/etc, and an image and autogenerate a page for each book I add (provided I spend a minute writing up the markdown page). This will let you instantly create a searchable, attractive database with full tag taxonomy (author, subject, genre, etc).
Of course I've got tons of other things to finish first, but if any other anarcho-hackers wants to get started on something similar, I think it'd be a great service to the FOSS and anarchist communities.
There are micro-frameworks that are able to parse a layout template and fill it with content that itself comes from an .html file. Or even markdown, if you want to go that route. Example: Pico