My thoughts:
I don't want to knock the developers in this post or the community in any-way shape or form. But just wanted to share some thoughts with suggestions for improvements.
Seblod has the potential to be awesome, but at the moment it is also very frustrating. I really want to love it, but sometimes it is hard. I would say though that for the most part the community here does try to help each other out as much as possible, and that is a good thing.
Although at points develop seems slow, that is understandable if people are giving this away for free.
Biggest frustration and time waster
I think that the main problems I have, come down to documentation. If you try and do anything that is slightly away from "adding a field", things get a little hazy (creating an RSS feed from a search result list for example). Documentation is bad in a number of different areas;
- Within the app itself. I often hover over a field (as it looks like it might have a tool-tip or something) in the hope that I would find out some more information about what is does or affects, and there is nothing.
- While there has been some new docs put on this site. So much important information still remains on the "V2" version of the site. People in the forums are often directed back there.
- There seems to be so much "secret" knowledge, about how to do things. Some of this is found in the forms, of which the search is pretty poor. Some in the old forums, which I think that search has been switched off.
- There are some good videos out there from community members that have really helped. I'm always so thankful and amazed that people have give their time freely to help others. Thanks. Google or Youtube searches tend to work well, but it would be great to have some type of collection here on the Seblod domain.
- I've tried to watch some videos from last years (Joomla) events that Seblod spoke at, and my goodness the recordings were the worst I've seen (terrible audio and not really able to even see what is going on) but seemed to contain good important help information. I know that this is not Seblod fault at all, but please at least check things are setup ok.
- Some of the extensions, evening understanding what they do, is ambiguous
I've used Yootheme's Zoo for years and years and one thing I appreciate is their documentation. Although it at points seems a little lacking, at least it is clear and to the point.
Suggestion for improvement (a community call)
I know that documentation writing is a real chore, but I wonder if we as the community could possible participate more in this process, and build a really well documented CCK. Leaving the developers to continue to work on... well.... developing the product, and only jumping in where needed. I know to a point that this already seems to happen, but is there room for improvement.
Yootheme use github for their documentation, which I think is a brilliant idea and something that could really work well for Sebold. Or hack even a wiki could work. Also I think that this would expose the gaps in documentation (knowledge) where the develops can easily jump in. Even just transferring and updating the old V2 documentation would be a good starting point.
Suggestion for training resulting in documentation
Something I have even considered, is buying time with the developers just for training on some of the knowledge gaps I have while trying to complete projects. Maybe there could be some sort of deal where there was a portion of free time given by the developer in exchange for create the documentation after will real world examples. I know that there would need to be some sort of coordination with that, but I think it would be possible.
For example one hour of time (which that developers currently give away one hour at the moment) with the developer to go through a predetermined subject/s. Then serval hours of documentation given by the person based on the training. I would see the benefit for Seblod and the documentation being huge.
Closing remarks
This has become a long reply, but I think Seblod could be "worth it" if documentation improved. And I'll willing to help. What's your response (community)?
Possibly some of the frustrations that Ricco feels in that questions going unanswered might be solved with great documentation.
Thanks again to all in the community to help out, and Seblod who are on their way to making a better CCK.