You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Developer name at the top of the "more extensions by" box on the add-on page should link to the developer account page which lists all their add-ons - the same as it does at the top of the page. This will ensure that developers with more than 6 add-ons will also get an option to showcase their entire set of work.
Open UX / product questions:
Handling multiple developers
Some add-ons might have more than one developer ; In that case, the frontend displays the full list at the top of the page, each with their own link, but below, the box contains add-ons from any of the developers, in one unified list, with the header text "More extensions by these developers".
The box contains add-ons from any developer in the list, so we can't really link to a single page. Should we change the header text for the card when there are multiple developers ? I don't remember why we chose not to repeat the full list of developers in there, it might look a bit awful if there are too many of them, since the card doesn't have as much horizontal space as the main title/summary area. Or repeating all the names might just be too verbose.
Handling different add-on types
The list we're showing in that card is currently filtered by add-on type, matching the add-on type we're currently looking at: if you're looking at an extension, it will say "More extensions by..." and only be extensions, but it can be dictionaries, language packs or themes at the moment.
We don't have a full page that to link to that does that kind of filtering, the best we have is the search results page (which doesn't expose the ability to filter by author at the moment, although it supports the corresponding query parameter in the URL) or the user profile page (which doesn't let you choose to filter by add-on type, showing both extensions and themes on the page, in different sections)
Should we drop the specificity in the header text always say "More add-ons by..." and link to the developer page without any filtering on the add-on type ? Come up with new special pages for each type ? Something else ?
Acceptance Criteria
The content you are editing has changed. Please copy your edits and refresh the page.
I propose we keep the text the same More extensions by these developers and not link to any accounts. In the case of a single developer, we link to their developer page - listing all their add-ons.
Handling different add-on types
I agree with this proposal you made and vote we proceed this way: Should we drop the specificity in the header text always say "More add-ons by..." and link to the developer page without any filtering on the add-on type ?
Description
From @abyrne-moz in #15287:
Developer name at the top of the "more extensions by" box on the add-on page should link to the developer account page which lists all their add-ons - the same as it does at the top of the page. This will ensure that developers with more than 6 add-ons will also get an option to showcase their entire set of work.
Open UX / product questions:
Handling multiple developers
Some add-ons might have more than one developer ; In that case, the frontend displays the full list at the top of the page, each with their own link, but below, the box contains add-ons from any of the developers, in one unified list, with the header text "More extensions by these developers".
The box contains add-ons from any developer in the list, so we can't really link to a single page. Should we change the header text for the card when there are multiple developers ? I don't remember why we chose not to repeat the full list of developers in there, it might look a bit awful if there are too many of them, since the card doesn't have as much horizontal space as the main title/summary area. Or repeating all the names might just be too verbose.
Handling different add-on types
The list we're showing in that card is currently filtered by add-on type, matching the add-on type we're currently looking at: if you're looking at an extension, it will say "More extensions by..." and only be extensions, but it can be dictionaries, language packs or themes at the moment.
We don't have a full page that to link to that does that kind of filtering, the best we have is the search results page (which doesn't expose the ability to filter by author at the moment, although it supports the corresponding query parameter in the URL) or the user profile page (which doesn't let you choose to filter by add-on type, showing both extensions and themes on the page, in different sections)
Should we drop the specificity in the header text always say "More add-ons by..." and link to the developer page without any filtering on the add-on type ? Come up with new special pages for each type ? Something else ?
Acceptance Criteria
Milestones/checkpoints
Checks
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: