This is where I share short updates and notes as I build Pure Commons. Every post is syndicated to Mastodon, and there's an RSS feed if that's more your thing.
Just dropped v1.8.0 of #PureComments which now includes #MFA, just like #PureBlog. Also has a tonne of quality of life improvements that I've been working on over the last couple months.
https://github.com/kevquirk/purecomments/releases/tag/v1.8.0
Been working on this on and off for around 3 months - MFA just dropped in #PureBlog.
Now have a live demo of #PureComments too. Enjoy!
Worth noting that this is probably the most difficult thing I've had to integrate into #PureBlog or #PureComments, so there's likely to be bugs. It's working well on my personal site so far though.
If you're using it and find a bug, please log an issue - https://github.com/kevquirk/purecomments
We have entered the #Fediverse! #PureComments now supports fediverse comments, likes and boosts via the amazing #Bridgy.
Read the docs - https://docs.purecomments.org/webmentions-and-fediverse/
Just added a #PureBlog demo so you can now try the entire project without installing it on your own infrastructure.
Try before you "buy"!
Really big update that I've been working on for a while in #PureBlog - this is all about theming and customisation.
You can now create/manage your own themes, as well as upload a custom logo to the sidebar. I'm particularly proud of how the themes worked out.
Read the docs - https://docs.pureblog.org/themes/
If you're using #PureBlog don't forget to add your site to the Pure Blogroll. Or just check it out to see what people running PB are writing about.
So the AI generated issue logging has found its way to #PureBlog. I had 2 overnight, both security vulnerbilities, both required authentication.
One was a nothing burger, but the other had the potential for an authenticated remote code execution, so fairly serious.
Anyway, both are patched in v3.7.3 so if you're running Pure Blog, I'd recommend patching ASAP.
PureBlog v3.7.0 just dropped with a new feature - dynamically generated Open Graph images.
You can read the docs here - https://docs.pureblog.org/open-graph-images/
Big thanks to @artfors for helping me create it.
I've been able to add a #PureBlog importer for #Ghost now too. So if you're running a Ghost site and want to give Pure Blog a try, you can do so pretty easily.
It will import posts, pages, images, and tags.
Just dropped a new release of #PureBlog that has better integration with #PureComments.
You don't have to mess around with embed codes anymore, it's all baked into Pure Blog.
New version of #PureBlog just dropped with a new sidebar layout in admin. Here's a quick demo...
Sooooo there's been a little update to the list of apps on the #PureCommons site - been meaning to update it for a couple weeks now, just haven't got around to it. 👀
Just released #PureBlog v3.1.0 which includes a feature people having been asking me to implement for a while - post scheduling!
Read the changelog here - https://pureblog.org/changelog
I've created a new Hooks library for #PureBlog. If you've created any interesting hooks for your site, please submit them so others can learn. :-)
Wooo that was a wild few hours!
- v3.0.0 of #PureBlog released on #Codeberg ✅
- v2.5.2 released on #GitHub for admin notice. ✅
- Pure Blog repo archived on GitHub. ✅
Pure Blog is now fully on Codeberg! 🎉
Next up, #PureComments. But that's for another day.
Problem with doing a pre-release is that people may not see the update at all (as the PB updater only looks for published released), so I may just be moving the problem when I subsequently release again.
For the past 6 weeks or so, I've been doing a major re-factor of Pure Blog to clean some stuff up. I'm ready to release it, but it will be a breaking update, as it includes changes to the update process.
So people won't be able to update from within #PureBlog, but I'm not sure how to manage this? Should I just communicate this everywhere and hope people see it? Or should I mark the next release as pre-release in GitHub so the in-app updater doesn't work?
I'm open to any other ideas to..