Full-text search
Press ⌘ K anywhere in the workspace to open the command palette — it searches your docs and doubles as a navigator (“Go to Home”, “Go to Docs”, …).- Every doc is indexed — search looks inside titles and content of all pages, including changelog entries. Type at least two characters.
- Results are ranked and grouped by repo — the best matches surface first.
- Snippets are highlighted — each result shows the matching passage with your terms highlighted, so you can judge relevance before clicking.
If results ever look empty or stale, run the palette’s Reindex docs for search action (requires edit rights) to rebuild the index for your repo.
Sidebar filtering
The search box in the docs sidebar works differently: it filters the file tree in place. Type a few characters and the tree collapses to matching files and their parent folders. This is the fastest option when you know roughly what a page is called or where it lives.Freshness
Search covers your published docs. Draft content on an unmerged change request branch is not part of the shared index — it becomes searchable when the CR merges.
A typical search flow
1
Open search
Press ⌘ K from any page in the workspace.
2
Type a phrase
Use the words you remember from the doc — a feature name, a process term, an error message.
3
Scan the snippets
The highlighted passages tell you which result actually answers your question.
4
Jump to the page
Select a result to open it in the docs viewer, with breadcrumbs showing where it lives.
Search-friendly docs
A few habits make your docs easier to find:- Descriptive titles — “Quote approval process” beats “Process notes”.
- Use your team’s vocabulary — write the terms people will actually type, including common synonyms.
- One topic per page — focused pages rank cleanly; sprawling pages match everything weakly.
- Tag docs to Salesforce components — tags don’t just power coverage; they keep docs organized around the things people search for.