Every Dokly site, on every plan including Free, has a search box in the top-right that opens a ⌘K palette. Search is fuzzy, instant, and runs entirely in the reader's browser.
Screenshot needed
screenshot of the open search palette showing typed query, results list with title + snippet, keyboard shortcut hints at the bottom
How it works#
When a reader loads any page, Dokly fetches a single JSON index of every published page in the project. The index contains titles, descriptions, and section headings — enough to find any page by keyword.
Search runs against that index in the reader's browser. Results show as they type, with no server roundtrip. The whole experience is sub-50ms.
What's indexed#
| Field | Weight |
|---|---|
| Page title | High |
| Page description | High |
| H1 / H2 / H3 headings within the page | Medium |
| Body paragraphs (first 500 chars) | Low |
Not indexed: code blocks, images, and component metadata. Code blocks are ignored on purpose — searching for function shouldn't return every page with a code sample.
Opening search#
| Action | Shortcut |
|---|---|
| Open palette | ⌘K (Mac) or Ctrl+K (Windows) |
| Click search box | (also opens) |
| Move through results | ↑ / ↓ |
| Open result | Enter |
| Close palette | Esc |
Mobile readers see a search button in the top bar that opens the same palette.
Search appearance#
By default, the search box reads "Search docs..." with a ⌘K hint. The placeholder, hint, and accent color match your project's theme automatically.
You can customize the placeholder text in Project Settings → Search → Placeholder. Useful for branded copy ("Search the Acme docs" instead of "Search docs").
Customizing what gets indexed#
By default, every published page is indexed. To exclude specific pages:
- Page Settings → Display → "Hide from search" — page is still public via direct URL but excluded from the search index.
This is useful for legal pages, internal-only references, or duplicate landing pages that would clutter results.
Why client-side?#
A few reasons:
- Speed. No network roundtrip. Results appear as you type.
- Privacy. Search queries don't leave the reader's browser. Nothing to log.
- Simplicity. No search server to run, no Algolia bill, no index re-build job.
The trade-off is that search is limited by what fits in the index payload. For projects with hundreds of pages, the index gets big enough to slow down the first page load — see the limits below.
Limits#
| Plan | Indexed pages | Notes |
|---|---|---|
| Free | All published pages | Search is included on every plan |
| Team | All published pages | |
| Business | All published pages | |
| Enterprise | All published pages |
Search isn't capped by plan. The practical limit is the size of the index payload: on sites with hundreds of pages, the first search can take a moment longer to load.
Server-side search (coming soon)#
For projects that genuinely outgrow client-side search (hundreds of pages, frequent search, AI-style natural language queries), we're building a server-side option. It'll be opt-in on Team+ and use a hosted vector search backend.
If you have an immediate need, reach out — we'll work with you.