@ozfossil Thank you for your detailed report. Installing could be easier. But if you managed that (which is doable given a “good hosting/web server” then you have to work out how all this new tech works.
I know several people that just want working web sites and Neos could work for them but the technical barrier (installer, upgrading, composer stuff, CR, Fusion, FlowQuery, Eel, Fusion, AFX…) is just too high.
I might be stating the obvious: not all problems could be solved by money. But working on specific issues with a set budget helps. Saying we need the new CR or more documentation is not specific enough.
The goal of a piece of open source software is usage. The bigger the user base the better. For everyone: users (faster bug fixes, more features, exisitence in the future), agencies (more customers, easy to sell)…
For me, we have a cascade of issues blocking or limiting a wider adoption.
- Installation and first steps should be easy like WordPress (there, I said it )
- Stability (no bugs, should behave as expected, if erros happen let them have a clear error message)
- New features
Those are the qualities I look for in any given OSS. I’ve worked on a different CMS that depended on a handful (literally less than five) people to do development and the releases. And eventually it broke away. They were all working with this system on client websites, earning money. Now it’s close to dead.
It must seem like I am a documentation-nazi but: Documentation is the general barrier.
Good docs support marketing, make installs easy, produces good content.
EDIT: We’re telling our clients to focus on their users needs and cater to them. To write relevant content and that stuff. And we’re not any better than them…