Closed Bug 602918 Opened 14 years ago Closed 14 years ago

[Step 3] Construct the Describe Your Add-on page

Categories

(addons.mozilla.org Graveyard :: Developer Pages, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED
5.12.3

People

(Reporter: clouserw, Assigned: gkoberger)

References

Details

(Whiteboard: [devtools][Q32010][qa-])

Current URL: Somewhere under https://addons.mozilla.org/en-US/developers/addon/submit 
New URL: https://addons.mozilla.org/en-US/developers/addon/submit/3 (we're
making unique URLs now) 
Mockup: http://people.mozilla.com/~chowse/drop/amo/devtools/v2/Submit_03_Describe.png

The add-on edit page is pretty close to done (eg. https://preview.addons.mozilla.org/z/en-US/developers/addon/5326/edit) so hopefully we can reuse a decent chunk of that code here.  This is a pretty basic form, only oddity is that you need to say "on step 4" in the database on successful submission.  Some notes:

- The "add-on's detail page" part is generated automatically/on-the-fly from the name using a slug function. (verify it's a slug on the backend too)
- Add-ons only get 1 slug, not 1-per-language
- field limits are available in the db (eg. summary = 255)
- max of 2 categories is enforced on front and backend
- if they choose "My add-on doesn't fit..." it unchecks all other categories, and vice versa


CCing fligtar for copy
Assignee: nobody → gkoberger
Target Milestone: 5.12.2 → 5.12.3
We can remove the intro paragraph copy from this step.

Also adding to what Wil said, when "my add-on doesn't fit" is selected we select the "Other" category appropriate for that application. Each application's Other category has a different id, and there's a map of these in the current code. Also, when this is selected, the other categories should not only be unchecked but disabled.
https://github.com/jbalogh/zamboni/commit/eccefe9e919348986959243e28f4bee0f72798ec
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.