DevRel Content Strategies

1 minute read

The very first developer relations online meetup of Stockholm was streamed live on Facebook on April 15, 2020. It was also recorded and later published on YouTube for those who couldn’t attend.

The event was organized and streamed by Oleg Pridiuksson, who is a decade-old experienced developer advocate who worked for great companies like King and Unity. He is now a developer relations program consultant and basically founded the Developer Relations Sweden meetup group.

There were three speakers: Hassan Al Kazmi, who is an artist advocate at King, who talked and answered questions about “how much support should a developer advocate provide”. The next speaker was Janina Łaszkiewicz, an agile coach, community manager, founder of Eventspace.by, who also talked and answered questions about “doing events so developers like them 3000”. Their talks were more of an unconference, where Oleg used to ask questions and the speakers would answer and discuss the answers. You can watch the 5 minutes summary of the online event.

I went into reverse by presenting with slides about “DevRel content strategies with a focus on SEO optimization for developers”, instead of the casual unconference style.

My talk was based on an article, named “Risk vs. Reward: How to Build a Diversified Content Portfolio” by Ryan Law. I took this article as the basis of my talk and then added the sauce of experience on my Medium articles about one single article about security, “Secure Code Review and Penetration Testing of Node.js and JavaScript Apps”, and a series of articles I’ve published about load testing with k6. I took the stats from Medium and tried to re-frame and present them in a way the conforms to the recommendations laid out in the article.

Although I have presented the talk on a DevRel event and it is named “DevRel Content Strategies”, it is still beneficial to anyone publishing content over the internet, no matter the area of interest.

I hope you’ll find it useful and I am happy to hear your feedback.

Updated:

Comments