Search

Search finds pages by their title and content across every space you can open in the current organisation. It runs from the command palette, which you open with Ctrl K (⌘K on a Mac).

Open search#

• Press Ctrl K, or ⌘K on a Mac, from anywhere in the app.
• Or choose Search... at the top of the sidebar.

The command palette opens. Before you type, it lists your Recent pages. Start typing and it shows Results as you go.

Use the arrow keys to move through the results and Enter to open one. Press Escape, or choose Cancel, to close the palette.

Each result shows the page's title, its group and its space. When the match is in the page's content, a short extract appears with the matching words highlighted.

What's searched#

Search covers pages in the organisation you're working in, in every space you can open. That includes My space and any page in the organisation that has been shared with you. It never shows a page you couldn't open, and pages in the recycle bin aren't included.

Inside a page, search looks at:

• the title;
• paragraphs, headings, lists, quotes, tables and alert boxes;
• code blocks and inline code;
• the labels in diagrams;
• image descriptions (alt text).

It doesn't search the names in @mentions or the titles shown by links to other pages.

Pages with a matching title are listed first, then pages that match in their content, best match first.

How long new content takes to appear#

• Titles are searchable straight away.
• Content becomes searchable about 30 to 40 minutes after the page was last edited. Folioso waits until a page has been left alone for a while before updating the search index, so a page you're actively writing isn't re-indexed on every keystroke.

Until then, search still finds the page by its title, and it may still find words you've just removed. Extracts are only shown for pages that haven't been edited since they were indexed, so text you've removed is never shown in a result.

Tips for better results#

• Every word must match. Searching deploy rollback finds pages containing both words, in any order.
• The last word can be a prefix. Typing migr finds "migration" and "migrate", so you can search mid-word. A single final letter is matched as a whole word.
• Prose is matched loosely. Ordinary words match their other forms, so deploying also finds "deployed" and "deploys".
• Code is matched exactly. Identifiers in code blocks and inline code, such as useState or getUserById, match as written, ignoring capitals.
• Keep it short. Only the first eight words of a search are used.

Known gaps#

A few kinds of search don't find what you'd expect:

• Dotted names and file paths. A search for config.php or app/Models/Page.php usually misses, because search splits it into separate words while the page stores it as one. Search for other words on the page, or its title, instead.
• Mixing prose and code in one search. A search that combines an ordinary word with an exact code identifier, such as deploying getUserById, can miss a page that contains both. Search for each one separately.
• Very recent edits. Content edited in the last 30 to 40 minutes may not be found yet. See How long new content takes to appear.

The command palette and the /search address#

There's no separate search results page. If you open /search?q=your+words in your browser's address bar, for example from a bookmark or a browser search shortcut, Folioso takes you to your current space and opens the command palette with your search filled in. Without q, it just takes you to your current space.

To search from a script or another tool, use the REST API. See Pages.