WWW future (v2 and v3)

[jamesplease]

Putting up our docs on the site is, in my mind, the mark of our website reaching v1. You guys did a ton of great work getting us here, and I'm really, really happy with what you've accomplished. Nice job @thejameskyle @jasonLaster @ahumphreys87 and @samccone! Moving traffic from the Github README's to the website is a really good step for us, I think. (...Ok so I know we're not quite done. We still need to link and stuff. But whatevs. Close enough.)

Anyway, once that's all squared away we'll need to start looking at what's next. So I'm making this issue to list what I'd like to see for the second version of the site. These are some lofty goals, but I think we can do it. And it goes without saying that I'd like y'alls feedback on these goals, and I'd love to hear what you think we should work on.

v2 goals

1. Unified website/docs theme. This could involve a major redesign of the site, or maybe minor tweaks. Either way I think they should look like the same entity. Right now the site looks fine, and the docs look fine, but they're much too different.
2. Splitting out the docs into API/Guides/Getting Started sections. In v2 of the site I want each of these endeavors to be off to a strong start, and a lot of my own resources will go toward making this a reality. I'll probably just go crazy for a week and try to finish all a first draft of the API in one go.

Yup, so just two goals. But I think it's enough work to keep us busy.

For v3, I'd like to see us utilize our website as a resource to the fullest extent that we can. We should have downloads for every version. We should have links to screencasts and tutorials. Meetup info, our official blog, changelogs, links to all of the tools we build for Marionette (upgrade scripts, polyfills)...all of this should be on the site in an intuitable, organized way.

Our website is our face, and likely the first thing people go to when they research the project. And when they do I want them to be compelled to sit down and learn what makes Marionette so awesome. I'm not sure if our website does that quite yet, but if we work on it some more I'm confident we can make it that way.

[ahumphreys87]

👍 the branding does need to be consistent I think.

For guides and getting started we could use recipes and add readme files, we can pull those in

[jasonLaster]

Thanks for the write up! I'm 100% behind this. Let's get it done.

On Sunday, May 18, 2014, Andrew Humphreys [email protected] wrote:

[image: 👍] the branding does need to be consistent I think.

For guides and getting started we could use recipes and add readme files,
we can pull those in

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/70#issuecomment-43434276
.

Jason Laster
Software Engineer
Etsy

[jamesplease]

Here's a doc that has some basic copy for marketing Marionette. I'm no copywriter but it's a start?

I'd say there are 5 big reasons to use Marionette, and those are three of them. The fourth would be how unopinionated it is, following in Backbone's footsteps. The fifth would be how customizable it is when you want to change the way something works.