Gutenberg is the future of content in WordPress. It will deliver the elegance of Medium but with far more power and flexibility of layouts and content types
I love how this looks and works and it’s certainly about time that WordPress had alternate means of publishing to its platform. (I miss the days when Twitter had thousands of different configurable apps to post to it, though these were far simpler.)
Not only does it remind me a bit of Medium.com’s interface, it is highly reminiscent of Aaron Parecki’sQuill editor which uses the open Micropub spec to publish to the Micropub endpoint on my blog. Though his isn’t as fully featured as the Gutenberg example, he could certainly add to it, but then it could be used to publish to any site that supports the spec.
The nice part about Micropub (and the fact that there’s already a Micropub plugin for WordPress) is that developers can build multiple competing publishing interfaces to publish to any website out there. (Or developers could even build custom publishing interfaces for their clients.)
In fact, if they wanted to do a highly valuable pivot, Medium.com could add publishing via Micropub to their platform and really become the billionaire’s typewriter that some have suggested it to be.
Automattic, the technology company that owns WordPress.com, has a beautiful office in a converted San Francisco warehouse, with soaring ceilings, a library, and a custom-made barn door. If you like the space, you're free to move in. The office at 140 Hawthorne went on the market after CEO Matt Mullenweg came to the realization not...
The state-of-the-art in feed readers was frozen in place sometime around 2010, if not before. By that time most of the format wars between RSS and Atom had long since died down and were all generally supported. The only new features to be added were simple functionalities like sharing out links from readers to social services like Facebook and Twitter. For fancier readers they also added the ability to share out to services like Evernote, OneNote, Pocket, Instapaper and other social silos or silo related services.
In particular, some asked about alternate projects for basing education projects around which aren’t WordPress. Some suggested using WithKnown which is spectacular for its interaction model and flexibility. I suspect that many in the conversation haven’t heard of or added webmentions (for cross-site/cross-platform conversations or notifications) or micropub to their WordPress (or other) sites to add those pieces of functionality that Known comes with out of the box.
Another section of the conversation mentioned looking for ways to take disparate comments from students on their web presences and aggregating them in a more unified manner for easier consumption by the teacher and other students (as opposed to subscribing to each and every student’s RSS feed, a task which can be onerous in classrooms larger than 20 people). To me this sounded like the general concept of a planet, and there are a few simple ways of accomplishing this already, specifically using RSS.
I was also thrilled to hear the ideas of POSSE and PESOS mentioned in such a setting!
An Invitation to Attendees
I’d invite those in attendance at the Domains 17 conference to visit not only the Indieweb wiki, but to feel free to actively participate in the on-going daily discussions (via IRC/Slack/Matrix/Web). I suspect that if there’s enough need/desire that the community would create a dedicated #education channel to help spur the effort to continue to push the idea of owning one’s own domain and using it for educational purposes out into the mainstream. The wiki pages and the always-on chat could be useful tools to help keep many of the educators and technologists who attended Domains17 not only connected after the event, but allow them to continue to push the envelope and document their progress for the benefit of others.
I’ll admit that one of my favorite parts of the Indieweb wiki is that it aggregates the work of hundreds of others in an intuitive way so that if I’m interested in a particular subject I can usually see the attempts that others have made (or at least links to them), determine what worked and didn’t for them, and potentially find the best solution for my particular use case. (I suspect that this is some of what’s missing in the “Domains” community at the moment based on several conversations I heard over the past several days.)
Micro.blog just launched in beta recently and one of the biggest things burning up the airwaves there is how to easily post content from one’s own site as notes without including titles. Why? If a post has a title, then micro.blog thinks it’s an article and just posts the title along with a permalink to it rather than the desired content of the status update.
In the long run and for easier mass adoption, I’m hoping Manton can figure out how to parse RSS feeds in a simpler way so that users don’t need to do serious gymnastics to import their microblog posts from other sources. I’d imagine it’s far easier for him to adapt to the masses than for the masses to adapt to micro.blog. At the very worst, he could create a checkbox on the RSS import feeds to indicate which feeds are status updates and which aren’t and this would quickly solve the problem for the average user as most CMSes allow users to define custom feeds based on content type.
While there are a number of people doing things from simply adding date/time stamps (which micro.blog ignores) to functions.php tweaks to to custom plugins, some of which I’ve tried, I thought I’d come up with my own solution which has helped to kill two proverbial birds with one stone. (Note: I’ve listed some of these others on the Indieweb wiki page for micro.blog.)
The other day, I’d had a short conversation about the issue in the Indieweb chat with several people and decided I’d just give up on having titles in notes altogether. Most people contemplating the problem have an issue doing this because it makes it more difficult to sort and find their content within their admin UI dashboard which is primarily keyed off of the_title() within WordPress. I share their pain in this regard, but I’ve also been experiencing another admin UI issue because I’ve got a handful of plugins which have added a dozen or so additional columns to my posts list. As a result the titles in my list are literally about four characters wide and stretch down the page while knucklehead metadata like categories needlessly eat up massively wide columns just for fun. Apparently plugins aren’t very mindful of how much space they decide to take up in the UI, and WordPress core doesn’t enforce reasonable limits on these things.
So my solution to both problems? If found a handly little plugin called Admin Columns with over 80,000 users and which seems to be frequently updated that allows one to have greater simple control over all of the columnar UI interfaces within their sites.
In just a few minutes, I was able to quickly get rid of several columns of data I’ve never cared about, expand the title column to a reasonable percentage of the space so it’s readable, and tweak all the other columns to better values. Even better, I was able to add the slug name of posts into the UI just after the title columns, so I can leave status update titles empty, but still have a field by which I can see at least some idea of what a particular post was about.
Syndicated copies to:
Sallying forth with my decision to post notes (aka status updates) into my system which don’t have any titles. I suppose I can put some other bit of data into my admin UI to better track them within the system.