Rethink the purpose of the home page

[jamesplease]

The home page does too much right now, and by doing that, it isn't doing enough.

Let's take downloads, for instance. The downloads section expands on the download link offered at the top of the page, but it doesn't expand on it enough. There isn't, for instance, a way to access downloads for versions older than the most recent one.

It would be insane, I think, to try to fit all of that content on the home page. If we left downloads where it is, then you would be able to access a download to year-old versions of the library before you've even seen an example of it in action!

This problem affects most of the sections of our homepage, I think. We're losing out by putting everything on this one page.

Ember and Angular have their home pages right. Other than the top part with a download button, the rest of the page is effectively marketing. Our home page should be, too.

For the things that we do decide to highlight on the home page, like perhaps screencasts and books, we should have dedicated pages for them that show a more complete list.

To break this issue into actionable items, I propose that we:

• Create a dedicated downloads page
  • Add the ability to download previous versions to that page
• Remove the downloads section from the home page
• Expand on the examples on the home page
• Add some number of dedicated pages for learning resources (blogs / screencasts / etc.). I'm not sure if we would want one page for them all, or different pages for each, or maybe grouped together?

What do y'all think?

[samccone]

related work that we have already done https://github.com/marionettejs/marionettejs.com/issues/52 https://github.com/marionettejs/marionettejs.com/issues/79 https://github.com/marionettejs/marionettejs.com/issues/96

[samccone]

any wireframes or sketches anyone has are more than welcome