I’ve had Webmentions enabled on this site for some time now. Sending a Webmention is pretty straightforward thanks to plugins like Webmention for WordPress and Semantic-Linkbacks. The question is how to send Webmentions in comments when someone replies to one of my posts? 🤔
Our new Recurring Payments feature for WordPress.com and Jetpack-powered sites lets you do just that: it’s a monetization tool for content creators who want to collect repeat contributions from their supporters, and it’s available with any paid plan on WordPress.com.
Let your followers support you with periodic, scheduled payments. Charge for your weekly newsletter, accept monthly donations, sell yearly access to exclusive content — and do it all with an automated payment system.
Accept ongoing payments from visitors directly on your site.
Bill supporters automatically, on a set schedule. Subscribers can cancel anytime from their WordPress.com account.
Offer ongoing subscriptions, site memberships, monthly donations, and more, growing your fan base with exclusive content.
Integrate your site with Stripe to process payments and collect funds.
One reason I really like the Recurring Payments feature is that it gives anyone with a paid plan (whether it’s a WordPress.com Personal plan, or a higher plan) a way to create a membership site that can help them grow a following, and a new income stream.
Ad revenue is a popular way of earning money through your site (we offer a WordAds ad platform, for example), but ad revenue really depends on substantial numbers of visitors to turn into meaningful income.
On the other hand, receiving recurring payments from a smaller group of passionate supporters just seems to be more sustainable, and meaningful.
It’s hard to be creative when you’re worried about money. Running ads on your site helps, but for many creators, ad revenue isn’t enough. Top publishers and creators sustain their businesses by building reliable income streams through ongoing contributions.
This new feature empowers creators, bloggers, knowledge workers, <insert your title here> to share something of value with your audience, and build a sustainable business in the process.
I like the default themes that ship with WordPress, and the themes that our team is building. Even though the new generation of themes aren’t perfect*, they’re built for the block editor. I keep forgetting how much flexibility that brings to WordPress.
So far, I like this new theme. I think the content container is a bit narrow on a larger screen, so I may tweak that a bit. The mobile view is pretty great, though.
Thanks to the open web it was possible to create massive platforms, which inevitably became closed.
He asks an important question:
Do we now abandon the open web or is it essential for keeping the closed platforms in check?
I think the only real answer to this question is not to abandon the open Web. The open Web remains essential, both in itself, and to offer a compelling alternative to closed platforms.
The open Web can offer a healthier, more sustainable alternative to closed platforms. What we need are services that are as good as, or better than, closed platforms. Perhaps more importantly, the open alternatives should be just as convenient to use. This is where open solutions seem to be lacking, for now at least.
Even though you can export your Facebook data into what seems like a nicely presented, local site of sorts, I’d like to be able to basically parse my Facebook timeline, and somehow migrate it to a WordPress blog.
This may be possible using an extension of the Keyring plugin for WordPress. I’d like to test this out, even though I’ve never really been able to get the Keyring plugin to work on my site.
I’d need to first configure a private WordPress site first though in case it works, and the site populates with private updates.
I really enjoyed reading Matthias Ott’s post titled Into the Personal-Website-Verse. It’s an essay about why it’s so important to have your own space on the Web, and why IndieWeb is a great way to get there. It’s well worth the read.
There are many reasons to have your own site, at your own domain, that you control. Aside from retaining effective control over your content, the risk of entrusting our stories, and our content to centralised services like social networks is arguably greater:
One day, Twitter and other publishing platforms like Facebook, Instagram, or Medium will indeed die, like so many sites before them. And every time this happens, we lose most of the content we created and with it a fair amount of our collective cultural history.
There are so many options for creating a personal site including WordPress.com*, Micro.blog, GitHub Pages, Squarespace, and many more. I prefer platforms that let me take my content out, and move it to another platform if I decide to. I think you should too.
*And yes, as you know, I’m partial to WordPress as a long-time user, and because I work for Automattic, the company behind WordPress.com.