Hi,
with Neos 9.0 we delivered the first backend module based on Fusion+HTMX with the Neos.Workspace.Ui. So far the approach works well and long-term we only want Fusion based modules in Neos to replace Fluid, make them extensible (to a certain extend) and also improve the UX at the same time.
During the contribution day after NeosCon 2025 several contributors started reimplementing the configuration module (and integrate , which I later combined into a draft PR FEATURE: Configuration UI by Sebobo · Pull Request #5653 · neos/neos-development-collection · GitHub .
This is not a super fancy topic, but we agreed before in the team that we want this and I would like to finish the PR and the concept/toolkit in the 9.x timespan, so that other modules can also adopt this in the future and integrators can use the toolkit to implement their own modules quicker and have more consistency.
What is the plan?
-
Finish the Configuration.Ui module and improve its value.
- Maybe integrate the packages module to have one module for system related information.
-
Implement a common package with a basic set of reusable backend components and HTMX helpers which are used by the Configuration.Ui and Workspace.Ui.
Who will work on this?
-
anyone who wants to join in
What do we need?
I’d like to apply for a funding of 5.000 €.
- Yes
- Abstain
- No (please leave a comment)