Client Configuration

By CobyCloud

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.

Workspace Defaults

  • Autosave: Enabled by default for local-first persistence.
  • Default View: Choose Editor, Preview, or Split to match your writing style.
  • Markdown Profiles: Enable optional profile features without forking the renderer.
  • Git Sync: Provide credentials only when you want to push or pull.
  • Extension Settings: First-party and external extensions register their own schema-backed settings panels.

Lander Environment Variables

The lander reads public navigation and metadata values at build time:

VariablePurpose
VITE_SITE_URLCanonical production origin used for sitemap and robots output.
VITE_APP_URLInstalled app URL used by hero app-entry actions.
VITE_DEMO_URLURL for the live demo call to action.
VITE_GITHUB_REPO_URLRepository link used by the header GitHub action.
VITE_NPM_REPO_URLnpm organization or package URL.
VITE_NPM_CLIENT_VERSIONPublished client package version shown in the hero.
VITE_NPM_ESM_CDN_URLESM CDN URL used by package examples.
VITE_X_URLX profile URL shown in the footer.
VITE_COMMUNITY_URLCommunity destination shown in the footer.

Defaults are kept in the lander source so local builds remain usable without a full environment file.

Reverse Proxy

Run the lander container on the internal Docker network and route traffic through your reverse proxy.

Package-Level Configuration

If you consume the split packages directly:

  • @mdwrk/markdown-editor-react owns source-authoring behavior.
  • @mdwrk/markdown-renderer-react owns rendered markdown output.
  • @mdwrk/theme-contract owns theme token and bridge compatibility.

Metadata and Discovery

The lander includes production metadata for:

  • canonical links
  • Open Graph previews
  • Twitter card previews
  • favicon assets
  • robots.txt
  • llms.txt
  • generated sitemap.xml

Regenerate the sitemap during every production build so public routes stay aligned with the current Markdown docs.

Frequently Asked Questions

What will I learn from Client 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.

Who should read Client Configuration?

Read this page if you need practical MdWrk guidance for client configuration, including the relevant workflow, product surface, and follow-up documentation paths.