Closed
Bug 708785
Opened 13 years ago
Closed 11 years ago
Update Mobile videos on MDN
Categories
(Developer Documentation Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jswisher, Assigned: sheppy)
Details
On the Mobile landing page on MDN: https://developer.mozilla.org/en-US/mobile The video for Fennec shows a pre-alpha version presented at the July 2010 Summit. Something more recent would be a better advertisement. One the doc root page for Mobile: https://developer.mozilla.org/en/Mobile There is an old video that shows Fennec, not Firefox Mobile. It would be great to update this to show the new native UI. Once new videos are available, anyone with an MDN account can update the doc root page. Need to file a bug for updating the landing page.
Comment 1•13 years ago
|
||
Jaclyn do we have a better video for this?
We have the Firefox for Android promo video: http://www.youtube.com/watch?v=zCe_1DxBQDc&feature=channel_video_title I'm not sure if we should show Native UI yet, I think it could use a little bit more polishing before we start using it marketing collateral.
Updated•12 years ago
|
Component: Evangelism → Website
Product: Firefox for Android → Mozilla Developer Network
Updated•12 years ago
|
Component: Website → Landing pages
Comment 3•11 years ago
|
||
The landing page is no more and redirects (bug 754131). Also, bug 717741 discusses content updates. Will, do you want to look into adding the video mentioned in comment 2 or is this just a dupe of the content discussions happening in bug 717741?
Assignee: nobody → eshepherd
Component: Landing pages → General
Flags: needinfo?(wbamberg)
Product: Mozilla Developer Network → Developer Documentation
Comment 4•11 years ago
|
||
Florian: no, that video itself is 2 years old. I think we should close this bug. When we have some idea of what we need for mobile content on MDN, we can raise new bugs to track it.
Flags: needinfo?(wbamberg)
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•