Send me a webmention with Drupal!

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 explain in a few steps how you can send a webmention to this page. Can you mention me?

Step 1: enabling modules

After you downloaded the module and installed the required composer packages, enable following modules: IndieWeb, Webmention and Microformats2. In case you are not authenticated as user 1, also toggle the following permissions: 'Administer IndieWeb configuration' and 'Send webmention'.

Step 2: expose author information

To discover the author of a website after receiving a webmention, your homepage, or the canonical url of a post needs author information. The module comes with an Author block so you can quickly expose a block where you can configure your name. Your real name or nickname is fine, as long as there's something. The minimal markup should look like something like this:

<p class="h-card">Your <a class="u-url p-name" rel="me" href="https://example.com">name</a></p>

Note: this can be anywhere in your HTML, even hidden.

Step 3: configure webmention module

All configuration exposed by the modules lives under 'Web services' > 'IndieWeb' at /admin/config/services/indieweb. To configure sending webmentions go to /admin/config/services/indieweb/webmention/send. Ignore the ' Syndication targets' fieldset and scroll down to ' Custom URL's for content' and toggle the 'Expose textfield' checkbox.

Scroll down a bit more and configure how you want to send webmentions, either by cron or drush (webmentions are stored in a queue first for performance reasons)

Step 4: configure Microformats module

When sending a webmention to me, it would be nice to be able to figure out what exactly your post is. To achieve this, we need to add markup to the HTML by using CSS classes. Let's configure the minimal markup at /admin/config/services/indieweb/microformats by toggling following checkboxes:

  • h-entry on node wrappers
  • e-content on standard body fields. In case your node type does not use the standard body field, enter the field name in the 'e-content on other textarea fields' textarea.
  • dt-published, p-name, u-author and u-url in a hidden span element on nodes.

Now create a post!

Create a post with a title and body. Your body needs to contain a link with a class so that when I receive your webmention, I know that this page is valid. As an example, we're going to write a reply:

Hi swentel! I just read your <a href="https://realize.be/blog/send-me-webmention-drupal" class="u-in-reply-to">article</a> and it's awesome!

Save the post and verify the markup more or less looks like underneath. Make sure you see following classes: h-entry, u-url, p-name, dt-published, e-content, u-author.

<article role="article" class="h-entry node node--type-article node--promoted node--unpublished node--view-mode-full clearfix">
     <div class="node__meta">
          Published on <span class=" field--label-hidden">Tue, 04/12/2018 - 22:39</span>
        <span class="hidden">
          <a href="https://example.com/canonical-url" class="u-url">
            <span class="p-name">Test send!</span>
            <span class="dt-published">2018-12-04T22:39:57+01:00</span>
          <a href="/" class="u-author"></a>
  <div class="node__content clearfix">
  <div class="e-content clearfix ">Hi swentel! I just read your <a href="https://realize.be/blog/send-me-webmention-drupal" class="u-in-reply-to">article</a> and it's awesome!</div>

If everything looks fine, go to the node form again. Open the 'Publish to' fieldset where you can enter 'https://realize.be/blog/send-me-webmention-drupal' in the custom URL textfield. Save again and check the send list at /admin/content/webmention/send-list. It should tell that there is one item in the queue. As a final step, run cron or the 'indieweb-send-webmentions' drush command. After that the queue should be empty and one entry will be in the send list and I should have received your webmention!

Note: You can vary between the 'u-in-reply-to', 'u-like-of' or 'u-repost-of' class. Basically, the class determines your response type. The first class will create a comment on this post. The other two classes will be a mention in the sidebar.

What's next?

Well, a lot of course. But the next step should be receiving webmentions no? If you go to /admin/config/services/indieweb/webmention, you can enable receiving webmentions by using the built-in endpoint. Make sure you expose the link tag so I know where to mention you!

I tried it, and it didn't work!

Maybe I missed something in the tutorial. Or you have found a bug :) Feel free to ping me on irc.freenode.net on #indieweb-dev or #drupal-contribute. You may also open an issue at https://github.com/swentel/indieweb

Send me a webmention with #drupal! 101 setup with the first release candidate of the #indieweb module. Can you mention me? https://realize.be/blog/send-me-webmention-drupal

Your site on the fediverse with Bridgy Fed

Lately, Mastodon is getting a lot of attention as an alternative for Twitter. It's a microblogging platform which allows you to setup your own instance, and still interact with users on a totally different domain. They are all part of the Fediverse. It uses open standard protocols and specifications as much as possible, which means that integration from other places should be possible, e.g. why not your own site !


To interact with Mastodon, and most other federated platforms, you need to implement Activitypub and add Webfinger support to your domain, which can be tricky to setup. Enter Bridgy Fed: it acts as a proxy for your domain and does all the heavy lifting for discovery, sending posts to the right instance and sending back interactions to your site. The Drupal IndieWeb module has all the necessary tools for sending and receiving webmentions and the markup needed for your content. In fact, there are only two simple things you need to do. Add "Fediverse|https://fed.brid.gy/" on the 'Sending' settings screen as a syndication target and two lines to .htaccess, and you're done: welcome to the Fediverse. Don't like Drupal ? No problem! Any framework, whether you are using Wordpress or Known, or even wrote yourself, which supports sending webmentions can get on the Fediverse! Read about webmentions and microformats on IndieWeb.org.


If you are on Mastodon, you can follow me by searching for 'swentel' which will give you two results. One is a test account I use for testing the AP protocol. The user that is managed by Bridgy Fed, and which will now get all the notes I syndicate from my site, is @realize.be@realize.be.

Since I don't have an actual account, how do I follow users? Mastodon exposes an atom and even a Microformats feed of every user. This allows everyone to follow accounts with even a simple RSS reader. In my case, I use Indigenous as my reader, and Aperture as the server (actually, I'm using the built-in server now in the IndieWeb module, but Aperture is a great alternative to get started!). From my client, I can directly interact with anyone on the Fediverse because it knows my micropub endpoint to post to my site which then starts syndicating posts to the right instance: replying, liking, boosting, posting .. it all works! Some tiny details need to be figured out still, like images, but simple content just works fine!

All of this has been tested with Mastodon. There are more federated platforms out there, so this is only the beginning! A big shout out to Ryan Barret, the maintainer of Bridgy Fed (and many other great tools)!

Getting on the Fediverse with your own site using Drupal and Bridgy Fed just became easy! https://realize.be/blog/your-site-fediverse-bridgy-fed #drupal #fediverse #indieweb

Quasi un'Utopia : tryouts first movement

It's official: I'm not going to perform the complete Moonlight Sonata this year. I'm not giving up the dream though, it will just take a little longer. The main reason for the delay is simply time, so I need to come up with a plan to make sure I have more time next year to study the entire piece. Hopefully, more on that later.

However! You can mark March 30/31 2019 in your agenda as I'm going to perform the first movement of the piece during a choir concert. A small teaser, and probably already stressful enough, but I'll learn a lot by getting on stage and controlling my nerves, and fingers before a fairly big crowd - last year, around 300 people attended.

Quasi un'Utopia : tryouts for movement one! https://realize.be/blog/quasi-unutopia-tryouts-first-movement #beethoven

Exclude entities which have a redirect from the search api index

For a custom project, we use a taxonomy to tag nodes. Some terms have their own page, while others redirect to a node. The search on the site has one index which contains both nodes and terms, but the terms which are redirecting shouldn't show up when viewing a search results page. While it's possible to use hook_search_api_index_items_alter(), a nicer way to exclude them is by using a processor plugin so you can enable them in the UI per index. The relevant code is underneath. Adjust to your own likings - and maybe inject the service if you want to as well :)

namespace Drupal\project\Plugin\search_api\processor;


 * Excludes entities which have a redirect.
 * @SearchApiProcessor(
 *   id = "entity_redirect",
 *   label = @Translation("Entity redirect"),
 *   description = @Translation("Exclude entities which have a redirect from being indexed."),
 *   stages = {
 *     "alter_items" = 0,
 *   },
 * )
class EntityRedirect extends ProcessorPluginBase {

   * {@inheritdoc}
public static function supportsIndex(IndexInterface $index) {
    foreach (
$index->getDatasources() as $datasource) {
$entity_type_id = $datasource->getEntityTypeId();
      if (!
$entity_type_id) {
      if (
$entity_type_id === 'node' || $entity_type_id == 'taxonomy_term') {

   * {@inheritdoc}
public function alterIndexedItems(array &$items) {
$repository = \Drupal::service('redirect.repository');
$pathAliasmanager = \Drupal::service('path.alias_manager');
/** @var \Drupal\search_api\Item\ItemInterface $item */
foreach ($items as $item_id => $item) {
$object = $item->getOriginalObject()->getValue();
      try {
$path = $object->toUrl()->toString();
$path = $pathAliasmanager->getPathByAlias($path);
$path = ltrim($path, '/');
$redirect = $repository->findMatchingRedirect($path);
        if (!empty(
$redirect)) {
      catch (\
Exception $ignored) {}

Exclude entities which have a redirect from the search api index: https://realize.be/blog/exclude-entities-which-have-redirect-search-api-index

Indigenous for Android

Over the last few weeks, I've been working on a Drupal module for IndieWeb and Indigenous, an Android application which supports micropub and microsub. I'm using it already to post notes, images and even awesome geocaches to my site, often syndicating them to Twitter. Progress on the app heavily depends on how fast I can add features to the Drupal module, but it's going faster than I expected, which is good as it's all very exciting! There is of course the time aspect, but I'm not complaining, yet - although I'm still figuring out if I can setup some funding for both projects, so ideas are welcome!

You can now download the app from Google Play. If you want to install it manually, you can also go over to the release section on GitHub. Use GitHub to post issues, ideas, documentation, nicer icons, design mockups ... everyone can help out!

Features available, with many more to come:

  • Sign in with IndieAuth and discover the authorization, token, microsub and micropub endpoints. The microsub endpoint is optional, so you can simply use the app for posting only. Multiple accounts are supported.
  • Posts: note, article, like, reply, repost, bookmark, event and RSVP. Add tags and an image, and share your location
  • Syndication: syndicate to your favorite social channel or to the reply/like/repost URL.
  • Microsub: list channels and read all posts per channel. You can directly reply, like or repost per post. Long articles have a 'Read more' button and images can be viewed in fullscreen. Oh, and audio can be listened to directly, so that makes Indigenous a podcast app too!
  • Sharing: Indigenous can accept images or text from other apps. Share an image on your site, or reply to a URL in no time.
Thanks to everyone already for the feedback, and especially Aaron Parecki for letting me use Aperture to test the microsub part and Eddie Hinkle, the maintainer of Indigenous for iOS.
Post a note
Introducing Indigenous for Android, supporting micropub and microsub - sign up for testing if you're interested! https://realize.be/blog/indigenous-android #indigenous #indieweb #drupal #android

Quasi un'Utopia : little steps

It's been little over a month now since I've started playing on the piano, reading notes, studying easy tunes and I have to say: it's big fun! Can I play the Moonlight sonata already ? Of course not, but I have still 8 and a half months to go, so no stress. As I explained in the first post, I will try and share my progress every month, so this clip is already a bit longer. And it features me, actually playing. I won't tell you the number of takes before I had one without mistakes :)

The next month will be interesting as I'm on the road for 3 weeks around Scotland, but I prepared myself: a roll up piano!. I'm carrying a set of headphones along too as I don't want to annoy my travelling companions too much when it's raining every day - fingers crossed it won't.

Quasi un'Utopia : little steps. Practicing, reading and still having fun with Beethoven! #piano https://www.youtube.com/watch?v=bgHVQASlc70