feat(search)!: Migrate to new Search UI powered by Meilisearch

[half0wl]

This replaces the existing tag-based search with site-wide full-text search, powered by Meilisearch Cloud.

• Index is built using a manually-triggered GH action introduced in Add "Build Search Index" job to GH Actions #235 (actions/build-search-index -> Run Workflow).
• Results are organized by the hierarchy root: each section in the sidebar maps to a section in results (e.g. "Deploy") with individual results as its children.
• Re-usability is a key design consideration. We plan to add this to nixpacks docs. The components introduced here contains as little logic as possible, with the core functionality exposed by a useDebouncedSearch hook.

Live demo

railway-docs-docs-pr-240.up.railway.app

Related PRs

• feat(search)!: Remove tag-based search #242
• feat(analytics): Track search events #241

Screens

Future Improvements

• Migrate from Meilisearch Cloud -> Meilisearch on Railway
  • Needs persistent vol. While the index gets nuked on each build, data going away on re-deploys or restarts is a recipe for "nothing shows up in search" class of issues until the build gets triggered again
• Auto-trigger index build on each deploy
  • Not worth doing a custom build for chaining actions right now
• Add back hotkey navigation
  • Removed this in favour of moving faster. Definitely a UX regression that should be taken care of.

Rollout

• Add new env vars to production:
  • NEXT_PUBLIC_MEILISEARCH_HOST
  • NEXT_PUBLIC_MEILISEARCH_READ_API_KEY
  • NEXT_PUBLIC_MEILISEARCH_INDEX_NAME
• Ideal landing order:
  1. feat(search)!: Migrate to new Search UI powered by Meilisearch #240
  2. feat(search)!: Remove tag-based search #242
  3. feat(analytics): Track search events #241

[railway-app]

This PR is being deployed to Railway 🚅

📚 railway docs: ◻️ REMOVED

[coffee-cup]

Overall looks good! I think there should be a follow up PR that fixes the keyboard navigation since that was pretty confusing when I first tried it out.

There also isn't a clear separation between the result items, but that is maybe a Jitachi question?

[ndneighbor]

Nothing else to add except from JR's comments. I have two nits, but mostly they are stylistic concerns that can be waived away if you don't feel that they are important.