@mdwrk/mdwrkcom-content-pack 0.1.5

package/data/markdown/blog/pwa-install-and-zoom-controls.md

@@ -0,0 +1,64 @@
+---
+title: PWA Install, Zoom Controls, and Preview Refinements Make MdWrk Ready for Daily Use
+date: 2026-01-22
+status: published
+author: CobyCloud
+excerpt: MdWrk gains PWA install support, zoom controls, preview refinements, and deployment rails that turn the workspace into a stronger everyday writing environment.
+---
+
+## What users gain
+
+- installable browser app behavior
+- clearer zoom scaling for long writing sessions
+- stronger markdown table rendering in preview
+- a more polished route from local development to hosted delivery
+
+## Install path
+
+Readers who want the current install flow can start here:
+
+- [PWA installation](/docs/getting-started/pwa-installation)
+- [Installation overview](/docs/getting-started/installation)
+
+## Screenshot
+
+![MdWrk theme selector and install-ready shell behavior](/blog/media/theme-selector-modal.jpg)
+
+## Example deployment-oriented workflow
+
+```bash
+npm install --ignore-scripts
+npm run build -w apps/client
+```
+
+That build flow feeds the installable client surface and supports teams that want a browser-first markdown experience with a product-grade feel.
+
+## Repo history for deeper review
+
+- [January 22 repository history](https://github.com/groupsum/markdown_workspace/commits/master/?since=2026-01-22T00:00:00Z&until=2026-01-23T00:00:00Z)
+
+This date matters because it shows how MdWrk serves writers, operators, and deployers in one cohesive flow.
+
+## Article Guide
+
+2026-01-22 marks this MdWrk product story: MdWrk gains PWA install support, zoom controls, preview refinements, and deployment rails that turn the workspace into a stronger everyday writing environment.
+
+This article is useful for readers tracking:
+
+- how MdWrk changes affect daily Markdown writing
+- which client, package, or extension surface the change touches
+- where to continue in the product documentation after reading
+
+Useful follow-up pages:
+
+- [Local-First Markdown Workspace](/features/local-first-markdown-workspace)
+- [Markdown Preview Editor](/features/markdown-preview-editor)
+- [Theme Packs](/features/theme-packs)
+
+January 22, 2026 moves MdWrk from an exciting workspace demo into an installable daily tool.
+
+The repo history for that step includes:
+
+- [Add PWA service worker and install controls](https://github.com/groupsum/markdown_workspace/commit/343925d0)
+- [Fix zoom scaling for UI text and icons](https://github.com/groupsum/markdown_workspace/commit/b5486fcd)
+- [implement deploy](https://github.com/groupsum/markdown_workspace/commit/2ea7e01b)

package/data/markdown/blog/responsive-authoring-and-export.md

@@ -0,0 +1,64 @@
+---
+title: Responsive Authoring, Keyboard Speed, and HTML Export Expand MdWrk in a Single Day
+date: 2026-01-21
+status: published
+author: CobyCloud
+excerpt: MdWrk expands quickly with responsive layout tuning, keyboard navigation, export actions, print flows, and richer markdown rendering, giving teams more range across screens and daily writing tasks.
+---
+
+## What changes for users
+
+Writers gain:
+
+- faster command access through keyboard flows
+- export coverage for HTML handoff
+- responsive layouts that scale across device sizes
+- richer markdown support for tables, syntax color, and project creation flows
+
+## Usage example
+
+```bash
+npm install --ignore-scripts
+npm run dev:client
+```
+
+Once the client is running, teams can open a draft, write in source mode, preview the output, and publish HTML for downstream sharing.
+
+## Screenshot
+
+![MdWrk editor surface showing a focused authoring workspace](/blog/media/mdwrk-workspace-editor.png)
+
+## Why this day matters in the product story
+
+January 21 gives MdWrk a practical answer to common product questions:
+
+- Can a writer move quickly with keyboard-first flows?
+- Can a team present markdown across multiple screens?
+- Can authored content leave the workspace as a web-friendly deliverable?
+
+Each answer turns into shipped functionality on the same date, which makes this one of the strongest velocity moments in the early repo history.
+
+## Article Guide
+
+2026-01-21 marks this MdWrk product story: MdWrk expands quickly with responsive layout tuning, keyboard navigation, export actions, print flows, and richer markdown rendering, giving teams more range across screens and daily writing tasks.
+
+This article is useful for readers tracking:
+
+- how MdWrk changes affect daily Markdown writing
+- which client, package, or extension surface the change touches
+- where to continue in the product documentation after reading
+
+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)
+
+January 21, 2026 packs a full set of user-facing wins into the repository history.
+
+Key commits from that date include:
+
+- [Add keyboard navigation and shortcuts](https://github.com/groupsum/markdown_workspace/commit/42c655cf)
+- [Add HTML export action for markdown](https://github.com/groupsum/markdown_workspace/commit/168f2f8a)
+- [Add responsive layout tuning across breakpoints](https://github.com/groupsum/markdown_workspace/commit/005396c6)
+- [Add print preview shortcut and UI](https://github.com/groupsum/markdown_workspace/commit/65dbcc5b)

package/data/markdown/blog/retained-client-versions-and-desktop-shell.md

@@ -0,0 +1,59 @@
+---
+title: Retained Client Versions and the Desktop Shell Expand How Teams Can Deploy MdWrk
+date: 2026-04-12
+status: published
+author: CobyCloud
+excerpt: MdWrk introduces retained client version delivery and a desktop shell track, giving teams more control over rollout pacing, install shape, and long-lived workspace adoption.
+---
+
+## What this means for teams
+
+Teams can now plan around:
+
+- browser delivery with retained client versions
+- installable desktop packaging
+- stronger release identity through versioned build outputs
+
+## Usage references
+
+- [Installation](/docs/getting-started/installation)
+- [Local setup](/docs/getting-started/local-setup)
+
+## Build example
+
+```bash
+npm run build:client
+npm run build:desktop
+```
+
+## Screenshot
+
+![MdWrk home surface that introduces the packaged client experience](/blog/media/lander-home-light.png)
+
+## Why this milestone matters
+
+Deployment flexibility matters for teams that want browser-first use, desktop packaging, or self-managed hosting. April 12 shows MdWrk growing into a platform that can support all three with one codebase.
+
+## Article Guide
+
+2026-04-12 marks this MdWrk product story: MdWrk introduces retained client version delivery and a desktop shell track, giving teams more control over rollout pacing, install shape, and long-lived workspace adoption.
+
+This article is useful for readers tracking:
+
+- how MdWrk changes affect daily Markdown writing
+- which client, package, or extension surface the change touches
+- where to continue in the product documentation after reading
+
+Useful follow-up pages:
+
+- [Local-First Markdown Workspace](/features/local-first-markdown-workspace)
+- [GitHub Sync](/docs/github-sync)
+- [PWA Installation](/docs/getting-started/pwa-installation)
+
+April 12, 2026 broadens MdWrk's delivery model.
+
+The timeline anchor includes:
+
+- [Implement retained client version delivery and PWA switching](https://github.com/groupsum/markdown_workspace/commit/5942849c)
+- [feat: +desktop](https://github.com/groupsum/markdown_workspace/commit/cba6ac9c)
+- [Bump all package versions and hash app build IDs](https://github.com/groupsum/markdown_workspace/commit/c13aba8c)

package/data/markdown/blog/screenshot-matrix-and-browser-sidebars.md

@@ -0,0 +1,57 @@
+---
+title: Screenshot Matrix Coverage Helps MdWrk Prove Themes Across Viewports and Workflows
+date: 2026-04-03
+status: published
+author: CobyCloud
+excerpt: MdWrk expands browser sidebars and screenshot-matrix automation, giving the project stronger visual verification for themes, panes, settings, and extension workflows across the viewport contract.
+---
+
+## What this adds
+
+- viewport-aware screenshot capture
+- richer pane coverage for studio workflows
+- stronger visual proof for theme behavior across the contract
+
+## Command example
+
+```bash
+npm run screenshots:all-aspect-ratios
+```
+
+## Screenshot
+
+![MdWrk theme studio surface inside the shared workspace](/blog/media/theme-studio-pane.jpg)
+
+## Why this matters
+
+Visual proof helps readers answer:
+
+- How does the workspace look in real use?
+- Which panes and tools are available?
+- How does theme work move through the client?
+
+MdWrk now supports those answers with concrete visual artifacts and a repeatable capture rail.
+
+## Article Guide
+
+2026-04-03 marks this MdWrk product story: MdWrk expands browser sidebars and screenshot-matrix automation, giving the project stronger visual verification for themes, panes, settings, and extension workflows across the viewport contract.
+
+This article is useful for readers tracking:
+
+- how MdWrk changes affect daily Markdown writing
+- which client, package, or extension surface the change touches
+- where to continue in the product documentation after reading
+
+Useful follow-up pages:
+
+- [Local-First Markdown Workspace](/features/local-first-markdown-workspace)
+- [Extension Platform](/docs/extensions/extension-platform)
+- [Theme Packs](/features/theme-packs)
+
+April 3, 2026 expands the visual verification surface for theme work, UI review, and cross-screen consistency.
+
+This moment is visible in:
+
+- [Add browser sidebars and screenshot matrix script](https://github.com/groupsum/markdown_workspace/commit/be6a8b6c)
+- [Embed studio browsers in the shared workspace sidebar](https://github.com/groupsum/markdown_workspace/commit/c90bc0e9)
+- [Refactor studio panes and persist language packs in IndexedDB](https://github.com/groupsum/markdown_workspace/commit/613cc751)

package/data/markdown/blog/settings-simplification-for-daily-flow.md

@@ -0,0 +1,54 @@
+---
+title: Settings Simplification Gives MdWrk a Faster Path from Installation to Daily Use
+date: 2026-05-01
+status: published
+author: CobyCloud
+excerpt: MdWrk refines its settings UX with cleaner labels and a calmer navigation model, helping users move from install to configuration with more momentum and less friction.
+---
+
+## What improves
+
+- settings labels become cleaner and faster to scan
+- the active workspace experience gains a calmer visual rhythm
+- configuration panels become easier to review in sequence
+
+## Screenshot
+
+![MdWrk settings visual panel with a simplified navigation experience](/blog/media/mdwrk-settings-visual.png)
+
+## Current docs for configuration and setup
+
+- [Installation](/docs/getting-started/installation)
+- [Configuration](/docs/getting-started/configuration)
+- [Local setup](/docs/getting-started/local-setup)
+
+## Example setup flow
+
+1. Install the client through the path that fits your team.
+2. Open settings and tune theme, language, and workspace preferences.
+3. Move into writing, extensions, or Git workflows with the same navigation language.
+
+MdWrk now carries a stronger onboarding story because the settings surface communicates action, structure, and next steps in a cleaner form.
+
+## Article Guide
+
+2026-05-01 marks this MdWrk product story: MdWrk refines its settings UX with cleaner labels and a calmer navigation model, helping users move from install to configuration with more momentum and less friction.
+
+This article is useful for readers tracking:
+
+- how MdWrk changes affect daily Markdown writing
+- which client, package, or extension surface the change touches
+- where to continue in the product documentation after reading
+
+Useful follow-up pages:
+
+- [Local-First Markdown Workspace](/features/local-first-markdown-workspace)
+- [Extension Platform](/docs/extensions/extension-platform)
+- [Theme Packs](/features/theme-packs)
+
+May 1, 2026 focuses on the path every product team cares about: the path from first run to confident daily use.
+
+This work is grounded in:
+
+- [Remove settings sidebar sublabels and bump client version](https://github.com/groupsum/markdown_workspace/commit/3ae204ec)
+- [Remove active theme chip from settings modal](https://github.com/groupsum/markdown_workspace/commit/2d6cf332)

package/data/markdown/blog/workspace-files-and-git-ops-packages.md

@@ -0,0 +1,53 @@
+---
+title: Workspace Files and Git Operations Packages Open a Larger Automation Surface for MdWrk
+date: 2026-04-22
+status: published
+author: CobyCloud
+excerpt: MdWrk expands its package platform with workspace-files and Git-operations modules, giving teams more room to automate file-aware and repository-aware workflows inside the client.
+---
+
+## What teams can do with this expansion
+
+- bring file navigation and repository work closer to the writing surface
+- package automation logic into extension flows
+- align client capabilities with a broader workspace model
+
+## Install example
+
+```bash
+npm install @mdwrk/extension-workspace-files @mdwrk/extension-git-ops
+```
+
+## Screenshot
+
+![MdWrk Git pane presented as part of the workspace flow](/blog/media/mdwrk-git-pane.png)
+
+## Where to go next
+
+- [Extension platform](/docs/extensions/extension-platform)
+- [Authoring overview](/docs/authoring/overview)
+- [April 22 repository history](https://github.com/groupsum/markdown_workspace/commits/master/?since=2026-04-22T00:00:00Z&until=2026-04-23T00:00:00Z)
+
+MdWrk now tells a larger story than writing alone. It also gives teams a package-ready route into repository-aware workspace operations.
+
+## Article Guide
+
+2026-04-22 marks this MdWrk product story: MdWrk expands its package platform with workspace-files and Git-operations modules, giving teams more room to automate file-aware and repository-aware workflows inside the client.
+
+This article is useful for readers tracking:
+
+- how MdWrk changes affect daily Markdown writing
+- which client, package, or extension surface the change touches
+- where to continue in the product documentation after reading
+
+Useful follow-up pages:
+
+- [Local-First Markdown Workspace](/features/local-first-markdown-workspace)
+- [Extension Platform](/docs/extensions/extension-platform)
+- [GitHub Sync](/docs/github-sync)
+
+April 22, 2026 expands MdWrk's practical automation surface.
+
+The key anchor is:
+
+- [Add workspace module packages for files and git ops](https://github.com/groupsum/markdown_workspace/commit/d4efae4c)

package/data/markdown/docs/authoring/authoring-overview.md

@@ -0,0 +1,59 @@
+---
+title: Authoring Overview
+slug: authoring/overview
+section: Authoring
+sectionOrder: 3.5
+order: 1
+toc: true
+date: 2026-05-02
+status: published
+author: CobyCloud
+excerpt: MdWrk authoring documentation groups extension, theme pack, and language pack workflows into focused surfaces for package and product contributors.
+---
+
+## Authoring domains
+
+The current public authoring domains documented on the lander are:
+
+- [Extension authoring](/docs/authoring/extensions)
+- [Theme pack authoring](/docs/authoring/theme-packs)
+- [Language pack authoring](/docs/authoring/language-packs)
+
+## Scope
+
+These docs are for package authors, extension maintainers, and internal builders who need to create reusable MdWrk surfaces.
+
+They are not the same as:
+
+- browser or PWA usage flows
+- local client operation
+- extension installation or runtime-only guidance
+
+## Ground rules
+
+Authoring in this repository follows a few durable rules:
+
+- reusable surfaces should live in publishable packages
+- browser hosts do not run raw `npm install` at runtime for external extensions
+- host/runtime trust, manifest, and compatibility declarations are part of the authoring contract
+- theme and language authoring must target the shared contracts rather than app-local shortcuts
+
+## Quick Reference
+
+Use this article to understand Authoring Overview in the MdWrk Authoring surface. Authoring Overview 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)
+- [Extension Platform](/docs/extensions/extension-platform)
+- [Theme Packs](/features/theme-packs)
+
+The authoring section explains how to produce MdWrk-facing artifacts rather than only how to consume them.

package/data/markdown/docs/authoring/extension-authoring-guide.md

@@ -0,0 +1,69 @@
+---
+title: Extension Authoring Guide
+slug: authoring/extension-authoring-guide
+section: Authoring
+sectionOrder: 3.5
+order: 3
+toc: true
+date: 2026-05-06
+status: published
+author: CobyCloud
+excerpt: The extension authoring guide gives package authors the current MdWrk workflow for manifests, host APIs, runtime activation, tests, bundles, and publishing artifacts.
+---
+
+## Authoring Model
+
+MdWrk extensions are normal workspace packages that declare a manifest, activate through the extension runtime, and use host APIs for commands, views, settings, diagnostics, themes, editor access, and workspace access.
+
+The core package surfaces are:
+
+- `@mdwrk/extension-manifest`
+- `@mdwrk/extension-host`
+- `@mdwrk/extension-runtime`
+- `@mdwrk/extension-manager`
+
+## Package Shape
+
+A first-party or installable extension package should include:
+
+- `package.json`
+- `README.md`
+- `src/manifest.ts`
+- `src/index.ts`
+- tests for manifest validity and runtime behavior
+- `src/version.ts` for package version exports
+
+Use `packages/extensions/extension-catalog-hello` as the smallest reference extension and `packages/extensions/extension-manager` as a fuller operator-facing surface.
+
+## Manifest Responsibilities
+
+The manifest declares identity, version, display metadata, activation mode, requested capabilities, compatibility ranges, contribution points, and settings schema. The runtime uses it before activation to evaluate compatibility and host capability access.
+
+## Runtime Responsibilities
+
+Extension code should register through the provided context:
+
+- commands through `context.registerCommand`
+- views through `context.registerView`
+- action rail items through `context.registerActionRailItem`
+- settings through manifest settings schema
+- diagnostics through host diagnostics APIs
+
+Extensions should clean up registered work with disposables returned by the runtime.
+
+## Publish Workflow
+
+```bash
+npm run build:extensions
+npm run extension:bundle
+npm run extension:sign
+npm run validate:extension-artifacts
+```
+
+The generated artifacts include installable payloads, integrity metadata, signed manifests, and catalog entries under `artifacts/extensions`.
+
+## Related Docs
+
+- [Extension Authoring](/docs/authoring/extensions)
+- [Extension Platform](/docs/extensions/extension-platform)
+- [Extension Host](/features/extension-host)

package/data/markdown/docs/authoring/extensions.md

@@ -0,0 +1,93 @@
+---
+title: Extension Authoring
+slug: authoring/extensions
+section: Authoring
+sectionOrder: 3.5
+order: 2
+toc: true
+date: 2026-05-02
+status: published
+author: CobyCloud
+excerpt: Extension authoring covers manifest shape, host APIs, activation lifecycle, package-local source, generated bundles, and trust metadata for MdWrk extensions.
+---
+
+## What an extension author owns
+
+The extension authoring surface in this repository is split across:
+
+- `@mdwrk/extension-manifest` for manifest shape and metadata
+- `@mdwrk/extension-host` for host-safe APIs
+- `@mdwrk/extension-runtime` for activation and lifecycle expectations
+- package-local source, tests, and build outputs inside an extension package
+
+## Typical workflow
+
+1. Create a normal npm package for the extension source.
+2. Export a valid MdWrk extension manifest and lifecycle entrypoint.
+3. Test the manifest, lifecycle, and runtime-facing behavior.
+4. Publish the source package for developer consumption when appropriate.
+5. Generate browser-installable artifacts through the formal distribution flow when targeting external installation.
+
+## Required package shape
+
+At minimum, an extension package should include:
+
+- `package.json`
+- `README.md`
+- `src/manifest.ts`
+- `src/index.ts`
+- tests for manifest, lifecycle, and runtime behavior
+
+## Runtime and distribution rules
+
+External extensions do not install through ad hoc `npm install` inside the browser.
+The browser host installs generated artifacts with manifest, integrity, compatibility, and signer metadata.
+
+That means an extension author should expect:
+
+- trust-policy enforcement
+- capability gating
+- compatibility declarations
+- signed/installable artifact generation for the external path
+
+## Reference package
+
+This repository already includes a reference external package:
+
+```text
+packages/extensions/extension-catalog-hello/
+```
+
+Use it as the concrete reference for:
+
+- manifest structure
+- distribution metadata
+- runtime install expectations
+- certification preparation
+
+## Related documents
+
+For the deeper operator workflow, see:
+
+```text
+docs/operations/third-party-extension-authoring.md
+docs/architecture/extension-package-layout.md
+```
+
+## Quick Reference
+
+Use this article to understand Extension Authoring in the MdWrk Authoring surface. Extension Authoring explains how this MdWrk surface works in the current client and package system.
+
+Key concepts covered here:
+
+- local Markdown files
+- extension host contracts
+- developer package reuse
+
+Useful follow-up pages:
+
+- [Local-First Markdown Workspace](/features/local-first-markdown-workspace)
+- [Extension Platform](/docs/extensions/extension-platform)
+- [Developer Documentation](/features/developer-documentation)
+
+Use this path when you want to author an MdWrk extension package rather than only install or operate one.

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

@@ -0,0 +1,81 @@
+---
+title: Language Pack Authoring
+slug: authoring/language-packs
+section: Authoring
+sectionOrder: 3.5
+order: 4
+toc: true
+date: 2026-05-02
+status: published
+author: CobyCloud
+excerpt: Language pack authoring uses the first-party studio package, locale catalogs, validation flows, export behavior, and host surfaces for MdWrk localization.
+---
+
+## Primary surface
+
+Language pack authoring in this repository centers on the first-party studio package:
+
+```text
+packages/extensions/extension-language-pack-studio/
+```
+
+That surface is responsible for browsing, editing, importing, exporting, and activating language packs.
+
+## Authoring expectations
+
+A language-pack author should expect to work with:
+
+- locale labels and message catalogs
+- import and export flows
+- built-in and installed pack visibility
+- activation and deactivation behavior through the host settings/runtime surfaces
+
+## What the studio proves
+
+Language Pack Studio demonstrates that language-pack management is not just a static bundle concern.
+It is a governed workspace surface with:
+
+- authoring UI
+- import validation
+- export behavior
+- persistence through the local host storage model
+
+## Artifact model
+
+Language packs should be portable artifacts that the host can inspect, import, and activate without requiring app-local rewrites.
+
+The authoring flow should preserve:
+
+- stable locale identity
+- portable message payloads
+- compatibility with the shared i18n surfaces
+
+## Reference surfaces
+
+Use these repo surfaces as the concrete reference:
+
+```text
+packages/extensions/extension-language-pack-studio/
+packages/shared/i18n/
+docs/conformance/extension-workspace-surfaces-claim.md
+```
+
+## Quick Reference
+
+Use this article to understand Language Pack Authoring in the MdWrk Authoring surface. Language Pack Authoring explains how this MdWrk surface works in the current client and package system.
+
+Key concepts covered here:
+
+- local Markdown files
+- workspace organization
+- privacy-first storage
+- extension host contracts
+- developer package reuse
+
+Useful follow-up pages:
+
+- [Local-First Markdown Workspace](/features/local-first-markdown-workspace)
+- [Extension Platform](/docs/extensions/extension-platform)
+- [Client Installation](/docs/getting-started/installation)
+
+Use this path when you want to author portable MdWrk language packs rather than only enable or disable built-in locales.