TODOs

There are quite a few things we need to work on. These are somewhat in the order of importance:

Prior to launch

1. Make the jumbotron (front page) a bit smaller. I think we want to keep it relatively big, so that people that have no knowledge of ModeShape can quickly understand what it is (e.g., "a database"). We might want to change the background to a light grey, making it stand out less and tie it in to the rest of the page.
2. Make the jumbotron subheaders on other pages (like Legal) smaller, too.
3. The new logo concept - have designers work on it
4. Try generating some pages from Textile. The goal is that the TOC used on the Legal page is completely generated from the main content. We don't necessarily need the documents for the announcement (we can simply point to Confluence), but it'd be good if we can know that we can generate the pages we want.
5. A "JBoss" page that summaries our integration with JBoss AS and EAP (e.g., benefits, how to install, how to use within web apps, perhaps links to the JBoss-specific document), contains some Red Hat marketing (this will be really important if modeshape.org is an independent site), and can be where we talk about support via EDS. Should this go in the menu? If not, where? Perhaps in the "marketing" blocks on the first page?
6. What to do about ModeShape Tools? Same as "JBoss"?
7. Should we have a "Support" page in the menu? Should we rename "Community" to "Support"? If so, we could just say on that page that ModeShape is an open source community project where the community does the support and that there is no paid support. (This would be a good spot to link to the JBoss page.) And then the page could talk about JIRA, IRC, forums, and GitHub community; see Arquillian's community page for a nice example of this. One benefit of changing "Community" to "Support" is that we can then remove the "Issues" link from the menu.
8. Create "Downloads" page. Not sure about the layout. The simplest would be to use a Ruby partial to generate (from the data in the _config/releases.yml file) a table containing a row for each release and a column for each artifact. Above the table we could describe each kind of artifact.
9. Page structure - are we happy with this. Maybe we should plan the structure for all of the pages (to make sure it's consistent and well-thought out), and then figure out which subset goes into the menu.
10. Custom 404 page (this is easy).

After launch

1. Add blog
   1. Add support for the blog generator.
   2. Migrate existing posts on old blog to files in here (should be able to export, but converting to textile may be time-consuming - though maybe faster than scripting it)
2. Documentation
   1. Determine what documents we want. Here are some ideas:
      • Getting Started
      • Introduction (detailed feature overview)
      • JCR Overview (or maybe "ModeShape API" that would cover both JCR and our extensions)
      • Embedding ModeShape (JSON configuration, ISPN configuration) using it in web apps and
      • Using ModeShape in JBoss AS (or EAP)
      • Using sequencers (including writing custom sequencers)
      • Using queries (including using text extractors; how to write custom text extractors)
      • ModeShape security
   2. Add content from Confluence