@edheil Yes. Here's a colophon page on my main site that outlines most of the pieces for many of my sites: https:/
@edheil Because of the IndieWeb principle of plurality, you've got a tremendous amount of choice. Part of the issue is that there are SO MANY options and potential combinations of doing things.
What do you want the site to do? How much admin time to you want to spend on it? How flexible and modifiable do you want it to be? What skills do you have? What skills do you want to work on?
Both of the options you mention are excellent, though there's probably more immediate flexibility in WordPress with plugins. If you want something with no admin, but still some reasonable flexibility then micro.blog is a great way to go. (All three support a very broad range of all the IndieWeb building blocks. Of course, this doesn't even touch the custom-built or static site generator spaces which are also available options. And who's to say you should only have one site? ;)
This is a great question to ask in the IndieWeb Dev chat channel for advice from a bigger group of people with a tremendous wealth and diversity of building experience. https:/
@edheil It creates a 1 to 1 correspondence between the post on your site & your post on Twitter to make it easier for Bridgy to match and sending responses. It also makes it easier to delete copies in the future because you'll know where else on the web you've posted things.
Settings at /wp-admin/admin.php?page=syndication_links will let you set syndication targets so you can use a simple checkbox for cross posting. I particularly love that it dovetails with https:/
@edheil Bridgy matches posts on your site to Twitter using one of a few methods so that it can backfeed the proper replies to the appropriate posts. Providing it with syndication links is usually easiest, and on WordPress try: https:/
David Shanske's Syndication Links plugin also should have a checkbox set up (non-Gutenberg) for more easily syndicating to Twitter and other services if you like. There are many ways to publish to Brid.gy without visiting it for each. Using Shankse's plugin which sends it Webmentions is probably the easiest, though it may require proper markup in your theme. For the technical part see: https:/
I think many of the options are documented either here or on related pages: https:/
For other options and advice, it may be best/easiest to visit the IndieWeb WordPress chat at chat.indieweb.org/wordpress
@edheil Easiest to think of it as you have one "account" for each website. Then each site has different sections for each social silo you connect it to.
@edheil Which of the various methods (manually, plugin(s), other) are you using? On fragility front, I'm not too worried as it is open source and has folks helping. It's also only a bridge as I can reply directly to your site.
https:/
https:/
Other than maybe #Pleroma or #WordPress with the ActivityPub plugin, are there any other #Fediverse projects that support multiple post types/kinds/objects so that one could have *one* Fediverse home instead of 10?
At Homebrew Website Club watching with great anticipation as @KevinMarks adds microformats to the base Tumblr theme to help make it more IndieWeb friendly. #RedCups #Flickr
https:/
@ChengduLittleA You're not doing them all manually like this are you? https:/
@pixelroiber@mastodon.social @pixelfed@mastodon.social Last I checked, this was the state of the art with respect to PixelFed and Brid.gy https:/