…and I am typing this in the new Gutenberg editor.
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?
In the end, this move is personal. I decided to look for a role at an organization that was remote-first. I wanted to try something new, outside my usual routine of journalism product management (although you should totally keep doing that, please), and I wanted to be in a position where I could focus on The Work for a while, rather than The Work About The Work, although it will always interest me, too.
So. If you hate your CMS, hit me up. And. AND! If you lovvvvvve your CMS, I want to hear all about that, too.
Oh, and, of course, Automattic is hiring.
Remember when I remembered blogging? Hard to believe that was almost four months ago, but there it is. Meanwhile…
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.)
- I wrote a Kinja post from my phone. It was about tacos and emoji and terrible garbage data. And writing on phones.
- I wrote a Tumblr post from my phone. It was about beach vacations and long books and reading habits. And writing on phones.
- That aforementioned Medium update happened, and in the process of trying it out, I wrote a “brief” guide to things like Apple News and Facebook Instant Articles and Google AMP and the stuff Medium was launching and it was “fun,” but also actual publishing labor. I can’t remember if I drafted any part of this on my phone, but maybe.
- Writing in Medium was remarkably pleasant, and they’re proving to be a really powerful platform for driving engagement with push notifications, at least until everyone gets annoyed and turns them off, and also we’ve been listening to the Hamilton cast album non-stop (get it?), so I wrote a thing about what Product Managers can learn from Hamilton the Musical. And that really was fun, no scare quotes.
An aside: ALSO OTHER THINGS ARE HAPPENING.
Anyway, that’s what I’ve been writing about. More to come. Medium has been fun.
One new development related to all these thoughts about content management systems for actual writing: WordPress is doing something lots of people are doing, moving to fancy modern node.js frameworks for publishing tools, not just for what I would usually call reader-facing UX.
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.
I really like what Daniel is doing with his “statuses” in WordPress. Assume this is a custom post type. I think he started blogging these while taking a(nother) break from Twitter.
In his RSS feed, these show up with a plain title of “Status” — I find this to be sort of amusing.
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.
Useful list of WordPress plugins for publishers: Plugins for publishers, April 2011 edition
A WordPress plugin to help readers correct your errors: MediaBugs, Scott Rosenberg’s Knight News Challenge-funded project, now for WordPress.