#indieweb setup

My site (rmendes.net) is powered by Indiekit

Indiekit is a server that sits between you and your website — you post to it, it writes to your site's repo. I've been extending it for about a year. What started as "add a couple of plugins" is now ~25 packages of my own plus forks of seven that Indiekit ships with. One codebase runs two sites (https://rmendes.net and https://indiekit-demo.rmendes.net/), each with a different plugin set.

Roughly what I added:

Publishing — a page post type for the root-level pages every site ends up with (/about, /now, /uses), multi-file uploads, a share bookmarklet that asks whether the thing is a note or a bookmark, and a permalink fix for the Eleventy preset.

Site config in the database — colours, navigation, categories, homepage layout. Changing a site doesn't mean editing files, which is what lets two sites share one theme.

Talking to other places — syndication to Mastodon, Bluesky, LinkedIn and IndieNews, extended to carry likes and reposts and not just posts. Webmentions both directions, with incoming ones stored in my own database so I can moderate them instead of trusting webmention.io to hold them. Comments from people who don't have their own site, via IndieAuth or RelMeAuth. A thread aggregator that pulls the replies scattered across Mastodon and Bluesky back under the original post. And a full ActivityPub implementation on Fedify: inbox, outbox, followers, a timeline I can read and post from in my own admin UI, a Mastodon-compatible API, and a migration path off a Mastodon account.

Reading — Microsub server, RSS aggregator, blogroll built from OPML, podroll pulled out of FreshRSS, read-it-later.

The rest of a person — GitHub activity, Last.fm and Funkwhale listening history, YouTube videos, a CV editor

Plumbing — a versioned plugin registry, so a site is described by which plugins it gets rather than by a Dockerfile; Cloudron and docker-compose packaging; a startup gate that keeps background pollers quiet until the first Eleventy build finishes, because that build is where all the memory goes.

Everything is published as @rmdes/* on npm. Source: github.com/rmdes.

Working On

ActivityPub for Indiekit via Fedify (Beta)
Indiekit Bluesky standard.site (alpha) - separate pds dependency
Microsub (beta)
CV indiekit plugin
Plume micropub browser extension
Newsdiff - Diff engine alternative + AP/ATproto

https://rmdes.github.io

Itches

- What would it take to use Indiekit to incarnate both a micropub indieweb blog with content representation in both native blog posts, ActivityPub and ATproto interface ?

Elsewhere

Contact

Backlinks

These are the pages where I'm linked.