Skip to content

One card toolkit for the catalogue pages, with search and filters as pills or dropdowns #200

Description

@harenome

Priority

medium. The change is in the web layer: shared templates and static files, the four catalogue pages, and the routes that give them their cards' values. In the backend, one string of the Getting started checklist changes.

Components

  • app/nullius (backend)
  • app/web (routes)
  • templates and static files
  • docs and the site
  • catalogue (benchmarks, agents, capabilities)
  • the standard (ports, kits, relay, runs)
  • CI, workflows and skills

Today

Benchmarks, Agents, Capabilities and Kits each write their own card markup.

  • The cards do not have the same parts in the same order.
  • A stat shows its value first and its label under it. On the Agents cards at 1280 px, "benchmarks it runs" runs into the next stat.
  • Benchmarks and Kits have a Find box and rows of chips: category, runner and origin on Benchmarks, family on Kits. Agents and Capabilities have no search.
  • The chip filter is in catalogue.js only. A table cannot use it.
  • An agent without a logo shows initials. A capability shows no icon. No rule says when a card shows an icon.

Wanted

  • One card structure with named slots, filled from the same field list as the table toolkit. A field names the slot it fills. A field without a slot is not on the card.
  • Stats show the label first, then the value.
  • The icon rule: when one item of a page has an icon, the items without one show their initials. When no item has an icon, no card shows one.
  • Search on the four catalogue pages, in the controls row of the table toolkit.
  • Filters, chosen per category: a row of pills, a dropdown of its own (with a chevron, and an optional icon), or the global Filter button. A category can use more than one form.
  • Benchmarks: category pills, and dropdowns for origin and runner. Kits: family pills.

The toggle between a table and cards is out of scope. A later change can add it.

Acceptance

  • _cards.html renders cards from a field list. Each field's card names its slot. A field without card is not on the card, and table false keeps a card-only field off a table.
  • The slots come in a fixed order. A card has exactly one title and at most three stats. A page that breaks a slot limit fails to render.
  • A stat is a <dt> with the label, then a <dd> with the value.
  • The icon rule holds: initials only when another item of the page has a real icon, and no icon when none has.
  • Benchmarks, Agents, Capabilities and Kits use the card toolkit and have a search box.
  • Search and filters hide the cards that do not match. A shelf with no visible card hides, and its count follows the visible cards.
  • A column's filter puts its choices in the Filter menu (default), a dropdown, a row of pills, or more than one of these. All forms show the same state. All clears one column, and Clear filters clears every column.
  • A dropdown button ends in a chevron that turns while the menu is open. Under reduced motion, it changes without animation. A field's filter_icon leads its dropdown button and its pill row.
  • Benchmarks has category pills and dropdowns for Origin and Runs with, and no Filter button. Kits has family pills.
  • A screen reader hears the number of visible cards once, after changes stop.
  • The Getting started step for Benchmarks points at the new controls row.
  • AGENTS.md names app/templates/_cards.html.

Dependencies and related

Activity

  1. added
    enhancementNew feature or request
    P2Planned: limited in scope, has a way around it, or a missing feature
    on Nov 18, 2026
  2. added theissue type on Nov 18, 2026
  3. added a commit that references this issue on Nov 19, 2026
    11cff16
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

    P2Planned: limited in scope, has a way around it, or a missing featureenhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions