mirror of
https://github.com/supermemoryai/supermemory.git
synced 2026-08-28 05:25:33 +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.
40 lines
1.8 KiB
Text
40 lines
1.8 KiB
Text
---
|
|
title: "Meeting Recall"
|
|
sidebarTitle: "Meeting Recall"
|
|
description: "Ask what was decided in a meeting and get the answer from synced notes"
|
|
icon: "calendar-check"
|
|
---
|
|
|
|
import { SlackThread, SlackMessage, Mention } from "/snippets/slack-message.mdx";
|
|
|
|
## The scenario
|
|
|
|
Someone missed the Acme call — or was there and forgot the outcome. They ask in Slack and get the decision, with a path back to the source notes.
|
|
|
|
## What happens
|
|
|
|
<SlackThread channel="#sales">
|
|
<SlackMessage self hasAvatar time="4:05 PM">
|
|
<img src="/images/company-brain/dhravya-slack-icon.jpg" alt="" />
|
|
<Mention>supermemory</Mention> what did we decide in the meeting with Acme?
|
|
</SlackMessage>
|
|
<SlackMessage bot hasAvatar time="4:05 PM">
|
|
<img src="/images/company-brain/supermemory-slack-icon.png" alt="" />
|
|
Acme is moving to annual billing at the current rate, with a 90-day pilot on the enterprise SSO add-on. Follow-up owned by **Priya**, due Friday. *(from Granola notes, Acme QBR — Jun 11)*
|
|
</SlackMessage>
|
|
</SlackThread>
|
|
|
|
## What's really going on
|
|
|
|
Meeting notes come in through a [connector](/company-brain/connectors) — Granola for live meeting notes, or Drive/Notion if notes land there. Once synced, they live in [public channel memory](/company-brain/permissions), so anyone on the team can ask about them. The answer cites the source so you can open the original notes and verify.
|
|
|
|
Ask about a decision, an owner, a date, or "what did we promise them" — plain language is fine.
|
|
|
|
<CardGroup cols={2}>
|
|
<Card title="Permissions" icon="shield-check" href="/company-brain/permissions">
|
|
Why meeting notes land in public channel memory.
|
|
</Card>
|
|
<Card title="Connectors" icon="plug" href="/company-brain/connectors">
|
|
Connect Granola, Drive, or Notion.
|
|
</Card>
|
|
</CardGroup>
|