Documentation would be GREAT but you know what? Our website(s) SUCK. I think this is where we start. I want something that at a glance can tell someone:
- This is what exists in the Fubu family of frameworks (maybe a simple graphic -- I'll explain later)
- Links to the details of each individual framework
- Links to the "philosophy/why" of the framework
I want it braindead simple like: http://nancyfx.org/. Friendly and very welcoming tone. One that makes noobs feel at ease.
We talk too much and don't put our money where our mouths are. We do it because, as you said, there are a LOT OF CONCEPTS. We just don't make quite make it real enough.
Two examples of what I'd like to see:
From the "main page" of the FubuMVC area, I want people to be able to:
- Get their hands on a sample app
- Find out who contributes and how active we are
- Find out some history if they're interested
- Immediately get prompted to learn more about how Fubu works
The prompting needs to push people into learning our core architectural concepts. I want to redo this one, but I had a lot of success with explaining things through this one: http://vimeo.com/27914383
I want something like that distilled across the site.
Again, people should be able to:
- Know that it's our foundational framework that everything depends on ("Ok, so using Fubu means I will ALWAYS have to deal with this")
- Know it's dependencies
- Find out what it can do (maybe we just copy/paste from Chad's "Cool stuff in FubuCore" series. Summarize his points and link to his posts)
Very soon we're going to have a thriving ecosystem made possible by Bottles and delivered through Nuget. A lot of the ones that Jeremy and I have planned are going to be able to do some CRAZY things for your apps.
Each framework area should sport a nice listing of the available "plugins". Give them nice landing pages of their own, shout outs to the author(s), etc.
Documentation is great but it's only helpful when people know just what it is they're learning about. Let's give them the first step, eh?