The Drupal IndieWeb module now supports contacts so clients like Indigenous can query the micropub contact endpoint and use those as suggestions when creating posts! // cc @dshanske @jackyalcine @aaronpk @dries pic.twitter.com/5SUMmAJZEp— Kristof De Jaeger (@swentel) December 4, 2019
An in-depth analysis of how Drupal's development was sponsored between July 1, 2018 and June 30, 2019.
I love the depth and reflection Dries puts into this report. Having recently watched the State of the Word for WordPress, I wonder if WordPress publishes these sorts of numbers and analysis? Could they in the future?
There’s no reason you can’t have multiple websites. Several of us do it for a variety of reasons:
I’ve been running versions of both for many years and they each have their pros and cons. In terms of IndieWeb support they’re both very solid. Why not try them both for a bit and see which appeals to you more? Depending on your skill level and what you’re looking for in your site you may find one easier to run and maintain than another.
Personally I’ve used WithKnown (I’ve used it for multiple sites since it started) in a more “set it and forget it” mode where I just post content there and worry less about maintenance or tinkering around. On my WordPress site I tend to do a lot more tinkering and playing around, particularly because there is a much larger number of plugins available to utilize without writing any of my own code. Lately I am kind of itching to play around with Drupal again now that it has a pretty solid looking IndieWeb module (aka plugin).
Building toward an independent web isn’t something one does overnight anyway. Small incremental steps will eventually win the day. I like the way that Brent Simmons describes what he’s working on and why. Perhaps that could be a useful model in addition to the related idea of itches?
If it helps you might take your passions for “diversity, inclusion, equity & justice” and inject them into the space? I would always welcome help in those areas for the broader community.
Doing maintenance on Display Suite today, thanks to @dropsolid ! One day a month does make an impact, so let's talk to see if I can get more days :) #drupal
This is awesome news. I wish there were more companies who did this sort of thing.
I'm pulling the plug on Facebook because of their recent privacy violations — which got me thinking about what is next for the Open Web.
I want to pull the plug myself. I’ve essentially stopped using Facebook and have had the mobile app off my phone for almost a year and a half. I’m half waiting for better data export so I can keep all my data the way I’d like, but I’m beginning to think the moral imperative to just leave is more important.
I’ve primarily relied on WordPress.org for ages and have and have often used WithKnown, but I also have a few sites using Drupal. While I wouldn’t suggest non-technical folks using Drupal, whose technical requirements have rapidly been increasing over the past several years, I would recommend taking a look at a fantastic Drupal fork called BackDrop CMS.
While it still has a lot in common with Drupal, it has reconfigured the core to include some of the most commonly used and requested plugins and they’ve done their best to make it prettier and easier to use for hobby-ists and bloggers as well as small businesses and non-profits that don’t need all the additional overhead that Drupal brings. It’s also got a small but very dedicated community of developers and users.
I’ve also been hearing some great things about Craft CMS, which you highlight, as well as Perch by Rachel Andrew and Drew McLellan.
Brad, I like and agree with your general thoughts, but I think that looking at the long term broader picture, most of what you’re describing is covered under the umbrella principle of plurality. For things to grow and thrive, we all need plurality to flourish. As a result there are several hundred projects within the broader IndieWeb which are growing and thriving. It seems far slower because a large number of the projects are single-maintainer single-user ones which are being built for personal use.
It’s nice that there are mass-scale projects like WordPress, WithKnown, Get Perch, Grav, Drupal, and a few others which have one or more “IndieWeb-centric” developers working on them that allow those without the coding skills to jump in and enjoy the additional freedom and functionality. The occasional drawback is that those big-hearted developers also fit into the broader fabric of those massively distributed projects and sometimes their voices aren’t as well heard, if at all.
I’m aware of the disruption of the Gutenberg Editor within WordPress v5.0 and how it applies to those using IndieWeb technology on WordPress. I’m sure it will eventually get sorted out in a reasonable fashion. Sadly, throwing out the baby out with the bathwater as it comes to WordPress and IndieWeb may not be the best solution for many people and may actually be a painful detriment to several hundreds.
While it would be interesting to see a larger group of developers converge on building an open and broadly used IndieWeb system as you suggest, it takes a massive amount of work and community collaboration to get such a thing moving. I think this bears out if you look at the lay of the land as it already exists. Just think of the time effort and energy that the core IndieWeb community puts into the tremendous amount of resources that exist today.
Looking back on the past 4+ years of IndieWeb within the WordPress community, I’m really amazed to see exactly how far things have come and where things currently stand. There used to be a dozen or more pieces that required custom code, duct tape, and baling wire to get things working. Now it’s a handful of relatively stable and well set up pieces that—particularly for me—really makes WordPress deliver as an open source content management system and next generation social medial platform that aims to democratize publishing. In terms of building for the future, I suspect that helping to bring new people into the fold (users, developers, designers, etc.) will increase and improve the experience overall. To some degree, I feel like we’re just getting started on what is possible and recruiting new users and help will be the best thing for improving things moving forward. IndieWeb integration into large-scale projects like WordPress, Drupal, etc. are very likely to be the place that these ideas are likely to gain a foothold in the mainstream and change the tide of how the internet works.
While it may seem daunting at times, in addition to the heroic (part-time, it needs to be noted) developers like Mathias Pfefferle, David Shanske, Micah Cambre, Michael Bishop, Ashton McAllan, Jack Jamieson, Ryan Barrett, Peter Molnar, Amanda Rush; enthusiastic supporters like you, Greg McVerry, Aaron Davis, Manton Reece; and literally hundreds of others (apologies to those I’ve missed by name) who are using and living with these tools on a daily basis, there are also quieter allies like Brandon Kraft, Ryan Boren, Jeremy Herve and even Matt himself, even if he’s not directly aware of it, who are contributing in their own ways as well. Given the immense value of what IndieWeb brings to the web, I can’t imagine that they won’t ultimately win out.
If it helps, some of the current IndieWeb issues pale in comparison to some of the accessibility problems that Gutenberg has neglected within the WordPress community. Fortunately those a11ys are sticking with the greater fight to make things better not only for themselves, but for the broader community and the world. I suggest that, like them, we all suit up and continue the good fight.
Of course part of the genius of how IndieWeb is structured: anyone is free to start writing code, make better UI, and create something of their own. Even then they benefit from a huge amount of shared work, resources, and simple standards that are already out there.
After months of reading, experimenting and a lot of coding, I'm happy that the first release candidate of the Drupal IndieWeb module is out. I guess this makes the perfect time to try it out for yourself, no? There are a lot of concepts within the IndieWeb universe, and many are supported by the module. In fact, there are 8 submodules, so it might be daunting to start figuring out which ones to enable and what they exactly allow you to do. To kick start anyone interested, I'll publish a couple of articles detailing how to set up several concepts using the Drupal module. The first one will explain in a few steps how you can send a webmention to this page. Can you mention me?
A red letter day in that there’s another open source Webmention set up for a huge CMS!
Happy birthday Dries! If I may, can I outline a potential web-based birthday present based on your wish?
With relation to your desire to know who’s subscribed and potentially reading your posts, I think there are a number of ways forward, and even better, ways that are within easy immediate reach using Drupal as well as many other CMSes using some simple web standards.
I suspect you’ve been following Kristof De Jaeger’s work with the Drupal IndieWeb module which is now a release candidate. It will allow you to send and receive Webmentions (a W3C recommendation) which are simple notifications much the way they work on Twitter, Facebook, etc. I’ve written a bit about how they could be leveraged to accomplish several things in Webmentions: Enabling Better Communication on the Internet.
Not mentioned in that article for brevity is the ability to send notifications via Webmention when one makes follow or subscription posts.
As an example, I’ve created a follow post for you for which my site would have sent a Webmention. Unfortunately at the time, your site didn’t support receiving it, so you would have missed out on it unless you support older legacy specs like pingback, trackback, or refback.
I’m unaware of anyone actually displaying these notifications on their website (yet!), though I’ve got some infrastructure on my own site to create a “Followed by” page which will store and show these follows or subscriptions. At present, they’re simply stored in my back end.
Heh – that’s funny – @lizzjoy and I were just saying we need to find a way of knowing who is reading the Drupal community and association blogrolls…
— Rachel Lawson 🇪🇺 (@rachel_norfolk) November 22, 2018
As for Rachel’s request, this too is also possible with “read” webmentions. I maintain a specific linkblog feed (RSS) with all of the online material I read. All of those posts send notifications to the linked sites. While it’s not widely supported by other platforms yet, there are a few which do, so that online publications can better delineate and display the difference between likes, bookmarks, reads, etc. There’s at least one online newspaper among 800+WordPress websites which support this functionality. I suspect that with swentel’s Drupal module and some code for supporting the proper microformats, this is a quick reality in the Drupal space as well. Because the functionality is built on basic web standards, it’s possible for any CMS to support them. All that’s left is to ramp up adoption.
A quick note on Microsub and feed readers
I know the Like icon doesn’t show up in your feed reader (maybe that can change)
Interestingly, swentel’s module also supports Microsub, so that reader clients will allow one to like (bookmark, or reply to) posts directly within readers which will then send Micropub requests to one’s website to post them as well as to potentially send Webmention notifications. These pieces help to close the circle of posting, reading, and easily interacting on the open web the way closed silos like Facebook, Twitter, et al. allow.
Milestone: the first Drupal to Drupal conversation over webmention (AFAIK)! Thanks @aleksip for testing :) https://www.aleksip.net/trying-out-the-indieweb-module #indieweb #drupal
Awesome news indeed!
There you go: release candidate 1 for the #drupal #indieweb module. Time for a little party! https://www.drupal.org/project/indieweb/releases/8.x-1.0-rc1
Gutenberg and WordPress core contributor Gary Pendergast has weighed in with this thoughts on ClassicPress, a fork of WordPress created by Scott Bowler. Pendergast praises the fork and extended an …
The potential forking of WordPress like this actually could present an interesting opportunity for the broader community and the platform. It reminds me a bit of the BackDrop fork of Drupal and how it has benefited both platforms going forward. BackDrop has about 100 solid contributors that are building and iterating much more rapidly on their platform than the bigger behemoth of Drupal. As a result, new plugins and cleaner UI have entered their core and improved more rapidly with active dogfooding while their security teams collaborate closely and pushes go back and forth between the two. In the end both platforms end up benefiting tremendously. Naturally the two need to have some collegiality and collaboration to help make sure this happens.
It's sad to see Megan go, both professionally and personally, but I'm grateful for the impact she has had on the Drupal project.