This really hit me — I spent a long time (several iterations) designing my perfect blogging static site generator, and wrote a few posts about my journey of creating the tool. After those few posts, I’ve had lots of ideas for new ones but haven’t pushed any to completion.
So I mostly just have a blog about creating the static site generator used to generate the blog...
Very nice! Seems easy enough to use. I went overboard with the config.yml and custom templates on my side [0]. My goal is a Jekyll drop-in replacement. Btw, I love how your Contributing section resembles what I wrote in my Readme. :)
I wrote my own static site generator for by blog, and it turned out to be enormously useful for a number of different client projects, so I don't regret spending many months of part time effort building the generator at all.
When people say "tools don't matter" what they really mean is that the "from 2004" part matters a lot more than the "WordPress setup" part.
That doesn't mean that static site generators aren't better though, and I'm sure we'll see more and more high volume blogs that are built in SSGs soon.
With web dev and marketing — and probably in many other areas — there is something equivalent of productivity porn that I don’t know what to call. It manifests in lengthy discussions with multiple stakeholders, endless iterations, and many thousands spent on tools that in the end mean nothing on their own. Like, cool, you shaved half a millisecond off your build time and your smartfridge sounds a ding at every successful deploy... What has that done for the bottom line?
People pay good money for books too. I had a co-worker who wrote a sci-fi serial and self-published on Amazon, and now that's all he does. He says he's made more money with this than his whole life coding.
Every day I think more and more I should do the same.
But being a dev, I always had the feeling coding is the way.
I'm not saying I still believe that stuff, but I did when I was a young coder right out of university and I guess that's one of the reasons why people build their own blog setup.
I switched from WordPress to Craft, both on my personal website, and the one that pays the rent.
Working with Craft is a lot more pleasant, but I spent so much time working on things that Wordpress has many plugins for. I also spent a lot of time fighting with Redactor, the WYSIWYG editor that often messes up the "WYG" part. I still have to clear the cache manually using the command line. I'm used to this workflow, but I'm not sure I could teach another editor to use it.
I'm the counter example. I made a medium blog purposely to stop myself falling into this trap but then I didn't consider any of the articles "finished" enough and never posted them.
Blogging had been around for long enough at that point that my first blog post was essentially "sigh I guess I should start doing this thing everyone else is doing".
Started with a home-built system in bash, moved to hosted Movable Type, then switched to Blosxom, and I've been running Blosxom in static mode since 2007.
This is hilarious because I’m currently converting my own blog engine (https://github.com/rcarmo/sushy, which powers https://taoofmac.com) to a static site generator, and have decided to port it to Rust sometime in the future.
I find HTML too complex and dirty for writing while focusing on the content. I chose plain-text with some spices of Markdown. I can generate HTML or other formats from Markdown with ease.
I'm going to start linking https://rakhim.org/honestly-undefined/13/ every time people try to bring up "Git is simple if you understand the model" on Hacker News again.
I was coming to say just that, don’t stop at the referenced comic but browse the eighteen others, you will not loose your time (I particularly like the diff between the frontend conf and the functional programming one) kudos to the author, I’ll be following you from now on
I wrote more than 500 posts on my current blog[1], and much more on other blogs I've had. The first advice I give to anyone who wants to blog is to just use wordpress, don't focus on the presentation, just on the content. Once you're like 10 blog posts in, then feel free to move the content elsewhere, but not before. Anything that prevents you from writing content is friction at this point.
Other advice I also give: write short posts and write unfinished posts. If you wanted to write perfect 10/10 content again and again, you should write a book instead. A blog is about low friction to write. People are interested in your thoughts, get them out there.
Actually even writing on wordpress.com is a bit too much, sometimes I just can't help but do the text decoration (font size, bold, underline). Nowadays, I write the blogs on the evernote first, it just makes your mind of writing more fluent. (Notepad also works, but you may lose the content accidentally.) Once you got the content, move it to a blog site and put down some cosmetics are just easiest tasks to do.
I had to accept the only way I would blog consistently is with one of the severely feature-limited managed plans from Automattic to keep me from tinkering. 18,000 words later, the system seems to work.
Yep. Wordpress is desperately uncool, you will be using a tool old enough to vote, you will be using old, proven technologies, but it fucking works and once you have set up your blog you can just keep coming back to it and actually making posts about whatever you want to share with the world, instead of abandoning it, then coming back a while later to check out a new blog setup built on whatever this month's hot language/framework is.
And you can get plugins to make that Wordpress blog auto-post to whatever the hell people use nowadays. Own your own data, be immune to having it all vanish when something happens to your account on Hot Social Site, or to the entire site.
I write less on my site(1) than I used to, twitter/mastodon has eaten a lot of that energy, but it is still where I go for anything lengthy, and it is still where I post my big comics projects.
I’m the exception to the rule — I wrote my own blogging software to power this site https://psalm.dev/articles but haven’t written about it.
Because it’s very boring! Basically just a souped-up markdown renderer that uses GitHub’s API for some draft functionality. I’ve spent maybe four hours building it in total. I’ve spent much longer writing individual posts.
108 comments
[ 4.5 ms ] story [ 177 ms ] threadI had a Livejournal for my private stuff back then.
But most of my friends had one and they were all over the country so this was the only way to keep up.
So I mostly just have a blog about creating the static site generator used to generate the blog...
Sigh, I guess I should get back to my GitHub repo and fulfill my destiny.
https://github.com/jacobkania/mmssg
0 - https://github.com/petarov/nenu
Signed up to dev.to in 2017 as a new years resolution to write a blogpost every week. Just started to write.
Now, I've written over 200 blogposts on my main blog, over 100 for other blogs, and make my main income from paid writing gigs.
Going to try this in 2021. Thanks for the idea.
But good luck!
Why not start right now? There is nothing magical in January the first. Next 5 minutes is perfect time for a new blog post, for example.
Luckily for me the learning experience has been worth it regardless if not a single person reads anything I post.
That doesn't mean that static site generators aren't better though, and I'm sure we'll see more and more high volume blogs that are built in SSGs soon.
How can something like blogging, something that thousands of boring food and travel bloggers do, be real work or even of value for anyone?
Coding, that's real work, that's what people pay good money for!
So why not create your custom blog before you start writing.
Every day I think more and more I should do the same.
But being a dev, I always had the feeling coding is the way.
I'm not saying I still believe that stuff, but I did when I was a young coder right out of university and I guess that's one of the reasons why people build their own blog setup.
"How can something like blogging, something that thousands of boring food and travel bloggers do, be real work or even of value for anyone?"
You gotta read something other than tech docs and forums.
Working with Craft is a lot more pleasant, but I spent so much time working on things that Wordpress has many plugins for. I also spent a lot of time fighting with Redactor, the WYSIWYG editor that often messes up the "WYG" part. I still have to clear the cache manually using the command line. I'm used to this workflow, but I'm not sure I could teach another editor to use it.
Mission accomplished!
There’s a lot of people who build static site generators and never even write a post.
In fact, I felt so "at home at xkcd" that I kept hovering my mouse over the images for a second punchline. :D
[1] https://news.ycombinator.com/item?id=21768264
Started with a home-built system in bash, moved to hosted Movable Type, then switched to Blosxom, and I've been running Blosxom in static mode since 2007.
Other advice I also give: write short posts and write unfinished posts. If you wanted to write perfect 10/10 content again and again, you should write a book instead. A blog is about low friction to write. People are interested in your thoughts, get them out there.
[1]: https://cryptologie.net/
Personally, minor decorations doesn’t impede my writing by much. What kills productivity, is endless editing while writing the first draft.
https://kyefox.com/
And you can get plugins to make that Wordpress blog auto-post to whatever the hell people use nowadays. Own your own data, be immune to having it all vanish when something happens to your account on Hot Social Site, or to the entire site.
I write less on my site(1) than I used to, twitter/mastodon has eaten a lot of that energy, but it is still where I go for anything lengthy, and it is still where I post my big comics projects.
1: http://egypt.urnash.com
Because it’s very boring! Basically just a souped-up markdown renderer that uses GitHub’s API for some draft functionality. I’ve spent maybe four hours building it in total. I’ve spent much longer writing individual posts.