595324 - Create developer profile first run and edit experience

Status: RESOLVED FIXED

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

Description

[Wil Clouser [:clouserw]]

Mockup: http://people.mozilla.com/~chowse/drop/amo/devtools/v2/Addon_06_Profile.png

This page has subtle differences between the "not been set up" and "content exists" states.  The first part of the mockup is the "not been set up" experience.  The second part is after content exists and is just text changes and showing the status bar at the top.

Backend:
- These fields already exist in the db, they just need to be sent to the templates.

Frontend:
- The bug being blocked by this one (contributions) wants to use the "create a developer profile" fields in its form.  Please make them flexible enough to be used in either place.

This bug does not include:
- The status bar at the top.  See dependent bug.

Fligtar:  we need copy for this page.

Comment 1

[Chris Howse [:chowse]]

Annotated mocks and workflows are now available:

http://people.mozilla.com/~chowse/drop/amo/devtools/v3/manage_addon/00_common.png
http://people.mozilla.com/~chowse/drop/amo/devtools/v3/manage_addon/09_profile.png

http://people.mozilla.com/~chowse/drop/amo/devtools/v3/manage_addon.pdf
http://people.mozilla.com/~chowse/drop/amo/devtools/v3/interaction.pdf

Comment 2

[Justin Scott [:fligtar]]

intro paragraph:
Your developer profile will tell users about you, why you made this add-on, and what's next for the add-on. This profile is required for add-ons requesting contributions, but can be useful for any developer interested in connecting with users.

Let's change the bold field descriptors to be questions:
Why did you make this add-on?
What's next for this add-on?

Comment 3

[Christopher Van Wiemeersch [:cvan]]

How is a developer profile defined as "public"? By checking that ``addon.status`` is public and ``addon.the_reason`` is nonempty? Or, do we want another field entirely to toggle the status of the developer profile?

Comment 4

[Wil Clouser [:clouserw]]

(In reply to comment #3)
> How is a developer profile defined as "public"? By checking that
> ``addon.status`` is public and ``addon.the_reason`` is nonempty? Or, do we want
> another field entirely to toggle the status of the developer profile?

If the_reason and the_future is filled out, it's public

Comment 5

[Christopher Van Wiemeersch [:cvan]]

In the mockup, there is a "Hide Profile" action button, which makes it seem like the developer profile public status is supposed to be toggle-able. Is this the intended behavior?

Comment 6

[Chris Howse [:chowse]]

(In reply to comment #5)
> In the mockup, there is a "Hide Profile" action button, which makes it seem
> like the developer profile public status is supposed to be toggle-able. Is this
> the intended behavior?

Oops, duplication of UI problem. Look at the section labeled "Profile Status" at the bottom of this mockup:

http://people.mozilla.com/~chowse/drop/amo/devtools/v3/manage_addon/09_profile.png

The banner is for removing the profile, not hiding it. (The Dev Profile's visibility was toggleable in a previous design, but the feature was removed.)

Comment 7

[Christopher Van Wiemeersch [:cvan]]

Committed: http://github.com/jbalogh/zamboni/commit/e3a4189