@mdwrk/mdwrkcom-content-pack 0.1.5

package/generated/llms.txt

@@ -0,0 +1,225 @@
+# MdWrk
+
+MdWrk is a local-first Markdown workspace with static, verifiable public documentation.
+
+- [Does MdWrk require a server?](https://mdwrk.com/answers/does-mdwrk-require-a-server/) - MdWrk does not require a hosted server for normal Markdown editing; networked flows are explicit integrations.
+- [How do MdWrk theme packs work?](https://mdwrk.com/answers/how-do-mdwrk-theme-packs-work/) - MdWrk theme packs target governed token and surface contracts so styling can travel across editor, preview, and lander surfaces.
+- [How does MdWrk store Markdown locally?](https://mdwrk.com/answers/how-does-mdwrk-store-markdown-locally/) - MdWrk uses browser-local persistence for workspace state so authoring can remain device-local unless users choose an integration.
+- [Answers](https://mdwrk.com/answers/) - Read direct answers about MdWrk, local-first Markdown workflows, offline editing, local storage, and theme-pack behavior.
+- [What is a local-first Markdown workspace?](https://mdwrk.com/answers/what-is-a-local-first-markdown-workspace/) - A local-first Markdown workspace keeps normal writing, preview, and organization local while sync and hosted integrations remain optional paths.
+- [What is an offline Markdown editor?](https://mdwrk.com/answers/what-is-an-offline-markdown-editor/) - An offline Markdown editor lets authors write and preview Markdown without requiring a live hosted backend for normal editing.
+- [MdWrk launch notes](https://mdwrk.com/updates/launch/) - The MdWrk launch article explains why the public lander is compiled from Markdown into static HTML, JSON-LD, LLM indexes, and Markdown mirrors.
+- [Compare MdWrk](https://mdwrk.com/compare/) - Compare MdWrk with Markdown editors and workspace tools by local-first behavior, browser delivery, package reuse, extension boundaries, and proof artifacts.
+- [Local-first Markdown editors](https://mdwrk.com/compare/local-first-markdown-editors/) - Compare local-first Markdown editors by storage defaults, browser/PWA support, preview behavior, package reuse, and extension boundaries.
+- [MdWrk vs Obsidian](https://mdwrk.com/compare/mdwrk-vs-obsidian/) - Compare MdWrk and Obsidian for local-first Markdown writing, package reuse, workspace behavior, privacy boundaries, and extensions.
+- [MdWrk vs Typora](https://mdwrk.com/compare/mdwrk-vs-typora/) - Compare MdWrk and Typora for local-first Markdown writing, live preview, package reuse, workspace organization, and extension surfaces.
+- [MdWrk vs VS Code Markdown](https://mdwrk.com/compare/mdwrk-vs-vscode-markdown/) - Compare MdWrk and VS Code Markdown workflows for writing, preview, local-first behavior, package reuse, and extension contracts.
+- [Extensions](https://mdwrk.com/docs/extensions/) - MdWrk extension docs explain manifests, host boundaries, runtime surfaces, capability expectations, and trust policy for Markdown workspace extensions.
+- [MdWrk quickstart](https://mdwrk.com/docs/quickstart/) - Start using MdWrk by understanding the local-first workspace model, the Markdown editor and renderer surfaces, and where public static docs fit.
+- [Theme packs](https://mdwrk.com/docs/theme-packs/) - MdWrk theme pack docs explain theme contracts, token surfaces, visual boundaries, and how Markdown workspace styling remains inspectable.
+- [Inicio rapido de MdWrk](https://mdwrk.com/es/docs/quickstart/) - Empieza con MdWrk entendiendo el modelo local-first, el editor Markdown, la vista previa y el papel de la documentacion estatica publica.
+- [Extension runtime](https://mdwrk.com/features/extension-runtime/) - MdWrk extensions use governed runtime, manifest, compatibility, and trust surfaces instead of patching the client directly.
+- [GitHub sync](https://mdwrk.com/features/github-sync/) - MdWrk treats GitHub sync as an optional repository integration path rather than the default authoring storage layer.
+- [MdWrk features](https://mdwrk.com/features/) - Explore MdWrk features for local-first Markdown writing, offline authoring, PWA use, browser-local storage, preview, themes, extensions, and GitHub sync.
+- [IndexedDB Markdown storage](https://mdwrk.com/features/indexeddb-markdown-storage/) - MdWrk uses browser-local persistence so workspace state can remain on the user device during normal authoring.
+- [Live Markdown preview](https://mdwrk.com/features/live-preview/) - MdWrk pairs Markdown source editing with live preview through reusable editor and renderer package surfaces.
+- [PWA Markdown editor](https://mdwrk.com/features/pwa-markdown-editor/) - MdWrk can run as an installable PWA Markdown editor with browser-based authoring, preview, and workspace navigation.
+- [Local-first Markdown workspace](https://mdwrk.com/) - MdWrk is a local-first Markdown workspace for writing, previewing, organizing, and extending Markdown documents with static documentation built for search and AI retrieval.
+- [Basic Markdown syntax](https://mdwrk.com/markdown/basic-markdown-syntax/) - Review basic Markdown syntax for headings, lists, links, emphasis, images, blockquotes, and code blocks in a readable plain-text format.
+- [Benefits of local-first markdown workspace](https://mdwrk.com/markdown/local-first-markdown-workspace/benefits/) - The benefits of Local-first Markdown workspace usually include source readability, workflow clarity, portability, and better alignment between writing and publishing.
+- [Local-first Markdown workspace best practices](https://mdwrk.com/markdown/local-first-markdown-workspace/best-practices/) - Local-first Markdown workspace best practices help teams keep Markdown workflows portable, readable, reviewable, and easier to publish.
+- [Local-first Markdown workspace checklist](https://mdwrk.com/markdown/local-first-markdown-workspace/checklist/) - A Local-first Markdown workspace checklist helps teams review authoring, preview, storage, portability, and publishing concerns before choosing or expanding a Markdown workflow.
+- [Local-first Markdown workspace examples](https://mdwrk.com/markdown/local-first-markdown-workspace/examples/) - Local-first Markdown workspace examples show how this Markdown workflow appears in practical authoring, preview, review, and publishing situations.
+- [Local-first Markdown workspace for developers](https://mdwrk.com/markdown/local-first-markdown-workspace/for-developers/) - Local-first Markdown workspace for developers focuses on Markdown workflows that intersect with repositories, package reuse, and code-adjacent documentation.
+- [Local-first Markdown workspace for teams](https://mdwrk.com/markdown/local-first-markdown-workspace/for-teams/) - Local-first Markdown workspace for teams focuses on shared Markdown workflows, review paths, ownership boundaries, and publishing expectations.
+- [Local-first Markdown workspace use cases](https://mdwrk.com/markdown/local-first-markdown-workspace/use-cases/) - Local-first Markdown workspace use cases cover the practical situations where teams choose this Markdown workflow, surface, or document model.
+- [Local-first Markdown workspace workflow](https://mdwrk.com/markdown/local-first-markdown-workspace/workflow/) - Local-first Markdown workspace workflow guidance explains how authors move from Markdown drafting to preview, review, packaging, and publishing.
+- [Benefits of markdown blogging](https://mdwrk.com/markdown/markdown-blogging/benefits/) - The benefits of Markdown blogging usually include source readability, workflow clarity, portability, and better alignment between writing and publishing.
+- [Markdown blogging best practices](https://mdwrk.com/markdown/markdown-blogging/best-practices/) - Markdown blogging best practices help teams keep Markdown workflows portable, readable, reviewable, and easier to publish.
+- [Markdown blogging checklist](https://mdwrk.com/markdown/markdown-blogging/checklist/) - A Markdown blogging checklist helps teams review authoring, preview, storage, portability, and publishing concerns before choosing or expanding a Markdown workflow.
+- [Markdown blogging examples](https://mdwrk.com/markdown/markdown-blogging/examples/) - Markdown blogging examples show how this Markdown workflow appears in practical authoring, preview, review, and publishing situations.
+- [Markdown blogging for developers](https://mdwrk.com/markdown/markdown-blogging/for-developers/) - Markdown blogging for developers focuses on Markdown workflows that intersect with repositories, package reuse, and code-adjacent documentation.
+- [Markdown blogging for teams](https://mdwrk.com/markdown/markdown-blogging/for-teams/) - Markdown blogging for teams focuses on shared Markdown workflows, review paths, ownership boundaries, and publishing expectations.
+- [Markdown blogging use cases](https://mdwrk.com/markdown/markdown-blogging/use-cases/) - Markdown blogging use cases cover the practical situations where teams choose this Markdown workflow, surface, or document model.
+- [Markdown blogging workflow](https://mdwrk.com/markdown/markdown-blogging/workflow/) - Markdown blogging workflow guidance explains how authors move from Markdown drafting to preview, review, packaging, and publishing.
+- [Benefits of markdown documentation](https://mdwrk.com/markdown/markdown-documentation/benefits/) - The benefits of Markdown documentation usually include source readability, workflow clarity, portability, and better alignment between writing and publishing.
+- [Markdown documentation best practices](https://mdwrk.com/markdown/markdown-documentation/best-practices/) - Markdown documentation best practices help teams keep Markdown workflows portable, readable, reviewable, and easier to publish.
+- [Markdown documentation checklist](https://mdwrk.com/markdown/markdown-documentation/checklist/) - A Markdown documentation checklist helps teams review authoring, preview, storage, portability, and publishing concerns before choosing or expanding a Markdown workflow.
+- [Markdown documentation examples](https://mdwrk.com/markdown/markdown-documentation/examples/) - Markdown documentation examples show how this Markdown workflow appears in practical authoring, preview, review, and publishing situations.
+- [Markdown documentation for developers](https://mdwrk.com/markdown/markdown-documentation/for-developers/) - Markdown documentation for developers focuses on Markdown workflows that intersect with repositories, package reuse, and code-adjacent documentation.
+- [Markdown documentation for teams](https://mdwrk.com/markdown/markdown-documentation/for-teams/) - Markdown documentation for teams focuses on shared Markdown workflows, review paths, ownership boundaries, and publishing expectations.
+- [Markdown documentation use cases](https://mdwrk.com/markdown/markdown-documentation/use-cases/) - Markdown documentation use cases cover the practical situations where teams choose this Markdown workflow, surface, or document model.
+- [Markdown documentation workflow](https://mdwrk.com/markdown/markdown-documentation/workflow/) - Markdown documentation workflow guidance explains how authors move from Markdown drafting to preview, review, packaging, and publishing.
+- [Benefits of markdown editor](https://mdwrk.com/markdown/markdown-editor/benefits/) - The benefits of Markdown editor usually include source readability, workflow clarity, portability, and better alignment between writing and publishing.
+- [Markdown editor best practices](https://mdwrk.com/markdown/markdown-editor/best-practices/) - Markdown editor best practices help teams keep Markdown workflows portable, readable, reviewable, and easier to publish.
+- [Markdown editor checklist](https://mdwrk.com/markdown/markdown-editor/checklist/) - A Markdown editor checklist helps teams review authoring, preview, storage, portability, and publishing concerns before choosing or expanding a Markdown workflow.
+- [Markdown editor examples](https://mdwrk.com/markdown/markdown-editor/examples/) - Markdown editor examples show how this Markdown workflow appears in practical authoring, preview, review, and publishing situations.
+- [Markdown editor for developers](https://mdwrk.com/markdown/markdown-editor/for-developers/) - Markdown editor for developers focuses on Markdown workflows that intersect with repositories, package reuse, and code-adjacent documentation.
+- [Markdown editor for teams](https://mdwrk.com/markdown/markdown-editor/for-teams/) - Markdown editor for teams focuses on shared Markdown workflows, review paths, ownership boundaries, and publishing expectations.
+- [Markdown editor use cases](https://mdwrk.com/markdown/markdown-editor/use-cases/) - Markdown editor use cases cover the practical situations where teams choose this Markdown workflow, surface, or document model.
+- [Markdown editor workflow](https://mdwrk.com/markdown/markdown-editor/workflow/) - Markdown editor workflow guidance explains how authors move from Markdown drafting to preview, review, packaging, and publishing.
+- [Benefits of markdown extension workflows](https://mdwrk.com/markdown/markdown-extension-workflows/benefits/) - The benefits of Markdown extension workflows usually include source readability, workflow clarity, portability, and better alignment between writing and publishing.
+- [Markdown extension workflows best practices](https://mdwrk.com/markdown/markdown-extension-workflows/best-practices/) - Markdown extension workflows best practices help teams keep Markdown workflows portable, readable, reviewable, and easier to publish.
+- [Markdown extension workflows checklist](https://mdwrk.com/markdown/markdown-extension-workflows/checklist/) - A Markdown extension workflows checklist helps teams review authoring, preview, storage, portability, and publishing concerns before choosing or expanding a Markdown workflow.
+- [Markdown extension workflows examples](https://mdwrk.com/markdown/markdown-extension-workflows/examples/) - Markdown extension workflows examples show how this Markdown workflow appears in practical authoring, preview, review, and publishing situations.
+- [Markdown extension workflows for developers](https://mdwrk.com/markdown/markdown-extension-workflows/for-developers/) - Markdown extension workflows for developers focuses on Markdown workflows that intersect with repositories, package reuse, and code-adjacent documentation.
+- [Markdown extension workflows for teams](https://mdwrk.com/markdown/markdown-extension-workflows/for-teams/) - Markdown extension workflows for teams focuses on shared Markdown workflows, review paths, ownership boundaries, and publishing expectations.
+- [Markdown extension workflows use cases](https://mdwrk.com/markdown/markdown-extension-workflows/use-cases/) - Markdown extension workflows use cases cover the practical situations where teams choose this Markdown workflow, surface, or document model.
+- [Markdown extension workflows workflow](https://mdwrk.com/markdown/markdown-extension-workflows/workflow/) - Markdown extension workflows workflow guidance explains how authors move from Markdown drafting to preview, review, packaging, and publishing.
+- [Benefits of markdown for developers](https://mdwrk.com/markdown/markdown-for-developers/benefits/) - The benefits of Markdown for developers usually include source readability, workflow clarity, portability, and better alignment between writing and publishing.
+- [Markdown for developers best practices](https://mdwrk.com/markdown/markdown-for-developers/best-practices/) - Markdown for developers best practices help teams keep Markdown workflows portable, readable, reviewable, and easier to publish.
+- [Markdown for developers checklist](https://mdwrk.com/markdown/markdown-for-developers/checklist/) - A Markdown for developers checklist helps teams review authoring, preview, storage, portability, and publishing concerns before choosing or expanding a Markdown workflow.
+- [Markdown for developers examples](https://mdwrk.com/markdown/markdown-for-developers/examples/) - Markdown for developers examples show how this Markdown workflow appears in practical authoring, preview, review, and publishing situations.
+- [Markdown for developers for developers](https://mdwrk.com/markdown/markdown-for-developers/for-developers/) - Markdown for developers for developers focuses on Markdown workflows that intersect with repositories, package reuse, and code-adjacent documentation.
+- [Markdown for developers for teams](https://mdwrk.com/markdown/markdown-for-developers/for-teams/) - Markdown for developers for teams focuses on shared Markdown workflows, review paths, ownership boundaries, and publishing expectations.
+- [Markdown for developers use cases](https://mdwrk.com/markdown/markdown-for-developers/use-cases/) - Markdown for developers use cases cover the practical situations where teams choose this Markdown workflow, surface, or document model.
+- [Markdown for developers workflow](https://mdwrk.com/markdown/markdown-for-developers/workflow/) - Markdown for developers workflow guidance explains how authors move from Markdown drafting to preview, review, packaging, and publishing.
+- [Benefits of markdown for teams](https://mdwrk.com/markdown/markdown-for-teams/benefits/) - The benefits of Markdown for teams usually include source readability, workflow clarity, portability, and better alignment between writing and publishing.
+- [Markdown for teams best practices](https://mdwrk.com/markdown/markdown-for-teams/best-practices/) - Markdown for teams best practices help teams keep Markdown workflows portable, readable, reviewable, and easier to publish.
+- [Markdown for teams checklist](https://mdwrk.com/markdown/markdown-for-teams/checklist/) - A Markdown for teams checklist helps teams review authoring, preview, storage, portability, and publishing concerns before choosing or expanding a Markdown workflow.
+- [Markdown for teams examples](https://mdwrk.com/markdown/markdown-for-teams/examples/) - Markdown for teams examples show how this Markdown workflow appears in practical authoring, preview, review, and publishing situations.
+- [Markdown for teams for developers](https://mdwrk.com/markdown/markdown-for-teams/for-developers/) - Markdown for teams for developers focuses on Markdown workflows that intersect with repositories, package reuse, and code-adjacent documentation.
+- [Markdown for teams for teams](https://mdwrk.com/markdown/markdown-for-teams/for-teams/) - Markdown for teams for teams focuses on shared Markdown workflows, review paths, ownership boundaries, and publishing expectations.
+- [Markdown for teams use cases](https://mdwrk.com/markdown/markdown-for-teams/use-cases/) - Markdown for teams use cases cover the practical situations where teams choose this Markdown workflow, surface, or document model.
+- [Markdown for teams workflow](https://mdwrk.com/markdown/markdown-for-teams/workflow/) - Markdown for teams workflow guidance explains how authors move from Markdown drafting to preview, review, packaging, and publishing.
+- [Benefits of markdown knowledge base](https://mdwrk.com/markdown/markdown-knowledge-base/benefits/) - The benefits of Markdown knowledge base usually include source readability, workflow clarity, portability, and better alignment between writing and publishing.
+- [Markdown knowledge base best practices](https://mdwrk.com/markdown/markdown-knowledge-base/best-practices/) - Markdown knowledge base best practices help teams keep Markdown workflows portable, readable, reviewable, and easier to publish.
+- [Markdown knowledge base checklist](https://mdwrk.com/markdown/markdown-knowledge-base/checklist/) - A Markdown knowledge base checklist helps teams review authoring, preview, storage, portability, and publishing concerns before choosing or expanding a Markdown workflow.
+- [Markdown knowledge base examples](https://mdwrk.com/markdown/markdown-knowledge-base/examples/) - Markdown knowledge base examples show how this Markdown workflow appears in practical authoring, preview, review, and publishing situations.
+- [Markdown knowledge base for developers](https://mdwrk.com/markdown/markdown-knowledge-base/for-developers/) - Markdown knowledge base for developers focuses on Markdown workflows that intersect with repositories, package reuse, and code-adjacent documentation.
+- [Markdown knowledge base for teams](https://mdwrk.com/markdown/markdown-knowledge-base/for-teams/) - Markdown knowledge base for teams focuses on shared Markdown workflows, review paths, ownership boundaries, and publishing expectations.
+- [Markdown knowledge base use cases](https://mdwrk.com/markdown/markdown-knowledge-base/use-cases/) - Markdown knowledge base use cases cover the practical situations where teams choose this Markdown workflow, surface, or document model.
+- [Markdown knowledge base workflow](https://mdwrk.com/markdown/markdown-knowledge-base/workflow/) - Markdown knowledge base workflow guidance explains how authors move from Markdown drafting to preview, review, packaging, and publishing.
+- [Benefits of markdown notes](https://mdwrk.com/markdown/markdown-notes/benefits/) - The benefits of Markdown notes usually include source readability, workflow clarity, portability, and better alignment between writing and publishing.
+- [Markdown notes best practices](https://mdwrk.com/markdown/markdown-notes/best-practices/) - Markdown notes best practices help teams keep Markdown workflows portable, readable, reviewable, and easier to publish.
+- [Markdown notes checklist](https://mdwrk.com/markdown/markdown-notes/checklist/) - A Markdown notes checklist helps teams review authoring, preview, storage, portability, and publishing concerns before choosing or expanding a Markdown workflow.
+- [Markdown notes examples](https://mdwrk.com/markdown/markdown-notes/examples/) - Markdown notes examples show how this Markdown workflow appears in practical authoring, preview, review, and publishing situations.
+- [Markdown notes for developers](https://mdwrk.com/markdown/markdown-notes/for-developers/) - Markdown notes for developers focuses on Markdown workflows that intersect with repositories, package reuse, and code-adjacent documentation.
+- [Markdown notes for teams](https://mdwrk.com/markdown/markdown-notes/for-teams/) - Markdown notes for teams focuses on shared Markdown workflows, review paths, ownership boundaries, and publishing expectations.
+- [Markdown notes use cases](https://mdwrk.com/markdown/markdown-notes/use-cases/) - Markdown notes use cases cover the practical situations where teams choose this Markdown workflow, surface, or document model.
+- [Markdown notes workflow](https://mdwrk.com/markdown/markdown-notes/workflow/) - Markdown notes workflow guidance explains how authors move from Markdown drafting to preview, review, packaging, and publishing.
+- [Benefits of markdown preview](https://mdwrk.com/markdown/markdown-preview/benefits/) - The benefits of Markdown preview usually include source readability, workflow clarity, portability, and better alignment between writing and publishing.
+- [Markdown preview best practices](https://mdwrk.com/markdown/markdown-preview/best-practices/) - Markdown preview best practices help teams keep Markdown workflows portable, readable, reviewable, and easier to publish.
+- [Markdown preview checklist](https://mdwrk.com/markdown/markdown-preview/checklist/) - A Markdown preview checklist helps teams review authoring, preview, storage, portability, and publishing concerns before choosing or expanding a Markdown workflow.
+- [Markdown preview examples](https://mdwrk.com/markdown/markdown-preview/examples/) - Markdown preview examples show how this Markdown workflow appears in practical authoring, preview, review, and publishing situations.
+- [Markdown preview for developers](https://mdwrk.com/markdown/markdown-preview/for-developers/) - Markdown preview for developers focuses on Markdown workflows that intersect with repositories, package reuse, and code-adjacent documentation.
+- [Markdown preview for teams](https://mdwrk.com/markdown/markdown-preview/for-teams/) - Markdown preview for teams focuses on shared Markdown workflows, review paths, ownership boundaries, and publishing expectations.
+- [Markdown preview use cases](https://mdwrk.com/markdown/markdown-preview/use-cases/) - Markdown preview use cases cover the practical situations where teams choose this Markdown workflow, surface, or document model.
+- [Markdown preview workflow](https://mdwrk.com/markdown/markdown-preview/workflow/) - Markdown preview workflow guidance explains how authors move from Markdown drafting to preview, review, packaging, and publishing.
+- [Benefits of markdown project docs](https://mdwrk.com/markdown/markdown-project-docs/benefits/) - The benefits of Markdown project docs usually include source readability, workflow clarity, portability, and better alignment between writing and publishing.
+- [Markdown project docs best practices](https://mdwrk.com/markdown/markdown-project-docs/best-practices/) - Markdown project docs best practices help teams keep Markdown workflows portable, readable, reviewable, and easier to publish.
+- [Markdown project docs checklist](https://mdwrk.com/markdown/markdown-project-docs/checklist/) - A Markdown project docs checklist helps teams review authoring, preview, storage, portability, and publishing concerns before choosing or expanding a Markdown workflow.
+- [Markdown project docs examples](https://mdwrk.com/markdown/markdown-project-docs/examples/) - Markdown project docs examples show how this Markdown workflow appears in practical authoring, preview, review, and publishing situations.
+- [Markdown project docs for developers](https://mdwrk.com/markdown/markdown-project-docs/for-developers/) - Markdown project docs for developers focuses on Markdown workflows that intersect with repositories, package reuse, and code-adjacent documentation.
+- [Markdown project docs for teams](https://mdwrk.com/markdown/markdown-project-docs/for-teams/) - Markdown project docs for teams focuses on shared Markdown workflows, review paths, ownership boundaries, and publishing expectations.
+- [Markdown project docs use cases](https://mdwrk.com/markdown/markdown-project-docs/use-cases/) - Markdown project docs use cases cover the practical situations where teams choose this Markdown workflow, surface, or document model.
+- [Markdown project docs workflow](https://mdwrk.com/markdown/markdown-project-docs/workflow/) - Markdown project docs workflow guidance explains how authors move from Markdown drafting to preview, review, packaging, and publishing.
+- [Benefits of markdown readme](https://mdwrk.com/markdown/markdown-readme/benefits/) - The benefits of Markdown README usually include source readability, workflow clarity, portability, and better alignment between writing and publishing.
+- [Markdown README best practices](https://mdwrk.com/markdown/markdown-readme/best-practices/) - Markdown README best practices help teams keep Markdown workflows portable, readable, reviewable, and easier to publish.
+- [Markdown README checklist](https://mdwrk.com/markdown/markdown-readme/checklist/) - A Markdown README checklist helps teams review authoring, preview, storage, portability, and publishing concerns before choosing or expanding a Markdown workflow.
+- [Markdown README examples](https://mdwrk.com/markdown/markdown-readme/examples/) - Markdown README examples show how this Markdown workflow appears in practical authoring, preview, review, and publishing situations.
+- [Markdown README for developers](https://mdwrk.com/markdown/markdown-readme/for-developers/) - Markdown README for developers focuses on Markdown workflows that intersect with repositories, package reuse, and code-adjacent documentation.
+- [Markdown README for teams](https://mdwrk.com/markdown/markdown-readme/for-teams/) - Markdown README for teams focuses on shared Markdown workflows, review paths, ownership boundaries, and publishing expectations.
+- [Markdown README use cases](https://mdwrk.com/markdown/markdown-readme/use-cases/) - Markdown README use cases cover the practical situations where teams choose this Markdown workflow, surface, or document model.
+- [Markdown README workflow](https://mdwrk.com/markdown/markdown-readme/workflow/) - Markdown README workflow guidance explains how authors move from Markdown drafting to preview, review, packaging, and publishing.
+- [Benefits of markdown theme packs](https://mdwrk.com/markdown/markdown-theme-packs/benefits/) - The benefits of Markdown theme packs usually include source readability, workflow clarity, portability, and better alignment between writing and publishing.
+- [Markdown theme packs best practices](https://mdwrk.com/markdown/markdown-theme-packs/best-practices/) - Markdown theme packs best practices help teams keep Markdown workflows portable, readable, reviewable, and easier to publish.
+- [Markdown theme packs checklist](https://mdwrk.com/markdown/markdown-theme-packs/checklist/) - A Markdown theme packs checklist helps teams review authoring, preview, storage, portability, and publishing concerns before choosing or expanding a Markdown workflow.
+- [Markdown theme packs examples](https://mdwrk.com/markdown/markdown-theme-packs/examples/) - Markdown theme packs examples show how this Markdown workflow appears in practical authoring, preview, review, and publishing situations.
+- [Markdown theme packs for developers](https://mdwrk.com/markdown/markdown-theme-packs/for-developers/) - Markdown theme packs for developers focuses on Markdown workflows that intersect with repositories, package reuse, and code-adjacent documentation.
+- [Markdown theme packs for teams](https://mdwrk.com/markdown/markdown-theme-packs/for-teams/) - Markdown theme packs for teams focuses on shared Markdown workflows, review paths, ownership boundaries, and publishing expectations.
+- [Markdown theme packs use cases](https://mdwrk.com/markdown/markdown-theme-packs/use-cases/) - Markdown theme packs use cases cover the practical situations where teams choose this Markdown workflow, surface, or document model.
+- [Markdown theme packs workflow](https://mdwrk.com/markdown/markdown-theme-packs/workflow/) - Markdown theme packs workflow guidance explains how authors move from Markdown drafting to preview, review, packaging, and publishing.
+- [Benefits of markdown writing workflow](https://mdwrk.com/markdown/markdown-writing-workflow/benefits/) - The benefits of Markdown writing workflow usually include source readability, workflow clarity, portability, and better alignment between writing and publishing.
+- [Markdown writing workflow best practices](https://mdwrk.com/markdown/markdown-writing-workflow/best-practices/) - Markdown writing workflow best practices help teams keep Markdown workflows portable, readable, reviewable, and easier to publish.
+- [Markdown writing workflow checklist](https://mdwrk.com/markdown/markdown-writing-workflow/checklist/) - A Markdown writing workflow checklist helps teams review authoring, preview, storage, portability, and publishing concerns before choosing or expanding a Markdown workflow.
+- [Markdown writing workflow examples](https://mdwrk.com/markdown/markdown-writing-workflow/examples/) - Markdown writing workflow examples show how this Markdown workflow appears in practical authoring, preview, review, and publishing situations.
+- [Markdown writing workflow for developers](https://mdwrk.com/markdown/markdown-writing-workflow/for-developers/) - Markdown writing workflow for developers focuses on Markdown workflows that intersect with repositories, package reuse, and code-adjacent documentation.
+- [Markdown writing workflow for teams](https://mdwrk.com/markdown/markdown-writing-workflow/for-teams/) - Markdown writing workflow for teams focuses on shared Markdown workflows, review paths, ownership boundaries, and publishing expectations.
+- [Markdown writing workflow use cases](https://mdwrk.com/markdown/markdown-writing-workflow/use-cases/) - Markdown writing workflow use cases cover the practical situations where teams choose this Markdown workflow, surface, or document model.
+- [Markdown writing workflow workflow](https://mdwrk.com/markdown/markdown-writing-workflow/workflow/) - Markdown writing workflow workflow guidance explains how authors move from Markdown drafting to preview, review, packaging, and publishing.
+- [Benefits of offline markdown editor](https://mdwrk.com/markdown/offline-markdown-editor/benefits/) - The benefits of Offline Markdown editor usually include source readability, workflow clarity, portability, and better alignment between writing and publishing.
+- [Offline Markdown editor best practices](https://mdwrk.com/markdown/offline-markdown-editor/best-practices/) - Offline Markdown editor best practices help teams keep Markdown workflows portable, readable, reviewable, and easier to publish.
+- [Offline Markdown editor checklist](https://mdwrk.com/markdown/offline-markdown-editor/checklist/) - A Offline Markdown editor checklist helps teams review authoring, preview, storage, portability, and publishing concerns before choosing or expanding a Markdown workflow.
+- [Offline Markdown editor examples](https://mdwrk.com/markdown/offline-markdown-editor/examples/) - Offline Markdown editor examples show how this Markdown workflow appears in practical authoring, preview, review, and publishing situations.
+- [Offline Markdown editor for developers](https://mdwrk.com/markdown/offline-markdown-editor/for-developers/) - Offline Markdown editor for developers focuses on Markdown workflows that intersect with repositories, package reuse, and code-adjacent documentation.
+- [Offline Markdown editor for teams](https://mdwrk.com/markdown/offline-markdown-editor/for-teams/) - Offline Markdown editor for teams focuses on shared Markdown workflows, review paths, ownership boundaries, and publishing expectations.
+- [Offline Markdown editor use cases](https://mdwrk.com/markdown/offline-markdown-editor/use-cases/) - Offline Markdown editor use cases cover the practical situations where teams choose this Markdown workflow, surface, or document model.
+- [Offline Markdown editor workflow](https://mdwrk.com/markdown/offline-markdown-editor/workflow/) - Offline Markdown editor workflow guidance explains how authors move from Markdown drafting to preview, review, packaging, and publishing.
+- [How to write Markdown](https://mdwrk.com/markdown/how-to-write-markdown/) - Learn how to write Markdown using headings, lists, links, emphasis, code fences, images, and other basic plain-text formatting patterns.
+- [Markdown](https://mdwrk.com/markdown/) - Learn what Markdown is, how Markdown writing and preview workflows work, and where MdWrk fits across local-first editing, rendering, and reusable package surfaces.
+- [Markdown vs HTML](https://mdwrk.com/markdown/markdown-vs-html/) - Compare Markdown and HTML for readability, authoring speed, portability, document control, and direct publishing workflows.
+- [What is a Markdown editor?](https://mdwrk.com/markdown/what-is-a-markdown-editor/) - A Markdown editor is a writing tool for creating and editing Markdown documents, often with preview, syntax highlighting, shortcuts, and file organization.
+- [What is Markdown used for?](https://mdwrk.com/markdown/what-is-markdown-used-for/) - Markdown is used for documentation, README files, notes, blog drafts, knowledge bases, technical writing, and other portable plain-text publishing workflows.
+- [What is Markdown?](https://mdwrk.com/markdown/what-is-markdown/) - Markdown is a lightweight plain-text writing format that uses readable symbols for headings, lists, links, emphasis, code blocks, and other document structure.
+- [@mdwrk/extension-runtime](https://mdwrk.com/packages/extension-runtime/) - The @mdwrk/extension-runtime package provides portable runtime utilities for governed MdWrk extension behavior.
+- [Packages](https://mdwrk.com/packages/) - Explore MdWrk packages for Markdown rendering, React integration, editor components, theme contracts, and extension runtime behavior.
+- [@mdwrk/markdown-editor-react](https://mdwrk.com/packages/markdown-editor-react/) - The @mdwrk/markdown-editor-react package provides React Markdown editor components for embedding MdWrk-style authoring surfaces.
+- [@mdwrk/markdown-renderer-core](https://mdwrk.com/packages/markdown-renderer-core/) - The @mdwrk/markdown-renderer-core package provides self-contained Markdown parsing and rendering utilities for package-level preview and HTML output.
+- [@mdwrk/markdown-renderer-react](https://mdwrk.com/packages/markdown-renderer-react/) - The @mdwrk/markdown-renderer-react package provides React bindings for rendering Markdown through the same package family used by MdWrk.
+- [@mdwrk/theme-contract](https://mdwrk.com/packages/theme-contract/) - The @mdwrk/theme-contract package defines theme token and compatibility contracts for MdWrk editor, preview, extension, and lander surfaces.
+- [Privacy policy](https://mdwrk.com/privacy/) - MdWrk privacy documentation explains the local-first storage model, explicit sharing boundaries, GitHub integration expectations, and extension trust policy.
+- [Browser support proof](https://mdwrk.com/proof/browser-support/) - MdWrk documents browser and PWA behavior as governed public product surfaces with static lander evidence.
+- [Markdown support proof](https://mdwrk.com/proof/markdown-support/) - MdWrk aligns Markdown editing and preview behavior with reusable renderer and editor package surfaces.
+- [Package surfaces proof](https://mdwrk.com/proof/package-surfaces/) - MdWrk exposes reusable package surfaces separately from the MdWrk-specific marketing and documentation content pack.
+- [Security notes](https://mdwrk.com/security/) - MdWrk security notes explain package boundaries, extension trust, static content verification, robots policy, and deployable artifact checks.
+- [Privacy boundary](https://mdwrk.com/trust/privacy-boundary/) - MdWrk keeps normal authoring local-first and makes sync, export, repository movement, and hosted integrations explicit boundaries.
+- [Getting Started](https://mdwrk.com/docs/) - Start using MdWrk with browser, PWA, local setup, configuration, and standalone package guidance.
+- [Client Installation](https://mdwrk.com/docs/getting-started/installation/) - Use the browser route for immediate access, the PWA route for an installable shell, local setup for development control, or standalone modules for package-level adoption.
+- [Browser Use](https://mdwrk.com/docs/getting-started/browser-use/) - The browser path runs the MdWrk client directly in a supported browser, keeps documents local by default, and remains usable offline after app assets are cached.
+- [PWA Installation](https://mdwrk.com/docs/getting-started/pwa-installation/) - The Progressive Web App path keeps the MdWrk client in the web platform, but lets supported browsers install it as a dedicated app window.
+- [Local Setup](https://mdwrk.com/docs/getting-started/local-setup/) - This path is for maintainers, internal adopters, and self-hosting operators who want more control than the browser or PWA flows provide.
+- [Standalone Modules](https://mdwrk.com/docs/getting-started/standalone-modules/) - MdWrk standalone modules expose the editor, renderer, extension contracts, theme tokens, and installable extension packages as reusable package surfaces.
+- [Client Configuration](https://mdwrk.com/docs/getting-started/configuration/) - Theme Selection Open Settings -> Theme to switch between built-in theme families. Themes are contract-backed and flow through the editor, preview, export, and extension theme APIs.
+- [Editor Basics](https://mdwrk.com/features/editor-basics/) - MdWrk combines a markdown source editor, split preview workflow, table builder, formatting toolbar, and local-first workspace model so drafting stays fast without hiding the underlying Markdown.
+- [Markdown Formatting](https://mdwrk.com/features/advanced-formatting/) - 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.
+- [Rendering And Preview](https://mdwrk.com/features/rendering-and-preview/) - MdWrk turns Markdown into a live rendered preview with internal-link navigation, profile-aware HTML handling, policy advisories, and export paths that stay aligned with the on-screen renderer.
+- [Checkbox Autocomplete](https://mdwrk.com/features/checkbox-autocomplete/) - Checkbox autocomplete documents how MdWrk turns list authoring into task-list Markdown while preserving plain-text portability.
+- [Text Wrap Previewer](https://mdwrk.com/features/text-wrap-previewer/) - Text wrap previewer documents how MdWrk keeps source wrapping, preview wrapping, and line-number rhythm readable across pane sizes.
+- [View Toolbar](https://mdwrk.com/features/view-toolbar/) - View toolbar documents the MdWrk controls for switching editor, split, and preview modes while keeping export and formatting actions discoverable.
+- [Offline Markdown Editor](https://mdwrk.com/features/offline-markdown-editor/) - 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.
+- [Local-first Markdown Workspace](https://mdwrk.com/features/local-first-markdown-workspace/) - MdWrk is a local-first Markdown workspace for projects, folders, files, preview links, themes, and extensions that should remain usable without forcing a cloud document model.
+- [Privacy-first Markdown Editor](https://mdwrk.com/features/privacy-first-markdown-editor/) - 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.
+- [Markdown File Manager](https://mdwrk.com/features/markdown-file-manager/) - MdWrk manages Markdown projects, files, folders, preview navigation, and workspace entries so documents stay organized inside the same surface where they are written.
+- [Markdown Preview Editor](https://mdwrk.com/features/markdown-preview-editor/) - MdWrk combines a Markdown source editor with live preview, profile-aware rendering, internal-link navigation, HTML export, and print-oriented output.
+- [Extension Host](https://mdwrk.com/features/extension-host/) - MdWrk includes a governed extension host with manifest, runtime, capability, trust, settings, command, view, diagnostics, theme, and language-pack surfaces.
+- [Desktop App Boundary](https://mdwrk.com/features/desktop-app-boundary/) - The desktop app boundary explains how MdWrk separates the browser workspace, Electron shell, preload bridge, and host filesystem access.
+- [Theme Packs](https://mdwrk.com/features/theme-packs/) - 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.
+- [Developer Documentation](https://mdwrk.com/features/developer-documentation/) - MdWrk developer documentation covers local setup, standalone packages, editor and renderer modules, extension authoring, theme packs, language packs, and package-level adoption paths.
+- [Markdown Profile Architecture](https://mdwrk.com/features/markdown-profile-architecture/) - Markdown profile architecture describes how MdWrk separates CommonMark, GFM, custom profile options, renderer configuration, and evidence snapshots.
+- [UIX Responsive Contract](https://mdwrk.com/features/uix-responsive-contract/) - The UIX responsive contract documents MdWrk viewport bands, aspect-ratio bands, height tiers, device classes, and theme responsibilities.
+- [Github Sync](https://mdwrk.com/docs/github-sync/) - Repository Access Use a GitHub personal access token with the narrowest permissions your workflow requires. Store the token only when you want mdwrk to read from or write to a repository.
+- [Authoring Overview](https://mdwrk.com/docs/authoring/overview/) - MdWrk authoring documentation groups extension, theme pack, and language pack workflows into focused surfaces for package and product contributors.
+- [Extension Authoring](https://mdwrk.com/docs/authoring/extensions/) - Extension authoring covers manifest shape, host APIs, activation lifecycle, package-local source, generated bundles, and trust metadata for MdWrk extensions.
+- [Extension Authoring Guide](https://mdwrk.com/docs/authoring/extension-authoring-guide/) - The extension authoring guide gives package authors the current MdWrk workflow for manifests, host APIs, runtime activation, tests, bundles, and publishing artifacts.
+- [Theme Pack Authoring](https://mdwrk.com/docs/authoring/theme-packs/) - Theme pack authoring uses MdWrk theme contracts, Theme Studio workflows, token exports, and package-ready surfaces for consistent editor and preview styling.
+- [Language Pack Authoring](https://mdwrk.com/docs/authoring/language-packs/) - Language pack authoring uses the first-party studio package, locale catalogs, validation flows, export behavior, and host surfaces for MdWrk localization.
+- [Extension Platform](https://mdwrk.com/docs/extensions/extension-platform/) - MdWrk extensions are governed through manifest metadata, host APIs, runtime activation, manager UX, settings, permissions, and compatibility checks.
+- [Theme Studio And Host Surfaces](https://mdwrk.com/docs/extensions/theme-studio-and-host-surfaces/) - Theme Studio demonstrates how first-party extensions use host surfaces, theme contracts, workspace panes, and export flows inside the MdWrk extension model.
+- [MdWrk Vs Marktext](https://mdwrk.com/compare/marktext/) - Compare MdWrk and MarkText when choosing between a local-first Markdown workspace with reusable packages and a focused desktop Markdown editor.
+- [MdWrk Vs Zettlr](https://mdwrk.com/compare/zettlr/) - Compare MdWrk and Zettlr when choosing between a local-first Markdown workspace and a research-oriented Markdown writing environment.
+- [MdWrk Vs Notion](https://mdwrk.com/compare/notion/) - Compare MdWrk and Notion when choosing between local Markdown files and a hosted collaborative workspace.
+- [MdWrk Vs Logseq](https://mdwrk.com/compare/logseq/) - Compare MdWrk and Logseq when choosing between Markdown workspace authoring and an outline-first knowledge graph workflow.
+- [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.
+- [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.
+- [Workspace Files and Git Operations Packages Open a Larger Automation Surface for MdWrk](https://mdwrk.com/updates/workspace-files-and-git-ops-packages/) - 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](https://mdwrk.com/updates/desktop-release-and-android-verification/) - 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](https://mdwrk.com/updates/retained-client-versions-and-desktop-shell/) - 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](https://mdwrk.com/updates/screenshot-matrix-and-browser-sidebars/) - 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](https://mdwrk.com/updates/extension-compatibility-and-publish-gates/) - 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](https://mdwrk.com/updates/governed-releases-and-package-docs/) - 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](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.
+- [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.
+- [Privacy Policy](https://mdwrk.com/legal/privacy/) - At MdWrk , we believe privacy is a fundamental human right. Our software is designed so that your data never touches our servers. Data Collection We do not collect, store, or process any of your personal data. All markdo...
+- [Terms of Service](https://mdwrk.com/legal/terms/) - Welcome to MdWrk. By using this application, you agree to the following: "As-Is" Software MdWrk is provided "as is" without any warranties. Ownership You own 100% of the content you create. Compliance MdWrk is intended f...

package/generated/robots.txt

@@ -0,0 +1,28 @@
+# MdWrk governed crawler policy
+# Categories: search-inclusion, answer-retrieval, training-ingestion
+User-agent: *
+# Category: search-inclusion
+# Purpose: general public indexing
+Allow: /
+
+User-agent: OAI-SearchBot
+# Category: answer-retrieval
+# Purpose: OpenAI search and answer retrieval
+Allow: /
+
+User-agent: ChatGPT-User
+# Category: answer-retrieval
+# Purpose: user-initiated browsing and answer retrieval
+Allow: /
+
+User-agent: GPTBot
+# Category: training-ingestion
+# Purpose: OpenAI model training ingestion
+Disallow: /
+
+User-agent: CCBot
+# Category: training-ingestion
+# Purpose: Common Crawl model training ingestion
+Disallow: /
+
+Sitemap: https://mdwrk.com/sitemap.xml