mirror of
https://github.com/supermemoryai/supermemory.git
synced 2026-08-25 00:14:08 +00:00
434c86e2c3
Keep docs asset URLs repo-root-relative and pass images as literal MDX children so Mintlify can compile them through OptimizedImage under the /docs mount. Mintlify's official guidance says: “Image paths are root-relative from your docs repository.” It also says relative paths such as `./screenshot.png` are unsupported. See [Image embeds](https://www.mintlify.com/docs/create/image-embeds). The existing `/images/...` paths were correct. The failure came from passing them through custom-component string props, which kept Mintlify from seeing those images during its MDX transform. - fix hero, building-block, and Slack avatar images - preserve Slack avatar clipping - normalize Hermes and Company Brain icon sizing Tested with Mintlify validation, broken-link checks, and browser checks across every changed route.
45 lines
1.8 KiB
Text
45 lines
1.8 KiB
Text
---
|
|
title: "Answering from Your Docs"
|
|
sidebarTitle: "From Docs"
|
|
description: "Ask about roadmaps, specs, and handbooks in plain language"
|
|
icon: "book"
|
|
---
|
|
|
|
import { SlackThread, SlackMessage, Mention } from "/snippets/slack-message.mdx";
|
|
|
|
## The scenario
|
|
|
|
The Q2 roadmap lives in Notion. Nobody wants to dig for the link mid-conversation — they just ask.
|
|
|
|
## What happens
|
|
|
|
<SlackThread channel="#product">
|
|
<SlackMessage self hasAvatar time="10:18 AM">
|
|
<img src="/images/company-brain/dhravya-slack-icon.jpg" alt="" />
|
|
<Mention>supermemory</Mention> what's in our Q2 roadmap?
|
|
</SlackMessage>
|
|
<SlackMessage bot hasAvatar time="10:18 AM">
|
|
<img src="/images/company-brain/supermemory-slack-icon.png" alt="" />
|
|
Three themes for Q2:
|
|
1. **Company Brain GA** — Slack bot, connectors, automations
|
|
2. **Memory Router v2** — lower latency, better multi-tenant isolation
|
|
3. **Enterprise SSO + audit log**
|
|
|
|
Full doc: *Q2 Roadmap* in Notion (last updated Jun 3).
|
|
</SlackMessage>
|
|
</SlackThread>
|
|
|
|
## What's really going on
|
|
|
|
This is a [data connector](/company-brain/connectors) (Notion, Google Drive, or OneDrive) feeding [public channel memory](/company-brain/permissions). Content is fetched, chunked, embedded, and re-synced on a schedule — so when the roadmap changes in Notion, answers stay current without anyone re-uploading.
|
|
|
|
Same pattern works for handbooks, design docs, RFCs, and "where do we document X?" style questions. If it doesn't know, it says so rather than guessing.
|
|
|
|
<CardGroup cols={2}>
|
|
<Card title="Connectors" icon="plug" href="/company-brain/connectors">
|
|
Bring Drive, Notion, and OneDrive into public channel memory.
|
|
</Card>
|
|
<Card title="Permissions" icon="shield-check" href="/company-brain/permissions">
|
|
Who can see what once it's indexed.
|
|
</Card>
|
|
</CardGroup>
|