I’m starting a new job today as an Enterprise Growth Engineer on the WordPress VIP team at Automattic.

I’m a little bit excited.

If you know me at all, you know that no matter the title, my job in news has always been to evangelize for new technology to serve journalism. As a reporter, an editor, a product manager, a team leader — I’ve tried to give journalists the tools and training they need to successfully reach (and move! and impact!) their readers, while growing their audience and building sustainable models for the future.

WordPress has often been a part of that equation for me. I suppose my first of many CMS migrations was the move of my own blog to WordPress from Blogspot, even if it was only a few weeks after I started writing here. Later came a WordPress theme for the blogs at what was then Inside Bay Area (in the 19th iteration since, it’s currently the East Bay Times but has somehow maintained the stories I wrote as an intern in 2006), then a move of all the Santa Cruz Sentinel’s blogs from pMachine (an early Expression Engine product IIRC) to WordPress, plus a couple Joomla (and Mambo?) verticals, too. I used WordPress as a platform for podcasting, for daily video newscasts, for blogs, naturally, and even once drafted plans for a university journalism department website, among other non-news odds and ends.

###

When I left corporate media for the nonprofit news world in 2015, it felt like I was starting a tour of duty. I had heard the same phrase used by people taking government tech work at places like 18F, and it fit the way I felt at the time. Would I stay in the nonprofit world for good? What would I learn, and how would I use it in the future? Would I look for another nonprofit role when the first one ran its course?

Here’s what I did after I posted that real live actual blog post on my blog here at ryansholin.com:

I wrote a Medium post from my phone. It was about Sleater-Kinney and writing and content management systems. And about writing on phones. (Not too long after, Medium updated lots of features, including their mobile writing/editing screens, so some of this was happily and quickly made totally invalid.)

As a matter of fact, even though I don’t quite understand how this works, I’m typing this very blog post in what I have to assume is the new node.js powered framework on WordPress.com, which hopefully is going to publish as intended on ryansholin.com, which still runs using the standard latest dot-org build.

Workshop: Advanced WordPress with NYU’s Studio20: Daniel Bachhuber’s notes from a workshop with Jay Rosen’s students. Sound basics and key points of entry for advanced manipulation of content types, version control, and (as always with Daniel) a metadata layer of his thoughts on education.