Add build-time library search index
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 52/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- javascript
- 领域
- build-system, frontend, search
调研方向
Start by tracing the existing build-time registry and page-resolution flow, then inspect the Library landing page and current build and browser test entry points. Implement normalized static records from resolved kb-docs artifacts/manifests, local grouped filtering, and route-aware results; done means the listed acceptance criteria and tests pass without runtime filesystem or network access.
由索引模型根据 Issue 内容生成。
描述
Feature Description
Add live client-side search to Library landing page. Search app metadata plus page/document titles and routes from each app. Generate static result data during build from resolved kb-docs artifacts/manifests.
Problem / Opportunity
Growing catalog needs direct discovery across apps and their supplied pages/documents. Search must stay consistent with build-resolved artifact metadata, without runtime filesystem access, crawling, or network calls.
Acceptance Criteria
- Landing page exposes accessible search input and live client-side results.
- Search matches app
name,description,tags, andslug. - Search matches supplied page/document title, section, and route.
- Build emits normalized static search records from effective expanded
kb-docsartifacts/manifests. - Results distinguish app and page/document matches.
- Result links navigate to correct routes in standalone and embedded modes.
- No full document-body indexing.
- No network request, filesystem crawl, or external indexing at runtime.
- Empty query, no-match, keyboard navigation, and accessible labels work.
- Build and browser tests cover index generation and live filtering.
Proposed Solution
Extend existing build-time registry/page resolution to emit normalized searchable app and page records. Landing page loads static records, filters locally as user types, and renders grouped app/page results. No AI model, provider, or AI query interface included in this scope.
Additional Context
Catalog metadata originates from artifact-owned kb-docs manifests; page routing resolves during build. Search index should use same sources, keeping catalog, routes, and results aligned.
- 主要语言
- JavaScript
- 星标
- 0
- 派生
- 0
- 平均合并
- 20 分钟
- 30 天内合并 PR
- 8
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
AbsaOSS/knowledge-base 的其他 Issue
-
enhancement
难度 5/5 一周以上 新手友好度 30/100
AbsaOSS/knowledge-base#118 ·
维护者通常 1 天内回复
-
feat: expose knowledge-base documentation through an MCP server可能已有人在做 @oto-macenauer-absa 于 16 天前认领。 未关闭enhancement
难度 5/5 一周以上 新手友好度 35/100
AbsaOSS/knowledge-base#117 · 已指派 1 人 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 35/100
AbsaOSS/knowledge-base#113 ·
维护者通常 1 天内回复
-
Dynamic responsive masthead menu from documentation manifests可能已有人在做 @oto-macenauer-absa 于 20 天前认领。 未关闭enhancement
难度 4/5 3-5 天 新手友好度 48/100
AbsaOSS/knowledge-base#111 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 AbsaOSS/knowledge-base 的全部 Issue
相似的 Issue
-
task
难度 1/5 1 小时以内 新手友好度 83/100
TAMULib/fw-registry#550 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 79/100
-
NWCWalletService.subscribe: response is never published if the handler finishes after unsubscribe (regression in 8.1.0)可能已有人在做 @ajaysehwal 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 83/100
-
难度 1/5 1 小时以内 新手友好度 88/100
bigskysoftware/htmx#4151 ·
维护者通常 4 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100