937719 - Add a pitch for careers in the source on the mozilla.org front page

Status: RESOLVED FIXED

(Websites :: Tabzilla, enhancement)

Description

[Fred Wenzel [:wenzel]]

Something I saw on the Interwebs:

To entice people to apply for a job or participate as volunteers, we should add a pitch for the careers page to the Mozilla.org front page.

I suggest the following:
- put a message into the DOM (in a display:hidden node, maybe?)
- push that same message to the console

This way both "view source" and "open the console" people see it.

If you give me a text, I am happy to file a pull request.

Comment 1

[Fred Wenzel [:wenzel]]

Mathew, what do you think, and do you want to give the phrasing a shot?

Comment 2

[Chris More [:cmore]]

Since the mozilla.org homepage is now localized, should this hidden comment be localized or en-US only? Probably en-US is suffice given the careers and jobvite en-US experience.

Comment 3

[Fred Wenzel [:wenzel]]

If the text is in the DOM somewhere, it can easily be localized. Doesn't mean it has to, of course.

If it originates from some JS code, then it's probably easiest to stick with English.

Comment 4

[Paul [:pmac] McLanahan]

This might be a cool addition to Tabzilla actually. It's both JS and has localized strings, so it could do both (just for the console) and would show up on most mozilla sites. We could do the source comment as well, but it'd be nice to get it out there even wider. It's possible this is too intrusive a use of Tabzilla though. Thoughts?

Comment 5

[Fred Wenzel [:wenzel]]

Are tabzilla users decidedly internal to Mozilla? Then I think it'd work quite well. When using Tabzilla you're already pulling in centrally provided content at the top, I don't think the console logging would be intrusive. After all, only a small amount of users will see it. Besides, it's not all that different from adding "want to join Mozilla?" to the tabzilla content itself.

Comment 6

[Paul [:pmac] McLanahan]

Agreed. I think tabzilla makes the most sense from a message distribution and l10n perspective. Let's do it :)

Comment 7

[Fred Wenzel [:wenzel]]

I added a pull request for this: https://github.com/mozilla/bedrock/pull/1411

pmac, Mathew: r?

Comment 8

[[github robot]]

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

https://github.com/mozilla/bedrock/commit/cebcf013aa8bf2a182056c0533863afb59fc141d
Careers teaser in comment and error console. Bug 937719.

https://github.com/mozilla/bedrock/commit/f3028a77e034cdc196f951e9e7eff5a2a9586eee
Merge pull request #1411 from fwenzel/careers-teaser

Careers teaser in comment and error console. Bug 937719.

Comment 9

[Fred Wenzel [:wenzel]]

Landed on master!

Comment 10

[raymond [:retornam] (inactive)]

fixed on dev

Comment 11

[raymond [:retornam] (inactive)]

verified fixed http://www.mozilla.org/en-US/

Comment 12

[Edgaras]

<meta charset> element must be *within the 512 first bytes* of the page.

This teaser should go after <meta charset>.

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta#attr-charset

Comment 13

[Chris More [:cmore]]

(In reply to Edgaras from comment #12)
> <meta charset> element must be *within the 512 first bytes* of the page.
> 
> This teaser should go after <meta charset>.
> 
> https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta#attr-charset

Thanks for the note!

Wenzel: can you do another PR to over the charset up above the careers teaser?

Comment 14

[Fred Wenzel [:wenzel]]

We don't reopen verified bugs for a new issue normally, but yes I can.

Comment 15

[[github robot]]

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

https://github.com/mozilla/bedrock/commit/875503f36ce558df58da7b0b54a39c355be761a5
Move charset declaration up in page, so it is within first 512 bytes. Bug 937719 comment 12.

https://github.com/mozilla/bedrock/commit/7ef5a41f2bb56bc571173e6f6b1a45e8de11609e
Merge pull request #1469 from fwenzel/meta-charset

Bug 937719 comment 12: Move charset declaration up in page

Comment 16

[Fred Wenzel [:wenzel]]

Sad that the W3C validator did not appear to flag this, btw.