948439 - Add the term HTML5 to the HTML one

Status: RESOLVED FIXED

(developer.mozilla.org Graveyard :: General, defect)

Description

[Robert Nyman]

Before the redesign launch we added the term HTML5, i.e. "HTML & HTML5" and it resulted in a higher click-through. I suggest we add it to the redesigned MDN as well.

Comment 1

[Jean-Yves Perrier [:teoli]]

Summary of my opinion (posted on IRC initially) [as requested by Maris]:
1. We deemphasize HTML5/CSS3 inside the pages. We indicate it in Specification boxes, but no more in banners.
2. We do SEO for HTML5 and CSS3 (we have specific pages for these), because people are looking for these words.
3. Opinion: we should have them (the word and the link to the specific HTML5/CSS3 pages) on the MDN home page (as people will look at them there)
So we de-emphasize them, but we don't obliterate them.

I proposed "HTML & HTML5" (two links) and "CSS & CSS3" (two links) on the landing page where now is HTML5 and CSS3

Comment 2

[Luke Crouch [:groovecoder]]

Which links? https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/HTML5 and https://developer.mozilla.org/en-US/docs/Web/CSS/CSS3 I assume?

Comment 3

[Luke Crouch [:groovecoder]]

What is "the landing page where now is HTML5 and CSS3" ? The home page?

Comment 4

[Jean-Yves Perrier [:teoli]]

Yes and yes (the home page).

Comment 5

[Luke Crouch [:groovecoder]]

Double-check me? https://github.com/mozilla/kuma/pull/1748

Comment 6

[Māris Fogels [:mars] (please needinfo)]

Are we tracking this fix's effect on the click-through rate?  Do we have a baseline?

Comment 7

[[github robot]]

Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/97941c5084527496b197125a8903c9fe8d70375f
fix bug 948439 - add HTML5 and CSS3 links

https://github.com/mozilla/kuma/commit/1af08a4b1e0f1f7d5ed0a57c548a3dfc883a1d2a
Merge pull request #1748 from groovecoder/buzzwords-bingo-948439

fix bug 948439 - add HTML5 and CSS3 links

Comment 8

[Luke Crouch [:groovecoder]]

Hmm ... we can track the click-thru rate in GA so we can always create a GA report on it later if someone challenges the decision.

I'm personally confident enough in the change based on the A/B test metrics though.