News about Bludit future ?

[randomuser]

Recently, Bludit got new versions and commit, made by Bludit's main maintainer, now using Claude (why not !). That's good news !

Do we know if it will be a long term support on any version ?

Is there something about the v4 ? All issues on the milestone seem closed (https://github.com/bludit/bludit/milestone/1?closed=1), no news since now 5 years (https://github.com/bludit/bludit/issues/1057)

The blog (https://blog.bludit.com/) giving news about Bludit, seems to have been deleted.

Is there a way to have official communication on the project ?

Thank you

[Edi]

There will also be updates for v3 in the future.

The development of v4 is discontinued.

The best way to communicate is at the moment here or on Facebook.

[lastpictures]

I think if we consistently pursue the development path of version 3.x, then it's fine. Many things have been fixed in recent weeks, so version 3.x can also be about preparing the CMS for the future. Currently, the system is working well; plugins are available, but can also be quickly developed in-house, as can themes.

A good new feature would be access control. Ensuring that an author can only write, etc.

[randomuser]

Thank you for your answers. So Bludit will forever be v3.xx ? Or maybe v5.xx in the future ?

Is there any increase of security report, as in many open source projects ?

Also, I can see GitHub history has been deleted (not very nice for contributors :/), is this to announce a more community driven behavior ?

"I think if we consistently pursue the development path of version 3.x, then it's fine" agreed, but when only 1 person maintains a project, it depends on the person private life, anyone can have more or less free time depending on time

[lastpictures]

You're free to create a fork and develop the CMS yourself. I know it's work, but it's a way to keep development going.

I customize Bludit after every update, constantly developing my theme further, including new features. I've also written plugins to streamline processes and add functionality that was either unavailable or only available in a rudimentary form.

For example, the Snicker plugin: unfortunately, it's no longer maintained. There was an update with Snicker Plus in 2025. I took that and developed it further. Just as an example

[randomuser]

Thanks for your answer

Well I'm just asking because it's good to know how to project will continue, if it should be used for new projects or not. Many people don't have time to maintain a whole CMS themselves (me included), or just want to blog
Also having my own fork for a long time would be a too big job (for not many result while the main project is developed), but it could be a good way to do PR, for sure !

"I've also written plugins to streamline processes and add functionality that was either unavailable or only available in a rudimentary form." That's a nice work, congrats ! But not every one have these skills not time I imagine

[lastpictures]

That wasn't meant to sound arrogant or anything like that

But yes, I understand your point! I think Bludit has a future!

[randomuser]

I didn't take it like that, no worry I meant the congrats haha

Okay, thank you for your answers !

[kbeezie]

... now using Claude (why not !). ...

I'm wondering if that might explain why some of the existing public documentation no longer line up with how the codes internal structure actually works now.

It can be slower to update the docs if some of it was rewritten by claude, which can be annoying considering it's still very much a developer-oriented CMS. (Some regular end user could use it well, but seems like they won't get the full benefits if they can't touch a lick of php/css/etc without some help).

Compared to a lot of other options out there tho? Can't really beat it for the minimum $2 a month support to get the pro version (which may not be needed by everyone, of course, but if you use it might as well contribute to it).