Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Add build-time library search index

Aberta
  • Algo errado?
#114 0 comentários 1 reação 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
52/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
javascript
Domínio
build-system, frontend, search

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

enhancement

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, and slug.
  • Search matches supplied page/document title, section, and route.
  • Build emits normalized static search records from effective expanded kb-docs artifacts/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.

Linguagem predominante
JavaScript
Estrelas
0
Forks
0
Merge médio
20min
PRs com merge (30d)
8

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de AbsaOSS/knowledge-base

Todas as issues de AbsaOSS/knowledge-base

Issues semelhantes

Mais issues de JavaScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.