A client-side search over the tutorial catalog. It strips question prefixes ('how do i', 'where do i find'), drops stopwords, then scores full authored intent phrases highest, followed by title, keyword and category hits — with one-edit typo tolerance on longer words so 'estimtes' still matches. Top six results; below the score floor it says 'No match — browse categories' instead of showing nothing.
Also called: how do i search · help search · tutorial search · search the academy
- 1Query is normalized and tokenized (INTENT_PREFIXES + STOPWORDS in search.ts)
- 2Each tutorial carries authored `intents` — full natural phrases a builder would actually type
- 3Damerau-Levenshtein distance ≤ 1 tolerates a typo on any query token of 5+ characters
- 4Searches that return nothing are logged (debounced, on the final query, never per keystroke) into a capped ring buffer on the user's prefs row, so the gaps in the content are visible
Nobody types the word the software uses. A builder wanting to bring in a spreadsheet of old customers types 'how do i import my leads' — not the name of the screen, and often not spelled the way it appears anywhere. Search matches the question the way it was asked, typos included, and answers only as deep as the tutorials that exist rather than inventing something. Every question that finds nothing is kept, so the next batch of tutorials gets written from what builders actually asked for instead of what somebody guessed they would need.
- Help search that only matches exact feature names is useless to someone who doesn't know the names
- No feedback loop showing which questions the help content can't answer
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →