- cross-posted to:
- blogging@programming.dev
- cross-posted to:
- blogging@programming.dev
Hey, just wanted to drop this here. It’s a technical follow-up to The Unreasonable Effectiveness of Static Sites which was reasonably popular, and explains the components of a static site’s stack.
For me, I write notes in Markdown anyways as part of a Zettelkasten, and by setting up my site this way I can stay in my development / note taking environment (nvim) and push stuff up to the site very quickly. It’s far easier as a developer to work off-the-cuff with this type of workflow, at least for me.
Also, would be very easy to self-host or move provider if Vercel or any other provider goes down.
I see, that makes sense
I use Markdown with Jekyll because it integrates nicely with GitHub Pages and I can run it locally for authoring. There’s tons of support for it, as far as I can tell. Jekyll uses Liquid for templating, and it seems pretty good. For layout, I use Minimal Mistakes which has a really nice feel and it’s comparatively easy to customize. Once I was through all the layout configuration stuff, it’s really just a matter of writing articles and pushing them up to GitHub - rarely fiddle with anything technical these days.