It isn't clear how the results are currently sorted, nor is there a way to change how they are sorted.
State how the results are being sorted, along with an ability to switch the sort criteria. Options could include:
- Most installed
- Most starred
- Date of most recent release
Decide on which sort criteria to use on each of the "recommended" and "all" search/browser pages.
Adding exposed sort dropdown.
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | Screen Shot 2021-11-18 at 10.25.06 AM.png | 94.71 KB | bnjmnm |
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
hmendes commentedComment #3
chrisfromredfinYes, I think this will be required for MVP. For MVP sort, we (Leslie and I) believe the two options should be (1) number of downloads (or active installs) and (2) name (alphabetical by project name).
Open to discussion if something else adds value.
Comment #4
mandclu commentedI would say recency of release should be another sort, but maybe that doesn't have to be MVP.
I would encourage us to treat filtering to projects with a stable release as a priority also.
Finally, based on my (admittedly limited) use of the current state, it doesn't appear to filter results to projects compatible with the current site (version of Drupal etc). I realize that's likely off topic for a ticket about sort options, but I definitely think that should be MVP. Happy to create a new ticket for that if there isn't one already.
Comment #5
chrisfromredfinLeslie and I are about to file a BUNCH of issues, and one is how to algorithmically determine "recommended," so that will be a good place for that other discussion. We did discuss "recency of release" but decided that might make more sense only on the "All" set of filters, but are open to discussion on it.
Comment #6
mandclu commented"Last release" is a sort currently available for the search on drupal.org, so hopefully it shouldn't be a big lift to include that. I know a lot of devs who consider this an important way to evaluate modules.
Comment #7
chrisfromredfinComment #8
mandclu commentedAdded #3240321: Only show projects compatible with the current site as a child issue to capture a requirement to only show projects compatible with the site's current major version of Drupal, which I think should really be included for MVP.
Comment #9
chrisfromredfinAfter thinking about this more today, I think we need an exposed sort with the following options:
* relevance (since you'll be doing keyword search; and this would be the default if you keyword-search)
* popularity ("most installed" in Drupal.org parlance)
* alphabetical (in case someone is searching for something specific? or maybe not needed at all? currently "title" on d.o)
We could, to this, possibly add:
* recent activity (kind of like "last release" - or could just be last release)
Comment #11
bnjmnmThe MR makes it possible to sort by the following properties:
These are the properties that can easily be sorted by after the changes implemented in #3249958: Mirror API in database to make sorting and other queries possible. That issue removed the need to depend on D.O. api functionality, and it's all done with local database queries.
I think it could be useful to commit this one -- so sorting is actually possible -- and open followups for additional sort properties. Additional sort properties would likely require expanding the hook_install process to compute additional properties. That isn't difficult, but I think there's benefit of getting this level of sorting committed asap, and we can expand as needed.
Comment #14
tim.plunkettMerged! Thanks Ben
Comment #15
tim.plunkettUhh idk why it says that I committed stuff. I just tried to use the merge button...
Comment #17
tim.plunkettTried again and it seems like it worked