I'm a big fan of Jekyll. I've been using it for ~5 years and just made a new site with it recently so I would still use it today.
I currently use it for:
- My personal blog with 250+ posts and tons of pages[0]
- A podcast platform[1] which is open source[2]
- The landing pages for all of my web development courses (not going to bother linking them since I don't want to seem like I'm fishing HN for sales)
I also recently wrote about my whole site's tech stack here[3]. That post might not fully apply to you since you want to host it on S3. I personally self host everything on DigitalOcean but using S3 wouldn't be a problem.
You mentioned "static assets" and this is where Jekyll shines IMO. The jekyll-assets plugin (optional) will md5 tag your assets for cache busting and bundle your scss / JS too. It's really handy and avoids having to set up more complicated tools. It pretty much works out of the box with close to zero configuration.
The plugin system is nice too. You can do some really useful things like automatically add certain rel attributes to external links with a few dozen lines of Ruby. It's very handy for a blog.
I’d second Jekyll because it’s easy to get hosted on GitHub pages with a custom domain, or just a .io default. A no-brainer for low maintenance pages with easy Markdown updates in my opinion. Also nice to know it will be supported by that group since it powers so many pages.
The markdown authoring experience is also one that I really love, personally, which is an added bonus.
Isn't Jekyll slow for a lot of blog posts? Also,adding all those plugins for everything must slow it down. Asking you since you have 250+ posts. I had read this in a Hugo vs Jekyll comparison and picked Hugo.
The thing about static site builders is that it's really easy to get started building one, and very difficult to make one that meets everyone's needs. The result of this is a sort of Life-Cycle of the Static Site Generator:
1. Look at the huge list of open-source static site generators (literally hundreds![1])
2. Try some out, and fail to find one that works exactly right.
3. Start writing a new one that fits better.
4. Gradually extend it and make it more general.
5. Get excited about how useful it is, and publish it as an open-source project so others can use it, adding it to the already enormous list.
I've taken to just building a new one one to meet whatever my immediate need is, and developing a sort of mental toolkit of techniques rather than trying to smush an existing program into the particular requirements of a specific project. You can get surprisingly far with just a handful of lines of code.
I like knocking up JS to pump out some HTML and often it’s quicker than using a framework when you consider how much of a dead end they leave you in when there is something they can’t do with their DSL or whatever.
I use Pelican. If you know Python, it's decently easy enough to extend it for your own needs. It was the first one I used way back in 2011, and I've not needed to use a different one.
I'm certainly not alone in going down that route! Sometimes it can be rewarding though, as you do get something you understand and which suits you completely.
I wrote a (perl-based) blog-compiler for my own site https://blog.steve.fi/ and recently rewrote it in golang to get the advantage of easier installation and faster generation.
Generating a thousand blog posts, over five+ years, shouldn't take more than a second. My Perl code used to take 30 seconds to rebuild and upload my site (via rsync) complete with comments, tags, etc. But the new rewrite takes 3 seconds to do the same job. So it was a good rewrite even if I'm not even going to pretend it is a general purpose utility any more.
Nice site. A suggestion: cleanup the duplicate languages. I saw there were two “TypeScript” options which were different only due to variation of capital letters.
- Single binary distribution. No dependencies or time wasted setting up things. Just extract and use.
- Dozens of themes to pick from [0]
- Straight forward customization of theme's styling
- Tinkering Go templates are fairly easy
- Accepts markdown and Org-mode as input formats
- Tags, categories, multilingual, search, etc.
- Support for comments [1]
I've been using it for my site [2] for more two years now. It has embedded JavaScript/CSS WebGL demos, code blocks with syntax highlighting (again no dependency on Pygments, etc. and has preset themes), images, footnotes, math equations using MathJax, etc. Tools enough to write a well-formatted book.
I've used Hugo for a while and was drawn to its single binary, quick builds, and nice template features. However, after a few years I've decided that it's not for me.
While the Hugo developers are very responsive and do a good job maintaining the project, they don't generally respect their users (be they theme or site developers) time. Every few versions I find that my sites are broken because the developers changed something on me, sometimes in ways that just silently change the behavior of the site (as opposed to a build error, which would be annoying but which is more discoverable).
The documentation is also very difficult for me to learn from. Despite being extensive, it's extremely hard to learn how to do anything and I find that it frequently makes assumptions that you already are an expert theme or site developer. I wish I had a better grasp on what makes their documentation so hard to use despite the fact that there's so much of it, but I find that what I'm reading is almost never what I need to actually understand what's going on. This might just be me though.
I made two fairly advanced SaaS / product sites using Hugo (https://vamp.io and https://checklyhq.com) and would actually advice to not use Hugo for any new initiatives.
- the templating syntax is just very confusing.
- the documentation was terrible, is still terrible and probably will remain terrible.
- the split between index and list pages is still a big pain. Many things work on one but not the other.
- upgrades break your site almost always.
- error messages are arcane
This might sound bitter, but I was a fan in the beginning. Development seems to have gone off track somewhere, probably when the original maintainer left.
Probably Vuepress for simple docs and blog site is the simplest one I’ve found, but I’m pretty comfortable with Vue.
Personally, I'd go with hugo as it is fast at generating but I've used nikola for years as it is python based (my prefered language). I'd recommend checking out https://www.staticgen.com/ as it tracks SSG's popularity and gives nice info. A SSG built on a language/platform you are comfortable with is always a plus as sometimes you just need to get under the hood and ti.ker with things.
And for people who want "Hugo but written in Rust" or "Hugo but written in Javascript" — then, there's Zola (Rust): https://github.com/getzola/zola, and 11ty (Javascript): https://github.com/11ty/eleventy. (Or at least that's how I think about these two.)
Thank you for pointing out StaticGen. Now I can find the product built with technologies I know so that I can get stuff done quickly instead of learning the tools of the most popular product on that list.
A slightly different take on this. I've recently seen people combine Pandoc[1] with their own (generally quite small) shell script. It's pretty amazing how little time it can take just using Pandoc / shell to come up with something that's just right for your needs, without all the bells and whistles.
I'd probably recommend Gatsby, it's super flexible, has great documentation, tons of plugins and includes good defaults.
I've previously used hugo to build some customer sites. It's super quick to build, but we ended up replicating a bunch of work that Gatsby has support for like image optimisation, minification, etc.
Netlify is a good hosting option if you're not married to S3.
Take a look at forestry.io - it's a CMS that can use various different static site generators, but edits in the CMS are committed directly to your git repo.
So all your content stays in git, and yet you can still collaborate with non-technical partners.
Also check out https://dlvrit.com/ - this posts new articles to social networks automatically. I've configured it so that:
* There's a tick-box in the forestry config for posting to social networks.
* When this is ticked, Hugo includes the article in a special custom RSS feed.
* dlvr.it uses that custom RSS feed as its input.
So as far as my non-technical collaborator is concerned, when they're happy with the article, they tick the Socials box in the forestry admin and it magically posts to all the social networks. It's awesome.
I'm using Hugo with Netlify. I've used just about every tool over the years, and I'm pretty happy with Hugo. Netlify makes deployment a breeze, and there's a free tier with 100GB of bandwidth which is fine for a basic blog.
If you want to do anything fancy, or you have a love for React, I'd suggest Gatsby as an alternative. It also makes it easier to pull in the JS ecosystem. Currently, pulling in JS libraries with Hugo is a bit clunky because it doesn't integrate directly with the standard JS tools (npm, webpack, etc).
I love this stack. Although the one where you are most comfortable with is the way to go, hugo + netlify (and eventually add forestry if you need a real CMS) is astonishingly easy and straightforward to set up. Just amazing.
edit: About adding js libraries, just import them via html instead of using package managers
It is a Python based, "make a blog from theme template and markdown content" engine. There's hundreds of themes and plugins for all sorts of functionality. I spent some time twisting it and its theme engine to make http://snafuhall.com/ (read as, don't blame them for my site, the horrors are all my responsibility)
It’s like asking what is the best web framework, or what is the best scripting language. There are several prominent static-site generators, each with their strengths and weaknesses.
1. What is your preferred language? For Ruby, it’s probably Jekyll, Middleman, and maybe nanoc. For Javascript, it’s Gatsby and Eleventy. If you don’t mind Go’s templating language, it’s Hugo.
2. What are your priorities for a static-site generator?
- available themes? then it’s probably Jekyll or Gatsby
- easy generation of documentation? Docusaurus might be worth a look
- flexibility? for a front-end developer, Gatsby is insanely flexible
- fast build time? Hugo is probably unbeatable
- small initial payload? not Gatsby then (eleventy looks nice, and was used by Google webrel folks to build the Chrome Dev Summit site). Keep in mind that server-side-rendered React, used in Gatsby, will leave your site non-interactive during the time javascript is loading
My personal preference, as a frontend developer who likes javascript/typescript and React, is Gatsby, but Eleventy is looking increasingly appealing.
The best CMS is the filesystem. Don't be afraid to just write HTML and use it.
For my personal site I write html posts as discrete files with filenames that allow me to use bash to cat them easily into pages. Then every time I write a new post for the blog I just run something like, ls -v 2019-*.html | tac | xargs cat > blog-2019.html
To style the raw posts themselves I use HTTP header linked CSS (https://www.w3.org/TR/html4/present/styles.html#h-14.6). It doesn't work in every browser but I don't care about every browser. That's the joy of personal sites. You can just do what you want.
For generating the RSS feed I wrote a small perl script. Everything is hosted from home with nginx running on my main desktop over a cable ISP connection.
I have a server-side CMS written entirely in bash. It was originally kind of a joke, but it's been working well on a relatively high-traffic site for over 5 years now so I guess the joke is now on me. I named it SCMS, which was originally "stupid CMS", but maybe now I can retcon it to "shell CMS".
We now have come the full circle, and I expect that people now - after rediscovering plain html - will next start to rediscover all the issues with maintaining purely static html sites, all those reasons why we ditched the idea back in 90s
If you are interested in learning about software, making your own SSG is a fun and simple project. If you don’t know HTML, handwriting a couple of pages is a great way to learn. If you want to make a website, writing by hand is a total waste of time.
If you really want the low-tech version I'd still recommend writing in Markdown and using Pandoc to convert to HTML. You can then use one HTML template to style all of your blog and a Makefile for the conversion and you got your static site generator.
I mostly do Tor onion sites. So I absolutely don't want any scripting. Because that would piss off the most valuable part of my potential audience. And given Tor's latency, you want to avoid unnecessary traffic.
I write mostly in ReText. It generates decent HTML. But I usually end up tweaking.
For my personal site I just I built my own with Ruby and I love it. It's perfectly molded to my use and I don't have to fuss around with keeping up with updates or handling edge cases that static site builder may not have thought of. For example, some of my work has been translated into other languages and having a template that was easy to streamline into French is really nice.
And really static site builders are EASY to build. It's just building strings! It feels like so much of development has turned into libraries and glue code these days. It's nice to have something small and simple.
Tried using Hugo but it was full of magic and silly naming and conventions that I really didn't like.
I even created my own little language which I used the Go parser to parse (but the syntax was closer to Lisp - the Go parser is just for the expressions after the commands - e.g. `(cmd expr)`).
After I made it, I discovered that this is one of the most popular projects for programmers to embark on and actually pull off something usable (it's both useful and interesting, while not being too overwhelming)...
Here's a full list with 100s of static site generators (mine included haha) : https://www.staticgen.com/
Honestly I haven't found any I really like. Gatsby for example I found overly bloated (eg. requiring GraphQL - with which you can't even dynamically generate queries) without offering everything I need out of the box (eg. Disqus integration), build times felt long, and there are very little templates (at least last time I used it) and like other SSGs switching a template basically requires re-architecting your whole app.
I think the biggest weakness with these SSGs is the difficulty of switching themes. With a CMS like Wordpress, changing themes takes no work, you just specify a new theme. In any popular SSG, changing themes generally means re-architecting your codebase, requiring a developer to dive into the codebase and spend an insignificant amount of time (leading one to question the value of their SSG framework), or otherwise abandon their current project and start over on the new template from scratch.
Because changing themes is such a hassle and time sink, if you just want to use a pre-made template and be done with it, then I actually recommend you look for the template you want first on ANY popular SSG, and then just use that (Jekyll seems to have the largest section of templates).
If you're planning to make your own custom template and you're a developer, then honestly I recommend you to just create your own project without these SSG frameworks, unless you just really happen to like the (often super overly opinionated) stack that they tie you into (that won't be cool anymore a year later as developers flock to the next shiny thing). Even then I think you'll find yourself working against the framework more often then you'd like, pretty much defeating the purpose. For my needs I found it easier to just parse my own Markdown files and use an npm library like showdown to convert them to HTML, and then just develop in my preferred stack.
If anyone wants to recommend something for beginners. Then checkout https://www.stackbit.com/. It can even convert your existing themes b/w various SSGs (like Hugo,Jekyll). And they have some pre-made themes too, although, small selection, but good ones.
For me, I'd rather brush up on my HTML and CSS than learn a new framework. So I coded a mockup webpage, google'd for responsive CSS layouts and tested on a few devices. Then a little python glue (which I enjoy hacking with) to turn that template and markdown into a simple website. Et viola! http://fadedbluesky.com/projects/sitegen.html
I have to plug mine, even though I haven’t touched it in years:
Frankenstein’s ___.sh , a bash script that mash some html placeholders together with your multimarkdown content into a bunch of static files. Supports blog, hierarchical and plain pages.
[+] [-] nickjj|6 years ago|reply
I currently use it for:
- My personal blog with 250+ posts and tons of pages[0]
- A podcast platform[1] which is open source[2]
- The landing pages for all of my web development courses (not going to bother linking them since I don't want to seem like I'm fishing HN for sales)
I also recently wrote about my whole site's tech stack here[3]. That post might not fully apply to you since you want to host it on S3. I personally self host everything on DigitalOcean but using S3 wouldn't be a problem.
You mentioned "static assets" and this is where Jekyll shines IMO. The jekyll-assets plugin (optional) will md5 tag your assets for cache busting and bundle your scss / JS too. It's really handy and avoids having to set up more complicated tools. It pretty much works out of the box with close to zero configuration.
The plugin system is nice too. You can do some really useful things like automatically add certain rel attributes to external links with a few dozen lines of Ruby. It's very handy for a blog.
[0]: https://nickjanetakis.com/
[1]: https://runninginproduction.com/
[2]: https://github.com/nickjj/runninginproduction.com
[3]: https://runninginproduction.com/interviews/1-100k-page-views...
[+] [-] sailfast|6 years ago|reply
The markdown authoring experience is also one that I really love, personally, which is an added bonus.
[+] [-] sharcerer|6 years ago|reply
Btw, checkout https://www.stackbit.com/. really good.
[+] [-] theSealedTanker|6 years ago|reply
[+] [-] nickthemagicman|6 years ago|reply
[+] [-] wolfgang42|6 years ago|reply
1. Look at the huge list of open-source static site generators (literally hundreds![1])
2. Try some out, and fail to find one that works exactly right.
3. Start writing a new one that fits better.
4. Gradually extend it and make it more general.
5. Get excited about how useful it is, and publish it as an open-source project so others can use it, adding it to the already enormous list.
6. Someone else starts at step 1.
[1]: https://www.staticgen.com/
I've taken to just building a new one one to meet whatever my immediate need is, and developing a sort of mental toolkit of techniques rather than trying to smush an existing program into the particular requirements of a specific project. You can get surprisingly far with just a handful of lines of code.
[+] [-] quickthrower2|6 years ago|reply
Another fine alternative is just use Wordpress!
[+] [-] BeetleB|6 years ago|reply
[+] [-] stevekemp|6 years ago|reply
I wrote a (perl-based) blog-compiler for my own site https://blog.steve.fi/ and recently rewrote it in golang to get the advantage of easier installation and faster generation.
Generating a thousand blog posts, over five+ years, shouldn't take more than a second. My Perl code used to take 30 seconds to rebuild and upload my site (via rsync) complete with comments, tags, etc. But the new rewrite takes 3 seconds to do the same job. So it was a good rewrite even if I'm not even going to pretend it is a general purpose utility any more.
[+] [-] peternicky|6 years ago|reply
[+] [-] legends2k|6 years ago|reply
- Single binary distribution. No dependencies or time wasted setting up things. Just extract and use.
- Dozens of themes to pick from [0]
- Straight forward customization of theme's styling
- Tinkering Go templates are fairly easy
- Accepts markdown and Org-mode as input formats
- Tags, categories, multilingual, search, etc.
- Support for comments [1]
I've been using it for my site [2] for more two years now. It has embedded JavaScript/CSS WebGL demos, code blocks with syntax highlighting (again no dependency on Pygments, etc. and has preset themes), images, footnotes, math equations using MathJax, etc. Tools enough to write a well-formatted book.
[0]: https://themes.gohugo.io/
[1]: Disqus, Utterances, Commento, etc.
[2]: https://legends2k.github.io
[+] [-] SamWhited|6 years ago|reply
While the Hugo developers are very responsive and do a good job maintaining the project, they don't generally respect their users (be they theme or site developers) time. Every few versions I find that my sites are broken because the developers changed something on me, sometimes in ways that just silently change the behavior of the site (as opposed to a build error, which would be annoying but which is more discoverable).
The documentation is also very difficult for me to learn from. Despite being extensive, it's extremely hard to learn how to do anything and I find that it frequently makes assumptions that you already are an expert theme or site developer. I wish I had a better grasp on what makes their documentation so hard to use despite the fact that there's so much of it, but I find that what I'm reading is almost never what I need to actually understand what's going on. This might just be me though.
[+] [-] elamje|6 years ago|reply
I still use it, but it’s not exactly beginner friendly.
[+] [-] tnolet|6 years ago|reply
- the templating syntax is just very confusing.
- the documentation was terrible, is still terrible and probably will remain terrible.
- the split between index and list pages is still a big pain. Many things work on one but not the other.
- upgrades break your site almost always.
- error messages are arcane
This might sound bitter, but I was a fan in the beginning. Development seems to have gone off track somewhere, probably when the original maintainer left.
Probably Vuepress for simple docs and blog site is the simplest one I’ve found, but I’m pretty comfortable with Vue.
[+] [-] spectramax|6 years ago|reply
- Confusing architecture
- Steep learning curve
I recommend Jekyll more than anything else. It is simple, beautiful and straight forward. Easy.
[+] [-] mmohammadi_9812|6 years ago|reply
[+] [-] drad|6 years ago|reply
[+] [-] KajMagnus|6 years ago|reply
[+] [-] heliodor|6 years ago|reply
[+] [-] hazbo|6 years ago|reply
[1]: https://github.com/jgm/pandoc
[+] [-] teodorlu|6 years ago|reply
[1]: https://jaspervdj.be/hakyll/
[+] [-] black_knight|6 years ago|reply
[+] [-] flir|6 years ago|reply
[+] [-] siod|6 years ago|reply
I've previously used hugo to build some customer sites. It's super quick to build, but we ended up replicating a bunch of work that Gatsby has support for like image optimisation, minification, etc.
Netlify is a good hosting option if you're not married to S3.
[+] [-] davelondon|6 years ago|reply
So all your content stays in git, and yet you can still collaborate with non-technical partners.
I built https://www.wildernessprime.com/ (https://github.com/dave/wildernessprime) with it.
Also check out https://dlvrit.com/ - this posts new articles to social networks automatically. I've configured it so that:
* There's a tick-box in the forestry config for posting to social networks.
* When this is ticked, Hugo includes the article in a special custom RSS feed.
* dlvr.it uses that custom RSS feed as its input.
So as far as my non-technical collaborator is concerned, when they're happy with the article, they tick the Socials box in the forestry admin and it magically posts to all the social networks. It's awesome.
[+] [-] tnolet|6 years ago|reply
[+] [-] brenden2|6 years ago|reply
If you want to do anything fancy, or you have a love for React, I'd suggest Gatsby as an alternative. It also makes it easier to pull in the JS ecosystem. Currently, pulling in JS libraries with Hugo is a bit clunky because it doesn't integrate directly with the standard JS tools (npm, webpack, etc).
Here's the source for my site: https://github.com/brndnmtthws/brndn-io
[+] [-] gcatalfamo|6 years ago|reply
edit: About adding js libraries, just import them via html instead of using package managers
[+] [-] hanniabu|6 years ago|reply
[+] [-] h2odragon|6 years ago|reply
It is a Python based, "make a blog from theme template and markdown content" engine. There's hundreds of themes and plugins for all sorts of functionality. I spent some time twisting it and its theme engine to make http://snafuhall.com/ (read as, don't blame them for my site, the horrors are all my responsibility)
[+] [-] robohoe|6 years ago|reply
[+] [-] azangru|6 years ago|reply
1. What is your preferred language? For Ruby, it’s probably Jekyll, Middleman, and maybe nanoc. For Javascript, it’s Gatsby and Eleventy. If you don’t mind Go’s templating language, it’s Hugo.
2. What are your priorities for a static-site generator?
- available themes? then it’s probably Jekyll or Gatsby
- easy generation of documentation? Docusaurus might be worth a look
- flexibility? for a front-end developer, Gatsby is insanely flexible
- fast build time? Hugo is probably unbeatable
- small initial payload? not Gatsby then (eleventy looks nice, and was used by Google webrel folks to build the Chrome Dev Summit site). Keep in mind that server-side-rendered React, used in Gatsby, will leave your site non-interactive during the time javascript is loading
My personal preference, as a frontend developer who likes javascript/typescript and React, is Gatsby, but Eleventy is looking increasingly appealing.
[+] [-] vira28|6 years ago|reply
I do mine on https://viggy28.dev hosted on Firebase. Source https://gitlab.com/viggy28-websites/viggy28.dev
[+] [-] prophesi|6 years ago|reply
Self-hosted, works with IPFS, open-source Commento for comments.
[+] [-] superkuh|6 years ago|reply
For my personal site I write html posts as discrete files with filenames that allow me to use bash to cat them easily into pages. Then every time I write a new post for the blog I just run something like, ls -v 2019-*.html | tac | xargs cat > blog-2019.html
To style the raw posts themselves I use HTTP header linked CSS (https://www.w3.org/TR/html4/present/styles.html#h-14.6). It doesn't work in every browser but I don't care about every browser. That's the joy of personal sites. You can just do what you want.
For generating the RSS feed I wrote a small perl script. Everything is hosted from home with nginx running on my main desktop over a cable ISP connection.
[+] [-] LeoPanthera|6 years ago|reply
I'm still too embarrassed to release it, though.
[+] [-] ivanhoe|6 years ago|reply
[+] [-] earthboundkid|6 years ago|reply
If you are interested in learning about software, making your own SSG is a fun and simple project. If you don’t know HTML, handwriting a couple of pages is a great way to learn. If you want to make a website, writing by hand is a total waste of time.
[+] [-] ofrzeta|6 years ago|reply
[+] [-] mirimir|6 years ago|reply
I mostly do Tor onion sites. So I absolutely don't want any scripting. Because that would piss off the most valuable part of my potential audience. And given Tor's latency, you want to avoid unnecessary traffic.
I write mostly in ReText. It generates decent HTML. But I usually end up tweaking.
[+] [-] mjurczyk|6 years ago|reply
[deleted]
[+] [-] hcarvalhoalves|6 years ago|reply
https://gist.github.com/hcarvalhoalves/27c3c43f21cd7c7df04ce...
[+] [-] 3pt14159|6 years ago|reply
And really static site builders are EASY to build. It's just building strings! It feels like so much of development has turned into libraries and glue code these days. It's nice to have something small and simple.
[+] [-] brabel|6 years ago|reply
Tried using Hugo but it was full of magic and silly naming and conventions that I really didn't like.
I even created my own little language which I used the Go parser to parse (but the syntax was closer to Lisp - the Go parser is just for the expressions after the commands - e.g. `(cmd expr)`).
After I made it, I discovered that this is one of the most popular projects for programmers to embark on and actually pull off something usable (it's both useful and interesting, while not being too overwhelming)...
Here's a full list with 100s of static site generators (mine included haha) : https://www.staticgen.com/
[+] [-] JDiculous|6 years ago|reply
I think the biggest weakness with these SSGs is the difficulty of switching themes. With a CMS like Wordpress, changing themes takes no work, you just specify a new theme. In any popular SSG, changing themes generally means re-architecting your codebase, requiring a developer to dive into the codebase and spend an insignificant amount of time (leading one to question the value of their SSG framework), or otherwise abandon their current project and start over on the new template from scratch.
Because changing themes is such a hassle and time sink, if you just want to use a pre-made template and be done with it, then I actually recommend you look for the template you want first on ANY popular SSG, and then just use that (Jekyll seems to have the largest section of templates).
If you're planning to make your own custom template and you're a developer, then honestly I recommend you to just create your own project without these SSG frameworks, unless you just really happen to like the (often super overly opinionated) stack that they tie you into (that won't be cool anymore a year later as developers flock to the next shiny thing). Even then I think you'll find yourself working against the framework more often then you'd like, pretty much defeating the purpose. For my needs I found it easier to just parse my own Markdown files and use an npm library like showdown to convert them to HTML, and then just develop in my preferred stack.
[+] [-] sharcerer|6 years ago|reply
Just a 4 step process: https://app.stackbit.com/create
[+] [-] intrepidhero|6 years ago|reply
[+] [-] benibela|6 years ago|reply
For example
is evaluated to Or becomes XQuery is a W3C standard, so there are several implementation of it. I wrote an XQuery interpreter (http://www.videlibri.de/xidel.html) myself[+] [-] frabert|6 years ago|reply
[+] [-] nico_h|6 years ago|reply
Frankenstein’s ___.sh , a bash script that mash some html placeholders together with your multimarkdown content into a bunch of static files. Supports blog, hierarchical and plain pages.
It’s 84 lines in total plus the ”templates”
https://github.com/nicolasH/frankensteins