Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Task]: "More extensions by" box on the add-on page should link to the developer account page #15356

Open
1 task
diox opened this issue Feb 12, 2025 · 1 comment
Labels
needs:info repository:addons-frontend Issue relating to addons-frontend

Comments

@diox
Copy link
Member

diox commented Feb 12, 2025

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

Preview Give feedback

Checks

  • If I have identified that the work is specific to a repository, I have removed "repository:addons-server" or "repository:addons-frontend"

┆Issue is synchronized with this Jira Task

@abyrne-moz
Copy link

Handling multiple developers

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 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs:info repository:addons-frontend Issue relating to addons-frontend
Projects
None yet
Development

No branches or pull requests

2 participants