I keep hoping to see a "Show HN" article one of these days featuring an Electron app that functions as blog editor and publishes static files via rsync to the server and backs up all blog content via distributed source control to the source control host of your choice through which other contributors to the blog can sync.
I would like to have something like CityDesk (I paid for that software back in... Y2K?).
I remember someone was able to "hack" it to embed articles inside excel sheets: he just used an excel sheet as a template (which was zipped XML) and Citidesk substitued some variables inside the templeate
I still love my self-hosted WordPress instance. I wanted, for so long, to not use WordPress (for stupid reasons).
I keep a minimal set of plugins activated and my blog just works. It allows me to focus on content instead of trying to do a bunch of "dev work" on it.
I used to have a blog, but for the last couple of years I've been using Medium.
For my use case, an unknown very occasional blogger, it doesn't make sense to invest in a dedicated website or pay for a service like Ghost. I imagine this is very different for full time bloggers or more notorious individuals such as Jeff Atwood (Coding Horror).
Twitter/Medium because I'm a normal person looking for the easiest solution that I know of. I'm not picky and I don't care about principles or owning my content. I just want to write and then get a link that I can share with people.
I know this perspective isn't well represented on HN so I figured it'd be helpful to share.
If I had a more acute reason for starting a blog like personal branding, or some sort of strategic media objective, I may look more into the implications of publishing on 3rd party sites, but for the casual use-cases that I anticipate for myself, that angle doesn't matter for me.
I tried Hugo years ago but couldn't get on board because it doesn't treat assets as a first class citizen.
For example with Jekyll, all you have to do is pull in Jekyll-Assets and you get perfect md5 asset tagging for cache busting along with typical SCSS / JS processing and other goodies. It takes about 2 minutes to configure a hyper optimized asset pipeline and you never have to think about it again.
Building scss/js with hugo hasn't been an issue for me yet - the theme I use shipped with its own build pipeline, as I imagine others do. Fortunately, the theme dev organized it well.
I didn't know about the cache busting with jekyll. Right now, I just toss assets into the 'static' dir so I don't think Hugo does anything with them, but I think there are other ways/shortcodes to serve them. Overall, I'm not super happy with hugo, I just latched onto the "it's fast" marketing line because I've had bad experiences with Ruby's performance. As far as my main gripe, the go templating engine seems pretty bad.. Either that, or I don't know how to use it well. I believe templating engines are swappable, however.
Overall, my content is so simple (photos + text) that the usability issues don't bug me yet.
Cache busting would be appending things like the last 8 characters of an asset's MD5 hash to the file name.
You end up serving logo-bad253c1.jpg as your asset file name, so you can cache it forever with nginx, and if the logo changes, the asset's filename gets changed.
With Jekyll-Assets (a plugin) all of that is taken care of for you under the hood. You just reference {% image logo.jpg %} in your templates and it does the rest when you build your site.
Doing things like converting SCSS to CSS and other optimizations are included too, but the main issue is I don't think Hugo has anything for that cache busting strategy that works in a generic way (adding a querystring is no good because a lot of proxies strip out that data).
I tried to go with Jekyll but didn't even bother setting up a ruby env. So I went with Hyde. It works OK but I still was rather annoyed that I had to learn yet another markup/template syntax. Customizing wasn't really straightforward either, docs were rather lacking on some areas, so it was mostly trial and error. I'd prefer some static blog generator that's really dumbed down enough to have a dead simple template system and uses some form of simple markdown, but my search wasn't successful...
If you run Linux or MacOS you could always run Jekyll in Docker and not worry about Ruby.
Unfortunately Jekyll with Docker for Windows doesn't work. The file watcher is completely busted (even with polling). It's strange too because every other language / framework works fine (Flask, Rails, Phoenix, Node), etc. It's just Jekyll that's broken.
I wrote my surrounding static text as a Common Lisp program; relevant BLOBs are put into a resources directory. Blog entries are in Markdown, then read into the program, transformed, and the entire thing spat out as HTML.
It then uploads to S3 and renders out in a domain. I'll be moving to the Google cloud edition of that sometime in the next 4 months, I figure.
I've dinked with wordpress, blogger, tumblr, livejournal, dreamwidth, and other platforms, along with 1 or 2 other static site generators, along with writing my own static site generator. This beats all of them in terms of maintainability and simplicity.
I'm a no-name software engineer and this is a way to write down things that I want to share with people. It works really well.
I also use Lisp, but slighly differently: I've really come to love how flexible and powerful Emacs Org is. With all static generation tools (including those i built myself) I've hit limits. Not with Org, yet.
Earlier this year, I threw together something in Rails with Bulma. It took an afternoon, except for never-ending css tweaks. Rails is built for that kind of thing so it wasn't a huge amount of effort.
It's not very socially media aware or SEO-savvy of me, but I'm doing it as a fun way to build a fun website, which was something people used to use the internet for.
Hugo. Self hosted. There is no way I'm going to hand my content to some third party to monitor and track the visitors and monetize at their discretion.
After trying both Wordpress and Hugo, I decided to keep it simple and set up Ghost using Digital Ocean's 1 click install. It has everything I need and I'm very satisfied with Ghost's editor.
Yes, Wordpress is still the default, but after getting hacked despite working hard to keep it up to date I will no longer host my own. A boring answer and it's not as customisable as I'd like, but a paid plan on wordpress.com is a lot less hassle and I don't regret the switch.
I used to use Tumblr but moved to the static site generator because
- I wanted full flexibility
- I didn't use web GUI to write or redesign my blog
- Tumblr looked outdated at some point - and this could happen to any platform.
64 comments
[ 3.3 ms ] story [ 130 ms ] threadAm I hoping for too much?
[0] https://shopkins.writeas.com
I'm going to give it a try for my next post.
I miss that piece of software.
I keep a minimal set of plugins activated and my blog just works. It allows me to focus on content instead of trying to do a bunch of "dev work" on it.
¹ https://github.com/Plume-org/Plume
https://gohugo.io
For my use case, an unknown very occasional blogger, it doesn't make sense to invest in a dedicated website or pay for a service like Ghost. I imagine this is very different for full time bloggers or more notorious individuals such as Jeff Atwood (Coding Horror).
I know this perspective isn't well represented on HN so I figured it'd be helpful to share.
If I had a more acute reason for starting a blog like personal branding, or some sort of strategic media objective, I may look more into the implications of publishing on 3rd party sites, but for the casual use-cases that I anticipate for myself, that angle doesn't matter for me.
Even with over 200 posts and a bunch of pages, it's a fast write -> preview loop (less than 3 seconds).
For example with Jekyll, all you have to do is pull in Jekyll-Assets and you get perfect md5 asset tagging for cache busting along with typical SCSS / JS processing and other goodies. It takes about 2 minutes to configure a hyper optimized asset pipeline and you never have to think about it again.
I didn't know about the cache busting with jekyll. Right now, I just toss assets into the 'static' dir so I don't think Hugo does anything with them, but I think there are other ways/shortcodes to serve them. Overall, I'm not super happy with hugo, I just latched onto the "it's fast" marketing line because I've had bad experiences with Ruby's performance. As far as my main gripe, the go templating engine seems pretty bad.. Either that, or I don't know how to use it well. I believe templating engines are swappable, however.
Overall, my content is so simple (photos + text) that the usability issues don't bug me yet.
You end up serving logo-bad253c1.jpg as your asset file name, so you can cache it forever with nginx, and if the logo changes, the asset's filename gets changed.
With Jekyll-Assets (a plugin) all of that is taken care of for you under the hood. You just reference {% image logo.jpg %} in your templates and it does the rest when you build your site.
Doing things like converting SCSS to CSS and other optimizations are included too, but the main issue is I don't think Hugo has anything for that cache busting strategy that works in a generic way (adding a querystring is no good because a lot of proxies strip out that data).
Hugo v0.43 has inbuilt cache busting on the roadmap, and Hugo v0.42 will probably be released in about a week.
Unfortunately Jekyll with Docker for Windows doesn't work. The file watcher is completely busted (even with polling). It's strange too because every other language / framework works fine (Flask, Rails, Phoenix, Node), etc. It's just Jekyll that's broken.
[0] https://github.com/11ty/eleventy [1] https://www.netlify.com
I haven't been working on it much lately, though, as it reached the point of my own personal itch being scratched.
I wrote my surrounding static text as a Common Lisp program; relevant BLOBs are put into a resources directory. Blog entries are in Markdown, then read into the program, transformed, and the entire thing spat out as HTML.
It then uploads to S3 and renders out in a domain. I'll be moving to the Google cloud edition of that sometime in the next 4 months, I figure.
I've dinked with wordpress, blogger, tumblr, livejournal, dreamwidth, and other platforms, along with 1 or 2 other static site generators, along with writing my own static site generator. This beats all of them in terms of maintainability and simplicity.
I'm a no-name software engineer and this is a way to write down things that I want to share with people. It works really well.
For the curious, here's an out of date edition of the site as Lisp: https://gist.github.com/pnathan/d57bb0e95fa68552a51755814844...
It's not very socially media aware or SEO-savvy of me, but I'm doing it as a fun way to build a fun website, which was something people used to use the internet for.
I only pay for the domain via namesilo.
I used to use Tumblr but moved to the static site generator because - I wanted full flexibility - I didn't use web GUI to write or redesign my blog - Tumblr looked outdated at some point - and this could happen to any platform.
Can import Wordpress, easy editing with Wagtail, sane templating from Django.
If Netlify ever dies, it would take me all of 15 minutes to get my site back online on a VPS somewhere.