Skip to content

Open the trail catalog on what is near and well rated, not the longest trails #1005

Description

@glennmichael123

Part of #1002.

Problem

/trails defaults to longest-first. The first screen of the catalog is therefore:

  1. North Country National Scenic Trail (MI) — 1,161.5 mi, HARD
  2. North Country National Scenic Trail (OH) — 1,069.7 mi, HARD
  3. Grand Enchantment Trail — 1,036.5 mi, HARD
  4. Iditarod National Historic Trail — 996.2 mi, HARD

Nobody browsing trails wants a 1,161-mile thru-hike. AllTrails opens on local favourites near you, which is the same catalog making the opposite first impression — and it is the specific comparison that reads as "they look higher quality than us".

The home page already has a Local favorites section, so the catalog page currently disagrees with our own front door.

Acceptance

  • Default ordering is near-me first, then well-rated, rather than longest.
  • Falls back sensibly with no location: a rated/popular ordering, not distance.
  • An explicit sort choice still wins, and the chip reflects what the list is actually sorted by.
  • Trails with no rating do not sink below the fold permanently — with 0% rated today (Close the catalog data gap with AllTrails and Strava #1002) a pure rating sort is a coin toss, so the tiebreak needs thought.
  • The empty and "nothing near you" states say what to do next.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions