20,000 views milestone, what I've learnt about blogging so far

🎉 Last week I hit 20,000 total views! 🎉

When I posted my first article on dev.to last July (2020) I never imagined that I'd be sitting here a few months later seeing +20,000 total post views on my stats dashboard but somehow I've achieved it. Big shout out if you've read one of my articles!

Why am I creating an article around this?

Answer: For more views... joking... sort of.

When I was approaching 20,000 total views I realised that the best way to celebrate this milestone was with a post, given that this is a blogging platform. I decided that I wanted to discuss my experience during my first few months of blogging. Hopefully, this will achieve a few things:

Inspire someone to start blogging. The most difficult thing is just to start and publish that first article, it took me years.
Document lessons that I've learnt so far. In life we're almost constantly improving, writing articles if definitely no different.
Describe my process. How do I develop ideas and turn them into full-blown articles?

3.1 Hope that someone calls me out regarding my process in the comments with a differing opinion or advice so that I can continue to improve the standard of my posts. I'd massively appreciate the feedback 🙏 .

What I've learnt

In no particular order.

Post titles matter. They're displayed on the Dev.to homepage and are what Google displays. Ideally, they should both summarise your article and entice users to read it! A couple of months ago, I posted an article which gained 25 views over two months. I modified the title to include the technology used and a few days later the count has tripled. It's not much but it proves it has an impact. - The post in question.
Keep posting. Sounds obvious right? My first few posts didn't get many views but over time the view count has risen. Additionally, every post that you complete you're becoming a better writer as you gain more experience.
Don't be discouraged by a low amount of reactions. I'll be honest, I usually forget to react to a post once I've read it, I'm sure many other people do too. Moreover, I have a tutorial that explains how to use EmailJS with React. That post doesn't have many reactions, however, I get notifications when the form is used and so far I've had a lot more test emails than post reactions.
Post what you find interesting. Most of the posts I've read regarding how to increase your views tell you to research which search terms are popular. While I might have been able to get more views this way, for me that would make blogging feel like a chore. When writing an article my primary aim is to teach the reader something, whether that introduces them to something interesting or guides them through a tutorial. Then when I gain a view or a reaction, I know that I've had a positive impact on their developer journey.
Write about what you're working on. When I'm working on a project I try to determine whether there is an angle I can use to write about it. My first series of blogs was documenting how I rebuilt my Dad's website in Next.js and contains my most popular posts.
Use a grammar checker. So many articles I read on blogging sites have little grammatical errors that distract the reader and ruin the flow of an article. I use Grammarly (free) in an attempt to keep my writing to a high standard.

My process

When I create an article for my blog this is the rough process that I follow.

Starting a new post usually goes one of three ways:
1. Jot down a random idea as a new post title and let it sit there for a few days/weeks until I feel motivated to write about that particular subject or create the project in mind.
2. Have an idea alongside a sudden burst of motivation, start writing straight away (rarely happens btw).
3. Realise I'm working on something that would be cool to tell people about. Write a rough post while developing the project - this is my favourite approach as I find it the most efficient, especially for tutorials.

The point is I don't have a strict method for starting a blog post, I just do it when I'm feeling it.

Once I'm in the zone and am focussing, the rest of the writing goes like this:

Determine the focus of the blog. What part of the initial idea is going to be the most unique and helpful to readers. Should the blog be a tutorial for people to follow or just to build knowledge on a subject?
Read the article back a few times, editing sentence length and changing some words.
Add 4 tags (Dev.to max). I try to go for ones that have descriptions as they are usually the most viewed ones. Only add tags that actually describe the article.
Edit the title from the initial idea to reflect the articles finished state. See above for more information on how I write my titles.
Post! Then sit back and pray for some views!

What I plan to do next

In the next six months, I'm aiming to reach 50,000 views. And, by the end of the year, I want to achieve 100,000 views. To achieve this I will:

Create more posts!
Update old posts with new content and correcting tutorials where the underlying software has changed.
Publicise my posts across the web and share them on Linkedin and other social sites. So far I haven't advertised them at all and rely on followers on dev.to, it's algorithm and Google rankings to gain views on my articles. This would be beneficial to gain more views, but means advertising my writing to people that know me - so we'll see whether I actually do it or not.

Summary

I've thoroughly enjoyed my first few months of blogging on Dev.to. Now that I've crossed the initial "do I really want people to read what I think" stage, I'm starting to find writing actually quite relaxing.

Let me know in the comments what you think about my thoughts, what I've learnt and my process, and tell me yours so I can improve mine.

Thanks for reading!