I’m a fan of content marketing and you’re in luck because dev-related content is in high demand, there are channels to promote such content (reddit, hackernews), and if you do it right, it won’t be spam.
For context, my last 3 blog posts (https://blog.kowalczyk.info/article/19f2fe97f06a47c3b1f118fd06851fad/lessons-learned-porting-50k-loc-from-java-to-go.html, https://blog.kowalczyk.info/article/fc9203f7c72a4532b1ae51d018fef7b3/trade-offs-in-designing-versatile-log-format.html, https://blog.kowalczyk.info/article/39a15945117440d99a9ef0f7de1b618a/the-things-we-do-to-ship-desktop-software.html) did get lots of reads from Reddit, HackerNews and as a result they also appeared on smaller sites like lobste.rs and featured in relevant newsletters (in my case Go-related newsletters).
Especially the “lessons learned porting 50k loc from Java to Go” blew up.
My formula is simple:
- write an in-depth, technical post
- post a link to it in the right place (sometimes it’s hacker news, most ofthen the right sub-reddit)
- participate in the discussion. Here’s an example of me participitaing: https://news.ycombinator.com/item?id=19589614 (kjksf). I use https://f5bot.com/ to be quickly notified about posts about “blog.kowalczyk.info” and projects
Here are some ideas for articles you could write:
- there’s an infinite number of articles related to webpack (there’s already plenty of content but there’s also almost infinite appetitie for new content, even if it says the same things as existing content)
- a subset of previous: every time webpack is about to add some new, notable feature, write a blog post about it
- “10 tips to reduce the size of webpack bundles”
- “The least bloated markdown parsers for you web app” (i.e. take popular markdown-to-html libraries, see which one is the smallest, write an article about it)
I’ve already said it twice, but I’ll say it 3rd time, for emphasis: in-depth content, long articles. Not fluffy-long but lots-of-information-long. Look at examples of my posts above. My writing style is “no fluff, just the facts” but even then those articles are long.
The best content is so-called evergreen like tutorials, books, cheat-sheets. They are the hardest to write but long term they provide the best ROI. An out-there idea: find an already popular, free book about webpack and offer to buy the rights from the author and add tasteful ads for your service.
It’s like buying an ad on a website by buying the whole website. This might not be in your budget (I have no idea if someone would be willing to sell and for how much but it doesn’t hurt to ask them).
Also, for SEO change product and domain name to webpacktracker.io, webpackbundletracker.io webpackbundleanalyzer.io or some such. You really want “webpack” in your domain name.
Another tactic I use is to participate in relevant discussions and plug my websites / projects when appropriate (see e.g. https://old.reddit.com/r/NotionSo/comments/bir18c/thoughts_on_notion_vs_evernote/em2k6tp/?context=0 for how I plugged my 2 website while not being spammy)