Today, I’m down at Google in Mountain View at Techraking, a gathering of technologists and investigative journalists. It’s been super inspiring because of the fresh to me perspectives — I’d love to help Portland media outlets with projects like those I’ve heard about.
At lunch, I learnt I was to lead a small group breakout on “the future of the CMS.” To keep the discussion going, we started out by brainstorming the things we liked and want to improve our respective software, and then did a roundtable to identify our six month personal goals.
Some things people like about their CMS:
- Drupal done well is easy to use; there are a ton of modules
- Affordability, open source is cheap
- Community to work with
- Many different homepage templates to choose from depending on the stories of the day
What people would like to improve (lots of conversation, as expected):
- Data portability
- More headless; produce output other than HTML
- Scalability, faster when many people are working in the admin
- Less steps for completing common, simple tasks
- Integration with story budgeting, calendaring; API for story flow
- Magical WYSIWYG editor; auto-save that works; track changes
- Support structured data / semantic markup
- Customization for story layout
- Small pieces loosely joined; better integration with other services
Given the short notice, I thought the breakout session went quite well. About twenty people showed up. In terms of what worked:
- Small group discussion; knew enough backgrounds to call out different people to talk
- Noted salient points on the whiteboard as a way of plotting direction
- I enjoyed the “what are you going to work on in the next six months” takeaways at the end
Next time, we should:
- Figure out the location ahead of time so we don’t waste time finding it
- Have people introduce themselves if they haven’t spoken yet
- Every fifteen minutes, have something for everyone to participate in so people don’t check out
Co-Authors Plus makes it easy to add multiple bylines to a given post, and has full support for custom post types. Out just a moment ago, v2.6.2 has the following improvements:
- AJAX user search matches against first name, last name, and nickname fields too, in addition to display name, user login, and email address.
- Comment moderation and approved notifications are properly sent to all co-authors with the correct capabilities.
- Filter required capability for user to be returned in an AJAX search with ‘coauthors_edit_author_cap’. This defaults to ‘edit_posts’
- Filter out administrators and other non-authors from AJAX search with ‘coauthors_edit_ignored_authors’
- Automatically adds co-authors to Edit Flow’s story budget and calendar views.
- Bug fix: Don’t set post_author value to current user when quick editing a post. This doesn’t appear in the UI anywhere, but added the post to the current user’s list of posts. See related forum conversation.
- Bug fix: Properly cc other co-authors on new comment email notifications
- Bug fix: If a user has already been added as an author to a post, don’t show them in the AJAX search again.
- Bug fix: Allow output constants to be defined in a theme’s functions.php file and include filters you can use instead.
Please post any questions, bug reports, feature requests, etc. in the WordPress.org forums. If you want to contribute code, I’m eyeballing co-author management in Quick Edit and guest author functionality for v2.7.
For WordPress.com VIPs, this update has already been deployed to the shared plugins repo.
The function of a newsroom in the future is to coordinate the voices of the world to produce a coherent news product. That job will be done in very much the model that Tumblr is doing it. You could have started with a blogging community or you could have started with a news organization, but they’re both heading to the same place.
The Times of course has the best newsroom. So why don’t they evolve a blogging platform like Tumblr’s? They should have. I’ve been begging them to do it since the mid-90s. There’s still time to gather some of the leftover energy in the web, and to be prepared to catch some of the deserters when Facebook, Tumblr, Twitter et al stumble at growing into the space formerly occupied exclusively by the Times, Wash Post, etc.
But less time remains all the time.
Dave Winer — NYT growing the wrong way.
Chiefly, though, I make sure I don’t rely on other people to find stuff for me to read. I mean, I do, of course; everything I’ve described so far is powered by other people. But I feel strongly about also hunting for material on my own, which is why RSS remains a huge part of my life. I subscribe to 881 feeds, although recently, in a moment of sanity, I decided to focus on about 200 of them that I find most valuable. (To pick those choice feeds, I mostly followed the advice of Marco Arment: “RSS is best for following a large number of infrequently updated sites.”)
RSS is frequently said to be a dead technology, which is silly on a lot of levels, but I don’t begrudge the many people who say that, for them, Twitter has replaced RSS. It’s just that I place a premium on reading stuff that others aren’t and don’t find that my Twitter stream reliably reaches into the bowels of the Web.
Zach Seward — Getting the News
Currently, works of journalism (articles, videos, galleries, graphics, etc.) no matter what subject (news, sports, entertainment, business, features, investigations, etc.) are quantitatively measured the same. An investigative piece that might be nowhere near as popular in pageviews across a mass audience (yes, sometimes, they can be) is quantitatively measured the same way a celebrity death story is. Either story could make a sensational splash, truly connect emotionally with readers, or both. Each has value, but there are different kinds of values across different subjects journalists cover.
If we value impactful accountability journalism, why are we quantitatively equating it one-to-one to entertainingly impactful news? For example, when an investigation is published that saves taxpayer money or even human lives, we should instead try to measure these in a more multi-dimensional way — instead of merely the simplistic ones — and measure them differently from journalism works that have different goals. We should do this not just because the quantification would be more accurate (again, still imperfect), but because it would be a better model of the complex real-world response.
Greg Linch — Quantifying impact: A better metric for measuring journalism.
Specifically, editors at separate organizations asked us the same question: Can you share some of that data with us? You know, the topic data and the data on authors?
Begrudgingly, we agreed, and started to send out reports on a monthly basis.
Editors: “Hmm, this is great! Can we get this quicker?”
Parse.ly: “Uh, sure. We can give it to you weekly.”
Editors: “Awesome! Actually, it’d be great if we could get this daily.”
Parse.ly: “OK, what’s up here? Why do you care more about the data than the recommendations?”
Well, as it turns out, nobody had really showed them this data before, and the data was simply eye-opening for the editorial team. They were using it to go beyond monitoring individual articles to understanding what was resonating with their audience.
Queue the second Aha! moment in early 2011. We took a step back and did some research on analytics tools for online publishers. What we found was astounding. Almost no innovation had happened on the analytics side for online publishers. Most tools were one-size-fits-all systems that treated an e-commerce site the same as a content site, and obviously, that’s not the way to do it.
Content-based sites are dramatically different than an e-commerce property from both a data and business perspective.
It’s no wonder these publishers were clamoring for data that provided fresh insights on their property. Publishers need to know how their content breaks out by topic, what causes a post to go viral, why one author does better with search traffic than another, and a bevy of other key insights that are specific to their needs. We knew this was a big opportunity, and decided to dive head-first into the analytics space.
Sachin Kamdar — Hello Publishers, Meet Dash
New York Times releases code to help journalists collaborate on WordPress, other platforms. Track changes within the WordPress editor. Code is available on Github; it would be awesome to see this support realtime collaborative editing too. (via Steve Myers)
Pipe Dream in numbers. 7,763 articles containing 4,136,279 words written by ~380 authors in the BU Pipe Dream’s export from College Publisher.
How to manage a proper multi-author WordPress blog. Latest version of Edit Flow makes the list of recommended tools. Interestingly, at the top of the list is a team blog, P2 in fact, for authors and editors to discuss ideas, share links, etc. Now, if only that were embedded within the admin too…
Today, MLK day even, two new sites launched on WordPress.com VIP that I’m personally pretty excited about.
PandoDaily is a brand new tech site started by Sarah Lacy, former senior editor at TechCrunch. From her announcement post:
We have one goal here at PandoDaily: To be the site-of-record for that startup root-system and everything that springs up from it, cycle-after-cycle. That sounds simple but it’ll be incredibly hard to pull off. It’s not something we accomplish on day one or even day 300. It’s something we accomplish by waking up every single day and writing the best stuff we can, and continually adding like-minded staffers who have the passion, drive and talent to do the same.
So… this sounds like a newer, better, and fresher TechCrunch starting from scratch. And she’s recruited Michael Arrington, MG Siegler, Paul Carr and Farhad Manjoo as regular contributors. Props to Sara Cannon for pulling off the design.
Grist, a non-profit environmental news publication, is near and dear to my heart. It’s why I’m on the technology side of publishing instead of photographing in the third world. In summer 2007, I worked an awesome web production internship where, in exchange for a bit of copy and pasting into the CMS, I had the freedom to explore publishing on the web and to start developing my skills. That was back in the days of Bricolage; Grist has since been on ExpressionEngine. Props to Matt Perry and Nathan Letsinger for making the switch happen (and to the Otto and Nacin show for their support).
Want to help publishers kick ass with WordPress? Come join my team — we’re hiring.