“Keeping tabs on your creation is hard, I mean, look at humans”.
I was randomly flipping through some portfolio sites the other day when I stumbled on an interesting profile — A Web Developer, who also happened to be a writer. With a couple of clicks, I found a link to his blog — Medium. Only this time, I wasn’t welcomed with a myriad of insightful articles and content, but a 410 error, saying:
Well, that sucks.
As I was interested in finding content written by this individual, I did a couple more digging around his portfolio; perhaps I’d find somewhere else where his works lay untouched…Nothing.
Of course, this was just my experience, but what’s to say there aren’t a dozen more people with similar experience (not to mention, recruiters)? Don’t get me wrong, blogging platforms like Medium and Devto have rules and codes of conduct guiding writers on how to use their products. Sometimes, the lines are a bit too blurry for you to see when you’ve stepped out of them, or, simply put, Nobody ever reads these things.
These things might be too small a policy violation to hurt anyone, but you still get locked out, and your contents confiscated. How to solve this? Just build a self-hosted blog, that way you and only you can guarantee the 24/7 availability of your content online. Here’s how to get started.
PS: I wrote a guide on how we built Devjavu. If you’d like to read a practical example, here’s one:
Domain Name
The first step would be to get a domain name. Naming things are hard. But here’s an excellent resource to help you develop catchy titles.
Be sure to choose a reliable provider, as the wrong service provider can be frustrating. Paypal left the chat_,Whogohost turned on DND._ One recommended Domain name provider would be Hostinger. You can buy a .com domain name for as low as USD 8.99 per year (mostly recommended because of their decent customer service).
PS: This is not a paid Ad. *psst! Hostinger, if you’re reading this, give me a call, who knows, we might work something out.
Another recommended option would be Namecheap. However, it is best to look up some of these providers on Trustpilot to get an idea of their reviews.
Hosting
You’d need to place your blog on someone else’s computer, aka the cloud. For this, there’s the cheap option and the not-so-cheap option. Note that the affordable option may require a bit of technical know-how to execute.
Whether or not you need a cheap or expensive option is determined by the technology stack you choose to go with (more about this further down).
Cheap/Free Option:
And pretty much any free static site hosting service. These services allow you to host static pages (most of what makes up a blog) for free (at least at the time of writing). The only disadvantage might be the technical know-how requirement. Some of these options require hosting/deployment knowledge. I wrote about deploying to some of these platforms here.
Not-so-cheap Option:
- Shared hosting: You can buy shared hosting from Hostinger or any other provider for about 1.99 USD per month. Of course, there may be cheaper options out there to choose from. Hostinger is one I’ve used extensively over the years and can recommend.
Development Stack
So far, you have a fancy name and have decided how you want to host your blog site. Now how do you get one up and running in the first place? Let’s discuss some of the options you have for building your blog. We’ll start from the least complex and walk our way up.
Low-code Website builders (Not so free)
Some blog development options require no code and are simply plug-and-play/drag-and-drop, although they aren’t free. Some of these include;
- WordPress Blog platform (alternatively download the WordPress blog tool and manually manage your blog)
- Webflow
- Wix
- Blogger
- Drop in Blog
Static Site Generators (SSG)
If you have some technical knowledge in web-related things you can go with Static Site Generators. There are a whole lot of options to choose from. See an extensive list here.
PS: It’ll be helpful to know markdown to an extent, as most of these options are built with markdown in mind.
The good part about the SSG options is that they’re mostly free to use or open source. The list is extensive; so here’s my filtered list:
- Next.js — if you have experience with React
- Hugo — If you have experience with Go (or any templating engine). The Hugo documentation is pretty extensive to guide you. There are also free themes to get you started.
- Gatsby — Also built around React
- Nuxt + Nuxt Content— If you have some Vue experience
- Gridsome — Also built around Vuejs
Building From Ground Up
If you’re feeling up to it, and time isn’t a factor for you, then you can decide to build your blogging platform from the ground up. If you do go with this option, here are some points to consider:
- Datasource — You need somewhere to store your data (images, blog posts, user accounts); this can be a managed database from any provider. Alternatively, you can use less costly options, like Github, or purchase a shared hosting plan and set up a database.
- SEO — most of the other options are out-of-the-box SEO friendly, so you mostly wouldn’t need to think much about it. As for building from scratch, you have to take care of SEO properly. Consider if you’d be building a Server Side or Client Side Rendered application.
- Editing Tool — The assumption is you would need an admin interface to publish your blog. For this, you can integrate a plug-and-play markdown editing library, or build one from scratch if you’re feeling funky.
- Design — Deciding what your blog should look like can be a hassle. Here’s a list of inspirations on Dribble to help give you a not-so-vague picture of what you can build.
- Templates — If frontend design isn’t your strongest forte, don’t be shy to look up templates to get you off the ground with that. Here’s a list of interesting templates you can get started with on Themeforest.
Conclusion
In retrospect, managed blogging services like Medium are probably the simplest options but, you’re now aware of the dangers around them. I may have covered less detail than I expected, but feel free to ask questions in the comments, and I’d gladly answer them.
Cheers ☕️
