Closed Bug 553450 Opened 11 years ago Closed 11 years ago
Discovery Pane placeholder
Please create a temporary, static, non-localized page that will be used as the placeholder until the real discovery pane is implemented. This page should live at services.addons.mozilla.org/discovery/ and look like the mockup attached. As the new add-ons manager should land on trunk at the end of next week, I'd like to get this page in with Tuesday's push if possible. QA: This does not require any testing. Thanks!
Looking for feedback on this patch. This makes the assumptions: 1) This should be using a URL consistent with the rest of SAMO and the API. In this case: /en-US/firefox/api/discovery 2) This is an HTML snippet, not an entire page with doctype, <html>, etc. 3) The page should not be loading external CSS
Assignee: nobody → clouserw
Attachment #433945 - Flags: feedback?(fligtar)
and here's a screenshot
(In reply to comment #1) > 1) This should be using a URL consistent with the rest of SAMO and the API. In > this case: /en-US/firefox/api/discovery > I'd prefer not to have /api -- this page isn't really an API, and should have its own section. We may eventually need to add subpages. > 2) This is an HTML snippet, not an entire page with doctype, <html>, etc. > That's fine for now, but the real one should probably have all that. > 3) The page should not be loading external CSS That's fine for now, but the real one probably will.
Comment on attachment 433945 [details] [diff] [review] patch Looks good to me! f+
Attachment #433945 - Flags: feedback?(fligtar) → feedback+
Once preview updates this will be at https://preview.addons.mozilla.org/en-US/firefox/discovery Commit is http://github.com/jbalogh/zamboni/commit/20d9ba9b5fbc018aea85db018fa8108d2cd58e43
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Verified FIXED on https://addons.mozilla.org/en-US/firefox/discovery. I verified this bug just to spite fligtar!
Status: RESOLVED → VERIFIED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.