More Time to Get Ready

So much for writing a daily post on WordPress 5.0/Gutenberg! I’m mostly managing to keep up with the plan to spend 15 minutes a day picking something up about the new release; mostly still a lot of reading. Writing about it is even harder to find time for.

Beginning to think a weekly roundup will do, but we’ll see if I can get more done this week.

Pushing Back the Release Date

Anyway, if you haven’t heard, we all have another week to get ready, as the WordPress 5.0 development team pushed back the release date from Monday, November 19 to Tuesday, November 27. It will be interesting to see if the date slips again.

It is my firm opinion that there is nothing magical about a release date. WordPress does not have to release a Gutenberg product so they can book a zillion sales by the end of the fiscal year. No one is anxiously awaiting the arrival of a shrink-wrapped copy of WordPress 5.0 under the tree in December. Matt Mullenweg has always maintained that Gutenberg would be released when it was ready. The team should stick to that.

On the other hand, Mullenweg told WordCamp Portland that “The hope is that the 5.0 release day is the most anti-climactic thing ever,” because so many sites have already decided to install Gutenberg, or stick with the Classic Editor (a version of the existing editor that is compatible with themes and plugins that are also Gutenberg-compatible). We can hope! I’m going to check out the video at WordCamp.tv too.

As I type this, I’m updating the Gutenberg plugin to v4.3. Still haven’t run into any trouble, but I haven’t exactly tried anything fancy yet.

Plan: Working Through “20+ Tips”

WPLift published a list of 20+ Tips for Gutenberg that will serve as a useful jumping off point for me, I think. Any technical article that starts with learning your way around the editor screen is an article that aims at being helpful to new users.

wordpress-gutenberg-editor-tips-1-1024x622

Alternative Editors?

While strolling through my Twitter feed last week, I saw this great chart from Birgit Pauli-Haack, and sent it around:

Of course, what this means is that if you decide you don’t like editing posts in Gutenberg (or Classic Editor, for that matter), you can use almost any word processor or gizmo that you can write with. Write in your preferred tool, copy and paste into the WordPress editor. See the complete chart in a readable version in the link to the Github project.

Birgit not only retweeted my retweet but also included it in this week’s Gutenberg Times update.

Well, back to testing the tips! If you’ve found something interesting and/or horrifying in your own Gutenberg tests, let me know in the Comments.

Previous Posts in the Series

Getting ready for Gutenberg

Getting Ready for Gutenberg: First Weekend

 

Advertisements

Getting Ready for Gutenberg: First Weekend

Sunday I wrote the first post in this series, “Getting Ready for Gutenberg.” It wasn’t the only thing I did to get ready for WordPress 5.0, though.

Getting News About Gutenberg

Nearly everything I know about WordPress 5.0 and the Gutenberg editor comes from two sources: WPTavern and the Gutenberg Times. If you want to be on top of all things WordPress, here’s where you want to start.

I do not know how Jeff Chandler (aka @Jeffr0) and Satah Gooding do it, but WPTavern takes its journalism very seriously. If it’s news in the WordPress World, the Tavern will have the story within hours. Here is everything they’ve written about Gutenberg in the last two years. It’s a lot. Their WordPress Weekly podcast is also helpful, though a little long for folks like me.

Birgit Pauli-Haack compiles and curates a weekly summary of Gutenberg news at the Gutenberg Times. She also shares much on Twitter. All in all, wonderful stuff. I spend Sunday afternoons reading and clicking on the site.

Getting Ahead of Myself

The other WordPress-related task I completed was to sign up for a one-day online course in designing Gutenberg-compatible themes presented by iThemes next week. From a user’s perspective, I fear that much of the content may be over my head, but I think I will learn something about Gutenberg guts, and perhaps hear what developers think. So it will be good.

If you happen to be a theme developer, you may want to check out the course too.

Monday: A New Beta

One thing I learned from WPTavern today was the release of WordPress 5.0, Beta 3. Got that installed on my test system Monday night. If you want to try it on:

  1. Install and activate the WordPress Beta Tester plugin on any non-production installation of WordPress.
  2. Go to Tools > Beta Testing
  3. Choose Bleeding Edge Nightlies to get the latest stuff. Click Save Changes. This is why you don’t want to put the betas where your live website lives — bad things can happen!
  4. WordPress will tell you there are updates. Download and install. You’ve got the new beta!

Tuesday, I’ll play with the beta a little bit when I’m not closely watching US Election returns.

 

Oh, and if it’s Tuesday, November 6, and you live in the United States — Go vote today! Vote.org will help you if don’t know how to find your  polling place and other critical information. WordPress is about democratizing the Web. Voting is about democratizing democracy.

Getting ready for Gutenberg

It’s November, and many writers are busy starting their novels during National Novel Writing Month (aka NaNoWriMo). While I wish all of them the best of luck, I want to honor a more recent tradition that seems to have fallen by the wayside in the last few years.

At the beginning of this decade, some folks who don’t necessarily write fiction decided to launch National Blog Posting Month (NaBloPoMo). They had the same basic goal as the novel writers: Write and post something every day during the month of November. WordPress joined in as an endorser some years after that, when I first got involved. It was mostly successful for me, in that I wrote an awful lot (we’ll let you judge how much of that was just awful — look for posts tagged NaBloPoMo and National Blog Post Month).

Eventually, NaBloPoMo went away. I didn’t continue the tradition, though there was nothing stopping me. But in 2018, I have a new reason for a big batch of posting in November: the impending release of WordPress 5.0. This is currently set for just two weeks from now, on Monday, November 19 (though it could still slip that date and many folks would like to see that happen).

What in heck is Gutenberg?

The central thing that makes this new release worthy of the major upgrade to v5.0 is the new post editor, codenamed Gutenberg. It’s been in the works since January 2017 and wants to revolutionize WordPress. There are many differing opinions about this.

When I logged in to WordPress.com to write this post, this graphic greeted me:

GutenbergInvite_Screenshot_2018-11-04 Dashboard ‹ Michael McCallister Notes from the Metaverse — WordPress

If you’re running a self-hosted version of WordPress on your own site, you’ve been seeing this for a couple of months, if you haven’t decided to test Gutenberg already.

Gutenberg changes the way you post mostly by introducing blocks of content, instead of just words, paragraphs and images.

How to get ready for Gutenberg

At the end of October, when I went to see if someone had revived the NaBloPoMo concept, it occurred to me that I still really didn’t know much about Gutenberg and the rest of the new release. I’d installed Gutenberg on my test system, but hadn’t done much with it. Life intervenes, and there are always other priorities. But suddenly the release was near, and I needed to get serious about learning it. Ah Hah!

I could spend the month of November trying to get a handle on Gutenberg, and share my attempt to get ready for the release with all of you!

So here’s my plan: I’m going to spend at least 15 minutes a day with Gutenberg, either hands-on with the editor or reading through other people’s takes and tutorials over the last year. I am coming at this with the profile of an ordinary user since I am seriously not an expert … yet. I hope that this month will allow us all to get on the road to being solid users of WordPress 5.0. In the worst case scenario, I’ll be one of the folks who question the sanity of the WordPress Core developers, but I hope not!

Whatever I do, I’ll report it here, ideally on the same day. I hope you’ll join me on this journey.

I also want to hear about your experiences with Gutenberg, and WordPress 5.0 generally, along the way. Have you tried the beta? What do you think? Does it work for you? What doesn’t work, and how can the WP team fix it?

Aside: If you live in the United States, do get out and vote Tuesday.

Inrupt: A Watershed for the Decentralized Web?

When Tim Berners-Lee launches a new project for the World Wide Web, it has an impact. Saturday morning I woke up to the news that Sir Tim had a new project. With an interview with Fast Company and a new website, Inrupt was born, and everything might change.

Inrupt is a startup company that will support the Solid project that Berners-Lee and his research group at MIT has been working on for a few years. Berners-Lee’s business partner, John W. Bruce writes:

Inrupt’s mission is to ensure that Solid becomes widely adopted by developers, businesses, and eventually … everyone; that it becomes part of the fabric of the web.

I love the basic idea of Solid, where you store all your relevant information in a “personal online data store,” or POD, and make your own decisions about what information you share online. If you want to tell people that you’re going to some concert tonight on some online service, go ahead and share it with that service’s Solid app. When you decide that you’re embarrassed that you ever liked that performer, you can revoke that permission, and it disappears, everywhere you shared it.

 

Tim Berners-Lee’s Solid POD (Personal Online Data store), via Fast Company

 

I’m really excited that Inrupt wants to build the ecosystem around Solid, get more developers, more apps. Ultimately, that should lead to more users, presumably leading to an Internet closer to the Web founders’ original vision.

Reactions

When I read the Fast Company piece, and read the Inrupt home page, I admit that I thought “This is really on the right track, and where do I send my resume?” I even filled out the contact form at Inrupt (before I saw the mailing list subscription link) suggesting that when they started thinking about user docs, they should keep me in mind! And yes, I’m following them on LinkedIn too.

After reading every word on their website (OK, maybe I skipped some of the developer parts), I asked myself whether Inrupt was just a way for Sir Tim to cash in on his invention. Not that there’s anything technically wrong with that, but there is a downside.

Just a year or so after caving to the Copyright Cartel on the Digital Rights Management (”Encrypted Media Enclosures”) standard at the World Wide Web Consortium (W3C), you have to wonder whether Berners-Lee has just become another corporate pawn.

Child of Silicon Valley

I don’t know much about John Bruce, Inrupt’s CEO. I’ll be doing more research.

What I do know is this: Inrupt seems to be following one of the traditional Silicon Valley funding paths. Charismatic founder starts company, sucks up a ton of venture capital to stimulate growth, then either goes public with an Initial Public Offering (IPO) or a sale to another big company. When successful, the end game makes the founder rich, and the venture capitalists even richer.

The Inrupt website describes John Bruce thusly:

John led four start-ups, three of which resulted in global acquisitions. John will apply his decades of strategic business leadership and experience with leading software and service companies to launch Inrupt and the next phase of the web.

There’s nothing wrong with this experience, either. I worry though.

Yet, there are more than a few companies in the world of free and open source software that manage to make money without projecting evil onto the landscape: Automattic, Mozilla Corp, Red Hat, and SUSE come immediately to mind.

I’d rest a little bit easier if Inrupt declared itself a Public Benefit Corporation, which bylaws aims to put social good ahead of profit.

I’ll be watching Inrupt’s progress with hope, mixed with a little bit of dread.

Very interested in hearing what you think about Inrupt, Solid, and their prospects. Leave a comment, or otherwise get in touch.

 

2nd Decentralized Web Summit Brings Piles of Working Code

Honestly, for a while there, I thought the movement for a decentralized web was quietly fading away. There wasn’t a followup to the 2016 Decentralized Web Summit, and hardly anyone outside of a television sitcom seemed to be talking about these ideas, much less building alternatives.

Well, I am here to happily admit I was wrong. Truth is, it takes time to build software that might change the world. The second Decentralized Web Summit happened at the beginning of August, again in San Francisco. I didn’t go, but followed it intensely from afar. The sponsoring Internet Archive promised “working code” as a theme, and it delivered. The summit opened with a “science fair,” where 70 different projects showed off what they’d been working on, and there were enough people to walk around and see the presentations!

Wendy Hanamura of the Internet Archive reported that 800 people registered for the conference. I don’t know what expectations organizers had, but that sounds like a lot of people to this observer!

Time to follow Mozilla

It’s really exciting to see how heavily involved folks at the Mozilla open-source browser project are with solving the problem of decentralization.

Before the Summit began, the Mozilla Hacks blog for developers started a series of posts “Introducing the DWeb.” Since then, every Wednesday the blog features a developer of a decentralized project describing the project. As of this writing, three projects received exposure:

Mozilla Chair Mitchell Baker also gave a keynote address at the Summit, “Revitalizing the Web.”

I am really looking forward to a version of Firefox that supports the decentralized Dat protocol that Beaker uses.

Where was the tech media?

Startling that more mainstream journalists weren’t there. Vanity Fair profiled Tim Berners-Lee the week before, but as I write this, there were no reporters like Dan Gillmor and Kevin Marks writing stories for Fast Company as in 2016. I could be wrong, of course.

In the meantime, I can point you to a pair of good conference summaries:

Computing.co.uk: A nice summary from John Leonard

TheNewStack

More summit resources

As you can see, a lot happened. As I watch more video and otherwise catch up with what happened in San Francisco, I’ll keep reporting here. I’m also looking forward to playing with MIT’s Solid protocol, which I almost didn’t mention!

In the meantime: You can pretty much watch the whole conference in bits here. You can also spend some time following the #DWebSummit hashtag on Twitter.

Two more keynotes to bring to your attention:

  • Cory Doctorow always gives a thought-provoking talk, this one focusing on the question of “big tech.” I would have loved to seen any interaction he had with Tim Berners-Lee during the summit.
  • Host Brewster Kahle (founder of the Internet Archive) gave a laid-back talk about how we got ourselves into this mess, and how we can get ourselves out.

This is all to say that I am more confident that we may be at the dawn of another age on the Web than I was six months ago. I’ll still be writing about it, here and elsewhere.

Were you at the Decentralized Web Summit? What’s the most important thing I missed? If you weren’t there, do you wish you had been? Thoughts on the prospects of decentralizing the web on a mass scale are also appreciated.