Pure Commons

Just dropped v2.3.0 of #PureBlog which includes a completely redesigned dashboard. Here's a demo:

https://pureblog.org/dashboard-stats

OK, v2.0.0 of #PureBlog is out the door and contains a tonne of new goodies. Because of this there's a bit of wonky update for this one though!

All details in the release notes:

https://github.com/kevquirk/pureblog/releases/tag/v2.0.0

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.

With the new features that have come to #PureBlog over the last few releases, I've updated the "Title-less Notes" how to guide that shows how to have a proper separate notes page, with its own feed.

It even includes an optional #Mastodon cross-poster!

https://pureblog.org/how-to-create-a-titleless-notes-page

v1.5.0 of #PureComments just dropped. It adds a "remember me" function for logging in (90 days) and filtering by post or commenter.

https://github.com/kevquirk/purecomments/releases/tag/v1.5.0

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..