Skip to content

Make the search box search the whole family - #48

Merged
oblomov-dev merged 1 commit into
mainfrom
claude/beautiful-gauss-3dlvr3
Nov 1, 2026
Merged

oblomov-dev merged 1 commit into
mainfrom
claude/beautiful-gauss-3dlvr3

Conversation

@oblomov-dev

Copy link
Copy Markdown
Member

What

The quiet pill under the greeting now searches the whole family from the docs' index (abap2UI5/docs: "Put the whole family into the search index"): docs, samples, every repository of both orgs, the tools, the essays, the page for decision makers, the addons, the client API and the framework's classes.

  • Best answer on top when the query names something: #1234, a class, a method, a repository, a tool
  • Actions per hit on the right: source of a sample, README / Issues / code-search of a repository; ←/→ walk them, Enter opens, Ctrl/⌘+Enter in a new tab
  • Scopes: repo:, api:, sample:, doc:, tool:, insight:, why:, addon:
  • The way out, pinned at the bottom of the list: the query on GitHub — Code (both orgs) · Issues · Discussions. Links only: nothing is fetched from GitHub, connect-src stays 'self'
  • Empty field offers the places to go
  • /search/?q=…: the search as a page with all results and a shareable address; opensearch.xml + <link rel="search"> let a browser add it as a search engine

Nothing is stored. The markup moved into src/components/Search.astro (home + /search/). public/search-engine.js is a fresh copy of the docs' matcher.

Works with today's index too (fewer areas, no best answers for repos); merge after the docs PR for the full effect.

Tests

The box test follows the new markup and the engine's new exports; new: /search/ has the box in page mode and the one script, the OpenSearch link on both pages, the template points at /search/?q={searchTerms}. npm run check: 8 pass. Checked in Chromium against a locally built full index: desktop, 390 px, keyboard (actions), /search/?q= round trip.


Generated by Claude Code

The box now reads what the docs' index carries since abap2UI5/docs
scripts/lib/search-family.mjs: the repositories of both organisations, the
tools, the essays, the page for decision makers, the addons, the client API
and the framework's classes, beside the docs and the samples.

- Best answer: a query that names something - #1234, a class, a method, a
  repository, a tool - gets it on top
- Actions per hit: the source of a sample, README and issues of a repository,
  a repository's code searched for the query; Right/Left walk them
- Scopes: repo:, api:, sample:, doc:, tool:, insight:, why:, addon:
- The way out, always in view: the query on GitHub - code of every
  repository, issues, discussions. Links only, nothing fetched from GitHub
- An empty field offers the places to go
- /search/?q=… : the search as a page, all results, an address to link;
  opensearch.xml lets a browser add it as a search engine

The matcher is a new copy of the docs' search-engine.js. Nothing is stored.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014YZFmFLTfBmZJXKPuRQWci
@oblomov-dev
oblomov-dev merged commit 8e2ac2e into main Nov 1, 2026
2 checks passed
@oblomov-dev
oblomov-dev deleted the claude/beautiful-gauss-3dlvr3 branch November 1, 2026 15:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants