4
I agree with the comments as well, however as someone with no coding ability at all, I think I've done quite well with XOOPS so far.
The size of the core does not matter to me but the simplicity of use does. If I had asked for a more basic explanation every time I read a thread that seemed to apply to my situation, but I just couldn't understand, I would be labeled a spammer.
I find that the documentation for installation is generally suited to my level of user. What I find lacking is the usage documentation for both the core and the modules. They say what you can do with a module, but not always how or why you would want to. XOOPS is an ongoing journey of discovery for me!
Fortunately my introduction to XOOPS was with an install of 2.2.3 that gave me no problems whatsoever while I used it. I'm not sure that I would still be here if that had been 2.3.1 but you never know.
Finding modules and establishing compatibility is another issue for me. There are so many modules not in, or not updated in the repository that it is work to determine if something works with 2.3.1 or not. Sure, there is the forum for exactly that, but a new user will be digging through 31 posts perhaps to build a list that would ideally be available on a single wiki page.
The forums are great of course, but a comprehensive list of what is compatible would save a lot of posts.
I think it is safe to say that the module and core developers are about as interested in writing manuals and help files as the basic users are in interested in reading readme files.
Do you ever write something and then think "Why did I spend that time suggesting that someone else do something?"
Here is a wiki page for
Modules compatible with 2.3.1
Optimism is the mother of disappointment.