Skip to content
This repository has been archived by the owner on Nov 21, 2018. It is now read-only.

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

Merged
merged 26 commits into from
Jan 14, 2015
Merged

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

merged 26 commits into from
Jan 14, 2015

Conversation

mikeal
Copy link
Contributor

@mikeal mikeal commented Jan 12, 2015

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
Copy link
Contributor

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.

iojs-v1 0-screenshot

@mikeal
Copy link
Contributor Author

mikeal commented Jan 12, 2015

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
Copy link
Contributor

domenic commented Jan 12, 2015

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

@mikeal
Copy link
Contributor Author

mikeal commented Jan 12, 2015

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

@ruimarinho
Copy link

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

<li><a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/template_strings">Template strings</a></li>
</ul>

<p>You can view a more detailed list, including a comparison with other engines, on the <a href="https://kangax.github.io/compat-table/es6/">compat-table</a> project page.</p>

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

@Fishrock123
Copy link
Contributor

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

<div class="faq-body">
<ul class="task-list">
<li><a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/class">Classes</a> (strict mode only)</li>
<li><a href="http://wiki.ecmascript.org/doku.php?id=harmony:object_literals">Object literal extensions</a></li>

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

@mikeal
Copy link
Contributor Author

mikeal commented Jan 12, 2015

@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.

Which ES6 features are behind the --es_staging flag?
</h2>
<div class="faq-body">
<ul class="task-list">

This comment was marked as off-topic.

@Fishrock123
Copy link
Contributor

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
Copy link
Contributor Author

mikeal commented Jan 12, 2015

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

@Fishrock123
Copy link
Contributor

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.

How do I find which version of V8 ships with a particular version of io.js?
</h2>
<div class="faq-body">
<p>io.js provides a simple way to list all dependencies and respective versions that ship with a specific binary through the <code>process</code> global object. In case of the V8 engine, type the following in your terminal to retrieve its version:</p>

This comment was marked as off-topic.

<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="description" content="iojs">
<meta name="keywords" content="iojs, io.js, io js, javascript io, uv, libuv, node-forward, node forward, node, node.js, node.js forward, nodejs, nodejs forward, javascript">
<title>Javascript IO - FAQ</title>

This comment was marked as off-topic.

@ruimarinho
Copy link

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.

<div class="release-windows"><a href="">Windows</a></div>
<div class="release-mac"><a href="">Mac</a></div>
</div>

<p>
<a href="https://iojs.org/download/nightly/">Nightly releases</a> are avaliable for testing.

This comment was marked as off-topic.

@ruimarinho
Copy link

@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
Copy link

fixe commented Jan 13, 2015

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

screen shot 2015-01-12 at 23 58 21

@mikeal
Copy link
Contributor Author

mikeal commented Jan 13, 2015

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 Fishrock123 deleted the 1.0.0 branch January 13, 2015 21:38
@Fishrock123
Copy link
Contributor

oh shit

i give up on git

@Fishrock123 Fishrock123 restored the 1.0.0 branch January 13, 2015 21:43
@Fishrock123 Fishrock123 reopened this Jan 13, 2015
@snostorm
Copy link
Contributor

@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 Fishrock123 mentioned this pull request Jan 13, 2015
@Fishrock123
Copy link
Contributor

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
Copy link
Contributor

Note to self: update the docs link before closing.

@snostorm
Copy link
Contributor

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
Copy link
Contributor

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.

Fishrock123 added a commit that referenced this pull request Jan 14, 2015
1.0.0 Release Website
@Fishrock123 Fishrock123 merged commit 41002a2 into master Jan 14, 2015
@rvagg
Copy link
Member

rvagg commented Jan 14, 2015

good work everyone involved in this!

@mikeal
Copy link
Contributor Author

mikeal commented Jan 14, 2015

Amazing job everybody!

@snostorm snostorm deleted the 1.0.0 branch January 14, 2015 15:29
snostorm pushed a commit that referenced this pull request Feb 27, 2015
Flytte /blogg.html over til /blogg
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants