Nodejs.org: Plans for frontpage related to 2 x LTS releases + current

[phillipj]

Any thoughts on how we could improve the current UX related to displaying 2 x LTS releases, plus the current release (v7) coming soon?

Tonight v6.9.0 transitioned into LTS 🎉 That means we currently have two LTS releases, and no current. With https://github.com/nodejs/nodejs.org/pull/973 merged we now display these two releases side by side, which I assume is quite confusing and not ideal in the long run.

And what should we promote when a new current release is cut? Only display v6 LTS + v7 current? v4 is still LTS thought, so it's probably still valuable for those who don't want to jump the v6 train just yet.

[MylesBorins]

the simplest way to move forward is to revert the change I landed when 7
drops and simply have a single Lts v6 and current v7

I've thought about this quite a bit and think it is the right move. people
who want v4 will know how to find it. we can bring the "all versions " link
further up the page and make it more noticeable

On Tue, Oct 18, 2016, 8:16 PM Phillip Johnsen [email protected]
wrote:

Any thoughts on how we could improve the current UX related to displaying
2 x LTS releases, plus the current release (v7) coming soon?

Tonight v6.9.0 transitioned into LTS 🎉 That means we currently have two
LTS releases, and no current. With #973
https://github.com/nodejs/nodejs.org/pull/973 merged we now display
these two releases side by side, which I assume is quite confusing and not
ideal in the long run.

[image: screen shot 2016-10-18 at 21 11 31]
https://cloud.githubusercontent.com/assets/1231635/19492571/78d0b89a-9577-11e6-8c91-49ecabd39d63.png

And what should we promote when a new current release is cut? Only display
v6 LTS + v7 current? v4 is still LTS thought, so it's probably still
valuable for those who don't want to jump the v6 train just yet.

[image: s1] https://github.com/nodejs/LTS/raw/master/schedule.png

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nodejs/nodejs.org/issues/982, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAecV3ipBan3EAtfCrIAS4WJUGRBl9Wzks5q1RrvgaJpZM4KaLm1
.

[phillipj]

Going back to promoting two releases in total would at least avoid "which LTS should I choose" questions which I see as the biggest confusion.

people who want v4 will know how to find it

Sure enough, if not, we'll probably hear from the users struggling.

[mairead]

I submitted a layout for a tabbed version in the previous issue #953, which Axel had originally suggested but I'm actually thinking if you want something scalable (so 1, or any future number of releases) and something mobile friendly you'd be much better putting it all in an accordion and having the preferred version expanded on page load. Horizontal layouts like tabs are lousy on mobile especially if the number of useful releases to promote is something which changes frequently. I am struggling to follow all the conversation here though. Is there actually a consensus on this yet?

[gibfahn]

@mairead I think all the opinions on here so far are against adding more than 2 releases, so I think the current website version (one LTS, one Current) should be fine.

[mhdawson]

I've also commented that I think the one LTS and one Current is fine. Next time we switch over I'd recommend that during the transition we should show the same release as LTS and as Current until the new current is available. In that way we'll be always be consistent with one LTS and one Current version being promoted. I agree may look a little odd during that week, but I think less odd than switching to 2 LTS releases for one week.

[MylesBorins]

what was particularly confusing was that current was an 6.8.1 while Lts was
6.90

On Wed, Oct 19, 2016, 2:58 PM Michael Dawson [email protected]
wrote:

I've also commented that I think the one LTS and one Current is fine. Next
time we switch over I'd recommend that during the transition we should show
the same release as LTS and as Current until the new current is available.
In that way we'll be always be consistent with one LTS and one Current
version being promoted. I agree may look a little odd during that week, but
I think less odd than switching to 2 LTS releases for one week.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/nodejs/nodejs.org/issues/982#issuecomment-254820649,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAecV1mn710JebXAfmwhJ6mr-lW7hfCKks5q1iIDgaJpZM4KaLm1
.

[gibfahn]

I guess we do need to have Current and LTS at least matching (e.g. at 6.9.0) in the interim period.

[MylesBorins]

we could also have a greyed out current that days coming soon

On Wed, Oct 19, 2016, 3:12 PM Gibson Fahnestock [email protected]
wrote:

I guess we do need to have Current and LTS at least matching (e.g. at
6.9.0) in the interim period.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/nodejs/nodejs.org/issues/982#issuecomment-254824675,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAecV-Sr2oRG7E6BGiMhwRnvyEpMK4e_ks5q1iU4gaJpZM4KaLm1
.

[mhdawson]

I like the idea of greying out with the coming soon.

[phillipj]

@TheAlphaNerd something like this?

[MylesBorins]

that looks great to me!

it doesn't cover the download page though

On Wed, Oct 19, 2016, 8:01 PM Phillip Johnsen [email protected]
wrote:

@TheAlphaNerd https://github.com/TheAlphaNerd something like this?

[image: screen shot 2016-10-19 at 20 59 03]
https://cloud.githubusercontent.com/assets/1231635/19533153/eba02a5a-963e-11e6-9289-9c4d61578fbd.png

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/nodejs/nodejs.org/issues/982#issuecomment-254909155,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAecV9AYDwqzylUJ7qlvJJUwpFFRCuseks5q1mkFgaJpZM4KaLm1
.

[ronkorving]

Please also mark v6 as LTS on https://nodejs.org/en/docs/

[mhdawson]

looks good to me as well, provide of course we do it everywhere the 2 are shown.

[MylesBorins]

We decided to stick to a single lts. Closing but feel free to reopen or make a new issue