@mdwrk/mdwrkcom-content-pack 0.1.5

package/data/markdown/docs/product/markdown-file-manager.md

@@ -0,0 +1,52 @@
+---
+title: Markdown File Manager
+slug: product/markdown-file-manager
+section: Features
+sectionOrder: 2
+order: 13
+toc: true
+date: 2026-05-03
+status: published
+author: CobyCloud
+displayAuthor: false
+excerpt: MdWrk manages Markdown projects, files, folders, preview navigation, and workspace entries so documents stay organized inside the same surface where they are written.
+relatedApis: @mdwrk/mdwrkspace, @mdwrk/extension-workspace-files
+---
+
+## File Operations
+
+The client supports project and entry workflows such as creating files, organizing folders, renaming entries, deleting obsolete content, and moving between documents without leaving the workspace shell.
+
+## Preview Navigation
+
+Internal Markdown links can navigate between files and headings. That makes the file manager useful for documentation sets, linked notes, release notes, and package READMEs.
+
+## Desktop-Backed Workflows
+
+Where the desktop shell is available, host file acquisition and filesystem-backed behavior can sit beside browser-managed workspaces. The client keeps those paths explicit.
+
+## Related Docs
+
+- [Local-First Markdown Workspace](/features/local-first-markdown-workspace)
+- [Rendering And Preview](/features/rendering-and-preview)
+- [Local Setup](/docs/getting-started/local-setup)
+
+## Quick Reference
+
+Use this article to understand Markdown File Manager in the MdWrk Product surface. MdWrk manages Markdown projects, files, folders, preview navigation, and workspace entries so documents stay organized inside the same surface where they are written.
+
+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)
+- [Browser Use](/docs/getting-started/browser-use)
+
+MdWrk includes file-management behavior as part of the writing workspace.

package/data/markdown/docs/product/markdown-preview-editor.md

@@ -0,0 +1,52 @@
+---
+title: Markdown Preview Editor
+slug: product/markdown-preview-editor
+section: Features
+sectionOrder: 2
+order: 14
+toc: true
+date: 2026-05-03
+status: published
+author: CobyCloud
+displayAuthor: false
+excerpt: MdWrk combines a Markdown source editor with live preview, profile-aware rendering, internal-link navigation, HTML export, and print-oriented output.
+relatedApis: @mdwrk/markdown-editor-react, @mdwrk/markdown-renderer-react, @mdwrk/markdown-renderer-core
+---
+
+## Editor And Preview Modes
+
+Use editor-only mode for drafting, split mode for validating output while writing, and preview-only mode for reading, review, and export inspection.
+
+## Rendering Contract
+
+The preview uses the same renderer family that powers reusable package surfaces. CommonMark, GFM, profile-aware optional syntax, advisory policy, and export behavior stay aligned.
+
+## Output Paths
+
+HTML export and print preview are connected to the preview pipeline so approved on-screen structure stays close to exported output.
+
+## Related Docs
+
+- [Editor Basics](/features/editor-basics)
+- [Rendering And Preview](/features/rendering-and-preview)
+- [Advanced Markdown Formatting](/features/advanced-formatting)
+
+## Quick Reference
+
+Use this article to understand Markdown Preview Editor in the MdWrk Product surface. MdWrk combines a Markdown source editor with live preview, profile-aware rendering, internal-link navigation, HTML export, and print-oriented output.
+
+Key concepts covered here:
+
+- live preview
+- developer package reuse
+- @mdwrk/markdown-editor-react
+- @mdwrk/markdown-renderer-react
+- @mdwrk/markdown-renderer-core
+
+Useful follow-up pages:
+
+- [Markdown Preview Editor](/features/markdown-preview-editor)
+- [Editor Basics](/features/editor-basics)
+- [Advanced Markdown Formatting](/features/advanced-formatting)
+
+MdWrk keeps source editing and rendered preview in the same workflow.

package/data/markdown/docs/product/markdown-profile-architecture.md

@@ -0,0 +1,51 @@
+---
+title: Markdown Profile Architecture
+slug: product/markdown-profile-architecture
+section: Features
+sectionOrder: 2
+order: 17
+toc: true
+date: 2026-05-06
+status: published
+author: CobyCloud
+displayAuthor: false
+excerpt: Markdown profile architecture describes how MdWrk separates CommonMark, GFM, custom profile options, renderer configuration, and evidence snapshots.
+---
+
+## Profile Purpose
+
+Markdown profiles let MdWrk describe which Markdown behaviors are active for editing, preview, export, and conformance evidence. The profile layer keeps rendering policy explicit instead of burying it inside ad hoc parser flags.
+
+## Current Surfaces
+
+The current profile implementation spans:
+
+- renderer core profile definitions
+- client profile settings
+- editor and preview configuration
+- generated conformance artifacts
+- SSOT feature, claim, test, and evidence links
+
+Client-facing profile configuration lives under `apps/client/src/features/markdownProfiles`. Renderer behavior lives under `packages/renderer/markdown-renderer-core`.
+
+## Profile Responsibilities
+
+A profile should declare:
+
+- enabled Markdown extensions
+- raw HTML policy
+- task-list behavior
+- underline and link policy
+- heading anchor behavior
+- renderer and preview expectations
+- evidence lane used to prove the profile
+
+## Evidence Lane
+
+Profile evidence should point at executable tests, generated snapshots, and conformance reports. This keeps profile claims auditable across package changes, app settings changes, and release gates.
+
+## Related Docs
+
+- [Rendering And Preview](/features/rendering-and-preview)
+- [Advanced Markdown Formatting](/features/advanced-formatting)
+- [Developer Documentation](/features/developer-documentation)

package/data/markdown/docs/product/offline-markdown-editor.md

@@ -0,0 +1,52 @@
+---
+title: Offline Markdown Editor
+slug: product/offline-markdown-editor
+section: Features
+sectionOrder: 2
+order: 10
+toc: true
+date: 2026-05-03
+status: published
+author: CobyCloud
+displayAuthor: false
+excerpt: MdWrk is an offline-capable Markdown editor that keeps writing, preview, workspace state, and installable app behavior available on the device after the client assets are loaded.
+relatedApis: @mdwrk/mdwrkspace, @mdwrk/markdown-editor-react, @mdwrk/markdown-renderer-react
+---
+
+## Offline Editing Model
+
+The workspace stores documents in browser-managed local storage and IndexedDB-backed client state. The PWA install path can keep the client available in a dedicated app window while the editor keeps source text and preview close together.
+
+## Writing Workflow
+
+Use the editor-only view for focused drafting, split view for live validation, and preview-only mode for review. Formatting commands write portable Markdown instead of proprietary document state.
+
+## Local Storage Boundary
+
+MdWrk does not require documents to be uploaded to a hosted service before editing. Sync and export are intentional workflows, not hidden defaults.
+
+## Related Docs
+
+- [Browser Use](/docs/getting-started/browser-use)
+- [PWA Installation](/docs/getting-started/pwa-installation)
+- [Editor Basics](/features/editor-basics)
+
+## Quick Reference
+
+Use this article to understand Offline Markdown Editor in the MdWrk Product surface. MdWrk is an offline-capable Markdown editor that keeps writing, preview, workspace state, and installable app behavior available on the device after the client assets are loaded.
+
+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)
+
+MdWrk gives Markdown authors a browser-first editor that continues to work when the network is unavailable.

package/data/markdown/docs/product/privacy-first-markdown-editor.md

@@ -0,0 +1,52 @@
+---
+title: Privacy-First Markdown Editor
+slug: product/privacy-first-markdown-editor
+section: Features
+sectionOrder: 2
+order: 12
+toc: true
+date: 2026-05-03
+status: published
+author: CobyCloud
+displayAuthor: false
+excerpt: MdWrk is a privacy-first Markdown editor that keeps documents on the device by default and makes sync, export, extension trust, and external services explicit choices.
+relatedApis: @mdwrk/mdwrkspace, @mdwrk/extension-host, @mdwrk/extension-manifest
+---
+
+## Privacy Boundary
+
+The default workspace keeps document content in local browser storage. The product does not need to upload Markdown to MdWrk servers before you can write, preview, or manage files.
+
+## Explicit Sharing
+
+Export, GitHub sync, and extension-based workflows are intentional paths. They make the boundary visible so authors can decide when content leaves the local workspace.
+
+## Extension Trust
+
+Installable extensions use manifests, integrity metadata, compatibility rules, and trust policy inputs. That gives extension behavior a documented control surface instead of treating every package as automatically trusted.
+
+## Related Docs
+
+- [Extension Platform](/docs/extensions/extension-platform)
+- [Client Configuration](/docs/getting-started/configuration)
+- [Privacy Policy](/legal/privacy)
+
+## Quick Reference
+
+Use this article to understand Privacy-First Markdown Editor in the MdWrk Product surface. MdWrk is a privacy-first Markdown editor that keeps documents on the device by default and makes sync, export, extension trust, and external services explicit choices.
+
+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 is designed so writing does not require a hosted document account.

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

@@ -0,0 +1,52 @@
+---
+title: Theme Packs
+slug: product/theme-packs
+section: Features
+sectionOrder: 2
+order: 16
+toc: true
+date: 2026-05-03
+status: published
+author: CobyCloud
+displayAuthor: false
+excerpt: MdWrk theme packs use a shared token and class-name contract so editor, renderer, extension, and workspace surfaces can be styled without private app selectors.
+relatedApis: @mdwrk/theme-contract, @mdwrk/extension-theme-studio, @mdwrk/ui-tokens
+---
+
+## Theme Contract
+
+Theme packs target shared tokens, bridge variables, and class names. This keeps theme behavior portable across the editor, renderer, host, and extension views.
+
+## Theme Studio
+
+The Theme Studio extension provides a first-party authoring workflow for inspecting tokens, previewing editor and renderer changes, applying draft values, reverting them, and exporting theme artifacts.
+
+## Viewport Contract
+
+Viewport and aspect-ratio breakpoints stay defined once in the client viewport contract. Themes can style each band, but they do not redefine the responsive taxonomy.
+
+## Related Docs
+
+- [Theme Pack Authoring](/docs/authoring/theme-packs)
+- [Theme Studio And Host Surfaces](/docs/extensions/theme-studio-and-host-surfaces)
+- [Client Configuration](/docs/getting-started/configuration)
+
+## Quick Reference
+
+Use this article to understand Theme Packs in the MdWrk Product surface. MdWrk theme packs use a shared token and class-name contract so editor, renderer, extension, and workspace surfaces can be styled without private app selectors.
+
+Key concepts covered here:
+
+- live preview
+- workspace organization
+- extension host contracts
+- theme portability
+- @mdwrk/theme-contract
+
+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 treats themes as portable product surfaces.

package/data/markdown/docs/product/uix-responsive-contract.md

@@ -0,0 +1,51 @@
+---
+title: UIX Responsive Contract
+slug: product/uix-responsive-contract
+section: Features
+sectionOrder: 2
+order: 18
+toc: true
+date: 2026-05-06
+status: published
+author: CobyCloud
+displayAuthor: false
+excerpt: The UIX responsive contract documents MdWrk viewport bands, aspect-ratio bands, height tiers, device classes, and theme responsibilities.
+---
+
+## Contract Summary
+
+MdWrk defines viewport and aspect-ratio bands once and lets themes style those bands without redefining the breakpoints. The contract keeps app structure predictable across phone, tablet, desktop, wide, and ultra-wide workspaces.
+
+The active contract is implemented in `apps/client/styles/base/viewports.css`.
+
+## Aspect Bands
+
+The workspace classifies layout by aspect ratio:
+
+- portrait
+- square-hybrid
+- landscape
+- wide
+- ultra-wide
+
+These bands guide shell density, pane stacking, sidebar behavior, and safe-area spacing.
+
+## Width And Height Tiers
+
+Width tiers are `xs`, `sm`, `md`, `lg`, `xl`, and `xxl`. Height tiers are `short`, `compact`, `tall`, and `ultra-tall`.
+
+Themes may respond to these tiers, but the tier names and cutoffs remain a base contract.
+
+## Device Class
+
+The contract distinguishes touch and precision devices. Touch layouts can enlarge hit targets and simplify pane density, while precision layouts can preserve denser controls for keyboard and pointer workflows.
+
+## Theme Responsibility
+
+Themes are responsible for unique styling per band. They should not copy breakpoint definitions into theme files. A theme can change color, spacing, surface treatment, and visual density while leaving the base viewport taxonomy intact.
+
+## Related Docs
+
+- [Editor Basics](/features/editor-basics)
+- [Desktop App Boundary](/features/desktop-app-boundary)
+- [Theme Packs](/features/theme-packs)

package/data/markdown/docs/usage/advanced-formatting.md

@@ -0,0 +1,181 @@
+---
+title: Markdown Formatting
+slug: usage/advanced-formatting
+section: Features
+sectionOrder: 2
+order: 2
+toc: true
+date: 2026-05-03
+status: published
+author: CobyCloud
+displayAuthor: false
+excerpt: MdWrk uses a CommonMark plus GFM baseline, exposes optional formatting profiles for footnotes, math, and related syntax, and adds opinionated editor tools for faster authoring without locking documents into a proprietary format.
+---
+
+## Baseline Conformance
+
+The repository default remains **CommonMark 0.31.2 + GFM 0.29-gfm**.
+
+That means MdWrk treats standard Markdown as the primary portable surface for:
+
+- headings
+- paragraphs
+- emphasis
+- strong emphasis
+- links
+- images
+- blockquotes
+- thematic breaks
+- inline code
+- fenced code blocks
+- ordered and unordered lists
+- GitHub-style task lists
+- GitHub-style tables
+- strikethrough
+
+```markdown
+# Product Overview
+
+MdWrk keeps drafting local by default.
+
+> Preview and source stay aligned.
+
+- local-first editing
+- portable Markdown output
+- optional sync later
+
+| Surface | Status |
+| :--- | :--- |
+| Editor | Ready |
+| Preview | Ready |
+
+- [x] Draft
+- [ ] Publish
+```
+
+## What the Renderer Guarantees
+
+The same renderer family powers the MdWrk preview surface and this lander, so the formatting contract is shared across documentation and the client.
+
+- Front matter is parsed into metadata and omitted from rendered body output.
+- Heading extraction is available for table-of-contents and navigation surfaces.
+- GFM task list items render as semantic checkbox rows.
+- GFM tables render as semantic table markup.
+- Fenced code blocks render into portable code block containers with a header/surface structure.
+- HTML export and full HTML document generation preserve the same Markdown render contract.
+
+## Optional Markdown Profiles
+
+MdWrk keeps the CommonMark plus GFM baseline on by default. Optional profiles can be enabled from the Markdown profile settings when a document needs more expressive syntax.
+
+### In-Scope Profiles
+
+- `front-matter`: YAML-style metadata blocks are parsed into document metadata and removed from rendered body content.
+- `footnotes`: Footnote references and definitions render into linked footnote sections.
+- `definition-lists`: Definition list syntax renders into `dl`, `dt`, and `dd` structures.
+- `math`: Inline and block math are structurally recognized. This checkpoint does not typeset equations with KaTeX or MathJax.
+- `superscript`: Caret-based superscript syntax is supported when the profile is enabled.
+- `subscript`: Tilde-based subscript syntax is supported when the profile is enabled.
+- `smart-punctuation`: Smart punctuation transforms are available when explicitly enabled.
+
+### Experimental or Out-of-Boundary Profiles
+
+- `citations`: Citation keys are recognized structurally, but bibliography resolution is still outside the certified formatting boundary.
+- `markdown-in-html`: Markdown inside trusted HTML containers is available only when that profile is enabled and trusted HTML preview/export is also enabled.
+
+## Trusted HTML Rule
+
+Trusted HTML is off by default.
+
+Use it only for content you trust. It exists so HTML-aware profiles such as `markdown-in-html` can pass through preview and export intentionally instead of silently broadening the parsing surface for every document.
+
+## Opinionated MdWrk Authoring Extras
+
+MdWrk adds editor conveniences on top of portable Markdown. These tools write Markdown for you, but the saved document remains plain text.
+
+### Toolbar Actions
+
+The editor toolbar currently exposes direct authoring controls for:
+
+- bold
+- italic
+- strikethrough
+- bullet lists
+- task lists
+- indent
+- outdent
+- inline math
+- footnotes
+- superscript
+- subscript
+- undo
+- redo
+- insert table
+
+The toolbar also includes editor, split, and preview view controls so formatting and rendered output stay close together while you write.
+
+### Keyboard and Editing Behavior
+
+MdWrk includes opinionated editing behaviors that speed up list-heavy writing:
+
+- `Ctrl/Cmd+B` wraps the current selection in `**bold**`
+- `Ctrl/Cmd+I` wraps the current selection in `_italic_`
+- `Ctrl/Cmd+Shift+X` wraps the current selection in `~~strikethrough~~`
+- `Ctrl/Cmd+Z` and `Ctrl/Cmd+Shift+Z` drive undo and redo
+- `Tab` indents the current line or selection
+- `Shift+Tab` outdents the current line or selection
+- `Enter` inside a list item continues the list automatically
+- `Enter` on an empty bullet, ordered, or task-list item terminates that list item cleanly
+
+### Table Builder
+
+MdWrk includes an opinionated table insertion control in the editor toolbar. It helps generate table scaffolding quickly instead of requiring you to hand-type the initial pipe layout.
+
+After insertion, the table remains ordinary Markdown:
+
+```markdown
+| Column A | Column B |
+| :--- | :--- |
+| Value | Value |
+```
+
+### Structured Inserts
+
+Some current toolbar actions intentionally scaffold a known Markdown pattern instead of leaving the exact syntax to memory:
+
+- footnote insertion adds a `[^1]` style reference marker
+- inline math wraps the selection in `$...$`
+- superscript wraps the selection in `^...^`
+- subscript wraps the selection in `~...~`
+
+These are authoring conveniences, not a separate file format.
+
+## Practical Portability Guidance
+
+Use the default CommonMark plus GFM surface when the same file needs to render well in MdWrk, GitHub, npm documentation, and other static Markdown tooling.
+
+Enable optional profiles only when the document actually needs them. This keeps the source more portable and reduces surprises when the file moves into another renderer.
+
+## Related Docs
+
+- [Editor Basics](/features/editor-basics)
+- [Rendering And Preview](/features/rendering-and-preview)
+- [Client Configuration](/docs/getting-started/configuration)
+
+## Quick Reference
+
+Use this article to understand Markdown Formatting in the MdWrk Product surface. MdWrk uses a CommonMark plus GFM baseline, exposes optional formatting profiles for footnotes, math, and related syntax, and adds opinionated editor tools for faster authoring without locking documents into a proprietary format.
+
+Key concepts covered here:
+
+- local Markdown files
+- live preview
+- theme portability
+
+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 page when you want the exact Markdown formatting contract that MdWrk previews, exports, and edits today.

package/data/markdown/docs/usage/checkbox-autocomplete.md

@@ -0,0 +1,51 @@
+---
+title: Checkbox Autocomplete
+slug: usage/checkbox-autocomplete
+section: Features
+sectionOrder: 2
+order: 6
+toc: true
+date: 2026-05-06
+status: published
+author: CobyCloud
+displayAuthor: false
+excerpt: Checkbox autocomplete documents how MdWrk turns list authoring into task-list Markdown while preserving plain-text portability.
+---
+
+## What Checkbox Autocomplete Is For
+
+Checkbox autocomplete helps writers create task lists without memorizing every Markdown marker. MdWrk keeps the source document portable by writing normal task-list syntax such as `- [ ] Task` and `- [x] Done`.
+
+Use this page when you want the current checklist behavior for notes, issue plans, release checklists, and documentation tasks.
+
+## Supported Markdown Shape
+
+MdWrk treats these forms as task-list rows:
+
+```markdown
+- [ ] Draft the doc
+- [x] Review the change
+1. [ ] Verify the build
+```
+
+The editor command layer can convert a plain line, bullet line, or ordered-list line into a task-list item. The renderer then displays the checkbox state while keeping the original Markdown available for export, Git, and copy/paste.
+
+## Authoring Flow
+
+1. Put the cursor on a line or select multiple lines.
+2. Use the task-list toolbar action.
+3. Continue writing the task text.
+4. Press `Enter` to continue the checklist.
+5. Press `Enter` on an empty checklist row to leave the list.
+
+The behavior is implemented in the editor command and list-continuation pipeline, so toolbar and keyboard entry stay aligned.
+
+## Focus Behavior
+
+Checkbox rows remain part of the source editor document. Toggling or continuing a checklist should keep the writing flow in the editor instead of forcing the user to recover focus from the preview.
+
+## Related Docs
+
+- [Editor Basics](/features/editor-basics)
+- [Advanced Markdown Formatting](/features/advanced-formatting)
+- [View Toolbar](/features/view-toolbar/)