Craft Docs Search Not Working? Why Modern Writing Apps Miss the Context Your Team Needs
Craft is a modern document and note-taking app used by product teams, engineers, and knowledge workers. It has a clean interface, real-time collaboration, and a block-based editor that feels lighter than Notion or Confluence. Teams choose it for internal docs, product specs, meeting notes, and team wikis.
The search works well for what it covers. The limitation is the same one every document tool faces: the reasoning behind every document lives somewhere else.
What Craft Search Covers
Craft search is full-text and fast. It indexes everything written directly into Craft. You get:
All documents and spaces: Every page and sub-page in your Craft workspace. Search runs across all spaces you have access to by default.
Text content and headings: Craft indexes heading structure and body text, so searching for a specific phrase finds the document and the section it is in.
Document metadata: Title, creation date, and last modified date are all searchable. If you remember approximately when something was written, Craft can filter by it.
Linked content titles: When you link to another Craft document, the link text is indexed. Clicking through still takes you to the external document, but the link itself is part of the search index.
For teams that write thorough documentation in Craft, search finds documents reliably. The limitation is everything that was never written into Craft.
What Craft Search Cannot Reach
Product and engineering teams using Craft typically run it alongside a broader stack. The operational context lives across all of it.
Slack threads where decisions were made: When a product team discusses a feature direction in Slack, the thread that shaped the spec is in Slack. The Craft document records the outcome. The constraints, tradeoffs, and context that produced it are not in Craft. Craft search cannot find them.
GitHub pull request discussions: Code review is where implementation decisions get made. The PR comment explaining why a design changed mid-implementation, why a specific approach was chosen, or why a deadline shifted is not in Craft. Even teams that link to GitHub from Craft docs cannot search PR content through Craft.
Jira and Linear tickets: Product requirements and bug context in project management tools are separate from Craft. A question about why a feature exists often requires both the Craft spec and the Jira ticket that defined the original scope. Craft finds the spec. It cannot find the ticket history.
Notion and Confluence pages: Teams migrating from or running alongside other tools end up with split knowledge. Craft search is scoped to Craft. It does not cross into Notion or Confluence content.
Google Drive and OneDrive documents: Async review documents, design files, and meeting recordings in file storage are outside Craft's index entirely.
Microsoft Teams and other chat platforms: Teams running Microsoft 365 alongside Craft have cross-tool context that Craft cannot reach.
Common Craft Search Failure Scenarios
The spec exists but the why does not: A developer reads the Craft product spec but needs to understand why the feature scope changed. The spec says what was decided. The Slack thread from the sprint planning where the constraint came up is not in Craft. The answer requires finding the right Slack message manually.
Cross-tool onboarding gap: A new team member reads through Craft documentation during onboarding. They can find the structured docs. They cannot find the Slack threads from three months ago where the team debated the approach, the GitHub issues that informed the architecture, or the Jira tickets that drove specific decisions. The full picture requires access to multiple separate tools and knowledge of where to look.
Repeated questions: A question answered in Slack that was never migrated into Craft will be asked again. The next person searches Craft and finds nothing. The knowledge exists. It is just in a tool Craft cannot search.
Decisions made in comments: Reviews happen across multiple surfaces. A product decision captured in a Notion comment or a GitHub discussion is not in Craft. Craft search finds only what was written into Craft.
Why Teams End Up with Split Knowledge
Every tool in a product team's stack does something specific well. Craft handles structured writing. Slack handles real-time communication. GitHub handles code and review. Jira handles project tracking. Each one is good at its job.
The problem is that answers to operational questions usually require context from two or more tools at once. A developer or PM asking about a past decision may need the Craft spec, the Slack thread that preceded it, the GitHub PR that implemented it, and the Jira ticket that requested it. Craft search finds only the first piece.
This is not a limitation of Craft specifically. It is structural. Every document tool searches what it contains. The context on adjacent tools is not visible from within it.
The Stack Teams Using Craft Usually Run
Product and engineering teams running Craft as their primary doc tool typically also use:
- Slack or Microsoft Teams for communication
- GitHub for code, review, and issues
- Jira or Linear for project tracking
- Notion or Confluence for additional documentation
- Google Drive or OneDrive for files
Craft covers one layer. The operational context is distributed across all five. Any search that needs to combine content from two or more layers cannot succeed through Craft alone.
What Changes with Cross-Tool Search
A search layer that connects to all tools in your stack treats the full knowledge graph as a single index. When a developer or PM searches for a decision, the search returns the Craft document, the Slack thread that preceded it, the GitHub PR that implemented it, and the Jira ticket that requested it, all at once.
AskOro connects to Slack, GitHub, Jira, Confluence, Notion, Google Drive, OneDrive, and Microsoft Teams. Search runs across all connected sources simultaneously. Results include citations pointing back to the specific Slack message, PR comment, or ticket where the context lives.
Craft stays as the structured writing layer. AskOro handles questions that require context from outside it.
| Question type | Best source |
|---|---|
| "What is our product spec for this feature?" | Craft document |
| "Why did the scope change mid-sprint?" | Slack thread + Jira combined |
| "What was the feedback on this design?" | GitHub or Craft comments |
| "What does the team know about this decision?" | Cross-tool search |
Getting Started
If your team runs Craft alongside Slack and GitHub, search for something in Craft that you know was decided in a Slack thread or GitHub PR that was never written up. If Craft finds nothing, the gap is confirmed.
**Try AskOro free for 14 days**. $49/month for the whole workspace. Connect it alongside Craft in under 10 minutes.
Related Guides
- BookStack search not working: why self-hosted wikis miss the context your team needs
- Outline search not working: why open source wikis miss the context your team actually needs
- Bit.ai search not working: why team wikis miss the context scattered across Slack and GitHub
- GitBook search not working: why dev team docs miss the GitHub context that matters
- Nuclino search not working: why wiki search still misses your team's context
- Microsoft Teams search not working: causes and fixes