Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E extensions.typo3.org
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 80
    • Issues 80
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • servicesservices
  • t3o sites
  • extensions.typo3.org
  • extensions.typo3.org
  • Issues
  • #368
Closed
Open
Issue created Oct 30, 2018 by Mathias Brodala@mbrodalaContributor

Smarter default sorting

What do you suggest?

It would be really useful if the default sorting of extensions upon search was a bit smarter. This means that properties really relevant to humans should have a higher weight:

  • number of downloads
  • date of last update
  • number of supported TYPO3 LTS versions
  • (possibly more)

This is slightly related to #168 (closed) but aims at the default sorting.

Why?

Users should get a useful suggestion for their searches. It is safe to assume that anyone who actually searches by terms instead of directly opening the detail page of an extension doesn't really know the most common and proven solutions.

Add an use case

A search for registration currently yields the following result:

  1. registration
  2. agency
  3. agency_tt_address
  4. sf_event_mgt
  5. slub_events
  6. sf_register
  7. autobeuser
  8. sr_feuser_register
  9. dated_news
  10. femanager
  11. ...

You can clearly see the mixed "quality" of the search results. The top hit is registration due to the exact name match but it's probably the extension most unlikely to solve the issue at hand since it is alpha, outdated and officially does not support any TYPO3 version. Instead femanager and sr_feuser_register should be the top hits, the number of downloads support this assumption.

Edited Oct 30, 2018 by Mathias Brodala
Assignee
Assign to
Time tracking