-
Notifications
You must be signed in to change notification settings - Fork 130
Improves homepage, FAQ to better describe the project #53
Comments
I'm going to take a lot of that feedback with a grain of salt. It's written by people who actually are familiar with the project describing what they think people who aren't familiar think about it. If you read it carefully you can tell that they are imposing their own ideas about the project on to the messaging which is what confuses them. The messaging is intended for developers who are slightly familiar with JavaScript and the ecosystem (probably have heard of npm but not io.js). And also for the press and outside commenters to get an idea of what people can use it for. |
You mean other than the "io.js" link in the topline messaging? |
Topline messaging should not include anything about semver. It's great that we've moved to it, I'm stoked, but it's very "inside baseball." This should probably be in the FAQ though, along with an explanation about how the version numbers line up with expectations on stability. |
Atom is already on io.sj?!?!?! |
Yes, @Fishrock123 just opened #54 on this. A "help improve this page" type link, especially on FAQ, ES6 (and future article-pages.) |
Now that the FAQ RP #54 contains a semver description, we can probably move it out of the homepage box or just say somewhere near the version something like "io.js now uses semver, read more" |
Oh I see! Link them to this repo, not to the io.js repo :) Yes, very nice :) |
Updates FAQ to expand “What is io.js”, adds semver section #53
homepage: switch to “unstable”, link changelog #53
There is a lot of feedback today that our website copy is doing a bad job of explaining to outsiders what
io.js
actually is.This is to track some PRs relating to doing a better job of explaining this, sooner than later, as we have a lot of traffic right now.
io.js
" Updates FAQ to expand “What is io.js”, adds semver section #53 #54io.js
? - could be premature. Collecting in WikiThe text was updated successfully, but these errors were encountered: