@mdwrk/mdwrkcom-content-pack 0.1.5

package/data/docs.ts

@@ -0,0 +1,111 @@
+import { parseMarkdown } from '../utils/markdownParser';
+import { isPublishedMetadata } from '../utils/publication';
+
+export interface DocEntry {
+  slug: string;
+  title: string;
+  section: string;
+  sectionOrder: number;
+  order: number;
+  content: string;
+  metadata: Record<string, string>;
+}
+
+const slugify = (value: string) =>
+  value
+    .toLowerCase()
+    .replace(/[^a-z0-9\s-/]/g, '')
+    .trim()
+    .replace(/\s+/g, '-');
+
+const toTitleCase = (value: string) =>
+  value
+    .replace(/\bmdwrk\b/gim, 'MdWrk')
+    .split(/\s+/)
+    .map((part) => {
+      if (!part) return part;
+      if (/^MdWrk$/.test(part)) return part;
+      if (/^[A-Z0-9.-]+$/.test(part)) return part;
+      return part.charAt(0).toUpperCase() + part.slice(1).toLowerCase();
+    })
+    .join(' ');
+
+const toCompareSlug = (slug: string) =>
+  `compare/${slug
+    .replace(/^comparisons\//, '')
+    .replace(/^mdwrk-vs-/, '')
+    .replace(/^mdwrk-vs/i, '')
+    .replace(/^vs-/, '')
+    .replace(/^vscode$/, 'vs-code')}`;
+
+const toFeatureSlug = (slug: string) =>
+  `features/${slug
+    .replace(/^product\//, '')
+    .replace(/^usage\//, '')}`;
+
+const rawDocs = import.meta.glob('./markdown/docs/**/*.md', {
+  eager: true,
+  query: '?raw',
+  import: 'default'
+});
+
+const docEntries = Object.entries(rawDocs).map(([path, raw]) => {
+  const { metadata, content } = parseMarkdown(raw as string);
+  const rawTitle = metadata.title || path.split('/').pop()?.replace('.md', '') || 'Document';
+  const title = toTitleCase(String(rawTitle));
+  const section = metadata.section || 'Docs';
+  const rawSlug = metadata.slug || slugify(title);
+  const isComparison = section === 'Compares' || String(rawSlug).startsWith('comparisons/');
+  const isFeature = section === 'Features';
+  const slug = isComparison ? toCompareSlug(String(rawSlug)) : isFeature ? toFeatureSlug(String(rawSlug)) : rawSlug;
+  const sectionOrder = Number(metadata.sectionOrder ?? 999);
+  const order = Number(metadata.order ?? 999);
+
+  return {
+    slug,
+    title,
+    section,
+    sectionOrder,
+    order,
+    content,
+    metadata
+  };
+}).filter((entry) => isPublishedMetadata(entry.metadata));
+
+export const compareDocs = docEntries
+  .filter((entry) => entry.section === 'Compares' || entry.slug.startsWith('compare/'))
+  .slice()
+  .sort((a, b) => a.sectionOrder - b.sectionOrder || a.order - b.order || a.title.localeCompare(b.title));
+
+export const compareDocsBySlug = compareDocs.reduce<Record<string, DocEntry>>((acc, doc) => {
+  acc[doc.slug.replace(/^compare\//, '')] = doc;
+  return acc;
+}, {});
+
+export const featureDocs = docEntries
+  .filter((entry) => entry.section === 'Features' || entry.slug.startsWith('features/'))
+  .slice()
+  .sort((a, b) => a.sectionOrder - b.sectionOrder || a.order - b.order || a.title.localeCompare(b.title));
+
+export const featureDocsBySlug = featureDocs.reduce<Record<string, DocEntry>>((acc, doc) => {
+  acc[doc.slug.replace(/^features\//, '')] = doc;
+  return acc;
+}, {});
+
+export const docs = docEntries
+  .filter((entry) => entry.section !== 'Compares' && !entry.slug.startsWith('compare/') && entry.section !== 'Features' && !entry.slug.startsWith('features/'))
+  .slice()
+  .sort((a, b) => a.sectionOrder - b.sectionOrder || a.order - b.order || a.title.localeCompare(b.title));
+
+export const docsBySlug = docs.reduce<Record<string, DocEntry>>((acc, doc) => {
+  acc[doc.slug] = doc;
+  return acc;
+}, {});
+
+export const docSections = docs.reduce<Record<string, DocEntry[]>>((acc, doc) => {
+  if (!acc[doc.section]) {
+    acc[doc.section] = [];
+  }
+  acc[doc.section].push(doc);
+  return acc;
+}, {});

package/data/markdown/AGENTS.md

@@ -0,0 +1,10 @@
+# MdWrk Markdown Copy Agent Instructions
+
+Markdown content here is an SEO, AEO, and AI answer-engine copy surface. Treat frontmatter, body copy, route intent, sitemap registration, and generated output as one discoverability contract.
+
+- Use the `content_seo_specialist` custom agent for delegated markdown copywriting work in this subtree.
+- Write for retrieval and direct answers: clear titles, concise descriptions, strong openings, question-led headings where appropriate, and grounded FAQ/comparison/supporting copy.
+- Keep frontmatter metadata specific to the page. Title, description, excerpt, image, tags, canonical route intent, and any schema-facing fields must match the body.
+- Prefer present-tense, current-state product guidance with concrete terminology from the live MdWrk surfaces. Do not pad pages with generic marketing filler.
+- When pages are added, moved, renamed, or removed, update content indexes, sitemap sources, and any generated discovery artifacts that depend on them.
+- Keep claims honest and attributable to the real product surface, package surface, or documented workflow described on the page.

package/data/markdown/blog/client-split-out-backstory.md

@@ -0,0 +1,97 @@
+---
+title: Build with the Same MdWrk Editor and Renderer the Client Ships
+date: 2026-03-23
+status: published
+author: CobyCloud
+excerpt: MdWrk packages its editor and renderer as reusable modules, giving product teams a direct path to embed the same authoring and preview surfaces the client uses every day.
+---
+
+## Why this matters
+
+Reusable packages give teams a clear path to:
+
+- ship MdWrk-powered editing inside internal tools
+- reuse the same renderer in docs, apps, and examples
+- keep extension work aligned with stable public package contracts
+- move from first integration to broader adoption with a package set that already fits the live client
+
+## What you can install today
+
+The public package family starts here:
+
+```bash
+npm install @mdwrk/mdwrkspace @mdwrk/markdown-editor-react @mdwrk/markdown-renderer-react
+```
+
+These docs carry the current usage details:
+
+- [Client installation](/docs/getting-started/installation)
+- [Standalone modules](/docs/getting-started/standalone-modules)
+- [Local setup](/docs/getting-started/local-setup)
+
+## React example
+
+```tsx
+import { MarkdownEditor } from '@mdwrk/markdown-editor-react';
+import { MarkdownViewer } from '@mdwrk/markdown-renderer-react';
+import { useState } from 'react';
+
+export function MdWrkDemo() {
+  const [value, setValue] = useState('# Release Notes\n\nMdWrk packages travel well.');
+
+  return (
+    <div style={{ display: 'grid', gap: '1rem', gridTemplateColumns: '1fr 1fr' }}>
+      <MarkdownEditor value={value} onChange={setValue} />
+      <MarkdownViewer content={value} />
+    </div>
+  );
+}
+```
+
+## Screenshot
+
+![MdWrk editor and preview running side by side](/blog/media/mdwrk-workspace-split.png)
+
+This split-view surface shows the kind of install target product teams get when they adopt the package family directly.
+
+## Repository history that shapes the package surface
+
+The package move sits inside a broader history arc:
+
+- [Standalone modules](/docs/getting-started/standalone-modules)
+- [Extension platform](/docs/extensions/extension-platform)
+- [Repository history for package alignment](https://github.com/groupsum/markdown_workspace/commits/master/?since=2026-03-23T00:00:00Z&until=2026-03-24T00:00:00Z)
+
+## Who should use this package family
+
+This package family fits:
+
+- React application teams that want a markdown editor and renderer with a shared visual contract
+- platform teams building governed docs or knowledge surfaces
+- extension teams that want their work to sit close to the live MdWrk runtime
+
+MdWrk turns package reuse into a practical adoption path, and this post marks the point where that path becomes easier to install, easier to use, and easier to extend.
+
+## Article Guide
+
+2026-03-23 marks this MdWrk product story: MdWrk packages its editor and renderer as reusable modules, giving product teams a direct path to embed the same authoring and preview surfaces the client uses every day.
+
+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)
+
+MdWrk now ships a reusable package stack that product teams can install directly, wire into React, and extend through the same public surfaces that power the client.
+
+This milestone is grounded in the March 23, 2026 packaging and naming run:
+
+- [feat(v0.2.0) init](https://github.com/groupsum/markdown_workspace/commit/ed7f04a3)
+- [standardize package authors](https://github.com/groupsum/markdown_workspace/commit/5b3eba78)
+- [migrate npm org and package references to @mdwrk](https://github.com/groupsum/markdown_workspace/commit/9da57335)

package/data/markdown/blog/desktop-release-and-android-verification.md

@@ -0,0 +1,65 @@
+---
+title: Desktop Release Automation and Android Verification Sharpen MdWrk Cross-Platform Delivery
+date: 2026-04-14
+status: published
+author: CobyCloud
+excerpt: MdWrk refines desktop release automation, version-tag generation, and Android artifact verification, giving release teams a stronger cross-platform shipment story.
+---
+
+## Why this matters
+
+This milestone gives teams a stronger answer to:
+
+- how desktop builds move into release
+- how Android artifacts are verified
+- how version tags stay aligned with package state
+
+## Commands that support the release path
+
+```bash
+npm run build:desktop:win
+npm run ci:desktop:build
+npm run ci:desktop:release
+```
+
+## Screenshot
+
+![MdWrk settings and configuration surface that supports packaged client delivery](/blog/media/settings-github-configurations.jpg)
+
+## Repo history links
+
+- [April 14 repository history](https://github.com/groupsum/markdown_workspace/commits/master/?since=2026-04-14T00:00:00Z&until=2026-04-15T00:00:00Z)
+- [Local setup docs](/docs/getting-started/local-setup)
+
+This is the point where MdWrk starts communicating a stronger release operations story alongside its authoring story.
+
+## Article Guide
+
+2026-04-14 marks this MdWrk product story: MdWrk refines desktop release automation, version-tag generation, and Android artifact verification, giving release teams a stronger cross-platform shipment story.
+
+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)
+- [Local Setup](/docs/getting-started/local-setup)
+
+April 14, 2026 marks one of the clearest release-engineering milestones in the repository history.
+
+The day includes:
+
+- [Auto-generate desktop release tag from package version](https://github.com/groupsum/markdown_workspace/commit/b94c4b46)
+- [Narrow desktop release workflow to installable artifacts](https://github.com/groupsum/markdown_workspace/commit/177c25aa)
+- [Fix release artifacts to include APK and exclude elevate.exe](https://github.com/groupsum/markdown_workspace/commit/edfe9135)
+- [Fix Android APK CI verification for unsigned artifacts](https://github.com/groupsum/markdown_workspace/commit/dd84df6e)
+
+It also lines up with published tags:
+
+- `v0.2.34`
+- `v0.2.35`
+- `v0.2.38`

package/data/markdown/blog/docs-surface-realignment.md

@@ -0,0 +1,70 @@
+---
+title: Explore the MdWrk Client, Packages, and Extensions Through a Sharper Docs Experience
+date: 2026-04-30
+status: published
+author: CobyCloud
+excerpt: The MdWrk site now presents a clearer path into the client, package family, and extension platform, with stronger navigation, sharper titles, and more direct routes into installation and usage.
+---
+
+## What readers get from the new docs surface
+
+The public docs now guide readers into:
+
+- installation choices
+- reusable module adoption
+- extension platform details
+- authoring flows for themes, language packs, and extensions
+- repository updates that explain how the platform grows
+
+## Docs that carry the current state
+
+- [Installation](/docs/getting-started/installation)
+- [Local setup](/docs/getting-started/local-setup)
+- [Standalone modules](/docs/getting-started/standalone-modules)
+- [Extension platform](/docs/extensions/extension-platform)
+
+## Screenshot
+
+![MdWrk docs view with the modernized navigation and content layout](/blog/media/lander-docs-dark.png)
+
+## What this update improves
+
+The site now gives readers:
+
+- user-facing titles that communicate product value immediately
+- technical detail that supports installation and implementation
+- direct links between installation, usage, authoring, and package surfaces
+- repository links that show the implementation timeline behind each update
+
+## Use this route in MdWrk
+
+1. Start with [installation](/docs/getting-started/installation).
+2. Move into [standalone modules](/docs/getting-started/standalone-modules) when package reuse is the main goal.
+3. Follow [extension platform](/docs/extensions/extension-platform) for the host and runtime surface.
+4. Read the [April 30 repository history](https://github.com/groupsum/markdown_workspace/commits/master/?since=2026-04-30T00:00:00Z&until=2026-05-01T00:00:00Z) for the concrete docs and brand refinements.
+
+MdWrk now gives readers a faster path from the landing page to installation, package usage, and extension workflows.
+
+## Article Guide
+
+2026-04-30 marks this MdWrk product story: The MdWrk site now presents a clearer path into the client, package family, and extension platform, with stronger navigation, sharper titles, and more direct routes into installation and usage.
+
+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 30, 2026 sharpens the MdWrk site for the client, the reusable packages, and the extension platform.
+
+This refresh lines up with:
+
+- [Refine lander docs metadata and blog ordering](https://github.com/groupsum/markdown_workspace/commit/56bf195f)
+- [Shorten menu labels and refresh lander branding](https://github.com/groupsum/markdown_workspace/commit/469ea94a)
+- [Refine lander markdown contrast and theme defaults](https://github.com/groupsum/markdown_workspace/commit/d612d2c6)

package/data/markdown/blog/extension-compatibility-and-publish-gates.md

@@ -0,0 +1,59 @@
+---
+title: Extension Compatibility Gates Turn MdWrk Publishing into a Clear Quality Signal
+date: 2026-04-01
+status: published
+author: CobyCloud
+excerpt: MdWrk sharpens extension compatibility checks, persistence flows, and publish gates, helping teams ship installable extensions with stronger confidence and cleaner runtime expectations.
+---
+
+## Why this matters for extension teams
+
+A governed extension platform works best when it communicates:
+
+- the host version it supports
+- the tests that protect installation and runtime
+- the UX where users manage extensions and settings
+
+## Example compatibility-focused workflow
+
+```bash
+npm run test -w @mdwrk/extension-runtime
+npm run test -w @mdwrk/extension-manager
+npm run validate:compatibility
+```
+
+## Screenshot
+
+![MdWrk settings and extension-related configuration surfaces](/blog/media/mdwrk-settings-visual.png)
+
+## What to read next
+
+- [Extension platform](/docs/extensions/extension-platform)
+- [Extension authoring](/docs/authoring/extensions)
+- [April 1 repository history](https://github.com/groupsum/markdown_workspace/commits/master/?since=2026-04-01T00:00:00Z&until=2026-04-02T00:00:00Z)
+
+This post marks the point where MdWrk's extension system becomes easier to trust, easier to document, and easier to carry into release workflows.
+
+## Article Guide
+
+2026-04-01 marks this MdWrk product story: MdWrk sharpens extension compatibility checks, persistence flows, and publish gates, helping teams ship installable extensions with stronger confidence and cleaner runtime expectations.
+
+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)
+- [Editor Basics](/features/editor-basics)
+- [Extension Platform](/docs/extensions/extension-platform)
+
+April 1, 2026 tightens the extension delivery story with compatibility gates, version alignment, and publish-focused verification.
+
+The milestone sits on these commits:
+
+- [Enforce test gate before package publish](https://github.com/groupsum/markdown_workspace/commit/9c3e88c5)
+- [Fix extension compatibility checks and editor overflow defaults](https://github.com/groupsum/markdown_workspace/commit/8f2cc526)
+- [Update extension modals, persistence, and workspace version matrix](https://github.com/groupsum/markdown_workspace/commit/a4aaec70)

package/data/markdown/blog/extension-host-rollout.md

@@ -0,0 +1,92 @@
+---
+title: Launch Extensions on the Same Governed Host the MdWrk Client Uses
+date: 2026-04-26
+status: published
+author: CobyCloud
+excerpt: The MdWrk client now presents a governed extension platform with manifest, runtime, manager, theme, language, and workspace surfaces that teams can adopt with a clear authoring path.
+---
+
+## What extension authors get
+
+MdWrk's extension platform includes:
+
+- `@mdwrk/extension-manifest` for declarative metadata
+- `@mdwrk/extension-host` for host-safe APIs
+- `@mdwrk/extension-runtime` for activation and lifecycle
+- `@mdwrk/extension-manager` for installation and management UX
+- first-party surfaces for theme authoring, language packs, Git operations, and workspace files
+
+## Installation and authoring references
+
+These docs carry the current usage details:
+
+- [Extension platform](/docs/extensions/extension-platform)
+- [Extension authoring overview](/docs/authoring/overview)
+- [Extension authoring guide](/docs/authoring/extensions)
+
+## Package-first install example
+
+```bash
+npm install @mdwrk/extension-runtime @mdwrk/extension-host @mdwrk/extension-manifest
+```
+
+## Manifest example
+
+```json
+{
+  "id": "acme.release-notes-tools",
+  "name": "Release Notes Tools",
+  "version": "1.0.0",
+  "publisher": "Acme",
+  "engines": {
+    "mdwrk": "^1.4.0"
+  }
+}
+```
+
+## Screenshot
+
+![MdWrk extension manager pane inside the client workspace](/blog/media/extension-manager-pane.jpg)
+
+This pane shows how MdWrk brings extension discovery and runtime management into the same workspace experience that writers and operators already use.
+
+## Why this rollout matters
+
+Extension teams want a host that communicates:
+
+- where extensions register
+- how compatibility is checked
+- where settings and commands appear
+- how first-party and third-party surfaces fit together
+
+MdWrk now expresses that story clearly in product terms and package terms at the same time.
+
+## Follow the repo history
+
+- [Extension platform docs](/docs/extensions/extension-platform)
+- [Authoring overview](/docs/authoring/overview)
+- [April 26 repository history](https://github.com/groupsum/markdown_workspace/commits/master/?since=2026-04-26T00:00:00Z&until=2026-04-27T00:00:00Z)
+
+## Article Guide
+
+2026-04-26 marks this MdWrk product story: The MdWrk client now presents a governed extension platform with manifest, runtime, manager, theme, language, and workspace surfaces that teams can adopt with a clear authoring path.
+
+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)
+
+MdWrk now gives extension authors a first-class product surface with runtime APIs, compatibility rules, settings adapters, and installation flows that match the live client.
+
+The April 26, 2026 extension milestone is anchored in these commits:
+
+- [Implement continuous extension experiences](https://github.com/groupsum/markdown_workspace/commit/fe9a53bb)
+- [Publish extension continuous experience release](https://github.com/groupsum/markdown_workspace/commit/b10b5332)
+- [Add workspace module packages for files and git ops](https://github.com/groupsum/markdown_workspace/commit/d4efae4c)

package/data/markdown/blog/governed-releases-and-package-docs.md

@@ -0,0 +1,69 @@
+---
+title: Governed Releases, CI Evidence, and Package Docs Give MdWrk a Stronger Public Shape
+date: 2026-03-31
+status: published
+author: CobyCloud
+excerpt: MdWrk expands its release and documentation surface with package evidence, governance checks, and public docs that help teams understand package scope, delivery, and verification commands.
+---
+
+## What this adds
+
+This update brings together the details teams usually need first:
+
+- How does the workspace verify package quality?
+- Which docs stay current?
+- Which commands carry release verification?
+
+MdWrk now answers those questions through docs and executable CI rails.
+
+## Commands that express the release story
+
+```bash
+npm run ci:workspace:verify
+npm run conformance
+```
+
+## Docs to read next
+
+- [Installation](/docs/getting-started/installation)
+- [Local setup](/docs/getting-started/local-setup)
+- [Extension platform](/docs/extensions/extension-platform)
+
+## Screenshot
+
+![MdWrk docs and product presentation aligned for package usage](/blog/media/lander-docs-dark.png)
+
+## Why this post matters
+
+March 31 is where MdWrk gives teams a clearer view of:
+
+- package verification
+- release commands
+- current docs
+- package boundaries
+
+It is a major point on the timeline because package usage, release checks, and public docs start moving together.
+
+## Article Guide
+
+2026-03-31 marks this MdWrk product story: MdWrk expands its release and documentation surface with package evidence, governance checks, and public docs that help teams understand package scope, delivery, and verification commands.
+
+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)
+
+March 31, 2026 brings together docs, governance, and release evidence in a way that gives MdWrk a clearer package and release surface.
+
+This milestone is grounded in:
+
+- [Add governance specs, CI checks, and documentation overhaul](https://github.com/groupsum/markdown_workspace/commit/3cb1ef10)
+- [Add markdown profile claim gate, tests, and CI evidence](https://github.com/groupsum/markdown_workspace/commit/1e511548)
+- [Align extension manifests and artifacts to 1.1.0](https://github.com/groupsum/markdown_workspace/commit/93ea12ef)

package/data/markdown/blog/markdown-workspace-launch.md

@@ -0,0 +1,75 @@
+---
+title: Meet the Markdown Workspace That Turns Writing, Preview, and Themes into One Fast Flow
+date: 2026-01-20
+status: published
+author: CobyCloud
+excerpt: Markdown Workspace opens with live writing, preview, themed presentation, and early export foundations that give teams a compelling browser-first markdown workflow from day one.
+---
+
+## What launches
+
+The launch surface already brings together:
+
+- a markdown editor
+- a live preview
+- theme switching
+- a workspace shell with clear product polish
+
+## How to try MdWrk today
+
+The current entry routes live here:
+
+- [Client installation](/docs/getting-started/installation)
+- [Browser use](/docs/getting-started/browser-use)
+- [PWA installation](/docs/getting-started/pwa-installation)
+
+## Screenshot
+
+![MdWrk home and writing surface at launch-stage theme richness](/blog/media/lander-home-light.png)
+
+## Example workflow
+
+```markdown
+# Product Overview
+
+MdWrk keeps writing and preview close together.
+
+- themes communicate brand tone
+- preview communicates final structure
+- markdown keeps the source portable
+```
+
+## Why the launch resonates
+
+Teams evaluating markdown tools often look for:
+
+- speed to first draft
+- visual clarity
+- easy theme variation
+- a clean route to later packaging and deployment
+
+MdWrk opens with all four, which gives the product a strong story from its first visible commits.
+
+## Article Guide
+
+2026-01-20 marks this MdWrk product story: Markdown Workspace opens with live writing, preview, themed presentation, and early export foundations that give teams a compelling browser-first markdown workflow from day one.
+
+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)
+
+The January 20, 2026 launch introduces a writing workspace built for fast authoring, visual polish, and theme-aware reading.
+
+This first day is visible in the earliest repo milestones:
+
+- [Initial commit](https://github.com/groupsum/markdown_workspace/commit/3964e6bf)
+- [Add acid etched theme skin](https://github.com/groupsum/markdown_workspace/commit/286faf28)
+- [Add theme cycling controls](https://github.com/groupsum/markdown_workspace/commit/99457cd9)