Closed Bug 690534 Opened 14 years ago Closed 14 years ago

Create new Apps landing page and update website navigation

Categories

(developer.mozilla.org Graveyard :: Wiki pages, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jay, Assigned: craigcook)

References

()

Details

(Whiteboard: c=apps u=visitor p=3)

In preparation for a more robust section for Apps, we need to create a new landing page similar to the current Web, Add-ons, Mobile and Mozilla pages and update the navigation to include Apps. Let's use the same general template and sections that exist for other landing pages and I will add more details here regarding the content to include under each heading. The new landing page should live under /apps
Blocks: 676061
sorry, meant to include this for 1.3... let's at least get the template and a few links together by next week.
Target Milestone: 1.4 → 1.3
I hesitate to add to 1.3 unless Craig does so.
When is code freeze for 1.3? Tuesday? If we have all the copy and any other resources (images, videos, etc) I'm sure I can have the page built by then.
Yup, code-freeze is Tuesday.
Dan: If you can get us some links and copy by today or Monday, we will be able to get the Apps landing page live by 10/11 with MDN 1.3. Otherwise it'll have to wait until 10/25 for our MDN 1.4 release.
Thanks Jay, on timing - this page should not go live until the end of October / beginning of June in time with the Apps Announcement. Please DO NOT push anything live before then. I really want to get this in staging so I can share with the Apps team for them to begin populating with links and content once something is up - is that possible?
(In reply to Dan Horner from comment #6) > I really want to get this in staging so I can share with the Apps team for > them to begin populating with links and content once something is up - is > that possible? Ok, that sounds good. We'll try to get things up on stage9 so your team can work on additional content. Luke: I think we have another bug to control this landing page with waffle so we can keep it out of prod, right?
Yeah, we can control this page with waffle. Bumping this to 1.4 so we can push the page in a disabled state on 10/25 and then turn it on whenever.
Target Milestone: 1.3 → 1.4
Any chance we can push it in a disabled state a little earlier than that?
(In reply to Dan Horner from comment #9) > Any chance we can push it in a disabled state a little earlier than that? We can get an empty page staged right after the current release goes out next week so you'll have time to flesh it out. The code can then go to production on 10/25 in a hidden state and we can then switch it on so the page is live and viewable when you're ready to make it public.
(In reply to Craig Cook from comment #10) > (In reply to Dan Horner from comment #9) > > Any chance we can push it in a disabled state a little earlier than that? > > We can get an empty page staged right after the current release goes out > next week so you'll have time to flesh it out. The code can then go to > production on 10/25 in a hidden state and we can then switch it on so the > page is live and viewable when you're ready to make it public. Dan: Yeah, we can get things setup on our staging server next week so you can see what it looks like. Once we have the basic template on stage9, your team can go take a look and fill in the blanks with copy and links so we can have a decent page ready to push to production in a hidden state on 10/25. After that point, we can add any new content you want and it should be easy to switch the page "on" on production whenever the Apps team is ready to go live. Craig: For the new Apps page, it might be a good time to create a template that we can apply to the other landing pages in the future. We discussed using a different color palette for the landing pages so we don't overload the colors used on the nav... so it would be nice to switch everything over to a more consistent look and feel in the future. I'll let you figure out the best way to do that, but I'm happy to discuss and provide input as needed.
Craig: I just talked to Dan and they have moved the launch date for the Apps Developer Hub to October 31st, which means we'll have to have the new page live on that date. Here are some dates we need to shoot for: 1. Apps template page live on stage9 asap (10/7 or 10/10) 2. Dan to provide copy and links by next week (10/14) 3. Apps page updated with copy and links stage9 (10/18) - code freeze for 1.4 4. Apps team review of content and necessary tweaks (10/28) - will make exceptions past code freeze to make sure the Apps team has what they need. 5. Push Apps page live (10/31) - this is out of cycle, but we will need to launch with the Apps Developer Hub on this date.
Whiteboard: c=apps u=visitor p=3
Depends on: 692800
Depends on: 692802
Depends on: 692803
Depends on: 692805
Depends on: 692814
Depends on: 692840
Depends on: 692841
Depends on: 692842
Depends on: 692844
Depends on: 692845
Depends on: 692849
Depends on: 692850
Depends on: 692852
Depends on: 692853
Commit pushed to https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/13594e50aac9a8b92bcd9c4a208257d5e71bcf48 Bug 690534 - new Apps landing page (pending final copy), and minor updates to other landing pages.
Commit pushed to https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/ffac32241d0b5a8700e67c59adf3bdaecfeabc05 Revert "Bug 690534 - new Apps landing page (pending final copy), and minor updates to other landing pages." This reverts commit 13594e50aac9a8b92bcd9c4a208257d5e71bcf48.
I've drafted copy for the landing page: https://etherpad.mozilla.org/Apps-MDN-LandingPage
Commit pushed to https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/18c506130c89d09890f8752b5457de0678c6e496 Bug 690534 - updating Apps page copy Bug 695113 - updated signup form, moved into to sidebar
Revised blurb for "Getting Started": This walk-through can quickly give you an understanding of what it takes to turn an ordinary site into an open Web application. "Identity Integration" doc probably won't be ready in time. Tentatively, replace with: <h4>Using apps offline</h4> <p>How to design apps so that they can be cached and used without an Internet connection.</p>
Hope I'm not too late on copy review here: "MDN on Twitter Correspondence on Twitter from the Mozilla developer community." The Twitter module is missing a link to www.twitter.com/mozhacks also, "Correspondence" is a bit of a big word for what happens on Twitter. Could we say something simpler like, or am i missing something - "Follow @mozhacks on Twitter for the latest from the Mozilla Developer Network."
(In reply to havi hoffman [:havi] from comment #22) > Hope I'm not too late on copy review here: > > "MDN on Twitter > > Correspondence on Twitter from the Mozilla developer community." > > The Twitter module is missing a link to > > www.twitter.com/mozhacks > > also, "Correspondence" is a bit of a big word for what happens on Twitter. > Could we say something simpler like, or am i missing something - "Follow > @mozhacks on Twitter for the latest from the Mozilla Developer Network." Not too late. We can get this in before the final push next week. But, it might be worth changing the Twitter link in the header and the feed in the sidebar to use a Apps account (if there is one). Does the Apps team have a Twitter account they plan to use for news, updates and tips for Apps developers?
(In reply to Jay Patel [:jay] from comment #23) > Does the Apps team have a Twitter account they plan to use for news, updates and > tips for Apps developers? Not yet, but I have been pushing for this and hoping to incorporate in a subsequent phase. Will get back to you on this.
Definitive answer- we won't have this in place until earliest December 1st. Until then we should keep the mozhacks account in place.
Target Milestone: 1.4 → 1.6
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: 1.6 → 1.5
Blocks: 705793
Status: RESOLVED → VERIFIED
Version: MDN → unspecified
Component: Website → Landing pages
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.