--- mw_bundle: 1 id: mw-ex-bundle title: "Sample Bundle: Tour of Memory.Wiki" url: https://memory.wiki/b/mw-ex-bundle document_count: 8 updated: 2026-05-24T17:48:04.005Z analysis_generated_at: 2026-05-14T19:04:29.031Z source: "Memory.Wiki" --- # Sample Bundle: Tour of Memory.Wiki > A three-document tour of Memory.Wiki: formatting, diagrams, and what the platform actually ships. Open the canvas to see how a bundle reads its own member docs. **Intent:** Show a newcomer what mdfy makes possible in three short docs. ## Summary This collection demonstrates mdfy as a next-generation markdown platform that bridges human writing and AI collaboration through flexible editing modes, universal content sharing, and intelligent document analysis. The documents showcase how mdfy eliminates traditional trade-offs in markdown editing while creating seamless workflows between different AI platforms. Together, they reveal mdfy's vision of making every document a shareable, AI-readable URL that preserves context across conversations and platforms. ## Themes - AI-human collaboration workflows - Cross-platform content portability - Flexible markdown editing - Knowledge preservation and analysis ## Cross-document insights - mdfy's three-view editing system solves a fundamental UX problem that other markdown editors forced users to choose between, revealing how interface flexibility can eliminate false trade-offs - The cross-AI portability through universal URLs creates a strategic moat that individual AI platforms cannot replicate due to competitive dynamics - mdfy treats AI conversations as first-class documents, suggesting a shift toward preserving AI interaction context as valuable knowledge assets - The bundle analysis system demonstrates how AI can provide meta-insights about human knowledge organization, creating feedback loops between content creation and understanding ## Key takeaways - mdfy eliminates the traditional WYSIWYG vs markdown source trade-off through its innovative three-view editing system - Universal URL sharing across all AI platforms creates unprecedented content portability and collaboration workflows - mdfy transforms AI conversations from ephemeral interactions into structured, shareable knowledge assets ## Open questions / gaps - No discussion of collaboration features for teams or multi-user scenarios beyond individual knowledge management - Missing details about data privacy, security, or offline capabilities for sensitive content - No mention of pricing model, limits, or enterprise features that might affect adoption decisions - Lack of examples showing how mdfy handles large-scale knowledge bases or performance at scale ## Notable connections - **doc:mdfy-ex-feat** ↔ **doc:mdfy-ex-edt** — The feature overview sets up the three-view editing system as a core differentiator - **doc:mdfy-ex-ai** ↔ **doc:mdfy-ex-dpl** — AI conversation capture directly enables the cross-platform sharing workflow - **doc:mdfy-ex-bun** ↔ **doc:mdfy-ex-hub** — Bundle analysis capabilities scale up to become the hub's knowledge graph insights - **doc:mdfy-ex-fmt** ↔ **doc:mdfy-ex-diag** — Both documents showcase mdfy's enhanced rendering capabilities beyond basic markdown - **doc:mdfy-ex-feat** ↔ **doc:mdfy-ex-dpl** — The platform overview's thesis about AI-readable URLs is proven by the deployment workflow ## Concepts (this bundle) - **Three-view editing system** - **AI-human collaboration** - **Cross-AI portability** - **Knowledge preservation** - **Cross-document analysis** ## Concept relations - **Three-view editing system** ↔ **AI-human collaboration** — supports - **Knowledge preservation** ↔ **Cross-AI portability** — enables - **Cross-document analysis** ↔ **Knowledge preservation** — builds on ## Documents ### 1. [Markdown formatting in mdfy](https://memory.wiki/mw-ex-fmt) > Start here — the formatting vocabulary every other mdfy doc assumes. mdfy renders standard GitHub-flavored Markdown plus a few extras worth knowing about. *sections:* Inline: Regular text, bold, italic, bold italic, ~~strikethrough~~, and inline code. | Lists: Bullets nest:; Second level; Third level; And tasks toggle inline (click the checkbox in Live mode):; [x] Done; [ ] Open; … | Tables: | Doc | Bundle | Hub | | Code: typescript | Math: Inline KaTeX: $E = mc^2$. ### 2. [Diagrams: Mermaid + ASCII](https://memory.wiki/mw-ex-diag) > Visual content. Mermaid is the default; ASCII is the LLM-friendly fallback. mdfy renders diagrams from two source dialects so you can paste either and get the same picture. *sections:* Mermaid: Use a fenced block with mermaid: | ASCII: Paste an ASCII diagram and mdfy renders it as a stylized container. | Why both: ASCII is what LLMs default to producing. Mermaid is what scales to complex graphs. mdfy keeps both in the same toolbox so you don't have to choose at the moment ### 3. [What ships in mdfy](https://memory.wiki/mw-ex-feat) > What the platform actually ships — Publish, Render, Capture, Compose, Deploy. A quick tour of the pieces, so the rest of the docs make sense. *sections:* Publish: Drop, paste, or type Markdown → get a permanent URL like mdfy.app/.; The URL is sharable, indexable, and AI-readable (every public URL has a clean-markdown variant at /raw/).; No login required to publish; signed-in users get a hub at mdfy.app/hub/. | Render: Rust → WebAssembly Markdown engine (comrak) for the heavy lifting.; highlight.js for code, KaTeX for math, Mermaid for diagrams.; Dark and light themes; the print stylesheet doubles as the PDF export path. | … ### 4. [Capturing AI conversations](https://memory.wiki/mdfy-ex-ai) > How AI conversations turn into permanent, AI-readable URLs. mdfy treats the AI conversation as a first-class document type. *sections:* Three paths in: 1. Paste a share URL. ChatGPT, Claude, or Gemini conversation links resolve to clean markdown automatically. | Why capture matters: Every captured chat lives at a permanent URL like mdfy.app/abc123. The URL is two-way readable: humans see a rendered doc, AIs fetch it as clean markdown. ### 5. [Bundles as thinking surfaces](https://memory.wiki/mdfy-ex-bun) > A bundle reads what you gathered — themes, insights, tensions, gaps. A bundle isn't a folder. It's a collection that reads itself. *sections:* The mechanics: Select 3 or more docs in the sidebar, choose Bundle, give it a one-line Intent ("Decide our SNS launch strategy"). The bundle URL mdfy.app/b/ opens to a can | What it produces: Run discovery and the canvas surfaces:; Themes that recur across docs; Insights the AI noticed reading them together; Tensions where two docs contradict each other; Gaps the collection misses; Connections as doc-to-doc relationships; … | Compile: From the canvas toolbar, Memo / FAQ / Brief synthesises the whole bundle into a coherent artifact. The compiled doc remembers its source bundle, so a single cli ### 6. [The Hub: your personal knowledge URL](https://memory.wiki/mdfy-ex-hub) > One URL that rolls up every doc and bundle, with a living concept index. A Hub rolls every doc and bundle you publish into one address: `mdfy.app/hub/`. *sections:* What the hub does: Indexes everything you publish with a concept ontology (conceptindex) so cross-doc references emerge as you write.; Exposes a single URL that any AI can fetch end-to-end via /raw/hub/ or /hub//llms-full.txt.; Supports compact digests — ?digest=1 returns a concept-clustered summary instead of the full body. | Why one URL beats many: Pasting 20 doc links into Claude works but wastes tokens and breaks ordering. The hub URL is one paste and the AI gets a coherent representation of your persona | … ### 7. [Deploying a URL to any AI](https://memory.wiki/mdfy-ex-dpl) > How a mdfy URL travels into Claude / ChatGPT / Cursor and why cross-AI is the moat. The viral loop in mdfy runs through URLs. *sections:* Paste, don't paste: Copy mdfy.app/ into Claude / ChatGPT / Cursor and the model fetches clean markdown automatically — no special configuration, no extensions, no API keys. Eve | Three token-economy knobs: | Query | What it returns | | Cross-AI is the moat: A single AI vendor can build deeper integration than mdfy with its own model. None of them can deliver a URL that works across their competitors' models — that ### 8. [Live, Split, and Source](https://memory.wiki/mdfy-ex-edt) > Three views of the same doc: Live, Split, Source. mdfy gives you three ways to look at the same document. *sections:* Live (default): WYSIWYG. You see the rendered output and type into it directly — bold is bold, headings are headings, the markdown source stays behind the scenes. Best for pros | Split: Two panes side-by-side: Source on the left, Live on the right. Edit either side; changes sync. Best for hand-written tables, math, or when you want to verify ho | Source: Pure markdown in a CodeMirror editor with full syntax highlighting and shortcuts. Best for bulk edits, find-and-replace, or pasting machine-generated markdown v | Why three: WYSIWYG markdown editors usually pick one — either you write in markdown and "preview," or you write in WYSIWYG and "export." mdfy refuses the trade-off: the so _Digest view — follow any link above to fetch that doc's full markdown. Add `?full=1` to this URL for the concatenated payload._