First things first. The title of this article may be a bit confusing, and it may make you think I've made an error. I haven't. There's no visual cues for this -- I couldn't think of any to use that wouldn't make this any less confusing -- but the word "Official" is being used in two separate sentences, while the word is only being included once. It reads this way: "It's official." and "Official contributing author." Both are now, officially, true.
I started writing for PowerShell.org this year, with my first article posting on January 2, 2019. As a part of making this commitment, I asked the folks in charge if in time, after a handful of posted articles, that my name be added to the About Us page. Well, it's happened. It happened after ten articles and a commitment to continue adding more PowerShell content. You may not already know this, but I blogged about PowerShell at tommymaynard.com for 4 and a 1/2 years, before deciding to do all my new writing right here.
Perhaps you're asking yourself, why did he bring this up? I brought this up, in order to formally invite anyone and everyone in the PowerShell community to also blog with us at PowerShell.org. It made sense to me to have stopped adding new content at my personal site. I believe that the community should have a central point for forums, discussions, articles, and news, and that it should be here, and that those of us that make up the community, should contribute to as wide an audience as we can.
If you don't already have a PowerShell blog, but have something you want to share with the community, then do it here. Get your feet wet; shoot for writing an article twice a year during your first year. Then four the next. Even if you don't get your name on the About Us page -- and seriously, why not try -- you can add this highlight to your résumé. Stop and ponder that for a moment. Write here consistently, and use it. as a highlight. on your résumé. Here's a small segment from mine (that's all about PowerShell).
If you already have a blog, successful or otherwise, donate two or three articles to PowerShell.org each year. If you'd rather not put a full article here, then just start it here, and then link to the completed article on your own site. Or vice versa. Finish it here and start it on your own site! Maybe mix it up and do both! Please do consider, though, how you can help PowerShell.org with your established influence.
PowerShell has always been about community in conjunction with technology. We have a common thread among us, and what you've been through with PowerShell, should be shared. Let us learn from you; let us help you learn. If you want a chance at mastering PowerShell, then you're going to have to teach about it, in one fashion or another, sooner or later. Build up your own brand and name recognition sure, but consider PowerShell.org and its consistency over the years to promote, to solve problems, to deliver news, and bring people together in person at the PowerShell + DevOps Global Summit. Be a part of that.
In closing, I've included a site link that will help answer any additional questions you might have about blogging at PowerShell.org: https://powershell.org/contributing/blogging-at-powershell-org/. You can even only do it once and totally hate it, but please do get involved here, no matter what you're doing elsewhere. Someone helped you along the way, and so you owe someone else that favor, too.
Whether you're new to writing about PowerShell or not, work with me before you publish, and I will gladly write an introductory, yet brief article about you to introduce your upcoming article. It's not a requirement, but I'm here if you would appreciate that. Let those paying attention, see your effort and willingness to help PowerShell.org with its content and our community.
≥ Tommy Maynard (Twitter: @thetommymaynard)