Notes tagged “indieweb”

You should probably not add “No Title” to your titleless “IndieWeb” notes. Even if your site’s front end doesn’t show these “titles,” your RSS feed still might. Which would cause feed readers to display these notes as “articles,” i.e., with a title (equal to “No Title”).

This right here.

Your home on the Internet? Get a website. Looking for interaction? Add comments (or Webmention).

“Quote toots?” Look at what I’m about to do instead:

The more I look at this “issue” the more I’m convinced the solution is already right there and it’s called the web.

This!

Choice is at the core of the IndieWeb approachability and accessibility challenge. […] I think there’s a place for more opinionated guides to the IndieWeb[.]

Created a website for IndieBlocks. Hoping to eventually add proper documentation (the end-user kind, with screenshots and stuff), and code snippets and so on.

Now, to actually bring the (released version of the) plugin in line with the Getting Started guide. 😬

The new IndieBlocks settings screen(s). 😬

Yes! My IndieBlocks plugin is now up on WP.org. Current version offers a single “Context” block, and, optionally, (1) some custom post types, and (2) the ability to add microformats2 to block-based (!) themes. More is on the way. https://wordpress.org/plugins/indieblocks/

Tested it on a nearly empty site with the Blockbase theme, and things like an h-entry’s post type and very basic h-card information is being picked up fine.

Testing my “all-in-one” “IndieWeb” plugin for WordPress with the new 6.1 beta and Twenty Twenty-Three. Seems to work OK, but I’m wondering why my “site doesn’t support the core/post-author-name block.” Like, I knew about the post author block … Of course, you’ve got to install Gutenberg! Makes perfect sense for the new default theme to not work without a plugin.

Somewhat inspired by https://www.zylstra.org/blog/2022/09/wordpressindieweb-as-the-os-of-the-open-social-web/, I did some experimenting with WordPress’s new Full Site Editor. The result is this, still very hacky, Twenty Twenty-Two child theme. https://github.com/janboddez/tt2-mf2

Hoping to update my “IndieWeb plugin” with basic block support. Fixing core would be even better.

Either way, themes will need to update, too.

And, after yesterday’s Webmention package, a basic IndieAuth package for Laravel.

Been toying with Laravel a bit more. Decided to split off some Webmention functionality into a package of its own, https://github.com/janboddez/laravel-webmention. There’s two classes here that matter, one for receiving (Http\Controllers\WebmentionController), and one for sending (WebmentionSender). Hoping to add a parser of sorts later, and some CLI/Artisan commands.

Nice write-up on IndieWebifying a static site.

That said, this is exactly why I favor dynamic sites (where you’d flush the cache and that’s about it) for this type of thing:

[M]y Webmention workflow is lacking. I need to implement a way to automatically rebuild my site[.]

Syndication is another troubling topic. The process is a bit convoluted[.]

Nope, not at all. Don’t even have a Twitter account.

Some middleware seems necessary? For example, I had to give a service called Bridgy access to my Twitter[.]

Exploring Laravel Sanctum. Trying my hand at an IndieAuth endpoint.

Bookmarked https://wordpress.org/plugins/shortnotes/.