Closed
Bug 665882
Opened 13 years ago
Closed 12 years ago
Update link to AddonSDK docs from MDN
Categories
(developer.mozilla.org Graveyard :: Wiki pages, defect, P2)
developer.mozilla.org Graveyard
Wiki pages
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: zandr, Unassigned)
References
()
Details
(Whiteboard: u=user c=docs p=)
The link to the "Add-ons Builder SDK Docs" from https://developer.mozilla.org/en-US/addons should point to the new home at https://addons.mozilla.org/en-US/developers/docs/sdk/latest/
Comment 1•13 years ago
|
||
Thanks for the report, Zandr. Jay: What do you think? I think I prefer the current link as it provides more information and additionally links to the docs mentioned here.
OS: Mac OS X → All
Priority: -- → P2
Hardware: x86 → All
Whiteboard: u=user c=docs p=
Comment 2•13 years ago
|
||
zandr: I'm not sure if updating that link makes sense. Do you have a particular reason for bypassing the main Add-on Developer Hub? That page has clear navigation to the docs and additional resources already. I recommend you have the AMO team add more visible SDK links to https://addons.mozilla.org/en-US/developers/builder, as I was not able to find a link to https://addons.mozilla.org/en-US/developers/docs/sdk/latest/ anywhere. If you still would like to link directly to the SDK docs, we can add a new item to the list for "Add-on SDK Docs" and rename the first one "Add-on Developer Hub". Thoughts?
Assignee | ||
Updated•12 years ago
|
Component: Website → Landing pages
Comment 3•12 years ago
|
||
Will leave as-is unless anyone has an objection. We are going to revisit these landing pages as part of the redesign anyway.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Comment 4•12 years ago
|
||
I don't have an objection to closing this, but I *do* think this landing page is badly in need of an update, which is captured by bug 759204, which I'd love to see rolled into the redesign.
Updated•4 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•