1.0.0 (Work in Progress, Releases on Jan 13th)

[mikeal]

I've improved the messaging, cut out a section for releases, and matched the css to the colors in the logo for the initial release.

Should implement all of #25

[snostorm]

For those curious what it looks like. I do prefer the return to a white scheme over the back.

My one "nit pick" would be the lines between the logo / Beta / date / etc. being a bit too dark.

[mikeal]

Ok, we now have a webpage for ES6 stuff. It is lifted from https://github.com/seegno/io.js/wiki/The-state-of-ES6-on-io.js so I'd like to get @seegno's signoff.

I also linked all the features so that people have an easier time learning more. Would love to get that proofed by @domenic.

[domenic]

Where is it to review? I'd prefer to avoid reviewing the raw HTML if possible.

[mikeal]

hrm.... ya, GitHub should add that feature :)

[ruimarinho]

@mikeal wdyt of adding target blank to all external links?

[Fishrock123]

Hmm, the yellow link text is somewhat difficult to read.

[mikeal]

@Fishrock123

Hmm, the yellow link text is somewhat difficult to read.

Yeah, I'm tying to match to the colors in the logo but they aren't entirely ideal.

[Fishrock123]

Yeah, I'm tying to match to the colors in the logo but they aren't entirely ideal.

I don't think that should be the aim. Can't we make something logo-agnostic? Also did we confirm this was the logo that is being used for 1.0.0?

[mikeal]

@Fishrock123 my thinking was that we could eventually templatize the colors and then swap them out for each release based on that logo :)

[Fishrock123]

my thinking was that we could eventually templatize the colors and then swap them out for each release based on that logo :)

I had also thought about that, but it seems like it would be a lot more work and/or radical design changes too often? Not sure.

[ruimarinho]

Should we add 1 or 2 anchors so that devs can quickly share links around? The FAQ isn't that lengthy right now, but it will probably keep expanding.

[ruimarinho]

@mikeal do you want me to update @seegno's wiki to point to the official FAQ (as soon as the website is published) and add a suggestion there on how to contribute to its content?

[fixe]

@mikeal what do you think about using a yellow background (#f5da55) instead?

[mikeal]

Ok, there's too much feedback for me to process all of it. If you turn feedback in to a PR to the 1.0.0 branch I can probably take it.

[Fishrock123]

oh shit

i give up on git

[snostorm]

@Fishrock123 I think I prefer having the "logo" / title versus nav links in slightly different shades (hence why I put them a bit brighter.) FYI another PR queued up for responsiveness, #32

[Fishrock123]

This is landable upon release as a fully static site, beyond what we have we need to start doing things dynamically, and that is beyond the scope of this PR I feel.

[Fishrock123]

Note to self: update the docs link before closing.

[snostorm]

Agreed on moving to dynamic sooner than later @Fishrock123. I was waiting for the "big launch" and the site to stabilize around it before daring to put up a proof-of-concept PR for it myself. We can continue that on #22.

Should we ping the open issues on mainline repo re: 1.0.0 that the site is more-or-less in a merge ready state for when they go live?

[Fishrock123]

Should we ping the open issues on mainline repo re: 1.0.0 that the site is more-or-less in a merge ready state for when they go live?

oh. Yeah. i forgot there were issue(s) over there.

[rvagg]

good work everyone involved in this!

[mikeal]

Amazing job everybody!