One of the things preventing “normal” people from using a static CMS is that there’s not a comfortable way to for them to edit and preview content. I myself prefer editing markdown in a local text editor. Most people don’t work well that way.
This post is being written in my browser using Netlify CMS. When saving, it’ll create a new markdown file in the Github repo and Netlify will automatically re-build the site and push it to the Netlify CDN.
Update 2017-03-17 It worked very well. The only thing I still need to deal with is adding Tags to the CMS UI. I tried using a “String” type but that put single quotes around the entire thing, breaking the build. Oh well. This is a nice way of editing existing posts via an easy-to-use web control panel, for times I’m not at my desktop computer.
I happened to see the Hugo 0.19 release
announcement and didn’t
think too much of it until I read this…
Native Emacs Org-mode Support
I installed it and tested with a few Org files and between my love of
static sites and Org Mode I’ve replaced everything with a new
Hugo-generated version. Again.
I upgraded my iMac to the latest macOS Sierra beta. I thought everything was working
fine until I tried to publish a short blog post about the experience.
My Hugo and/or Go installation was broken so I could not
build my site. This meant I couldn’t publish to my blog. Ironic, no? Rather than
waiting for things to be fixed, I decided to find a way around the problem.
I’ve wanted to use Netlify again ever since they’d removed the builds-per-day
limit. (I tend to make a lot of corrections after publishing). I added my site’s
configuration to Netlify, pointed it to my
Gitlab repo and added the
appropriate DNS records. Five minutes later the site was built (via Hugo) and
deployed to Netlify’s servers and CDN.
Now, every time I commit to master and push to Gitlab, Netlify automatically
builds and deploys everything for me. I’m a fan of simple, static files on a
server I control, but Netlify offers benefits that make it worth giving up a
little control. For example, I can fix a typo by editing a file using the
Gitlab web UI and the site will be built and deployed automatically. This lets
me make edits on my iPad, which can be handy.
Continuous Deployment, a CDN, easy rollbacks, CLI, free one-click SSL, and a
generous free tier. Pretty nice, Netlify.
I spent today learning how to create a static website with
Middleman is a static site generator using all the shortcuts and tools in
modern web development.
I’m a fan of static websites and excited to see that static site generators are
proliferating like mad lately.
I’ve created static sites using Movable Type, Emacs (org mode), Hugo, Jekyll,
and completely hand-coded HTML files. I wanted to try something new, and decided
upon Middleman. Middleman uses Ruby and feels much like working with a Ruby on
Rails app, which I’m familiar with.
The installation went pretty well. I did need to deal with some RubyGems issues,
which is par for the course. Once installed, I had no further problems.
Middleman isn’t as easy out of the box as something like Jekyll, but it seems
significantly more flexible. It’s mostly just Ruby in Erb templates.
For a simple blog, I’d go with something else. Most of the static generators
lean toward creating blogs by default. Middleman requires extra configuration
and setup in order to get rolling with a blog. Middleman should shine for
building sites that are more complex than a basic blog.
As a test, I ported Fusionary’s site (currently built
with CraftCMS). It took a few hours, and I don’t have the asset pipeline stuff
worked out, but it was easy. I’ll try a few more, but so far so good with
notes.baty.net is entirely unnecessary. I should just post everything at
https://baty.net. Except I enjoy having a static blog and using Hugo
to publish a bunch of simple markdown files. So here we are again.