Live data from Hacker News

Ask HN: What is setup for your static blog generator?

news.ycombinator.com

21–30 of 98 posts

Re: Ask HN: What is setup for your static blog generator?

#22
Jekyll for my podcast's web site (https://allthingsgit.com/). I became a fan of Jekyll when I worked at GitHub, but I don't use GitHub Pages, I needed to scale it larger. (edit: in particular, I needed something that can host audio and video.) So my workflow is GitHub for hosting, and Visual Studio Team Services for CI builds. It monitors the GitHub repository and on commits to master, it runs Jekyll in a docker container. It then deploys to Azure, where I host the static web site. (I use Azure CDN for hosting the audio episodes.)

I would use VSTS for the whole pipeline, including the Git repository hosting, but I wanted to have a public repository, in case listeners wanted to submit pull requests. So far that hasn't happened, so I'm missing out on some of the VSTS features, but maybe it still will.

I also have a weekly newsletter (https://developertoolsweekly.com/) that uses a static site generator that I build myself. It's very Jekyll-inspired and uses Liquid templates, but instead of generally processing markdown, it takes a simple list of links and descriptions and emits a website as well as the HTML and plain text for the emails.

This workflow is similar, the generator is run in a Docker container, but this workflow is entirely VSTS and Azure.

Re: Ask HN: What is setup for your static blog generator?

#23

Not a direct answer, but I just wanted to point out how handy it is that you can publish to your public keybase directory, and have it hosted at keybase.pub, something like this: https://abhi.keybase.pub/2016/02/15/git-and-keybasefs.html The general gist is that keybase.io is promising that it will only serve data at abhi.keybase.pub that has been signed for by that user.

This is brilliant information. Thanks for sharing it.

Re: Ask HN: What is setup for your static blog generator?

#24

This will probably forever be too half-baked to "release", but I wrote my own: https://github.com/jakelazaroff/adjective It's written in Node and features multithreading and incremental builds for fast development. I host on Netlify, which has continuous integration built in, so it builds and deploys the site every time I push to GitLab.

I'm also using Netlify (with Hugo). Their service is simple to use, and send to work quite well.

Re: Ask HN: What is setup for your static blog generator?

#26
Jekyll was slow and hard to customize. A tiny script can convert a template + a directory of markdown files to a blog pretty easily.

Less code and configuration makes it easy to add custom features; I stuck incremental rebuilds and hot reloading into my blog while keeping it below 70 LOC:

https://github.com/1wheel/roadtolarissa/blob/master/index.js

Re: Ask HN: What is setup for your static blog generator?

#27

I have Jekyll setup (not recommended, see below) to generate my sites in a Docker container. The builder container outputs my websites into a volume that's shared with nginx. I have shared assets for multiple websites and had to create a custom plugin to support this setup in Jekyll: https://github.com/sumdog/jekyll-multisite There are open issues and pull requests for the plugin. I started building a test suite so I…

I wouldn't recommend trying to fit a square peg into a round hole either.

Re: Ask HN: What is setup for your static blog generator?

#29
I generate html from templates which are html interspersed with js. JS is used to generate the dynamic parts. A simple js program prepopulates some data structures and hands it over to the template. Once html files are generated I put them up on S3. I write the posts in HTML because I've generally had bad luck with getting markdown to get things to look exactly as i want them.
Post reply on HN