Personal AI, On Personal Devices
Python
docs(showcase): add outcome-first gallery tier above Tutorials (#500)
Jon Saad-Falcon68b27654a87b
diff --git a/docs/assets/showcase/README.md b/docs/assets/showcase/README.mdnew file mode 100644index 00000000..07cac7f0--- /dev/null+++ b/docs/assets/showcase/README.md@@ -0,0 +1,45 @@+# Showcase screenshots++This directory holds the hero screenshot for each Showcase entry in `docs/showcase/`. Convention is one file per entry, named to match the entry's slug:++| Entry | Screenshot path |+|---|---|+| `docs/showcase/morning-brief.md` | `morning-brief.png` |+| `docs/showcase/persistent-memory.md` | `persistent-memory.png` |+| `docs/showcase/cost-savings.md` | `cost-savings.png` |+| `docs/showcase/discord-companion.md` | `discord-companion.png` |+| `docs/showcase/coding-assistant.md` | `coding-assistant.png` |++## Conventions++| | |+|---|---|+| Format | PNG, sRGB, no alpha channel |+| Size | 1600×1000 (4:2.5 — wider than 16:9, so screenshots don't get letterboxed in the docs grid) |+| File size | Under 400 KB after `pngquant --quality 70-90 --speed 1` |+| Loading | All `<img>` and `<figure>` tags in showcase pages use `loading=lazy` — these images are below the fold on the gallery page |++## What to redact++- Real email addresses+- API keys, OAuth tokens, anything starting with `sk-`, `ghp_`, `xox`, `eyJ`+- Personal phone numbers+- Conversation partners' faces or full names (unless they've signed off)+- File paths that include other people's home directories++## What to keep++- Model names ("llama3.1:8b", "qwen2.5:14b") — they're informative+- Timestamps — proves the screenshot is recent+- Dollar amounts on the leaderboard — the whole point+- Emoji reactions, your own first name, your own avatar++## Placeholder PNGs++This directory ships with no images on the initial PR. The Showcase pages reference image paths that don't exist yet — MkDocs will render a broken-image placeholder, and the figcaption still conveys what should be there. Real screenshots arrive in follow-up PRs as Showcase entries are populated with each contributor's actual setup.++If you're contributing the first real entry, drop your PNG at `docs/assets/showcase/<your-slug>.png` in the same PR that adds your markdown page. The image filename must match the slug used in the showcase page's `<img>` reference.++## Regenerating screenshots in bulk++A future enhancement (tracked as PR #3 in the showcase-tier roadmap) will add `scripts/showcase/regen_screenshots.py` — a Playwright-driven pipeline that boots a demo `jarvis serve` against a sealed config and captures fresh screenshots for every showcase entry on each release tag. Until that lands, screenshots are contributed manually by each Showcase author.diff --git a/docs/assets/showcase/coding-assistant.png b/docs/assets/showcase/coding-assistant.pngnew file mode 100644index 00000000..bde08dfbBinary files /dev/null and b/docs/assets/showcase/coding-assistant.png differdiff --git a/docs/assets/showcase/cost-savings.png b/docs/assets/showcase/cost-savings.pngnew file mode 100644index 00000000..bde08dfbBinary files /dev/null and b/docs/assets/showcase/cost-savings.png differdiff --git a/docs/assets/showcase/discord-companion.png b/docs/assets/showcase/discord-companion.pngnew file mode 100644index 00000000..bde08dfbBinary files /dev/null and b/docs/assets/showcase/discord-companion.png differdiff --git a/docs/assets/showcase/morning-brief.png b/docs/assets/showcase/morning-brief.pngnew file mode 100644index 00000000..bde08dfbBinary files /dev/null and b/docs/assets/showcase/morning-brief.png differdiff --git a/docs/assets/showcase/persistent-memory.png b/docs/assets/showcase/persistent-memory.pngnew file mode 100644index 00000000..bde08dfbBinary files /dev/null and b/docs/assets/showcase/persistent-memory.png differdiff --git a/docs/index.md b/docs/index.mdindex 32222d79..de67043c 100644--- a/docs/index.md+++ b/docs/index.md@@ -14,6 +14,18 @@ OpenJarvis is a research framework for composable, on-device AI systems.Build personal AI that runs on your hardware. Cloud APIs are optional.</p>+<div class="grid cards" markdown>++- :material-image-multiple:{ .lg .middle } **See what people use it for**++ ---++ A gallery of real setups — morning briefs that summarize your overnight Slack and email, a Discord companion that knows your calendar, a code reviewer that works at 30,000 feet. Outcome-first, with links to the docs that explain how to build each one.++ [:octicons-arrow-right-24: Browse the Showcase](showcase/index.md)++</div>+---## Why OpenJarvis?diff --git a/docs/showcase/CONTRIBUTING.md b/docs/showcase/CONTRIBUTING.mdnew file mode 100644index 00000000..6fc3f2e2--- /dev/null+++ b/docs/showcase/CONTRIBUTING.md@@ -0,0 +1,104 @@+---+title: Contributing a Showcase Entry+description: How to add your setup to the OpenJarvis Showcase+---++# Contributing a Showcase Entry++The Showcase exists for one reason: to help a confused, curious, *non-technical* reader figure out whether OpenJarvis is worth their weekend. That goal sets every editorial choice on this page.++## The format++```markdown+---+title: <Your Title — short, capitalized>+description: <One sentence. The hook a stranger sees in search results.>+---++# <emoji> <One-sentence hook — what it does FOR you, in plain English>++<figure markdown>+ { .showcase-screenshot loading=lazy }+ <figcaption>A one-sentence caption that adds context the image can't show on its own.</figcaption>+</figure>++<2–3 short paragraphs of context: when do you use this, what changed for+you, what the experience feels like. Concrete > abstract. "I read it on+my phone before coffee" > "improves morning productivity."++A bulleted list of two or three CONCRETE OUTCOMES works well — your+calendar, your inbox, your code. Specific verbs and proper nouns.>++## Why it's nice++- **<one-line benefit>.** <one or two sentences of evidence>+- **<one-line benefit>.** <one or two sentences of evidence>+- **<one-line benefit>.** <one or two sentences of evidence>++## How I set this up++→ **[Tutorial: <name>](../tutorials/<file>.md)** is the closest match.++→ **[Recipe: <name>](https://github.com/open-jarvis/OpenJarvis/tree/main/src/openjarvis/recipes/data)** if you want the exact config.++→ **[<one more related doc>](../<path>.md)** if the reader is going deeper.+```++## Editorial conventions++These are guardrails, not rules. Break them if you have a reason.++### Lead with the outcome, not the technology++❌ "Multi-channel routing with MCP-backed memory and an orchestrator agent."<br>+✅ "Jarvis answers my Discord messages while I sleep."++The reader doesn't know what an "orchestrator agent" is yet. They know what a Discord message is.++### Show one screenshot. Make it the headline.++A single, large, *interesting* screenshot beats five small ones. Crop it to show the result, not the UI chrome. If you can convey it in an image, don't write the paragraph.++**Screenshot specs:**++- 1600×1000 PNG, sRGB, no alpha+- File path: `docs/assets/showcase/<your-slug>.png`+- Redact: real email addresses, API keys, personal phone numbers, conversation partners' faces or full names (unless they've signed off)+- Keep: model names, timestamps, dollar amounts, emoji reactions, your own first name++### Specific over impressive++❌ "Saves significant time every morning."<br>+✅ "Cut my morning catch-up from 25 minutes to 2."++Numbers, durations, dollar amounts, and named tools build trust. Adjectives don't.++### Three paragraphs is plenty++A reader who wants more clicks the "How I set this up →" link at the bottom. Showcase pages are a funnel into the docs, not a replacement for them. If you find yourself explaining configuration in the showcase entry, that material belongs in the linked tutorial.++### "Why it's nice" is for the experience, not the architecture++The bullets under **Why it's nice** should answer "what's different *for you*?" — not "what's different about how the framework works?". Save the architecture talk for the linked docs.++❌ "Uses local SQLite for state with WAL mode for concurrent reads."<br>+✅ "I can read my own memory file in a text editor. I can delete a line and the memory is gone."++### Every entry must end with at least one "How I set this up →" link++If there isn't a relevant tutorial yet, link to the closest [User Guide](../user-guide/cli.md) and open an issue noting that the tutorial is missing. We will write it.++## Submitting++1. **Fork** the repo and create a branch: `docs/showcase-<your-slug>`.+2. **Add** your markdown file at `docs/showcase/<your-slug>.md` and screenshot at `docs/assets/showcase/<your-slug>.png`.+3. **Add a tile** to the grid in `docs/showcase/index.md` (matches the existing pattern — emoji + title + 1-sentence summary + `[:octicons-arrow-right-24: See it](<your-slug>.md)`).+4. **Open a PR** with the title `docs(showcase): <your title>`. Tag a maintainer if you'd like editorial feedback before merge.++## Where this goes after merge++Hannah and the docs team post merged showcase entries to **`#config-showcase`** in [the OpenJarvis Discord](https://discord.gg/openjarvis). You'll get tagged in the post — you don't have to do it yourself.++## Questions, drafts, half-finished ideas++Drop them in **`#config-showcase`** on Discord *before* opening a PR. Editorial feedback is faster on chat than in a PR review, and you'll save yourself a round of revisions.diff --git a/docs/showcase/coding-assistant.md b/docs/showcase/coding-assistant.mdnew file mode 100644index 00000000..223c6b03--- /dev/null+++ b/docs/showcase/coding-assistant.md@@ -0,0 +1,36 @@+---+title: Offline Code Reviewer+description: Review a pull request on a transatlantic flight, no internet required+---++# 🛠️ Offline Code Reviewer — code review on an airplane++<figure markdown>+ { .showcase-screenshot loading=lazy }+ <figcaption>Airplane mode in the menu bar. Jarvis reading a `git diff`, the surrounding files, and producing a code review at gate-level Wi-Fi (i.e., none).</figcaption>+</figure>++Earlier this month I was on a flight from SFO to FRA — eleven hours, no usable Wi-Fi. I had a teammate's pull request open in VS Code. I asked Jarvis to review it. It read the diff, read the three files the diff touched, read the project's `CLAUDE.md` for conventions, and produced a review with five comments — two of which caught real bugs.++The review took about 40 seconds on the laptop's built-in GPU. No API call. No "you're offline" error. By the time we landed I'd dropped the comments into GitHub and the PR was merging.++The same setup handles:++- **Code review** — diff + context files + conventions, structured comments.+- **Debugging** — paste a traceback, Jarvis reads the stack, opens the relevant files, suggests fixes.+- **Test generation** — point at a function, get back a `pytest` file with edge cases.+- **Documentation** — generate docstrings that actually match the code, because Jarvis has the file open.++## Why it's nice++- **It works on a plane.** Or a train, or a hotel with bad Wi-Fi, or your couch when Comcast is having a day. Same speed every time.+- **It sees your repo, not a sanitized chunk.** Cloud coding assistants make you upload a context window. The local one just reads `git status` and the files you're working on.+- **No "we trained on your code" question.** Your code never leaves your laptop. Period.++## How I set this up++→ **[Tutorial: Code Companion](../tutorials/code-companion.md)** walks through the ReAct-agent + git/file/shell tool stack this uses end-to-end.++→ **[User Guide: Code Assistant](../user-guide/code-assistant.md)** is the focused recipe walkthrough for daily-driver code review.++→ **[OpenAI-compatible server](../getting-started/quickstart.md)** — point your editor's existing AI integration (Cursor, Continue, Cody, Aider) at `localhost:8000`. They mostly don't know they're not talking to OpenAI.diff --git a/docs/showcase/cost-savings.md b/docs/showcase/cost-savings.mdnew file mode 100644index 00000000..f5ab787f--- /dev/null+++ b/docs/showcase/cost-savings.md@@ -0,0 +1,38 @@+---+title: Track Your Savings+description: A leaderboard that tells you exactly how much you saved by running locally+---++# 💸 Track Your Savings — the leaderboard that makes local-first feel real++<figure markdown>+ { .showcase-screenshot loading=lazy }+ <figcaption>The public leaderboard. The bar on the right is what a month of my Jarvis usage would have cost on the cloud — measured per-query, not estimated.</figcaption>+</figure>++OpenJarvis tracks every inference call you make — the tokens, the latency, the GPU energy — and computes what that same call *would have cost* on OpenAI, Anthropic, Google, and Bedrock. There's a public leaderboard at **[/leaderboard](../leaderboard.md)** where anyone running Jarvis can opt in and watch their savings rack up.++My current month is roughly:++| | |+|---|---|+| Local inference cost | **`$0.00`** |+| Cloud-equivalent cost | **`$342.18`** (Claude Sonnet 4.6 baseline) |+| Energy used | **`1.4 kWh`** (~12¢ of grid power) |+| Prompts sent to a third party | **`0`** |++The dollar number is the hook. The bottom row is the actual reason I run Jarvis.++## Why it's nice++- **You can see what each query costs you.** Not estimated, not "roughly" — measured. Watt-hours per token, FLOPs per token, latency. Every primitive in OpenJarvis treats compute cost as a first-class quantity alongside accuracy.+- **It makes "local-first" stop being abstract.** Watching a bar chart accumulate `$X` a week that *didn't* leave your hands is a different kind of motivating than "your data is private" claims that you can't verify.+- **Privacy stops being an act of faith.** Every prompt I send to Jarvis can be traced through the codebase to local-only paths. No "cloud failover" hiding behind a switch.++## How I set this up++You don't, really — it's on by default. Every `jarvis ask`, `jarvis serve` request, and channel-routed message is metered by the [telemetry system](../telemetry.md). To opt your savings into the public leaderboard:++→ **[Leaderboard guide](../leaderboard.md)** — one command to opt in, one command to opt out. Telemetry is local-only by default.++→ **[Telemetry overview](../telemetry.md)** — what's measured, where it's stored, and how to inspect it yourself with `jarvis telemetry`.diff --git a/docs/showcase/discord-companion.md b/docs/showcase/discord-companion.mdnew file mode 100644index 00000000..9dbc51a9--- /dev/null+++ b/docs/showcase/discord-companion.md@@ -0,0 +1,34 @@+---+title: Discord Companion+description: Jarvis answers questions in your private Discord while you sleep — reads your notes, checks your calendar, schedules things+---++# 💬 Discord Companion — a personal assistant that lives in my Discord++<figure markdown>+ { .showcase-screenshot loading=lazy }+ <figcaption>I DM'd Jarvis from my phone at midnight. It checked my Google Calendar, cross-referenced a note from last week, and answered — running on the Mac mini in my closet.</figcaption>+</figure>++I have a private Discord server with two channels and one user (me). Jarvis lives there. I can DM it from my phone, my laptop, or my watch — anywhere Discord runs. Sample things I've asked it this week:++- "What's the address of the place I had that meeting last Tuesday?" → Jarvis searches my calendar + meeting notes, replies in 4 seconds.+- "Reply to Mom's text from earlier saying I'll call tomorrow at 7." → drafts a reply, asks me to confirm, sends.+- "Add 'Sam's birthday is March 12' to my long-term memory." → updates `MEMORY.md`, confirms.+- "Summarize the last hour of conversation in `#deploys-prod`." → reads the Slack channel via MCP, summarizes.++I used to use my phone's voice assistant for this. The two differences that matter: **Jarvis answers in three sentences, not one,** and **it actually has my context** — my notes, my calendar, my projects, my history.++## Why it's nice++- **Latency feels like talking to a person.** Local inference on a modest GPU is 5–10× faster than round-tripping to a cloud API. Question to answer in 3 seconds.+- **The Discord interface is multi-device for free.** Same conversation thread on my phone, laptop, watch — no special app to install.+- **It's already private.** A Discord server I run, talking to a model on a machine I own. The data trail is two endpoints I control.++## How I set this up++→ **[Tutorial: Messaging Hub](../tutorials/messaging-hub.md)** is the closest match — same channel-adapter + orchestrator-agent pattern, with Discord substituted for Slack.++→ **[Channel docs](../user-guide/cli.md)** walks through Discord/Slack/Telegram/WhatsApp setup. Discord is two environment variables and a bot token.++→ **[MCP integration guide](../user-guide/cli.md)** if you want Jarvis to reach into Notion, Linear, Gmail, etc.diff --git a/docs/showcase/index.md b/docs/showcase/index.mdnew file mode 100644index 00000000..24c163cf--- /dev/null+++ b/docs/showcase/index.md@@ -0,0 +1,72 @@+---+title: Showcase+description: What people actually do with OpenJarvis — outcomes first, scripts later+---++# Showcase++These are stories from people who use OpenJarvis day to day. Each entry shows the **result** — a screenshot, a paragraph of context, and a short link to the docs that explain how to build it. If you're trying to figure out whether OpenJarvis is worth a weekend of your time, start here.++!!! tip "New here?"+ The Showcase answers *"what's possible?"*. When you find something you want for yourself, follow the **How I set this up** link at the bottom of each page — it lands on a [Tutorial](../tutorials/index.md) that walks through the build.++<div class="grid cards" markdown>++- :material-coffee:{ .lg .middle } **Morning Brief**++ ---++ Slack, email, GitHub, and calendar — read overnight, summarized into 5 bullets in your phone by 7am. Cuts the daily "what did I miss" tax to zero.++ [:octicons-arrow-right-24: See it](morning-brief.md)++- :material-brain:{ .lg .middle } **Memory That Doesn't Reset**++ ---++ Tell Jarvis you're allergic to shellfish once. Three months later it brings it up when you're restaurant-planning. Plain markdown files, no vector-DB tricks.++ [:octicons-arrow-right-24: See it](persistent-memory.md)++- :material-piggy-bank-outline:{ .lg .middle } **Track Your Savings**++ ---++ A leaderboard that tells you exactly how much you saved by running locally — and reminds you that none of your prompts ever left your house.++ [:octicons-arrow-right-24: See it](cost-savings.md)++- :material-message-text:{ .lg .middle } **Discord Companion**++ ---++ Jarvis answers questions in your private Discord while you sleep. Reads your notes, checks your calendar, schedules things, replies in your voice.++ [:octicons-arrow-right-24: See it](discord-companion.md)++- :material-code-tags-check:{ .lg .middle } **Offline Code Reviewer**++ ---++ Review a pull request on a transatlantic flight. Jarvis reads the diff, the surrounding files, and the project conventions — without an internet connection.++ [:octicons-arrow-right-24: See it](coding-assistant.md)++</div>++---++## Share your setup++The Showcase grows from real users. If you've built something interesting on top of OpenJarvis — or just have a configuration you're proud of — the format is simple and the bar is low:++1. **One-sentence hook**: what does this *do for you*?+2. **A screenshot or 15-second screen recording**: the visible result.+3. **2–3 short paragraphs**: when you use it, why it's nice (cost, privacy, speed, calm).+4. **"How I set this up →"**: a link to the relevant [Tutorial](../tutorials/index.md), [User Guide](../user-guide/cli.md), or [Recipe](https://github.com/open-jarvis/OpenJarvis/tree/main/src/openjarvis/recipes/data).++See [Contributing a Showcase Entry](CONTRIBUTING.md) for the template and the editorial conventions (screenshot sizing, what to redact, tone).++## Want to talk to other people doing this?++The **`#config-showcase`** channel in the [OpenJarvis Discord](https://discord.gg/openjarvis) is where people post and discuss personal setups. Drop a screenshot, ask "how would I do X?", or browse what others have shared.diff --git a/docs/showcase/morning-brief.md b/docs/showcase/morning-brief.mdnew file mode 100644index 00000000..0c0924cc--- /dev/null+++ b/docs/showcase/morning-brief.md@@ -0,0 +1,39 @@+---+title: Morning Brief+description: Slack, email, GitHub, and calendar — summarized into a 5-bullet brief on your phone by 7am+---++# ☕ Morning Brief — Jarvis reads everything overnight so I don't have to++<figure markdown>+ { .showcase-screenshot loading=lazy }+ <figcaption>The 7am brief that arrives in my private Discord — 5 bullets, two minutes to read, written by an agent that ran on my desk while I slept.</figcaption>+</figure>++Every morning at 7am, before my first coffee, a message appears in my private Discord with five bullets:++- what shipped at work overnight (GitHub releases + merged PRs)+- the two emails I actually need to act on (with one-line summaries)+- anything mentioned in my team's `#general` Slack channel+- today's calendar with the next 24 hours of meetings+- one thing I asked Jarvis to track for me ("did Tuesday's deploy roll out cleanly?")++It's the first thing I read on my phone, while I'm still in bed. The brief used to take me 25 minutes — opening four apps, scrolling, deciding what mattered. Now it's two minutes of reading and I'm done.++## Why it's nice++- **Costs me nothing per month.** It runs on a Mac mini in my closet. Same prompt-volume on the OpenAI API would be `~$18/month` based on the leaderboard's estimates.+- **Nothing leaves my house.** My inbox, my Slack DMs, my calendar — Jarvis reads them locally and writes the digest locally. The only network call is the Discord webhook to my own private server.+- **It learns my taste.** Over a few weeks Jarvis figured out that PR titles starting with `chore:` aren't worth surfacing and that I don't want to see calendar holds I created myself. The summarizer has a `MEMORY.md` it updates when I react with 👎 to a bullet.++## What you'd need++A laptop or mini-PC that stays on overnight, an inference engine (Ollama is the easy default), accounts on whichever surfaces you want summarized (Slack, Gmail, GitHub, Google Calendar), and a Discord (or Slack, or Telegram, or email) destination to post the brief to.++## How I set this up++→ **[Tutorial: Scheduled Personal Ops](../tutorials/scheduled-ops.md)** walks through the cron-scheduled agent pattern this uses. The morning-brief flavour is `orchestrator` agent + the channel adapters + the scheduler primitive — three primitives, one TOML recipe.++→ **[User Guide: Morning Digest](../user-guide/morning-digest.md)** is the focused recipe walkthrough if you only want this one workflow.++→ **[User Guide: Channels](../user-guide/cli.md)** for connecting Discord/Slack/Telegram as the destination.diff --git a/docs/showcase/persistent-memory.md b/docs/showcase/persistent-memory.mdnew file mode 100644index 00000000..dba445d6--- /dev/null+++ b/docs/showcase/persistent-memory.md@@ -0,0 +1,34 @@+---+title: Memory That Doesn't Reset+description: Tell Jarvis something once. It remembers — three months later, across every conversation+---++# 🧠 Memory That Doesn't Reset — Jarvis actually knows me++<figure markdown>+ { .showcase-screenshot loading=lazy }+ <figcaption>Three months after I mentioned the allergy in passing, Jarvis brings it up — unprompted — while helping me pick a birthday-dinner restaurant.</figcaption>+</figure>++I mentioned to Jarvis once, in a throwaway sentence in April, that I'm allergic to shellfish. In July, when I asked it to help me pick a restaurant for my partner's birthday, it volunteered "you'll want to filter for menus that have non-shellfish options" — without being reminded, in a totally different conversation, on a different topic.++That's not magic. The trick is that Jarvis writes to three plain markdown files in my home directory whenever it learns something worth remembering:++- `SOUL.md` — how I want it to behave (tone, length, what to push back on)+- `MEMORY.md` — facts about me, my projects, my preferences+- `USER.md` — who I am: my role, my team, my context++Every new conversation starts by reading those three files. I can open them in any text editor. I can delete a line and the memory is gone. The whole thing is `~6 KB` of markdown. No vector DB, no embedding cache, no opaque "personalization layer."++## Why it's nice++- **It's auditable.** I can read what Jarvis "knows" about me in 30 seconds. Most personal-AI products literally can't tell you.+- **It's portable.** I keep my three files in iCloud Drive. When I set up Jarvis on a new machine, my memory comes with me — without re-onboarding.+- **It compounds.** After two weeks Jarvis stopped re-asking what my code style is. After six weeks it stopped re-asking who's on my team. The conversations get shorter because the context is already there.+- **It can't drift.** Vector retrieval can confidently surface the wrong "memory" and you'd never know. Plain markdown that I can read can't lie about what it contains.++## How I set this up++→ **[User Guide: Agents](../user-guide/agents.md)** explains the persistent-agent pattern, including how `SOUL.md` / `MEMORY.md` / `USER.md` are loaded at conversation start.++→ **[Tutorial: Deep Research Assistant](../tutorials/deep-research.md)** uses the same persistent-memory primitive — a good place to see it in action with code.diff --git a/docs/stylesheets/extra.css b/docs/stylesheets/extra.cssindex 7079e0fd..e3f370cd 100644--- a/docs/stylesheets/extra.css+++ b/docs/stylesheets/extra.css@@ -569,3 +569,18 @@display: none !important;}}++/* ---------------------------------------------------------------------------+ * Showcase screenshots+ *+ * Hero images on docs/showcase/* pages. Constrains width on wide screens and+ * adds a subtle border so placeholder/broken-image states still look intentional+ * before community-contributed screenshots populate docs/assets/showcase/.+ * ------------------------------------------------------------------------- */+.showcase-screenshot {+ max-width: 100%;+ height: auto;+ border-radius: 8px;+ border: 1px solid var(--md-default-fg-color--lightest, rgba(0, 0, 0, 0.08));+ box-shadow: 0 2px 8px rgba(0, 0, 0, 0.06);+}diff --git a/mkdocs.yml b/mkdocs.ymlindex ad42712c..e5e4df94 100644--- a/mkdocs.yml+++ b/mkdocs.yml@@ -150,6 +150,14 @@ nav:- Quick Start: getting-started/quickstart.md- Code Snippets: getting-started/snippets.md- Configuration: getting-started/configuration.md+ - Showcase:+ - Overview: showcase/index.md+ - Morning Brief: showcase/morning-brief.md+ - Memory That Doesn't Reset: showcase/persistent-memory.md+ - Track Your Savings: showcase/cost-savings.md+ - Discord Companion: showcase/discord-companion.md+ - Offline Code Reviewer: showcase/coding-assistant.md+ - Contributing: showcase/CONTRIBUTING.md- Tutorials:- Overview: tutorials/index.md- Deep Research Assistant: tutorials/deep-research.md