Searchlight: design a clearer way to show search options

Aperta
  • Qualcosa non va?
#2,997 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
12/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
design, frontend

Direzione di ricerca

This is a design task, not a code change: the search options are described in the table and the inconsistencies list in the body. Start by confirming each option combination in the running app, then compare the three directions named in the acceptance criteria against the OCL design system. Done means the team has reviewed the mockups, the decision is recorded on this issue, and build tickets with any design system gaps are filed.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

component/web decision/human-review signal/low-risk signal/needs-human signal/small-scope signal/well-specified stage/triaged type/feature

Searchlight offers 1 to 4 options depending on where you are, and they're hard to tell apart. Each row packs what you're searching and where into one sentence, so you have to read each one closely. Research and mock up a clearer, consistent design for the team to decide on before any build. OpenConceptLab/ocl_issues#2996 is the stopgap wording fix.

Where you are Options today
Home, global search All of OCL
Organization or user page Owner's repositories · Owner's concepts · All of OCL
Mapping Projects tab Owner's mapping projects · Owner's concepts · All of OCL
Source or collection This repository · Owner's concepts · All of OCL · Match (when available)
URL registry, user settings This URL registry · All of OCL
After choosing a / filter One filtered search

Inconsistencies to address:

  • The top row searches repositories on an owner page, but concepts on a repository page.
  • The right-hand hints mostly repeat the row. The URL registry row's hint says "Search this repository", and user settings offers a URL registry search.
  • The Match row is English-only in es and zh.

Acceptance criteria

  • Every option combination is confirmed in the app.
  • Research how similar products show search scope (e.g. GitHub).
  • Mockups on the OCL design system compare at least three directions: a scope icon on each row, the owner or repository as a chip with an icon, and a scope selector instead of extra rows. Each covers keyboard use, long names and all four languages.
  • The team reviews them, and the decision is recorded here.
  • Build tickets are filed, and any design system gaps are flagged.

Related: OpenConceptLab/ocl_issues#2987, OpenConceptLab/ocl_issues#2996, OpenConceptLab/ocl_issues#1754, OpenConceptLab/ocl_issues#2689, OpenConceptLab/ocl_issues#2998

Lingua principale
Nessun dato sulla lingua
Stelle
4
Fork
2
Merge medio
2h 12m
PR unite (30g)
1

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OpenConceptLab/ocl_issues

Tutte le issue di OpenConceptLab/ocl_issues

Issue simili

Altre issue su Design

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.