71–80 of 137 posts
I ended up staying with Hugo because I post loads of photos and image optimisation, or responsive images, was much easier to implement in Hugo.
I heard Astro now has better image processing, so I might give it another try as migrating templates and posts between Hugo and Astro was actually pretty easy.
You could probably get far with Wordpress. Why? Because if you're technical you can navigate the tricky setup well, and it's made in a way to support a lot of things for non-technical people. Of course you gotta get it running (or pay people like WP Engine), but you're going to end up with a thing that will work. That or dev.to is a good spot I think.
I also use for manually saving some comments/replies I post on social media Scribbles - a simple blog engine. I publish them on a subdomain[3] in case you want to see how it looks like.
Here are some things I would look for when choosing a platform:
1. Bring your own domain - this is very important because it allows flexibility to switch to any other platform while keeping your audience/place
2. Export as markdown - while markdown is not the best format, still exporting to it makes the possibility to migrate easier.
3. Have support for RSS - I use RSS to track a big number of technical blog and consider it important
4. Have support to display author name and date of publishing. This is important for technical topics to allow proper citation and to put the knowledge in context.
- [0] https://hashnode.com
- [1] https://allaboutcoding.ghinda.com
- [2] https://scribbles.page
- [3] https://notes.ghinda.com
-s anyway.
I run allaboutberlin.com for a living. I switched from Craft CMS to a homebrew static site generator (Markdown + Jekyll) and it was a game changer. Static sites are almost maintenance-free. They cost pennies to host. You work on your content using the tools that you love, if necessary offline. There are many excellent markdown editors and no CMS comes close. Everything is under source control and deploys with a push.…
Why not roll your own? Sure, you have to build it and maintain it, but isn’t that in the spirit of programming? It’s fun.
I use substack thinkingthrough.substack.com I have hosted many in the past. Self hosted, wordpress, and a php version (I forgot what it was called) The biggest problem with all those was dealing in spam comments and bad cross links. Then I tried medium but it didn’t use to share subscriber emails. Ended up migrating to Substack and been very happy with it for past 3 years
Have you considered not having Comments? That would completely eliminate spam and ~100% of your troubles.