The things I made are on the Github thing so you can upload them to your thing to make things easier/better!
That's a lot of things...
@chris I've been pretty happy with #ClassicPress over the last year. It's very lightweight and straightforward to not deal with FSE and the block editor for a bare bones blog.
Small update for my #WordPress plugin #Personio Integration Light: it is now also compatible with #ClassicPress 2.x. I am already working on a major update that will include support for the new Personio API v2. https://wordpress.org/plugins/personio-integration-light/
A #wordpress tool to give tribute to #OzzyOsbourne and should work on both WordPress and #ClassicPress so everyone can keep Ozzy's name alive.
#blogging #wordpressplugin #wordpressdev
Open Calendar is a libre, #selfhosted web application -not a library- designed as a plug-and-play #CalDAV client. It bundles #opensource components to provide a sleek interface connected to one or more CalDAV servers. Currently in beta and open to contributions, it's distributed under the MIT license, ensuring freedom and transparency. Potential #WordPress plugin ? Explore the project at :
Having such a hard time setting up #WordPress or #ClassicPress and getting #LetsEncrypt set up. The instructions for LE mandate either Pip or #Ubuntu #Snap which #Trisquel does not have. And I still can't even access #Nginx even after forwarding and opening ports... Ugh!
Updated my dev site too :)
No more bitcoin as a payment option and redid all support pages. They're actually part of the support system now.
The other week I switched my weblog, which has been running on #WordPress since 2004, to @classicpress.
So far, it's been great (with only a few minor challenges). #ClassicPress provides (almost) all the features I love and none of the ones I don't need.
Deep-dive and learnings: https://danq.me/2025/02/18/wordpress-to-classicpress/
Just installed #ClassicPress on remote test server. Its significantly snappier and and from what I've see, a lot of #wordpress themes and plugins seem to actually work which I didn't expect. Next steps will be trying to harden it using common WP strategies.
@kudra favicon is often managed in the Customize settings, and needs to be set manually following a migration. I don't believe those settings get saved in the database. #ClassicPress
Path: Appearance > Site Identity > Site Icon.
Balanced intro to #ClassicPress, lightweight #WordPress #fork without block editor. Not huge userbase, but it looks mature and its regulary updated. I'm definitely going to try it on next project. #alternative
https://lwn.net/Articles/992219/
@kelson @mcc are jou satisfied with the #classicpress? I'm planing new website and I'm reluctant to go with #wordpress since I don't need block editor and hate the overall complexity and sluggishness that has become the default.
We're in the first full week of #Kinder (last week only had 1 full day) and thus I am now able to do more Work from Home (and soon, mobile) rurally. It's chucking it down out there, so indoor stuff it is today.
Feeling great about migrating all my websites over to an #Australian host, switching them all to #ClassicPress (though I'm a bit nervous about my main work website as it's been built with a truly stupid amount of plugins by someone who no longer does my website maintenance) but migration so far going well. Didn't seem to bring the #favicon over for first migration, not sure why.
Also! exploring #Nextcloud which this host allows through Softaculous and thus reducing my dependence on The Goog.
There are various WordPress plugins to block AI bots. I strongly suggest WP and CP site owners choose one and install it.
#WordPress
#ClassicPress
#AIbots
@samuel @Spelpipa
Jag vill slå ett slag för #ClassicPress som ett (bättre) alternativ till WordPress. Finns som one-click-installation på de flesta webbhotell.
Stoked that my first ClassicPress theme (and first publicly released theme) has passed review and is now available on the ClassicPress directory 
https://directory.classicpress.net/themes/archetype/
#classicPress #wordPress #webDevelopment
Conversing to the Fediverse With WordPress
Reading Time: < 1 minute
Recently I saw a post stating that WordPress can speak with the fediverse more effectively. For months we could post to the fediverse but if we replied to a toot via WordPress it would be lost. Those on Mastodon instances would comment but be "ignored".
For months I thought that it was bizarre that WordPress would only broadcast to the fediverse, but not allow for two way chats to occur. I found this frustrating because if people did comment on a post I'd have to use another account to answer, and acknowledge that comment.
Yesterday I saw my blog post in the fediverse so I commented on it, and then I replied within my blog, and then I replied to my reply, and was able to have a threaded exchange between the fediverse and my wordpress blog. I believe that this would work with ClassicPress too.
The reason for which this is significant is that from now on, we do not need to use Mastodon or other fediverse instances to be part of the fediverse. We can use our blogs as Fediverse instances. The barrier to entry for the fediverse has been lowered.
And Finally
Yesterday I was toying with the idea of restarting a Mastodon instance until I experimented with the chat ability of WordPress and the Fediverse and when I saw that it works well now that desire to setup an instance went away. We could now share photos without the need for Pixelfed or other solutions.
The next step would be to experiment with ClassicPress.
I recently migrated my websites from WordPress to ClassicPress. The plugin and theme ecosystem isn't as robust but, damn, it's faster and I didn't realise how much I didn't like the Gutenburg block editor. Colour me pleased.
