Website checklist for 1.0.0

[Fishrock123]

See nodejs/node#304 & nodejs/node#302

Critical

• Better design
• Static blog for announcements Static Blog page #68
  • some sort of changelog integration?
• docs / linkage doc: update style for iojs node#297
• Updated FAQ
• ES6 on io.js

When possible

• Release page that is updated on release and nightly build Dynamic Release Page #67
• Better site navigation
• Changes since node 0.10 opted for link to CHANGELOG.md

Please edit this to fill gaps / etc as necessary.
cc @mikeal @chrisdickinson @rvagg @zeke

[snostorm]

Can we add a simple one on here? Moving to using a dist/, build/ or public/ sooner than later? That way if/when a build workflow is incorporated it'll be less of a hassle to migrate forthcoming PRs.

I can open a dual-PR in here and build (based around dist/, my preference.)

• #22 Adds compiled assets directory #26
• www: sync from public/ for iojs/website#26 build#31

[snostorm]

Just cross-linking the "changelog integration?" thought to nodejs/node#305

[mikeal]

I don't think we need a blog yet. We can get by without one for the initial release.

For a changelog we can just link to the changelog in the source tree.

I think the main page should have the latest releases on it (for now) and once we have quite a few the front page should only have latest stable and unstable.

[Fishrock123]

I don't think we need a blog yet. We can get by without one for the initial release.

I think we can get a static blog up for announcements, I'll look into it.

I think the main page should have the latest releases on it (for now) and once we have quite a few the front page should only have latest stable and unstable.

stable, unstable, and nightly imo

(second thought.. yeah maybe not nightly. idk)

[mikeal]

stable, unstable, and nightly imo

Definitely. At the moment we only have an unstable (beta) release to put there, and we're still linking to the nightlies page. Once the build process automatically updates the website we can have it update the nightly every night.

[snostorm]

@Fishrock123 getting a static blog up probably ties in to #22

Are you guys discussing some of this "offline" in IRC or something? I've been meaning to jump on the freenode and get a little more involved there in realtime.

[Fishrock123]

@snostorm I'm almost always in irc (#io.js), but @mikeal doesn't like irc haha

[Fishrock123]

added - [ ] Changes since node 0.10 since I don't think there is full summary anywhere.

[mikeal]

What updates do we want to make to the FAQ? I'll write a better "how to get involved" section. What else?

[Fishrock123]

@mikeal this stuff http://blog.izs.me/post/104685388058/io-js

[rvagg]

https://github.com/joyent/node/wiki/API-changes-between-v0.10-and-v0.12

but it's usually very poorly updated

[ruimarinho]

@Fishrock123 what about adding analytics of some sort like ga? It would be interesting (and probably just that) to have an idea of reach. Is anyone taking care of twitter too? The iojs handler is taken by an individual already. The first tweet coinciding with v1.0.0 would be cool :)

[shuhblam]

any designers in the mix for this site?

[mikeal]

@colegillespie I wish! :)

[Fishrock123]

@zeke should be, I think. :o

[zeke]

I took a pass at cleaning it up here: #30

[snostorm]

@colegillespie I am trying to ramp up my ability to help but unable to meet the imminent deadline this time. But now, we have another full release cycle to really get things organized.

[shuhblam]

@snostorm zekes update looks pretty slick though

[snostorm]

@colegillespie things are looking a lot better. I agreed zeke added some nice improvements. Long term the design will still need to evolve with the more complex needs of growing content / sections. That's all I mean :)

[Fishrock123]

Splitting into multiple issues.