mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-27 13:06:20 +02:00
* chore(docs-site): add @multica/ui bridge and dev:docs script Link @multica/ui as a workspace dep of @multica/docs so the docs app can consume the shared design tokens (tokens.css, base.css) via a relative import — same pattern the web and desktop apps use. Add a top-level pnpm dev:docs script for a one-command docs dev server (port 4000). Preparation for the docs site rewrite tracked in docs/docs-outline.md. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * feat(docs-site): apply Multica tokens and pure-sans typography Replace Fumadocs' neutral color preset with a @theme inline bridge that maps the --color-fd-* chrome tokens to Multica's --background / --foreground / --border / --sidebar-* etc. Sidebar, nav, cards now pick up Multica's cool-gray palette automatically, and switching Multica's .dark flips Fumadocs chrome with it. Typography: pure sans (36px / weight 600 / tight tracking h1, h2+h3 tuned to match), landing continuity without serif display. Code blocks: pinned to near-black (oklch(0.12 0.01 250)) regardless of page theme so they read as a continuation of the landing hero surface. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(plan): add rewrite plan and outline tracker Two planning documents for the docs site rewrite: - docs/docs-rewrite-plan.md — strategic rationale (positioning, reader personas, design principles, visual direction, phase breakdown). - docs/docs-outline.md — execution tracker. 25 v1 pages with per-page entries (source files, audience, what-to-write, what-not-to-write, ⚠️ verify-before-drafting). Workflow: claim via Owner + Status, read source, verify checklist, draft, review, ship. Language: zh only for v1. Outline is the source of truth for scope and status; the earlier "EN first, ZH as Phase 10" line in rewrite-plan.md is superseded. Welcome (§1.1) is claimed under this tracker and currently in 👀 review. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(docs-site): write first Welcome page (zh) — §1.1 Implements §1.1 Welcome per docs/docs-outline.md. Chinese-first (per outline language decision); terms translated to their clearest Chinese equivalents (issue → 任务, agent → 智能体, daemon → 守护进程, etc.), product proper nouns and commands kept in English. Voice: reference-style, not marketing. Follows google-gemini/docs-writer skill rules (BLUF opener, second-person, active voice, no hype, overview prose before every list). Content: - Opens by describing Multica as a 任务协作 platform and how humans + AI 智能体 share the same 工作区 - Two interaction modes: 分配任务 and 聊天 - 智能体在哪里运行: local daemon (today), cloud runtime (soon, waitlist). 10 providers listed from source (server/pkg/agent/*.go). - Three usage paths split into back-end (Cloud / Self-host) and client (Desktop) choices — Desktop bundles CLI and auto-starts daemon. - Status: 👀 In review. Also simplifies content/docs/meta.json to just ["index"] (placeholder page entries removed; IA skeleton will be populated in Phase 2). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * chore(docs-site): wire up client-side Mermaid rendering Add a <Mermaid> React component under apps/docs/components/ that dynamic- imports the mermaid package in useEffect and renders the resulting SVG. Deps added: mermaid@^11.14.0 and next-themes@^0.4.6 (transitively present via fumadocs-ui but needs explicit declaration to be importable). Design choices: - Client-side render (not build-time). No Playwright / browser automation in CI. Mermaid bundle (~400 KB) is loaded only on pages that use the component, thanks to the dynamic import. - Theme flips automatically — useTheme() from next-themes re-invokes mermaid.initialize() with the correct theme on .dark toggle. - SSR safe: the component returns a "Rendering diagram…" placeholder on the server; the SVG appears after hydration. - securityLevel "strict" — diagrams render as static SVG with no inline script or event handlers. Usage in mdx (explicit import, same pattern as Cards/Callout): import { Mermaid } from "@/components/mermaid"; <Mermaid chart={` graph LR User --> Server `} /> Verified by a scratch /app/mermaid-test/ route that compiled to 4665 modules and returned HTTP 200 (cleanup done pre-commit). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * feat(docs-site): adopt v2 editorial palette and typography Replace the Linear/Vercel-style cool-gray token override with a warm editorial palette (bg matches landing #f7f7f5, brand-color primary via Multica's existing --brand hue 255) and wire Source Serif 4 for heading typography. Italic is avoided sitewide — Chinese italic renders as a synthetic slant against upright-designed glyphs and reads as broken; emphasis is carried by serif/sans contrast, brand color, and weight. Sidebar adopts the product app's active-fill pattern (solid sidebar-accent background, no ::before mark). Code blocks drop the always-dark hero treatment and follow page theme so the reading column stays coherent. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * feat(docs-site): add editorial MDX components New components/editorial.tsx exposes Byline, NumberedCards/NumberedCard, and NumberedSteps/Step — the "wow moment" pieces from v2-editorial (ruled-divider bylines, No. 01 serif card numbering, large serif step counters). All escape prose via not-prose so they run their own type scale. DocsHero is rewritten as an editorial showpiece: title accepts ReactNode so callers can pass a brand-color em accent, eyebrow becomes a small uppercase sans label, lede uses serif at 20px. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(docs-site): rewrite welcome page as editorial showpiece Welcome page now opens with an editorial hero (eyebrow + serif h1 with brand-color em accent on "共处一方。" + serif lede), a ruled byline strip carrying the section / updated / read-time metadata, and then flows into prose. The three deployment paths switch from fumadocs's <Cards> to <NumberedCards> so each gets a No. 01/02/03 label, and the "next steps" list becomes a <NumberedSteps> block with large serif counters. These are the highest-impact visual moments on the page; the rest of the guide pages still get the global editorial chrome without needing per-page code. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * feat(docs-site): add bilingual flat content tree with i18n routing Restructures the docs site from nested topic folders (cli/, getting-started/, developers/, guides/) into a flat content tree, and adds Chinese alongside English. The old nested structure forced contributors to think about both the topic AND the user-journey grouping; the flat tree lets a single meta.json control reading order with separator labels, and lets the same slug serve both languages via the `foo.zh.mdx` parser convention. Routing - New `app/[lang]/` segment hosts layout, home, slug page, and not-found - Self-contained basePath-aware middleware (fumadocs's built-in middleware isn't basePath-aware, so its rewrite/redirect targets break under /docs) - `hideLocale: 'default-locale'` keeps English URLs prefix-less; Chinese lives under /docs/zh/ - Sitemap excluded from middleware matcher so crawlers don't get rewritten into a non-existent locale-prefixed sitemap route - Default-language redirect preserves search string (UTM safety) - Home page declares its own generateStaticParams (Next layout params don't cascade) so /docs/ and /docs/zh are SSG, not dynamic per request SEO - New app/sitemap.ts emits hreflang alternates for every page - absoluteDocsUrl normalizes the home `/` so canonical URLs don't carry a trailing slash that mismatches the page's own canonical link - apps/web/app/robots.ts now advertises the docs sitemap Search - CJK tokenizer registered for the zh locale (Orama's English regex strips Han characters; without this Chinese search either returns empty or throws) Chrome - Custom DocsSettings replaces fumadocs's default icon-only sidebar footer with two labelled buttons (language + theme), matching the editorial design language Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
158 lines
4.5 KiB
TypeScript
158 lines
4.5 KiB
TypeScript
/**
|
|
* Multica architecture diagram for §1.2 "How Multica Works".
|
|
*
|
|
* Boundary-style layout: one large panel for "Your side" (where all the
|
|
* interesting stuff happens — code, keys, compute), one smaller panel for
|
|
* "Multica" (metadata store and coordinator). The asymmetric sizes and the
|
|
* brand-tinted left panel visually argue Multica's core thesis: AI runs on
|
|
* your machine, not ours.
|
|
*
|
|
* No SVG arrows. Relationships are carried by the layout itself — client
|
|
* side vs. server side is the universal mental model, readers don't need
|
|
* arrows to understand it.
|
|
*/
|
|
export function ArchitectureDiagram() {
|
|
return (
|
|
<div className="not-prose my-8">
|
|
{/* Desktop: asymmetric two-panel with connector */}
|
|
<div className="hidden md:grid md:grid-cols-[1.7fr_auto_1fr] md:gap-4 md:items-stretch">
|
|
<YourSide />
|
|
<Connector horizontal />
|
|
<MulticaSide />
|
|
</div>
|
|
|
|
{/* Mobile: stacked */}
|
|
<div className="md:hidden space-y-4">
|
|
<YourSide />
|
|
<Connector horizontal={false} />
|
|
<MulticaSide />
|
|
</div>
|
|
</div>
|
|
);
|
|
}
|
|
|
|
function YourSide() {
|
|
return (
|
|
<div className="rounded-lg border border-brand/30 bg-brand/[0.03] p-6 flex flex-col">
|
|
<div className="text-[11px] font-semibold uppercase tracking-[0.12em] text-brand mb-5">
|
|
Your side
|
|
</div>
|
|
|
|
<div className="flex-1 space-y-5">
|
|
{/* Client surfaces */}
|
|
<div>
|
|
<SectionLabel>Client</SectionLabel>
|
|
<div className="flex flex-wrap gap-2">
|
|
<Pill>Web app</Pill>
|
|
<Pill>CLI</Pill>
|
|
</div>
|
|
</div>
|
|
|
|
{/* Horizontal separator */}
|
|
<div className="h-px bg-brand/15" />
|
|
|
|
{/* Daemon + local tools */}
|
|
<div>
|
|
<SectionLabel>Daemon</SectionLabel>
|
|
<div className="text-xs text-muted-foreground mb-2.5">
|
|
Polls work from Multica. Invokes local AI coding tools:
|
|
</div>
|
|
<div className="flex flex-wrap gap-1.5">
|
|
<Pill>Claude Code</Pill>
|
|
<Pill>Codex</Pill>
|
|
<Pill>Cursor</Pill>
|
|
<Pill>Copilot</Pill>
|
|
<Pill muted>+ 6 more</Pill>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
|
|
{/* Tagline */}
|
|
<div className="mt-6 pt-4 border-t border-brand/20 flex items-center justify-center gap-3 text-[13px] font-medium text-brand">
|
|
<span>Your code.</span>
|
|
<span className="text-brand/40">·</span>
|
|
<span>Your keys.</span>
|
|
<span className="text-brand/40">·</span>
|
|
<span>Your CPU.</span>
|
|
</div>
|
|
</div>
|
|
);
|
|
}
|
|
|
|
function MulticaSide() {
|
|
return (
|
|
<div className="rounded-lg border border-border/70 bg-muted/25 p-6 flex flex-col">
|
|
<div className="text-[11px] font-semibold uppercase tracking-[0.12em] text-muted-foreground mb-5">
|
|
Multica
|
|
</div>
|
|
|
|
<div className="flex-1 flex flex-col">
|
|
<SectionLabel>Server</SectionLabel>
|
|
<div className="text-xs text-muted-foreground mb-4">
|
|
Cloud or self-hosted
|
|
</div>
|
|
|
|
<div className="text-xs space-y-1.5 text-foreground/80">
|
|
<div>Workspaces</div>
|
|
<div>Issues & tasks</div>
|
|
<div>Agent definitions</div>
|
|
<div>Realtime (WebSocket)</div>
|
|
</div>
|
|
</div>
|
|
|
|
<div className="mt-6 pt-4 border-t border-border/60 text-[11px] text-muted-foreground text-center uppercase tracking-[0.08em]">
|
|
No AI execution here.
|
|
</div>
|
|
</div>
|
|
);
|
|
}
|
|
|
|
function Connector({ horizontal }: { horizontal: boolean }) {
|
|
if (horizontal) {
|
|
return (
|
|
<div
|
|
className="flex items-center justify-center text-muted-foreground/50 text-xl select-none px-1"
|
|
aria-hidden="true"
|
|
>
|
|
⇄
|
|
</div>
|
|
);
|
|
}
|
|
return (
|
|
<div
|
|
className="text-center text-muted-foreground/50 text-xl select-none"
|
|
aria-hidden="true"
|
|
>
|
|
⇅
|
|
</div>
|
|
);
|
|
}
|
|
|
|
function SectionLabel({ children }: { children: React.ReactNode }) {
|
|
return (
|
|
<div className="text-[10px] font-medium uppercase tracking-[0.1em] text-muted-foreground/70 mb-1.5">
|
|
{children}
|
|
</div>
|
|
);
|
|
}
|
|
|
|
function Pill({
|
|
children,
|
|
muted = false,
|
|
}: {
|
|
children: React.ReactNode;
|
|
muted?: boolean;
|
|
}) {
|
|
return (
|
|
<span
|
|
className={`inline-flex items-center rounded-md border px-2 py-1 text-[11px] font-medium ${
|
|
muted
|
|
? "border-border/50 bg-background/50 text-muted-foreground"
|
|
: "border-border/70 bg-background text-foreground"
|
|
}`}
|
|
>
|
|
{children}
|
|
</span>
|
|
);
|
|
}
|