Overheard at #domains19 "ugh Gutenberg, that's why I use elementor. I use Divi to avoid this"— Bryan ✻llendyke (@btopro) June 10, 2019
This is what we are here to break. 3 projects that all landlock your content to a database, all used to basically just position static things 99% of the time.
I stumbled across this post by Chris Aldrich while lurking through my Twitter feed. Which has inspired me throw back a reply and briefly summarize how I have been increasingly using IndiWeb core ideas and concepts to re-focus how I use the web.More than a website Recently I’ve been building a cust...
WordPress plugin developer Jeffrey Carandang continues to plough forward with new features for EditorsKit, a collection of page building block options for Gutenberg. What began as a block visibilit…
As mentioned in the description on the plugin Post Kinds is not yet compatible with Gutenberg. If it’s something you want to use, you’ll have to install and activate the Classic Editor.
Learn how to write a WordPress plugin that registers custom Gutenberg blocks and build out those blocks to provide an instant preview/feedback as they’re being edited in the wp-admin, as well as ho…
All this WordPress 5.0 Gutenberg stuff got me thinking. With WordPress it seems like the Indieweb starts making serious and cool progress and the WordPress people come along and knock the game board and pieces off the table. And it sounds like the disruption from WordPress is going to continue for a couple of years.
Why not take a page out of Apple’s playbook and take control higher up in the food chain? Why not come out with an Indieweb compatible blog engine of our own? Either fork an existing open source project or build new? This does not mean you have to make it exclusive but make it the way the Indieweb wants the Indieweb elven magic to function. Also put in the standard blogging features most people expect. Why keep trying to adapt the Indieweb stuff to blog or CMS platforms that are at best indifferent, never designed for or just that don’t want to play ball?
This isn’t a slam on the coders who are working so hard to make everything work on WordPress, I’m just asking if maybe it’s not time to find better terrain to fight from.
If the Indieweb really wants widespread adoption they need to come out with a turnkey solution. It would act as a solution for many and a proof of concept for others to emulate. Something that can be put in hosting C-panels for one touch install. Something that just works, is easy to move to and move away from. Something supported, active, growing with enough polish that it inspires confidence in the user.
I’d really like to hear serious discussion on this.
I have several blogs: 1 x Micro.blog hosted blog plus 2 x WordPress blogs. After the Holidays, I’ll probably migrate my main WP blog (you are here) to some other blogging platform. No matter what I do I will lose my Indieweb features on that blog. But that said, I forsee it becoming increasi...
For those of you who are reading this in your inbox, the context for this post is the recently-published, (as in yesterday), target release date for WordPress 5.0, which rolls out the new Gutenberg editor. I’d like to say I’m surprised by this, but I’m just not. I find myself asking a few ques...
My rapid fire thoughts:
So with Gutenberg we can have more autoplaying Youtube embeds, more snarky memes, fewer words and meaningful sentences in blogging so we can be just like Facebook and Twitter. Feh!
You break my WP blog and I’ll find a new platform and host.
I have until 2022 to find a new platform. Maybe.
I just want to write. I don’t want more friction to banging out sentences.
There is a reason I hyperlink to stuff rather than embed.
/waves cane/ like grumpy old git.
I’m almost ready to be a grumpy old git too.
We are nearing the release date for WordPress 5.0 and Gutenberg, one of the most important and exciting projects I’ve worked on in my 15 years with this community. I knew we would be taking a big leap. But it’s a leap we need to take, and I think the end result is going to open up many new oppo...
There’s a new WordPress fork called ClassicPress that’s been making some waves recently, with various members of the Twitterati swinging between decrying it as an attempt to fracture the WordPress community, to it being an unnecessary over-reaction, to it being a death knell for WordPress. Pers...
Again, here, I’m reminded of some of the benefits that the BackDrop fork of Drupal is providing not only to itself, but to the larger Drupal community. Naturally there’s a better way of doing these things, but it takes foresight and work–a lot of work.
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’s Quill 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.