@mdwrk/mdwrkcom-content-pack 0.1.5

package/data/markdown/docs/authoring/theme-packs.md

@@ -0,0 +1,81 @@
+---
+title: Theme Pack Authoring
+slug: authoring/theme-packs
+section: Authoring
+sectionOrder: 3.5
+order: 3
+toc: true
+date: 2026-05-02
+status: published
+author: CobyCloud
+excerpt: Theme pack authoring uses MdWrk theme contracts, Theme Studio workflows, token exports, and package-ready surfaces for consistent editor and preview styling.
+---
+
+## Primary surface
+
+Theme authoring in this repository centers on:
+
+- `@mdwrk/theme-contract` for the formal token and bridge surface
+- `@mdwrk/extension-theme-studio` for first-party theme authoring UX
+- the shared editor and renderer package families that consume those tokens
+
+## What Theme Studio proves
+
+Theme Studio exists to prove that theme authoring can happen through the governed extension and token contracts instead of through app-local DOM patching.
+
+The first-party theme authoring flow covers:
+
+- inspecting formal theme tokens
+- previewing token changes against editor and renderer surfaces
+- applying and reverting draft changes
+- exporting portable theme artifacts
+
+## Authoring rules
+
+Theme packs should target the shared contract directly.
+They should not depend on application-local selectors or private client-only CSS assumptions.
+
+That means a valid theme authoring workflow should preserve:
+
+- contract-backed token names
+- editor and renderer bridge compatibility
+- reusable package independence from `apps/client/*` styling internals
+
+## Package and artifact expectations
+
+Theme authoring may produce:
+
+- exported CSS aligned with the theme contract
+- portable theme package scaffolds
+- previewable artifacts that can be consumed by the host, editor, and renderer surfaces
+
+## Reference surfaces
+
+Use these repo surfaces as the concrete reference:
+
+```text
+packages/extensions/extension-theme-studio/
+packages/contracts/theme-contract/
+docs/architecture/theme-studio-extension.md
+docs/architecture/theme-mapping-guide.md
+```
+
+## Quick Reference
+
+Use this article to understand Theme Pack Authoring in the MdWrk Authoring surface. Theme Pack Authoring explains how this MdWrk surface works in the current client and package system.
+
+Key concepts covered here:
+
+- local Markdown files
+- live preview
+- extension host contracts
+- theme portability
+- developer package reuse
+
+Useful follow-up pages:
+
+- [Local-First Markdown Workspace](/features/local-first-markdown-workspace)
+- [Markdown Preview Editor](/features/markdown-preview-editor)
+- [Editor Basics](/features/editor-basics)
+
+Use this path when you want to author portable MdWrk theme artifacts rather than only switch between built-in themes.

package/data/markdown/docs/comparisons/mdwrk-vs-logseq.md

@@ -0,0 +1,49 @@
+---
+title: MdWrk Vs Logseq
+slug: comparisons/mdwrk-vs-logseq
+section: Compares
+sectionOrder: 6
+order: 7
+toc: true
+date: 2026-05-03
+status: published
+author: CobyCloud
+displayAuthor: false
+excerpt: Compare MdWrk and Logseq when choosing between Markdown workspace authoring and an outline-first knowledge graph workflow.
+relatedApis: @mdwrk/mdwrkspace, @mdwrk/markdown-renderer-react
+---
+
+## Best Fit
+
+Choose MdWrk when you want document-centered Markdown with explicit editor and preview panes, file management, export, and package reuse.
+
+Choose Logseq when the primary workflow is block references, daily journals, outlines, and graph navigation.
+
+## Product Difference
+
+MdWrk keeps Markdown documents portable and easy to move through GitHub, npm, static docs, and local project workflows.
+
+## Related Docs
+
+- [Local-First Markdown Workspace](/features/local-first-markdown-workspace)
+- [Markdown Preview Editor](/features/markdown-preview-editor)
+
+## Quick Reference
+
+Use this article to understand MdWrk Vs Logseq in the MdWrk Comparisons surface. Compare MdWrk and Logseq when choosing between Markdown workspace authoring and an outline-first knowledge graph workflow.
+
+Key concepts covered here:
+
+- local Markdown files
+- live preview
+- workspace organization
+- extension host contracts
+- developer package reuse
+
+Useful follow-up pages:
+
+- [Local-First Markdown Workspace](/features/local-first-markdown-workspace)
+- [Markdown Preview Editor](/features/markdown-preview-editor)
+- [Editor Basics](/features/editor-basics)
+
+MdWrk is a Markdown workspace for files, preview, export, and extension-hosted tooling. Logseq is commonly used as an outline-first knowledge graph and journaling tool.

package/data/markdown/docs/comparisons/mdwrk-vs-marktext.md

@@ -0,0 +1,49 @@
+---
+title: MdWrk Vs MarkText
+slug: comparisons/mdwrk-vs-marktext
+section: Compares
+sectionOrder: 6
+order: 4
+toc: true
+date: 2026-05-03
+status: published
+author: CobyCloud
+displayAuthor: false
+excerpt: Compare MdWrk and MarkText when choosing between a local-first Markdown workspace with reusable packages and a focused desktop Markdown editor.
+relatedApis: @mdwrk/mdwrkspace, @mdwrk/markdown-editor-react
+---
+
+## Best Fit
+
+Choose MdWrk when you need browser/PWA availability, live workspace state, package-ready editor and renderer modules, extension contracts, and governed theme behavior.
+
+Choose MarkText when you want a desktop-focused Markdown editor with a minimal authoring experience.
+
+## Product Difference
+
+MdWrk connects writing, preview, workspace management, extensions, and package distribution as one product architecture.
+
+## Related Docs
+
+- [Offline Markdown Editor](/features/offline-markdown-editor)
+- [Theme Packs](/features/theme-packs)
+
+## Quick Reference
+
+Use this article to understand MdWrk Vs MarkText in the MdWrk Comparisons surface. Compare MdWrk and MarkText when choosing between a local-first Markdown workspace with reusable packages and a focused desktop Markdown editor.
+
+Key concepts covered here:
+
+- local Markdown files
+- live preview
+- workspace organization
+- extension host contracts
+- theme portability
+
+Useful follow-up pages:
+
+- [Offline Markdown Editor](/features/offline-markdown-editor)
+- [Local-First Markdown Workspace](/features/local-first-markdown-workspace)
+- [Markdown Preview Editor](/features/markdown-preview-editor)
+
+MdWrk and MarkText both keep Markdown authoring close to the source file.

package/data/markdown/docs/comparisons/mdwrk-vs-notion.md

@@ -0,0 +1,49 @@
+---
+title: MdWrk Vs Notion
+slug: comparisons/mdwrk-vs-notion
+section: Compares
+sectionOrder: 6
+order: 6
+toc: true
+date: 2026-05-03
+status: published
+author: CobyCloud
+displayAuthor: false
+excerpt: Compare MdWrk and Notion when choosing between local Markdown files and a hosted collaborative workspace.
+relatedApis: @mdwrk/mdwrkspace, @mdwrk/extension-workspace-files
+---
+
+## Best Fit
+
+Choose MdWrk when you want portable Markdown, local-first storage, explicit export, and a workspace that does not require a hosted document account for daily writing.
+
+Choose Notion when your priority is hosted collaboration, databases, shared workspaces, and rich block-based documents.
+
+## Product Difference
+
+MdWrk keeps the Markdown file as the durable content surface. That makes it practical for READMEs, docs repositories, changelogs, static-site content, and package documentation.
+
+## Related Docs
+
+- [Privacy-First Markdown Editor](/features/privacy-first-markdown-editor)
+- [Markdown File Manager](/features/markdown-file-manager)
+
+## Quick Reference
+
+Use this article to understand MdWrk Vs Notion in the MdWrk Comparisons surface. Compare MdWrk and Notion when choosing between local Markdown files and a hosted collaborative workspace.
+
+Key concepts covered here:
+
+- local Markdown files
+- workspace organization
+- privacy-first storage
+- extension host contracts
+- developer package reuse
+
+Useful follow-up pages:
+
+- [Privacy-First Markdown Editor](/features/privacy-first-markdown-editor)
+- [Local-First Markdown Workspace](/features/local-first-markdown-workspace)
+- [Editor Basics](/features/editor-basics)
+
+MdWrk and Notion solve different document problems.

package/data/markdown/docs/comparisons/mdwrk-vs-obsidian.md

@@ -0,0 +1,49 @@
+---
+title: MdWrk Vs Obsidian
+slug: comparisons/mdwrk-vs-obsidian
+section: Compares
+sectionOrder: 6
+order: 1
+toc: true
+date: 2026-05-03
+status: published
+author: CobyCloud
+displayAuthor: false
+excerpt: Compare MdWrk and Obsidian when you need local Markdown writing, preview, workspace management, extensions, and package-friendly developer surfaces.
+relatedApis: @mdwrk/mdwrkspace, @mdwrk/extension-host
+---
+
+## Best Fit
+
+Choose MdWrk when you want a browser/PWA-centered Markdown workspace, reusable editor and renderer packages, governed extension contracts, and explicit local privacy boundaries.
+
+Choose Obsidian when your primary workflow is a long-lived personal vault with graph navigation and a mature community plugin ecosystem.
+
+## Product Difference
+
+MdWrk emphasizes portable Markdown editing, preview, file management, extension-host contracts, and developer-facing packages that can be embedded in other products.
+
+## Related Docs
+
+- [Local-First Markdown Workspace](/features/local-first-markdown-workspace)
+- [MdWrk Extension Host](/features/extension-host)
+
+## Quick Reference
+
+Use this article to understand MdWrk Vs Obsidian in the MdWrk Comparisons surface. Compare MdWrk and Obsidian when you need local Markdown writing, preview, workspace management, extensions, and package-friendly developer surfaces.
+
+Key concepts covered here:
+
+- local Markdown files
+- live preview
+- workspace organization
+- extension host contracts
+- developer package reuse
+
+Useful follow-up pages:
+
+- [Privacy-First Markdown Editor](/features/privacy-first-markdown-editor)
+- [Local-First Markdown Workspace](/features/local-first-markdown-workspace)
+- [Markdown Preview Editor](/features/markdown-preview-editor)
+
+MdWrk is best evaluated as a local-first Markdown workspace and package platform. Obsidian is widely used for personal knowledge management and graph-oriented note collections.

package/data/markdown/docs/comparisons/mdwrk-vs-standard-markdown-editors.md

@@ -0,0 +1,49 @@
+---
+title: MdWrk Vs Standard Markdown Editors
+slug: comparisons/mdwrk-vs-standard-markdown-editors
+section: Compares
+sectionOrder: 6
+order: 8
+toc: true
+date: 2026-05-03
+status: published
+author: CobyCloud
+displayAuthor: false
+excerpt: Compare MdWrk with standard Markdown editors when you need more than a single-file writing surface: workspace management, preview policy, extensions, themes, and reusable packages.
+relatedApis: @mdwrk/mdwrkspace, @mdwrk/markdown-editor-react, @mdwrk/extension-host
+---
+
+## Best Fit
+
+Choose MdWrk when you need a broader workspace: projects, file organization, preview navigation, profile-aware rendering, HTML export, theme packs, extensions, and package-level reuse.
+
+Choose a standard Markdown editor when single-file drafting is enough and you do not need a governed extension host or reusable package architecture.
+
+## Product Difference
+
+MdWrk turns Markdown authoring into a product surface that can serve writers, documentation teams, package authors, extension authors, and local-first operators.
+
+## Related Docs
+
+- [Offline Markdown Editor](/features/offline-markdown-editor)
+- [Developer Documentation](/features/developer-documentation)
+
+## Quick Reference
+
+Use this article to understand MdWrk Vs Standard Markdown Editors in the MdWrk Comparisons surface. Compare MdWrk with standard Markdown editors when you need more than a single-file writing surface: workspace management, preview policy, extensions, themes, and reusable packages.
+
+Key concepts covered here:
+
+- local Markdown files
+- live preview
+- workspace organization
+- extension host contracts
+- theme portability
+
+Useful follow-up pages:
+
+- [Offline Markdown Editor](/features/offline-markdown-editor)
+- [Local-First Markdown Workspace](/features/local-first-markdown-workspace)
+- [Markdown Preview Editor](/features/markdown-preview-editor)
+
+Standard Markdown editors usually focus on opening a file, editing text, and showing a preview.

package/data/markdown/docs/comparisons/mdwrk-vs-typora.md

@@ -0,0 +1,49 @@
+---
+title: MdWrk Vs Typora
+slug: comparisons/mdwrk-vs-typora
+section: Compares
+sectionOrder: 6
+order: 2
+toc: true
+date: 2026-05-03
+status: published
+author: CobyCloud
+displayAuthor: false
+excerpt: Compare MdWrk and Typora across Markdown authoring surfaces, workspace-oriented preview/editor flows, and minimal single-document writing apps.
+relatedApis: @mdwrk/markdown-editor-react, @mdwrk/markdown-renderer-react
+---
+
+## MdWrk Fit
+
+Choose MdWrk when you need a workspace with projects, panes, live preview, package reuse, extension host behavior, and browser/PWA delivery.
+
+Typora is commonly associated with minimal single-document writing and inline rendered editing. Use that comparison point to clarify when MdWrk's workspace, preview, package, and extension architecture is the better product fit.
+
+## Product Difference
+
+MdWrk keeps source editing and preview explicit, which is useful when the exact Markdown file, rendered output, and export behavior need to stay visible.
+
+## Related Docs
+
+- [Markdown Preview Editor](/features/markdown-preview-editor)
+- [Editor Basics](/features/editor-basics)
+
+## Quick Reference
+
+Use this article to understand MdWrk Vs Typora in the MdWrk Comparisons surface. Compare MdWrk and Typora across Markdown authoring surfaces, workspace-oriented preview/editor flows, and minimal single-document writing apps.
+
+Key concepts covered here:
+
+- live preview
+- workspace organization
+- extension host contracts
+- developer package reuse
+- @mdwrk/markdown-editor-react
+
+Useful follow-up pages:
+
+- [Local-First Markdown Workspace](/features/local-first-markdown-workspace)
+- [Markdown Preview Editor](/features/markdown-preview-editor)
+- [Editor Basics](/features/editor-basics)
+
+MdWrk and Typora both serve Markdown authors, but they optimize for different operating shapes.

package/data/markdown/docs/comparisons/mdwrk-vs-vs-code.md

@@ -0,0 +1,49 @@
+---
+title: MdWrk Vs VS Code
+slug: comparisons/mdwrk-vs-vs-code
+section: Compares
+sectionOrder: 6
+order: 3
+toc: true
+date: 2026-05-03
+status: published
+author: CobyCloud
+displayAuthor: false
+excerpt: Compare MdWrk and VS Code when you need Markdown editing in either a purpose-built writing workspace or a general developer IDE.
+relatedApis: @mdwrk/mdwrkspace, @mdwrk/extension-host, @mdwrk/markdown-renderer-react
+---
+
+## Best Fit
+
+Choose MdWrk when the primary job is writing, previewing, managing, and exporting Markdown in a focused local-first workspace.
+
+Choose VS Code when Markdown sits beside code editing, terminal work, language tooling, debugging, and broad IDE extension workflows.
+
+## Product Difference
+
+MdWrk makes document workspace behavior, preview policy, theme packs, and Markdown package reuse the center of the product instead of one capability inside a larger IDE.
+
+## Related Docs
+
+- [Developer Documentation](/features/developer-documentation)
+- [Markdown File Manager](/features/markdown-file-manager)
+
+## Quick Reference
+
+Use this article to understand MdWrk Vs VS Code in the MdWrk Comparisons surface. Compare MdWrk and VS Code when you need Markdown editing in either a purpose-built writing workspace or a general developer IDE.
+
+Key concepts covered here:
+
+- local Markdown files
+- live preview
+- workspace organization
+- extension host contracts
+- theme portability
+
+Useful follow-up pages:
+
+- [Local-First Markdown Workspace](/features/local-first-markdown-workspace)
+- [Markdown Preview Editor](/features/markdown-preview-editor)
+- [Extension Platform](/docs/extensions/extension-platform)
+
+MdWrk is a Markdown workspace. VS Code is a general-purpose developer IDE with Markdown support.

package/data/markdown/docs/comparisons/mdwrk-vs-zettlr.md

@@ -0,0 +1,49 @@
+---
+title: MdWrk Vs Zettlr
+slug: comparisons/mdwrk-vs-zettlr
+section: Compares
+sectionOrder: 6
+order: 5
+toc: true
+date: 2026-05-03
+status: published
+author: CobyCloud
+displayAuthor: false
+excerpt: Compare MdWrk and Zettlr when choosing between a local-first Markdown workspace and a research-oriented Markdown writing environment.
+relatedApis: @mdwrk/mdwrkspace, @mdwrk/markdown-renderer-core
+---
+
+## Best Fit
+
+Choose MdWrk when you need a local-first workspace with explicit preview/export behavior and reusable package surfaces.
+
+Choose Zettlr when citation-heavy research writing and academic organization are the primary concern.
+
+## Product Difference
+
+MdWrk keeps optional Markdown profile behavior visible through the renderer and workspace settings so authors can decide which syntax belongs in a document.
+
+## Related Docs
+
+- [Advanced Markdown Formatting](/features/advanced-formatting)
+- [Privacy-First Markdown Editor](/features/privacy-first-markdown-editor)
+
+## Quick Reference
+
+Use this article to understand MdWrk Vs Zettlr in the MdWrk Comparisons surface. Compare MdWrk and Zettlr when choosing between a local-first Markdown workspace and a research-oriented Markdown writing environment.
+
+Key concepts covered here:
+
+- local Markdown files
+- live preview
+- workspace organization
+- privacy-first storage
+- extension host contracts
+
+Useful follow-up pages:
+
+- [Privacy-First Markdown Editor](/features/privacy-first-markdown-editor)
+- [Local-First Markdown Workspace](/features/local-first-markdown-workspace)
+- [Markdown Preview Editor](/features/markdown-preview-editor)
+
+MdWrk focuses on Markdown workspace, preview, packages, and extension host behavior. Zettlr is commonly used for research writing, citation-heavy notes, and academic workflows.

package/data/markdown/docs/extensions/extension-platform.md

@@ -0,0 +1,64 @@
+---
+title: Extension Platform
+slug: extensions/extension-platform
+section: Extensions
+sectionOrder: 4
+order: 1
+toc: true
+date: 2026-01-22
+status: published
+author: CobyCloud
+excerpt: MdWrk extensions are governed through manifest metadata, host APIs, runtime activation, manager UX, settings, permissions, and compatibility checks.
+---
+
+## Runtime shape
+
+The extension stack is split into governed surfaces:
+
+- `@mdwrk/extension-manifest` for declarative metadata
+- `@mdwrk/extension-host` for host-safe APIs
+- `@mdwrk/extension-runtime` for activation, registration, and lifecycle
+- `@mdwrk/extension-manager` for installed and bundled extension UX
+
+## Host responsibilities
+
+The client owns:
+
+- capability gating
+- trust policy enforcement
+- settings registration
+- command, view, and action-rail registration
+- theme, i18n, and diagnostics adapters
+
+## Bundled first-party extensions
+
+Current first-party extension surfaces documented in this repo include:
+
+- Theme Studio
+- Gemini Agent
+- Extension Manager
+- Language pack tooling
+
+## External installables
+
+External extensions do not run through ad hoc `npm install` inside the browser. They ship as signed installable artifacts with manifest, integrity, and compatibility declarations.
+
+## Quick Reference
+
+Use this article to understand Extension Platform in the MdWrk Extensions surface. Extension Platform explains how the MdWrk client hosts governed extension packages, runtime lifecycle, capability checks, and operator-facing extension management.
+
+Key concepts covered here:
+
+- extension host contracts
+- developer package reuse
+- `@mdwrk/extension-manifest`
+- `@mdwrk/extension-host`
+- `@mdwrk/extension-runtime`
+
+Useful follow-up pages:
+
+- [Extension Authoring](/docs/authoring/extensions)
+- [MdWrk Extension Host](/features/extension-host)
+- [Theme Studio And Host Surfaces](/docs/extensions/theme-studio-and-host-surfaces)
+
+The MdWrk client is the extension host. The lander only documents that host surface.

package/data/markdown/docs/extensions/theme-studio-and-host-surfaces.md

@@ -0,0 +1,54 @@
+---
+title: Theme Studio and Host Surfaces
+slug: extensions/theme-studio-and-host-surfaces
+section: Extensions
+sectionOrder: 4
+order: 2
+toc: true
+date: 2026-02-05
+status: published
+author: CobyCloud
+excerpt: Theme Studio demonstrates how first-party extensions use host surfaces, theme contracts, workspace panes, and export flows inside the MdWrk extension model.
+---
+
+## Theme Studio
+
+Theme Studio is the first-party extension surface for:
+
+- inspecting formal theme tokens
+- previewing token changes against editor and preview bridges
+- applying and reverting draft theme changes
+- exporting theme artifacts for host, renderer, or editor targets
+
+## Shared contract
+
+Theme compatibility is governed through `@mdwrk/theme-contract`. That contract allows:
+
+- client built-in themes
+- extension-authored themes
+- renderer and editor bridge variables
+- exportable CSS and preset payloads
+
+## Why this matters
+
+The lander now uses the same editor and renderer package family with lander light and dark themes, instead of documenting itself as if it were the main product.
+
+## Quick Reference
+
+Use this article to understand Theme Studio And Host Surfaces in the MdWrk Extensions surface. Theme Studio connects theme authoring, shared token contracts, editor previews, renderer previews, and extension-host delivery.
+
+Key concepts covered here:
+
+- theme portability
+- extension host contracts
+- live preview
+- `@mdwrk/theme-contract`
+- `@mdwrk/extension-theme-studio`
+
+Useful follow-up pages:
+
+- [Theme Packs](/features/theme-packs)
+- [Theme Pack Authoring](/docs/authoring/theme-packs)
+- [Extension Platform](/docs/extensions/extension-platform)
+
+The theme story is shared across the client, editor, renderer, and extension host.

package/data/markdown/docs/getting-started/browser-use.md

@@ -0,0 +1,59 @@
+---
+title: Browser Use
+slug: getting-started/browser-use
+section: Getting Started
+sectionOrder: 1
+order: 2
+toc: true
+date: 2026-05-02
+status: published
+author: CobyCloud
+excerpt: The browser path runs the MdWrk client directly in a supported browser, keeps documents local by default, and remains usable offline after app assets are cached.
+---
+
+## What it is
+
+The browser path runs the MdWrk client directly in a supported browser. Documents stay local by default, and the workspace remains usable even when you are offline after the app assets have already been cached.
+
+## How to start
+
+1. Open the MdWrk site.
+2. Launch the workspace from the primary app action.
+3. Start writing, previewing, and organizing documents in the browser.
+
+## Best fit
+
+- quick access
+- personal writing on one machine
+- environments where you cannot install local software
+- trying editor and renderer behavior before adopting packages
+
+## Storage model
+
+Browser use keeps workspace data in browser-managed local storage. That is convenient, but it also means your normal backup and export habits still matter.
+
+## When to choose another path
+
+Choose the PWA route when you want a more app-like shell.
+Choose the local setup route when you need a repo checkout, a controlled local build, or self-managed hosting.
+Choose standalone modules when you want the reusable package surfaces inside another application.
+
+## Quick Reference
+
+Use this article to understand Browser Use in the MdWrk Getting Started surface. Browser Use explains how this MdWrk surface works in the current client and package system.
+
+Key concepts covered here:
+
+- local Markdown files
+- live preview
+- workspace organization
+- privacy-first storage
+- extension host contracts
+
+Useful follow-up pages:
+
+- [Offline Markdown Editor](/features/offline-markdown-editor)
+- [Local-First Markdown Workspace](/features/local-first-markdown-workspace)
+- [Markdown Preview Editor](/features/markdown-preview-editor)
+
+Use the browser workflow when you want the fastest path into the workspace without installing a package or a desktop shell.