@mdwrk/mdwrkcom-content-pack 0.1.5 → 0.1.6

package/generated/llms-full.txt

@@ -1620,9 +1620,9 @@ MdWrk's privacy boundary starts with local-first authoring. Normal Markdown writ
 
 URL: https://mdwrk.com/updates/
 
-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.
+MdWrk adds a developer-facing learning map that connects structured data builders, React JSON-LD components, and lander discovery helpers in one visual reference.
 
-Product Updates 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. Settings Simplification Gives MdWrk a Faster Path from Installation to Daily Use - 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. Explore the MdWrk Client, Packages, and Extensions Through a Sharper Docs Experience - 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. Launch Extensions on the Same Governed Host the MdWrk Client Uses - 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. Workspace Files and Git Operations Packages Open a Larger Automation Surface for MdWrk - 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. Desktop Release Automation and Android Verification Sharpen MdWrk Cross-Platform Delivery - MdWrk refines desktop release automation, version-tag generation, and Android artifact verification, giving release teams a stronger cross-platform shipment story. Retained Client Versions and the Desktop Shell Expand How Teams Can Deploy MdWrk - 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. Screenshot Matrix Coverage Helps MdWrk Prove Themes Across Viewports and Workflows - 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. Extension Compatibility Gates Turn MdWrk Publishing into a Clear Quality Signal - MdWrk sharpens extension compatibility checks, persistence flows, and publish gates, helping teams ship installable extensions with stronger confidence and cleaner runtime expectations. Governed Releases, CI Evidence, and Package Docs Give MdWrk a Stronger Public Shape - 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. Build with the Same MdWrk Editor and Renderer the Client Ships - 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. PWA Install, Zoom Controls, and Preview Refinements Make MdWrk Ready for Daily Use - MdWrk gains PWA install support, zoom controls, preview refinements, and deployment rails that turn the workspace into a stronger everyday writing environment. Responsive Authoring, Keyboard Speed, and HTML Export Expand MdWrk in a Single Day - 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. Meet the Markdown Workspace That Turns Writing, Preview, and Themes into One Fast Flow - 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.
+Product Updates MdWrk adds a developer-facing learning map that connects structured data builders, React JSON-LD components, and lander discovery helpers in one visual reference. Structured Data Learning Map Makes the MdWrk Lander Pipeline Easier to Teach - MdWrk adds a developer-facing learning map that connects structured data builders, React JSON-LD components, and lander discovery helpers in one visual reference. MdWrk Package Dependency Maps Show How Apps, Shared Packages, and Lander Packages Connect - Package dependency maps show how the app entrypoints, shared foundations, editor and renderer packages, and lander packages fit together. Settings Simplification Gives MdWrk a Faster Path from Installation to Daily Use - 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. Explore the MdWrk Client, Packages, and Extensions Through a Sharper Docs Experience - 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. Launch Extensions on the Same Governed Host the MdWrk Client Uses - 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. Workspace Files and Git Operations Packages Open a Larger Automation Surface for MdWrk - 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. Desktop Release Automation and Android Verification Sharpen MdWrk Cross-Platform Delivery - MdWrk refines desktop release automation, version-tag generation, and Android artifact verification, giving release teams a stronger cross-platform shipment story. Retained Client Versions and the Desktop Shell Expand How Teams Can Deploy MdWrk - 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. Screenshot Matrix Coverage Helps MdWrk Prove Themes Across Viewports and Workflows - 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. Extension Compatibility Gates Turn MdWrk Publishing into a Clear Quality Signal - MdWrk sharpens extension compatibility checks, persistence flows, and publish gates, helping teams ship installable extensions with stronger confidence and cleaner runtime expectations. Governed Releases, CI Evidence, and Package Docs Give MdWrk a Stronger Public Shape - 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. Build with the Same MdWrk Editor and Renderer the Client Ships - 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. PWA Install, Zoom Controls, and Preview Refinements Make MdWrk Ready for Daily Use - MdWrk gains PWA install support, zoom controls, preview refinements, and deployment rails that turn the workspace into a stronger everyday writing environment. Responsive Authoring, Keyboard Speed, and HTML Export Expand MdWrk in a Single Day - 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. Meet the Markdown Workspace That Turns Writing, Preview, and Themes into One Fast Flow - 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.
 
 ## January 2026
 
@@ -1654,7 +1654,7 @@ URL: https://mdwrk.com/updates/archive/2026-05/
 
 Product Updates by Month
 
-May 2026 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. Settings Simplification Gives MdWrk a Faster Path from Installation to Daily Use - 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.
+May 2026 MdWrk adds a developer-facing learning map that connects structured data builders, React JSON-LD components, and lander discovery helpers in one visual reference. Structured Data Learning Map Makes the MdWrk Lander Pipeline Easier to Teach - MdWrk adds a developer-facing learning map that connects structured data builders, React JSON-LD components, and lander discovery helpers in one visual reference. MdWrk Package Dependency Maps Show How Apps, Shared Packages, and Lander Packages Connect - Package dependency maps show how the app entrypoints, shared foundations, editor and renderer packages, and lander packages fit together. Settings Simplification Gives MdWrk a Faster Path from Installation to Daily Use - 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.
 
 ## CobyCloud
 
@@ -1662,7 +1662,7 @@ URL: https://mdwrk.com/updates/author/cobycloud/
 
 Product Updates by Author
 
-CobyCloud 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. Settings Simplification Gives MdWrk a Faster Path from Installation to Daily Use - 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. Explore the MdWrk Client, Packages, and Extensions Through a Sharper Docs Experience - 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. Launch Extensions on the Same Governed Host the MdWrk Client Uses - 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. Workspace Files and Git Operations Packages Open a Larger Automation Surface for MdWrk - 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. Desktop Release Automation and Android Verification Sharpen MdWrk Cross-Platform Delivery - MdWrk refines desktop release automation, version-tag generation, and Android artifact verification, giving release teams a stronger cross-platform shipment story. Retained Client Versions and the Desktop Shell Expand How Teams Can Deploy MdWrk - 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. Screenshot Matrix Coverage Helps MdWrk Prove Themes Across Viewports and Workflows - 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. Extension Compatibility Gates Turn MdWrk Publishing into a Clear Quality Signal - MdWrk sharpens extension compatibility checks, persistence flows, and publish gates, helping teams ship installable extensions with stronger confidence and cleaner runtime expectations. Governed Releases, CI Evidence, and Package Docs Give MdWrk a Stronger Public Shape - 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. Build with the Same MdWrk Editor and Renderer the Client Ships - 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. PWA Install, Zoom Controls, and Preview Refinements Make MdWrk Ready for Daily Use - MdWrk gains PWA install support, zoom controls, preview refinements, and deployment rails that turn the workspace into a stronger everyday writing environment. Responsive Authoring, Keyboard Speed, and HTML Export Expand MdWrk in a Single Day - 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. Meet the Markdown Workspace That Turns Writing, Preview, and Themes into One Fast Flow - 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.
+CobyCloud MdWrk adds a developer-facing learning map that connects structured data builders, React JSON-LD components, and lander discovery helpers in one visual reference. Structured Data Learning Map Makes the MdWrk Lander Pipeline Easier to Teach - MdWrk adds a developer-facing learning map that connects structured data builders, React JSON-LD components, and lander discovery helpers in one visual reference. MdWrk Package Dependency Maps Show How Apps, Shared Packages, and Lander Packages Connect - Package dependency maps show how the app entrypoints, shared foundations, editor and renderer packages, and lander packages fit together. Settings Simplification Gives MdWrk a Faster Path from Installation to Daily Use - 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. Explore the MdWrk Client, Packages, and Extensions Through a Sharper Docs Experience - 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. Launch Extensions on the Same Governed Host the MdWrk Client Uses - 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. Workspace Files and Git Operations Packages Open a Larger Automation Surface for MdWrk - 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. Desktop Release Automation and Android Verification Sharpen MdWrk Cross-Platform Delivery - MdWrk refines desktop release automation, version-tag generation, and Android artifact verification, giving release teams a stronger cross-platform shipment story. Retained Client Versions and the Desktop Shell Expand How Teams Can Deploy MdWrk - 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. Screenshot Matrix Coverage Helps MdWrk Prove Themes Across Viewports and Workflows - 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. Extension Compatibility Gates Turn MdWrk Publishing into a Clear Quality Signal - MdWrk sharpens extension compatibility checks, persistence flows, and publish gates, helping teams ship installable extensions with stronger confidence and cleaner runtime expectations. Governed Releases, CI Evidence, and Package Docs Give MdWrk a Stronger Public Shape - 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. Build with the Same MdWrk Editor and Renderer the Client Ships - 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. PWA Install, Zoom Controls, and Preview Refinements Make MdWrk Ready for Daily Use - MdWrk gains PWA install support, zoom controls, preview refinements, and deployment rails that turn the workspace into a stronger everyday writing environment. Responsive Authoring, Keyboard Speed, and HTML Export Expand MdWrk in a Single Day - 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. Meet the Markdown Workspace That Turns Writing, Preview, and Themes into One Fast Flow - 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.
 
 ## Build with the Same MdWrk Editor and Renderer the Client Ships
 
@@ -1720,6 +1720,14 @@ The MdWrk launch story centers on a local-first Markdown workspace and a public
 
 MdWrk's public launch story is not only about a Markdown editor. It is also about how the product explains itself. The public lander uses Markdown files as source content, validates frontmatter, builds a normalized registry, and produces static artifacts that can be verified before the production domain is live. Static Before Runtime The first principle is that public content should not require a browser application shell. If a crawler, assistant, or user downloads the raw HTML response, the primary content should already be present in the page. Machine-Readable By Default The build emits JSON-LD, sitemap data, robots policy, LLM index files, a content index, and Markdown mirrors. These artifacts are generated from the same registry so content identity, metadata, and links stay aligned. Why It Matters A Markdown product should be able to prove its own documentation quality. MdWrk uses the compiler to check source validity, static readability, SEO signals, answer visibility, AI-oriented artifacts, and internal links without depending on production deployment. What Comes Next The static compiler can grow as the content set grows. The important contract is already clear: Markdown body content remains the article, frontmatter remains metadata, and answer or FAQ metadata must be visibly rendered when used for structured data.
 
+## MdWrk Package Dependency Maps Show How Apps, Shared Packages, and Lander Packages Connect
+
+URL: https://mdwrk.com/updates/package-dag-for-mdwrk-and-lander/
+
+Package dependency maps show how the app entrypoints, shared foundations, editor and renderer packages, and lander packages fit together.
+
+The May 18 update adds a visual package DAG for MdWrk contributors. The graph shows the direct internal dependency relationships between app entrypoints, package surfaces, and foundational contracts in the workspace. This map is useful because the MdWrk repo is intentionally split into focused package lanes. Shared packages provide reusable contracts and primitives. Editor, renderer, and extension packages build the writing workspace. Lander packages turn content, structured data, SEO helpers, React components, and themes into mdwrk.com. The app layer then consumes those packages through apps/client and apps/mdwrkcom. Package DAG The DAG set is split into focused images so each surface can be read without forcing unrelated package families into the same graph. apps/client apps/mdwrkcom Lander packages What the graph shows Each graph is top-down. The entrypoint or package roots sit at the top, the packages they consume sit below them, and foundational contracts sit near the bottom. Each arrow points from a consumer package to the internal package it depends on. The graph includes shared foundations and contracts: @mdwrk/theme-contract, @mdwrk/ui-tokens, @mdwrk/icons, @mdwrk/i18n, @mdwrk/testing, and @mdwrk/structured-data @mdwrk/extension-manifest and @mdwrk/extension-host Those packages support the MdWrk editor, renderer, and extension lane: @mdwrk/markdown-renderer-core and @mdwrk/markdown-renderer-react @mdwrk/markdown-editor-core, @mdwrk/markdown-editor-react, and @mdwrk/markdown-edit-in-renderer-react @mdwrk/extension-runtime, @mdwrk/extension-manager, @mdwrk/extension-theme-studio, @mdwrk/extension-language-pack-studio, @mdwrk/extension-workspace-files, @mdwrk/extension-git-ops, and @mdwrk/extension-gemini-agent The lander lane stays separate and focused on the public site: @mdwrk/lander-content-contract @mdwrk/lander-core @mdwrk/lander-react @mdwrk/lander-seo @mdwrk/lander-theme @mdwrk/lander-markdown-content-adapter @mdwrk/lander-page-templates @mdwrk/lander-page-template-presets @mdwrk/mdwrkcom-content-pack apps/mdwrkcom consumes lander packages, renderer packages, structured data, and UI tokens. apps/client consumes the editor, renderer, extension, shared UI, and contract packages. Why this matters The DAG gives contributors a practical review map. A change to @mdwrk/structured-data can be checked for its effect on @mdwrk/lander-react and apps/mdwrkcom. A change to @mdwrk/ui-tokens can be reviewed through both the workspace client and the lander. A change to the extension runtime can be evaluated through the extension packages that depend on it before it reaches the client app. The same structure also keeps package ownership clear. Shared foundations stay small and reusable. Runtime packages stay focused on editing and rendering behavior. Lander packages stay focused on publishing, discovery, and reusable public-site content. App packages assemble those capabilities without hiding the dependency paths. How to use it Use the DAG when planning package work, reviewing pull requests, or deciding where a new capability belongs. Start with the package that owns the primitive or behavior. Follow its outgoing dependency path to the packages that consume it. Check the app entrypoint that exposes the behavior to users. Keep new functionality in the lowest package lane that owns the domain cleanly. For adjacent package context, continue with the MdWrk package and lander references: Package Surfaces Quickstart Extension Platform
+
 ## PWA Install, Zoom Controls, and Preview Refinements Make MdWrk Ready for Daily Use
 
 URL: https://mdwrk.com/updates/pwa-install-and-zoom-controls/
@@ -1760,6 +1768,14 @@ MdWrk refines its settings UX with cleaner labels and a calmer navigation model,
 
 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 Current docs for configuration and setup Installation Configuration Local setup Example setup flow Install the client through the path that fits your team. Open settings and tune theme, language, and workspace preferences. 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.
 
+## Structured Data Learning Map Makes the MdWrk Lander Pipeline Easier to Teach
+
+URL: https://mdwrk.com/updates/structured-data-learning-map/
+
+MdWrk adds a developer-facing learning map that connects structured data builders, React JSON-LD components, and lander discovery helpers in one visual reference.
+
+The May 18 update adds a developer learning map for the MdWrk lander pipeline. The visual gives contributors one place to understand how content intent turns into schema.org JSON-LD, how the React lander renders that graph, and how the lander helper package emits discovery artifacts for the published site. This work is useful when developers need to move across three related packages without losing the boundary between them: @mdwrk/structured-data owns the typed JSON-LD builders. @mdwrk/lander-react owns the React components and page graph assembly. @mdwrk/lander-seo owns metadata, graph artifacts, sitemap inputs, robots output, and crawler-facing files. What the map shows The map follows the pipeline from left to right. First, structured data types such as WebPage, WebSite, Organization, SoftwareApplication, Article, FAQPage, BreadcrumbList, Dataset, Event, Product, Course, Recipe, and JobPosting start as builder inputs in the structured-data package. These builders keep schema.org nodes explicit and reusable instead of burying JSON-LD inside individual pages. Next, lander React components such as JsonLd, StructuredDataNode, ReadActionStructuredData, and buildLanderJsonLdGraph turn those builders into a page-level graph. The runtime output is still the familiar script tag: Finally, the lander helper layer packages the same content model into site-wide outputs: page metadata, canonical URLs, Open Graph tags, Twitter cards, jsonld-graph.json, sitemap resources, robots.txt, and llms.txt. Learning asset Why this matters for contributors The lander is easier to extend when each package keeps a clear job. A developer adding a new schema type can start in @mdwrk/structured-data, expose the relevant React integration in @mdwrk/lander-react, and then confirm that the discovery helper output still reflects the page content accurately. That separation also makes reviews cleaner. Package work can be evaluated at the builder layer, component work can be evaluated at the rendering layer, and publishing work can be evaluated through generated artifacts. The learning map gives those review paths a shared vocabulary. How to use the map Use the map when onboarding a contributor, reviewing a structured-data change, or deciding where a new page intent belongs. Start with the schema.org type or content intent. Confirm the matching builder surface in @mdwrk/structured-data. Trace the React component or graph helper that renders it. Verify the lander helper output that makes the page discoverable. For package-level details, continue with the MdWrk package surfaces and lander documentation: Package Surfaces Quickstart Theme Packs
+
 ## Workspace Files and Git Operations Packages Open a Larger Automation Surface for MdWrk
 
 URL: https://mdwrk.com/updates/workspace-files-and-git-ops-packages/

package/generated/llms.txt

@@ -203,7 +203,9 @@ MdWrk is a local-first Markdown workspace with static, verifiable public documen
 - [MdWrk Vs Standard Markdown Editors](https://mdwrk.com/compare/standard-markdown-editors/) - 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.
 - [UI Refresh 1.3.28](https://mdwrk.com/docs/archive/ui-refresh-1-3-28/) - MdWrk 1.3.28 improves editing ergonomics, toolbar grouping, markdown list rendering, status footer behavior, and workspace action placement.
 - [UI Refresh 1.3.29](https://mdwrk.com/docs/archive/ui-refresh-1-3-29/) - This release focuses on visual clarity, modal usability, and responsive behavior improvements-
-- [Product Updates](https://mdwrk.com/updates/) - 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.
+- [Product Updates](https://mdwrk.com/updates/) - MdWrk adds a developer-facing learning map that connects structured data builders, React JSON-LD components, and lander discovery helpers in one visual reference.
+- [Structured Data Learning Map Makes the MdWrk Lander Pipeline Easier to Teach](https://mdwrk.com/updates/structured-data-learning-map/) - MdWrk adds a developer-facing learning map that connects structured data builders, React JSON-LD components, and lander discovery helpers in one visual reference.
+- [MdWrk Package Dependency Maps Show How Apps, Shared Packages, and Lander Packages Connect](https://mdwrk.com/updates/package-dag-for-mdwrk-and-lander/) - Package dependency maps show how the app entrypoints, shared foundations, editor and renderer packages, and lander packages fit together.
 - [Settings Simplification Gives MdWrk a Faster Path from Installation to Daily Use](https://mdwrk.com/updates/settings-simplification-for-daily-flow/) - 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.
 - [Explore the MdWrk Client, Packages, and Extensions Through a Sharper Docs Experience](https://mdwrk.com/updates/docs-surface-realignment/) - 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.
 - [Launch Extensions on the Same Governed Host the MdWrk Client Uses](https://mdwrk.com/updates/extension-host-rollout/) - 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.
@@ -216,8 +218,8 @@ MdWrk is a local-first Markdown workspace with static, verifiable public documen
 - [Build with the Same MdWrk Editor and Renderer the Client Ships](https://mdwrk.com/updates/client-split-out-backstory/) - 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.
 - [PWA Install, Zoom Controls, and Preview Refinements Make MdWrk Ready for Daily Use](https://mdwrk.com/updates/pwa-install-and-zoom-controls/) - MdWrk gains PWA install support, zoom controls, preview refinements, and deployment rails that turn the workspace into a stronger everyday writing environment.
 - [Responsive Authoring, Keyboard Speed, and HTML Export Expand MdWrk in a Single Day](https://mdwrk.com/updates/responsive-authoring-and-export/) - 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.
-- [CobyCloud](https://mdwrk.com/updates/author/cobycloud/) - 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.
-- [May 2026](https://mdwrk.com/updates/archive/2026-05/) - 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.
+- [CobyCloud](https://mdwrk.com/updates/author/cobycloud/) - MdWrk adds a developer-facing learning map that connects structured data builders, React JSON-LD components, and lander discovery helpers in one visual reference.
+- [May 2026](https://mdwrk.com/updates/archive/2026-05/) - MdWrk adds a developer-facing learning map that connects structured data builders, React JSON-LD components, and lander discovery helpers in one visual reference.
 - [April 2026](https://mdwrk.com/updates/archive/2026-04/) - 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.
 - [March 2026](https://mdwrk.com/updates/archive/2026-03/) - 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.
 - [January 2026](https://mdwrk.com/updates/archive/2026-01/) - MdWrk gains PWA install support, zoom controls, preview refinements, and deployment rails that turn the workspace into a stronger everyday writing environment.