3 ms·
I was thinking of how to setup a simple static blog without the baggage of a full-blow framework. Of course, I'd be re-inventing the wheel, but at least it'll m
by pradn 2y ago
I was thinking of how to setup a simple static blog without the baggage of a full-blow framework. Of course, I'd be re-inventing the wheel, but at least it'll make sense to me, personally.
What I came up with:
* Each page gets its own folder.
* An optional METADATA file in each folder has stuff like the type of the page (blog post, photo gallery, code listing).
* The index file can be in Markdown or rST or something. I'd just branch to a different parser based on the file name suffix.
This is simple and lets me evolve the blog over time.
For a personal blog, an ideal mix might be just branching to a different HTML converter based on the
- vunderba 2y agoI have a customized version of pelican which is a python based static side generator. It basically supports this type of structure, except that in place of a physical separate meta-data file all the metadata goes in the front matter section at the top of the markdown file, and it gets stripped out of the actual rendered HTML.
- pradn 2y agoThat makes sense. The only reason to separate the metadata out is to avoid having to parse the main content files for front-matter. Plus the metadata files themselves could be in several formats, if necessary. I don't see a great need for that, however.
- lmm 2y agoHugo/Jekyll/etc. all work the way GP described too.