TechnicalCollectible prompt

Site search with instant results and keyboard support

Add fast, accessible search across your content, with an approach sized to your site.

CodexClaude CodeCursor

Curated by Nvoka

Nvoka wordmark logo
Nvoka wordmark logoTechnical

Site search with instant results and keyboard support

Add site search to my {{tech_stack}} project. Read the existing code first, list the public pages and content types that search should cover, and show me a short plan before changing files. Pick the approach by size and tell me why: a prebuilt static index for a few hundred pages or fewer, the database's own full-text search for content stored there, or a hosted search service only if we need typo tolerance at scale. Experience: - A search box in the header that the slash key opens, and a full-screen search view on phones - Results as you type after two characters, with a short debounce - Each result shows the title, a snippet with the matched words highlighted, and its section or type - A results page with the query in the URL, so searches can be shared and bookmarked - A helpful no-results state with suggestions and popular links Rules: - Only published content, and never anything the visitor isn't allowed to see - Keyboard and screen reader support using the combobox pattern: arrow keys, Enter, Escape and an announced result count, meeting WCAG 2.2 AA - Log searches that return nothing, without personal data, so I know what content to add When you're done, list the files changed, how the index stays up to date, and anything you assumed.
Technicalnvoka.com/library/nvoka-site-search-with-instant-resultsScan to open
Technical

Site search with instant results and keyboard support

Add fast, accessible search across your content, with an approach sized to your site.

Nvoka logo

Curated by Nvoka

CodexClaude CodeCursorWindsurf
Add to my library

Make it yours

Fill in the blanks and change any word. Only your copy changes, never the card.

Fill in the blanks

0 of 1 filled

Your prompt

Add site search to my {{tech_stack}} project. Read the existing code first, list the public pages and content types that search should cover, and show me a short plan before changing files. Pick the approach by size and tell me why: a prebuilt static index for a few hundred pages or fewer, the database's own full-text search for content stored there, or a hosted search service only if we need typo tolerance at scale. Experience: - A search box in the header that the slash key opens, and a full-screen search view on phones - Results as you type after two characters, with a short debounce - Each result shows the title, a snippet with the matched words highlighted, and its section or type - A results page with the query in the URL, so searches can be shared and bookmarked - A helpful no-results state with suggestions and popular links Rules: - Only published content, and never anything the visitor isn't allowed to see - Keyboard and screen reader support using the combobox pattern: arrow keys, Enter, Escape and an announced result count, meeting WCAG 2.2 AA - Log searches that return nothing, without personal data, so I know what content to add When you're done, list the files changed, how the index stays up to date, and anything you assumed.
See all