Closed Bug 918127 Opened 11 years ago Closed 10 years ago

Create Developer Program landing page content

Categories

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

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: openjck, Unassigned)

References

Details

Attachments

(1 file)

When we launch the redesign beta at the end of Q3, we will link to a Developer Program landing page. This page will need to be completed by that time.
Blocks: 918129
The page does not have to be done at that time. We don't plan on officially launching the Program by then, so the link to the Developer Program should initially be hidden.
Blocks: 914840
No longer blocks: 917852
Blocks: MDNLaunchBlockers
No longer blocks: 914840
Blocks: 910513
No longer blocks: 910513, 918129
Ping: We're including the dev program landing page with the redesign launch, right? 

Robert: can you create a wireframe and/or mockup of the landing page for implementation by dev and content teams?
Flags: needinfo?(robert)
Short answer: it depends on what things we can have in place, I believe. I don't want to launch it if we don't really have much to offer. On the other hand, getting the word out there and then working in short iterations to improve the Program can also be an option.

I plan to file a few bugs to reflect that state - Maris has helped me to set up a component, but I've just been held up by many other things lately.

Question: when is the redesign due to be officially launched?

And yes, I'll try to create a good mockup as soon as I can, but that might take a week.
Flags: needinfo?(robert) → needinfo?(lcrouch)
We are tracking a redesign burndown based on bugs filed/fixed over time:

https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AqjZCAHNVaWEdC1Vclc3aTZaRjRkNUpyeXlDWTdJQWc&usp=drive_web#gid=2

The current projection is first week of December, but things can always change.
Flags: needinfo?(lcrouch)
Ok, thanks!
Assignee: eshepherd → nobody
Component: General → Developer Program
Product: Developer Documentation → Mozilla Developer Network
Blocks: 932711
Summary: Write Developer Program landing page → Create Developer Program landing page content
Depends on: 932717, 932705
Robert, if you put together the main goals and priorities for the developer program page and all the information that will be ready for the first state of its launch, then I can put together a wireframe to review with you. We will be working on a top level template that pages like this, Tools, and others can follow.
Flags: needinfo?(robert)
Hi Holly, thanks, sounds great! Delving through things - it's Monday, after all - but will get back to you in a few days.
Flags: needinfo?(robert)
Depends on: 935711
Depends on: 935712
Thanks for the patience, Holly!
With the Developer Program and where we are right now, I would say that the goals and priorities are:

- Make people aware that it exists
- Stress our will to do good for, and help, developers (with direct help, resources and more)
- Get them excited about the initiative and implications (rather than the few current features we have at this point)

The features that we believe will be in place by early December are:

- Content Zone page on MDN
- Forums on Stack Overflow (http://stackoverflow.com/r/mozilla)
- Newsletter sign-up
- Sign-up. This will initially be for MDN, but should be a single-sign on solution for MDN, Marketplace and AMO over time (discussed/worked on in https://bugzilla.mozilla.org/show_bug.cgi?id=933031)

I've attached a file to give a brief overview of the components that should be in the Developer Program landing page. They are:

- Introduction text, explaining what the Developer Program is (this bug)
- Stack Overflow integration (through the Stack Overflow API, https://bugzilla.mozilla.org/show_bug.cgi?id=932705)
- Hacks feed (https://bugzilla.mozilla.org/show_bug.cgi?id=932717)
- Sign up for the program (https://bugzilla.mozilla.org/show_bug.cgi?id=932707)
- Sign up for the newsletter (https://bugzilla.mozilla.org/show_bug.cgi?id=935711)
- Where is Mozilla? (https://bugzilla.mozilla.org/show_bug.cgi?id=935712)
This is really great, Robert. Thanks a lot. My plan is to take a look at the needs of all top level pages like Tools, Developer Program, and (thinking ahead for) Demos and propose a base template for these pages to use that differs from the Zone level layout. 

I'll look through this further on Friday and at least send you any questions I have before next week since I'll be at a work week in SF then. Thanks again.
Chris, 

It looks like you can you can get much of this content via KumaScript requests to feeds - StackOverflow API [1] hacks rss [2], and events CSV [3].

Les,

Any reason we could not - or should not - use KumaScript to generate all that dynamic content?

[1] https://api.stackexchange.com/2.1/questions?order=desc&min=3&max=3&sort=votes&tagged=firefox-os&site=stackoverflow
[2] https://hacks.mozilla.org/feed/
[3] https://spreadsheets.google.com/pub?key=0AsZa7UiEJyV7dHFQalNmTHF3Qm9md043UkdNV3k3Znc&output=csv
Flags: needinfo?(lorchard)
Flags: needinfo?(cmills)
> This is really great, Robert. Thanks a lot. My plan is to take a look at the
> needs of all top level pages like Tools, Developer Program, and (thinking
> ahead for) Demos and propose a base template for these pages to use that
> differs from the Zone level layout. 
> 
> I'll look through this further on Friday and at least send you any questions
> I have before next week since I'll be at a work week in SF then. Thanks
> again.

Thank you! Just let me know if I can help in any way.
> It looks like you can you can get much of this content via KumaScript
> requests to feeds - StackOverflow API [1] hacks rss [2], and events CSV [3].
> 
> Les,
> 
> Any reason we could not - or should not - use KumaScript to generate all
> that dynamic content?
> 
> [1]
> https://api.stackexchange.com/2.1/
> questions?order=desc&min=3&max=3&sort=votes&tagged=firefox-
> os&site=stackoverflow
> [2] https://hacks.mozilla.org/feed/
> [3]
> https://spreadsheets.google.com/
> pub?key=0AsZa7UiEJyV7dHFQalNmTHF3Qm9md043UkdNV3k3Znc&output=csv

Yeah, if there's an easy existing solution to do this, the better!
(In reply to Luke Crouch [:groovecoder] from comment #10)
> Chris, 
> 
> It looks like you can you can get much of this content via KumaScript
> requests to feeds - StackOverflow API [1] hacks rss [2], and events CSV [3].
> 
> Les,
> 
> Any reason we could not - or should not - use KumaScript to generate all
> that dynamic content?

If what you're looking to pull for dynamic content comes from a JSON-based web API that does not require authentication and offers data that rarely changes... KumaScript is the tool to use.

The gotchas with KumaScript might include:

* We don't yet have an XML (bug 765642) or CSV (no bug) parser available in KumaScript, just JSON.

* Pages with KumaScript macros do not update automatically (bug 773522 & bug 880614) - they need to be edited or shift-refreshed in order to re-run all the macros and fetch fresh data.

* It's difficult to do auth with a web API in KumaScript, because the source of all templates is public and credentials would be exposed. 

If there's just no way to get around auth, I think we might be able to do something like hide the credentials in the config file on the server. Of course, that doesn't guarantee safety of the credentials if someone writes a script that accidentally exposes them.

I tried to include the relevant bug numbers in the gotchas, because they might be worth flagging as blockers to this one. They're things we've wanted to do, but haven't prioritized so far.
Flags: needinfo?(lorchard)
Thanks Les!

> The gotchas with KumaScript might include:
> 
> * We don't yet have an XML (bug 765642) or CSV (no bug) parser available in
> KumaScript, just JSON.
> 
> * Pages with KumaScript macros do not update automatically (bug 773522 & bug
> 880614) - they need to be edited or shift-refreshed in order to re-run all
> the macros and fetch fresh data.
> 
> * It's difficult to do auth with a web API in KumaScript, because the source
> of all templates is public and credentials would be exposed. 
> 
> If there's just no way to get around auth, I think we might be able to do
> something like hide the credentials in the config file on the server. Of
> course, that doesn't guarantee safety of the credentials if someone writes a
> script that accidentally exposes them.
> 
> I tried to include the relevant bug numbers in the gotchas, because they
> might be worth flagging as blockers to this one. They're things we've wanted
> to do, but haven't prioritized so far.

Yeah, I guess some of these could pose problems for us. A quick question about your assessment:

To make this work, would it be worth pursuing those bugs and make it work with KumaScript, or are there other alternatives that might be more suitable?
(In reply to Robert Nyman from comment #14)

> Yeah, I guess some of these could pose problems for us. A quick question
> about your assessment:
> 
> To make this work, would it be worth pursuing those bugs and make it work
> with KumaScript, or are there other alternatives that might be more suitable?

KumaScript is pretty much the best tool we have for this kind of content generation. 

I mean, we could build a script that runs somewhere (not sure where) and uploads changes to wiki pages. But, by the time we hack something like that together, we probably could have made the required improvements to KumaScript
Les, Luke and I were just in a meeting and we discussed the options here. Decision was that KumaScript is the best way to go, and this bug will dependent on the three other bugs Les listed:

Bug 765642
Bug 773522
Bug 880614
Depends on: 765642, 773522, 880614
Removing blocker for bug 880614. If we have a solution for bug 773522, that should be enough for keeping this page up to date and probably simpler to implement.
No longer depends on: 880614
Holly, I believe we need to point to other resources as well from that landing page, such as the YouTube account for Mozilla Hacks: http://www.youtube.com/user/mozhacks Think that can be worked into the template work?
Flags: needinfo?(hhabstritt.bugzilla)
(In reply to Robert Nyman from comment #18)
> Holly, I believe we need to point to other resources as well from that
> landing page, such as the YouTube account for Mozilla Hacks:
> http://www.youtube.com/user/mozhacks Think that can be worked into the
> template work?

Robert, that shouldn't be a problem. I'll dive into this on Monday and share something for you next week.
Flags: needinfo?(hhabstritt.bugzilla)
(In reply to Holly Habstritt [:Habber] from comment #19)
> (In reply to Robert Nyman from comment #18)
> > Holly, I believe we need to point to other resources as well from that
> > landing page, such as the YouTube account for Mozilla Hacks:
> > http://www.youtube.com/user/mozhacks Think that can be worked into the
> > template work?
> 
> Robert, that shouldn't be a problem. I'll dive into this on Monday and share
> something for you next week.

Great, thank you!
I've also started to make the real page on MDN (https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program) look like the mockup, just to get a feel of what we're aiming for.
Robert, I have a few questions for you. The mockup was very helpful, but since I'm creating a new template for landing pages I have a few questions about some of the links. 

In our zones template, the left navigation is used for links within MDN and not link to external sites. In the new landing template, I'll be sure to account for external links (Hacks Blog) or items that we might want to stand out (Sign-up). 

In your navigation in the mockup (http://cl.ly/image/3q3R2X470O20) I want to know the expectations of each link. Can you answer my questions and/or confirm where the links need to go? 

Signup
- You mention that this is specifically for MDN. Do you mean this is this the same as the MDN sign-up in the global nav or completely separate? Bug 932707 makes me think it is separate. If separate, how so? Do we need to ask the users any additional questions in the sign-up flow? Having 2 sign-ups might be confusing, so we may want to consider an opt-in option in the MDN sign-up form from global nav.
 
Mission
- Will this content be displayed as a docs page or is the content short enough to display in this page?

Tools
- Will this link to Tools item in Global Nav?

Documentation
- Where will this link to? Do you want a page that talks about the types of documentation we have or is there a landing page that already exists for documentation?

Hacks Blog
- Links to external Hacks Blog, that leaves MDN site completely. (please confirm)

Ask Questions
- Would this go to a form?

Thanks!


(In reply to Robert Nyman from comment #20)
> (In reply to Holly Habstritt [:Habber] from comment #19)
> > (In reply to Robert Nyman from comment #18)
> > > Holly, I believe we need to point to other resources as well from that
> > > landing page, such as the YouTube account for Mozilla Hacks:
> > > http://www.youtube.com/user/mozhacks Think that can be worked into the
> > > template work?
> > 
> > Robert, that shouldn't be a problem. I'll dive into this on Monday and share
> > something for you next week.
> 
> Great, thank you!
> I've also started to make the real page on MDN
> (https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program) look
> like the mockup, just to get a feel of what we're aiming for.
That's what I get for working with a professional who pays attention to details. :-)
The side navigation was just a mockup that Chris Mills threw together months ago, and I haven't really thought about what it should contain (please interpret that as open for suggestions).

So, I'll skip most questions about the items there. :-)

> In our zones template, the left navigation is used for links within MDN and
> not link to external sites. In the new landing template, I'll be sure to
> account for external links (Hacks Blog) or items that we might want to stand
> out (Sign-up). 
> 
> In your navigation in the mockup (http://cl.ly/image/3q3R2X470O20) I want to
> know the expectations of each link. Can you answer my questions and/or
> confirm where the links need to go? 
> 
> Signup
> - You mention that this is specifically for MDN. Do you mean this is this
> the same as the MDN sign-up in the global nav or completely separate? Bug
> 932707 makes me think it is separate. If separate, how so? Do we need to ask
> the users any additional questions in the sign-up flow? Having 2 sign-ups
> might be confusing, so we may want to consider an opt-in option in the MDN
> sign-up form from global nav.

The idea is that it's the same sign-up that it leads to. There's also another bug about including a signup for the newsletter (bug 932707 and bug 936123). There will be one account for all of MDN, and in the future, including Marketplace and AMO as well.


> Hacks Blog
> - Links to external Hacks Blog, that leaves MDN site completely. (please
> confirm)

I think this one would be good to have, but it has to very clear that it leads to an external web site then.
 
> Ask Questions
> - Would this go to a form?

Same as above. These aren't entirely thought through, though, so I'm definitely open for suggestions and input!


(In reply to Holly Habstritt [:Habber] from comment #21)
> Robert, I have a few questions for you. The mockup was very helpful, but
> since I'm creating a new template for landing pages I have a few questions
> about some of the links. 
> 
> In our zones template, the left navigation is used for links within MDN and
> not link to external sites. In the new landing template, I'll be sure to
> account for external links (Hacks Blog) or items that we might want to stand
> out (Sign-up). 
> 
> In your navigation in the mockup (http://cl.ly/image/3q3R2X470O20) I want to
> know the expectations of each link. Can you answer my questions and/or
> confirm where the links need to go? 
> 
> Signup
> - You mention that this is specifically for MDN. Do you mean this is this
> the same as the MDN sign-up in the global nav or completely separate? Bug
> 932707 makes me think it is separate. If separate, how so? Do we need to ask
> the users any additional questions in the sign-up flow? Having 2 sign-ups
> might be confusing, so we may want to consider an opt-in option in the MDN
> sign-up form from global nav.
>  
> Mission
> - Will this content be displayed as a docs page or is the content short
> enough to display in this page?
> 
> Tools
> - Will this link to Tools item in Global Nav?
> 
> Documentation
> - Where will this link to? Do you want a page that talks about the types of
> documentation we have or is there a landing page that already exists for
> documentation?
> 
> Hacks Blog
> - Links to external Hacks Blog, that leaves MDN site completely. (please
> confirm)
> 
> Ask Questions
> - Would this go to a form?
> 
> Thanks!
> 
> 
> (In reply to Robert Nyman from comment #20)
> > (In reply to Holly Habstritt [:Habber] from comment #19)
> > > (In reply to Robert Nyman from comment #18)
> > > > Holly, I believe we need to point to other resources as well from that
> > > > landing page, such as the YouTube account for Mozilla Hacks:
> > > > http://www.youtube.com/user/mozhacks Think that can be worked into the
> > > > template work?
> > > 
> > > Robert, that shouldn't be a problem. I'll dive into this on Monday and share
> > > something for you next week.
> > 
> > Great, thank you!
> > I've also started to make the real page on MDN
> > (https://developer.mozilla.org/en-US/docs/Mozilla/Developer_Program) look
> > like the mockup, just to get a feel of what we're aiming for.
Thanks, Robert. One more question:

I was also wondering exactly how the Developer Program relates to the Contributing to MDN section. 

https://developer.mozilla.org/en-US/docs/Project:MDN/Contributing

If we are using a single sign-in method for dev program and all of MDN, we should be clear (especially to current users with a profile) how the Dev Program is different and an addition to what we offered before. Should we link to the Contributing section from the Dev Program page?
The Developer Program is intended to be your account with Mozilla as a developer. For current users, it won't mean much at this time - only extra added setting/option is the newsletter. Over time, though, we will definitely need to communicate to them that: "Your MDN account has now been turned into a Developer Program membership, and [1, 2, 3] all all the extra benefits you get, for free!".

Ali and I discussed the Contributing section the other day, and initially at least, I don't want to have it in the landing page. Mostly because we're trying to attract a number of new users, and directly asking people to contribute, than "getting stuff", could be a turn-off.
Flags: needinfo?(cmills)
Robert, Ali, David, and I met yesterday to discuss the Developer Program page. We used this wireframe for reference (copy and content subject to change): http://cl.ly/image/381t1a2T1n1V

Template notes:
The global landing page template is similar to the Zone landing template in that it has the same header area (color block with title, headline, and optional image) and inline content styles, but it does not have a left nav. The left nav is removed, allowing for full horizontal space of page to be used to display content. Blocks (3 for the dev program) are placed at top of page - slightly overlapping color block as left nav does on the zone pages. The style of the blocks is the same white used in the zone left nav.

Timeline for implementation will be discussed at the MDN Planning meeting today.
At today's MDN planning meeting we discussed the dev program page and how much of it will block the redesign launch.

We're committing to everything above the "Forums on Stack Overflow", "Mozilla Hacks", and "Where is Mozilla?" sections on Holly's wire-frame from https://bugzilla.mozilla.org/show_bug.cgi?id=918127#c25. David will craft some HTML & CSS that Sheppy will use to create the template of the page with all that static content.

#mdndev will continue to work on the platform features and coordinate with writing team to iterate on the dynamic sections of the page, but for now we're not comfortable committing to launch them with the redesign.
Development is complete for this:

https://github.com/mozilla/kuma/pull/1708

Sheppy: info in that pull request will help you.  Talk to me in IRC when you need help!
Flags: needinfo?(eshepherd)
Blocks: 941452
The page is now structured correctly, and the Hacks blog section is now dynamically pulling in content. I am now starting work on the Stack Overflow section, to make it dynamic as well.

The login/sign-up box at the top is not done yet, obviously, among other things, but it's coming along quickly now.
Flags: needinfo?(eshepherd)
We've implemented enough of bug 765642 to support the MDP homepage content, so I'm removing it from the blockers list.
No longer depends on: 765642
OK, here's my status on implementing the MDP homepage.

The page is basically as complete as I can make it at this time, with the hacks, events, and stack overflow sections being dynamically built (although having this done on a schedule is pending resolution of IT work).

I need the following to complete the page:

* Replacement image for the photo near the bottom of the page.

* The mockup shows the "Join the developer program" box with a Persona button in it, but we're not sending people directly to a Persona login, but to their MDN profile page (which will prompt them to create an account if they don't have one). For now, the title of the box is a link to the profile page, but if we want a button or something, tell me what to do.

* Related: Do we want an attractive button for the link to hacks? Do I just add a textual link under the explanation? Do we keep the headings in the boxes as links?

With those answered, I can finish this sucker up.
Flags: needinfo?(robert)
Flags: needinfo?(hhabstritt.bugzilla)
Keep the CTAs in the blocks as buttons or links under the Titles. The box titles should not be links. 

http://cl.ly/image/2T2E0H2s1I3X

Boxes and CTAs:
Join/sign-in block - contains copy + Persona button

Hacks blog block - contains short description and a link to Hacks Blog inline

Help/Discussion block (copy is FPO, we won't say "forums" here - Robert to write this) - contains short blurb saying what the Stack Overflow is for and links below. Looks good as it is, but just unlink the "Help Q&A" box title. 


Copy in wireframes is FPO. 

Copy tips so that Titles are not redundant with the links in the blocks: Keep block titles actionable, like "Join the Developer Program" and description copy would say that by signing in with Persona you get all the benefits of the Developer Program.
Flags: needinfo?(hhabstritt.bugzilla)
Depends on: 945971
Depends on: 945970
Robert, Ali, after the homepage content is complete and Holly's notes have been resolved, could you tell us if you think the homepage is ready for launch on Monday Dec. 9th?
Flags: needinfo?(aspivak)
The way it looks right now, with the small fixes/changes described on other bugs and e-mail, does imply that it is ready for launch.
Flags: needinfo?(robert)
This is now complete, other than the photo and any wordsmithing Rob might want to do, but he's already said that the text is fine and the photo does not need to be done prior to launch.

So yay! I think we're ready here, other than these:

Holly: We can't use the Persona button because you only get a Persona login form if you're not already logged in, since we're taking people to their profile on MDN, not Persona. I think it would confuse people to have a Persona button there. Are you really sure you want that?

And also, I don't understand what you're asking for in the last paragraph ("Copy tips so that Titles are not redundant...). Please clarify.

In addition, I do not know what "FPO" stands for.
Flags: needinfo?(hhabstritt.bugzilla)
(In reply to Eric Shepherd [:sheppy] from comment #34)

> In addition, I do not know what "FPO" stands for.

OK, someone explained this to me. Holly -- Rob has already said the text in place there is acceptable for launch.
(In reply to Eric Shepherd [:sheppy] from comment #34)
> This is now complete, other than the photo and any wordsmithing Rob might
> want to do, but he's already said that the text is fine and the photo does
> not need to be done prior to launch.
> 
> So yay! I think we're ready here

Great work, thank you! I'll go through the text over the weekend.

> Holly: We can't use the Persona button because you only get a Persona login
> form if you're not already logged in, since we're taking people to their
> profile on MDN, not Persona. I think it would confuse people to have a
> Persona button there. Are you really sure you want that?

Yeah, I think just sending users directly to the sign up/in page makes more sense, and there they have Persona and all the rest that is needed.
Sorry to ask a possibly bigger question at the last minute, but we want visitors to help us shape the developer program itself right?

So what if we change:

"We have a lot of plans and ideas how to iteratively expand the Developer Program, so stay tuned!"

to:

"We have a lot of plans and ideas how to iteratively expand the Developer Program, and we want you involved as we do so! So, follow the tags on Stack Overflow, subscribe to hacks, and Sign up."

(With repeated corresponding links for all actions.)
(In reply to Luke Crouch [:groovecoder] from comment #37)
> Sorry to ask a possibly bigger question at the last minute, but we want
> visitors to help us shape the developer program itself right?
> 
> So what if we change:
> 
> "We have a lot of plans and ideas how to iteratively expand the Developer
> Program, so stay tuned!"
> 
> to:
> 
> "We have a lot of plans and ideas how to iteratively expand the Developer
> Program, and we want you involved as we do so! So, follow the tags on Stack
> Overflow, subscribe to hacks, and Sign up."
> 
> (With repeated corresponding links for all actions.)

Works for me! Can you update the wiki?
(In reply to Robert Nyman from comment #38)
> (In reply to Luke Crouch [:groovecoder] from comment #37)

> > "We have a lot of plans and ideas how to iteratively expand the Developer
> > Program, and we want you involved as we do so! So, follow the tags on Stack
> > Overflow, subscribe to hacks, and Sign up."
> > 
> > (With repeated corresponding links for all actions.)
> 
> Works for me! Can you update the wiki?

Done.
Looks good to me! I had just wanted to make sure the copy for the title of the box wasn't exactly the same as the link and that the copy was somewhat actionable. The new copy does this with "join or log in" or "read it now". 

The way the sign-in flow works now, it is still a little unclear to me how signing up for the dev program is different than just signing up for MDN. I thought the landing page for sign-in would explain this and have a check-box to receive the newsletter, for instance. Right now it is just the normal sign-in landing page. For launch, will this be different?



(In reply to Eric Shepherd [:sheppy] from comment #34)
> This is now complete, other than the photo and any wordsmithing Rob might
> want to do, but he's already said that the text is fine and the photo does
> not need to be done prior to launch.
> 
> So yay! I think we're ready here, other than these:
> 
> Holly: We can't use the Persona button because you only get a Persona login
> form if you're not already logged in, since we're taking people to their
> profile on MDN, not Persona. I think it would confuse people to have a
> Persona button there. Are you really sure you want that?
> 
> And also, I don't understand what you're asking for in the last paragraph
> ("Copy tips so that Titles are not redundant...). Please clarify.
> 
> In addition, I do not know what "FPO" stands for.
Flags: needinfo?(hhabstritt.bugzilla)
> The way the sign-in flow works now, it is still a little unclear to me how
> signing up for the dev program is different than just signing up for MDN. I
> thought the landing page for sign-in would explain this and have a check-box
> to receive the newsletter, for instance. Right now it is just the normal
> sign-in landing page. For launch, will this be different?

The check-boxes should be there in time: they are in bug 945970 and bug 936123. RIght now an MDN account is a Developer Program membership, i.e. a MDN accounts become something bigger, and will iteratively grow with more offerings over time.

On that topic, I think the page at https://developer.mozilla.org/en-US/users/browserid_register needs a mention of the Developer Program and becoming a member. I guess that means switching MDN Member lingo to Developer Program Membership?

Sheppy, what do you think works best?
Flags: needinfo?(eshepherd)
(In reply to Robert Nyman from comment #41)

> The check-boxes should be there in time: they are in bug 945970 and bug
> 936123. RIght now an MDN account is a Developer Program membership, i.e. a
> MDN accounts become something bigger, and will iteratively grow with more
> offerings over time.

I'm a little confused due to what sounds like mixed messages. Do we need to add an explicit box about the newsletter to the MDP page or is that going somewhere else? If it goes somewhere else, file a bug for that.

> On that topic, I think the page at
> https://developer.mozilla.org/en-US/users/browserid_register needs a mention
> of the Developer Program and becoming a member. I guess that means switching
> MDN Member lingo to Developer Program Membership?

This needs a bug filed against the Mozilla Developer Network component as it will require a code change. That's not something I can configure. When you file that bug, be sure to ping mars about it because it will need to be flagged for immediate attention.
Flags: needinfo?(eshepherd)
(In reply to Eric Shepherd [:sheppy] from comment #42)
> (In reply to Robert Nyman from comment #41)
> 
> > The check-boxes should be there in time: they are in bug 945970 and bug
> > 936123. RIght now an MDN account is a Developer Program membership, i.e. a
> > MDN accounts become something bigger, and will iteratively grow with more
> > offerings over time.
> 
> I'm a little confused due to what sounds like mixed messages. Do we need to
> add an explicit box about the newsletter to the MDP page or is that going
> somewhere else? If it goes somewhere else, file a bug for that.

Nope, no box or anything will be added. In bug 945970 and bug 936123 it is meant to add that checkbox when you sign up/edit your account. The sufficient text is already there in the top box on the left: "Sign up for the Developer Program! You will get a membership, be able to subscribe to our newsletter and get access to features over time as we roll them out."

> > On that topic, I think the page at
> > https://developer.mozilla.org/en-US/users/browserid_register needs a mention
> > of the Developer Program and becoming a member. I guess that means switching
> > MDN Member lingo to Developer Program Membership?
> 
> This needs a bug filed against the Mozilla Developer Network component as it
> will require a code change. That's not something I can configure. When you
> file that bug, be sure to ping mars about it because it will need to be
> flagged for immediate attention.

Understood, will file that bug right away.
Hello, I notice a text overlap and image issue in the header area of this page. 

See - http://cl.ly/image/2J1u26333U1R

1. The left side of the Firefox icon is cut off. 
2. When I make my window a bit smaller, the image overlaps the text. 

Should I make separate bugs for these or are there already plans to fix?
The Developer Program should also be added to the global nav. That was my understanding. Has this changed or are we just waiting until tomorrow to do so?
(In reply to Holly Habstritt [:Habber] from comment #44)
> Hello, I notice a text overlap and image issue in the header area of this
> page. 
> 
> See - http://cl.ly/image/2J1u26333U1R
> 
> 1. The left side of the Firefox icon is cut off. 
> 2. When I make my window a bit smaller, the image overlaps the text. 
> 
> Should I make separate bugs for these or are there already plans to fix?

I hadn't noticed this. Not sure what's up. davidwalsh needs to take a look. We continue to have problems with the interaction between the blurb text and the header artwork.

I don't know what's up with adding the MDP to the global nav. Where is it supposed to go, other than replacing the MDN Beta block in the body of the home page?
Flags: needinfo?(hhabstritt.bugzilla)
Flags: needinfo?(dwalsh)
> I don't know what's up with adding the MDP to the global nav. Where is it
> supposed to go, other than replacing the MDN Beta block in the body of the
> home page?

It should be added next to the others, i.e. Zones, Web Platform, Tools, Demos. I assume it would be between Web Platform and Tools.
I've filed a bug for adding the MDP to global nav, since we don't seem to have one (I hadn't realized it was supposed to be there, for my part).

I've fixed the CSS for the MDP landing page so the logo problems mentioned in c#46 seem to be fixed.
Flags: needinfo?(hhabstritt.bugzilla)
Flags: needinfo?(dwalsh)
Flags: needinfo?(aspivak)
Is this all set?
Flags: needinfo?(eshepherd)
(In reply to John Karahalis [:openjck] from comment #49)
> Is this all set?

Other than the dependency of the newsletter flow, yes. I don't know where that stands.
Flags: needinfo?(eshepherd)
Yes, all seems good It's just the newsletter flow and to verify that that one is ok. From what I can see it's possible with signing up for the newsletter with new accounts, and add it to existing ones (although I'd like a higher placement for it there).

Otherwise, I'd like to change the wording in the create account page (bug 947597), but this bug isn't really dependent on that one. So, if the newsletter part is in place, I'm in favor for closing this bug.
w00t! Thanks everyone!
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Weee! Indeed, thanks everyone for your hard work on this!
Moving to General component.
Component: Developer Program → General
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: