Community Docs

Some Reasoning

Github repos are great. Wikis are informative. However, code-heavy and pattern-rich jargon usually just scares people off. Let's shoot for enjoyable, informative, and most importantly: non-threatening. Also, make sure we answer the often-overlooked question: "what the hell am I looking at?"

Portal for all Fubu projects

Aggregate (nothing fancy or dynamic, just a quick "splash page") info for the fubu-family of frameworks. The purpose is to have a central place to point people for information about everything "Fubu".

Perhaps it would be a good idea to have a dedicated section for what the "fubu mindset" is about as this reflects all fubu related projects.

We need to decide on:

Dynamic content (CMS) vs. Static content (basic html) vs. ??

Site for each Fubu project

Something we can point people to for project-specific info (e.g., validation). Give a splash site for basic info and then subdir for docs (using Sphinx?). Good example: http://masstransit-project.com

Layout and styling

Need to try and keep some consistency across all of our projects. It is important that we keep our style simple and user-friendly.

Backend for documentation

We need to make a decision on what we're going to use. Seems like Sphinx is going to be the way to go. We need to figure out the most sound approach to integrate these docs with a site.