Moves in-site nav links to header, adds docs link

[snostorm]

No description provided.

[Fishrock123]

[Fishrock123]

cc @zeke Thinking of this with the same sizing/color as the text logo, LGTY? I'll fix it up.

[zeke]

👍

[mikeal]

I'd like to move back to the messaging I put together yesterday. This is a little long winded :)

For reference, this was the messaging:

Bringing ES6 to the Node Community!
io.js is an npm compatible platform originally based on node.js™.

[Fishrock123]

Oh, Whoops. Didn't realize that was removed.

[snostorm]

If the structural changes are good we can handle any tweaks (especially to content wording, as per @mikeal) back on the primary 1.0.0 branch?

[Fishrock123]

Maybe we should move the government and nightly lines into the footer, or below the release?

[mikeal]

It would be best to note the nightly link in a similar style as the beta release and, hopefully soon, we can actually swap that out for an automated link to the latest nightly.

[snostorm]

I'm sure soon enough there will be some sort of download/releases page.

[mikeal]

Governance should be another link next to the GitHub Issues and whatnot. It was top level messaging before we had a release, and still is an important part of the project, but IMO the top level messaging should just be about what is the in current release and what users can sink their teeth in to.

[Fishrock123]

It would be best to note the nightly link in a similar style as the beta release and, hopefully soon, we can actually swap that out for an automated link to the latest nightly.

Yeah. I'm mulling over build options right now, though I'm still just leaning towards a .js that builds markdown and shoves it into a handlebars template.

[Fishrock123]

Governance should be another link next to the GitHub Issues and whatnot. It was top level messaging before we had a release, and still is an important part of the project, but IMO the top level messaging should just be about what is the in current release and what users can sink their teeth in to.

it's in the FAQ iirc.

[mikeal]

any objections to merging this? i'd like to tweak the messaging back in the 1.0.0 branch.

[Fishrock123]

I'm going to tweak this and land it. Feel free to patch the other branch with other things.

[mikeal]

@Fishrock123

Yeah. I'm mulling over build options right now, though I'm still just leaning towards a .js that builds markdown and shoves it into a handlebars template.

Why don't I log an issue about the logo selection and nightly process in io.js so that we can statically link to a "latest logo" and "latest nightly" build of each type rather doing a whole build and push process?

[Fishrock123]

The idea is to have a script which the build triggers, not us. (and out of repo)

[snostorm]

+1 latest nightly (being a static and predictable link.) Same for nightly docs, etc.

Logo I have mixed feelings on, since (if) we have 1-logo-per-release down the line, we might end up having the CHANGELOG/release articles/etc. show the logo that existed for the version. Would be a nice touch for historic purposes, eventually.

[mikeal]

I reverted the messaging the main branch.

[snostorm]

@mikeal @Fishrock123 Fixed this branch to deal with the conflict that commit added. It is merge-able once again. (We should probably merge sooner than later and just tweak anything else on the main 1.0.0 PR, as it isn't live anyway.)

[Fishrock123]

Please don't merge upstream. Rebase, if anything.

[mikeal]

I understand the need to be picky about cleanliness off the commit log on bigger projects but this is just a simple website, I don't think that we need to be obsessing about merge vs. rebase issues.

[snostorm]

@Fishrock123 @mikeal I squashed this back to a single commit. I'll stay out of the rebase-or-not debate for tonight ;) Should be good to merge to the mainline 1.0.0 branch.

[Fishrock123]

landing in 1732823 / #27