Searchlight: design a clearer way to show search options
还没有人认领这个 Issue。
评估
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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
- 主要语言
- 没有语言数据
- 星标
- 4
- 派生
- 2
- 平均合并
- 2 小时 12 分钟
- 30 天内合并 PR
- 1
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
OpenConceptLab/ocl_issues 的其他 Issue
-
component/fhir type/bug
难度 2/5 1-3 小时 新手友好度 82/100
OpenConceptLab/ocl_issues#3026 ·
-
component/api decision/human-review signal/needs-access signal/quick-win signal/small-scope signal/well-specified stage/triaged type/bug
难度 2/5 1-3 小时 新手友好度 72/100
OpenConceptLab/ocl_issues#3012 · 2 条评论 ·
-
component/design-system decision/ai-ready signal/low-risk signal/quick-win signal/small-scope signal/well-specified stage/triaged type/docs
难度 2/5 半天 新手友好度 70/100
OpenConceptLab/ocl_issues#2983 · 1 条评论 ·
-
component/mapper decision/ai-ready signal/low-risk signal/quick-win signal/small-scope signal/well-specified stage/triaged type/bug
难度 2/5 1-3 小时 新手友好度 78/100
OpenConceptLab/ocl_issues#2966 · 2 条评论 ·
-
component/mapper component/web decision/human-review signal/low-risk signal/needs-human signal/quick-win signal/small-scope signal/well-specified stage/triaged type/bug
难度 2/5 1-3 小时 新手友好度 76/100
OpenConceptLab/ocl_issues#2920 · 1 条评论 ·
查看 OpenConceptLab/ocl_issues 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 82/100
-
could-have design seo
难度 1/5 1-3 小时 新手友好度 82/100
-
🕷️ bug
难度 2/5 1-3 小时 新手友好度 66/100
sysadminsmedia/homebox#1841 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
area:midi area:ui bug P3
难度 2/5 1-3 小时 新手友好度 68/100
transit-audio/transit#496 ·
维护者通常 1 天内回复