GitHub sync

GitHub sync supports repository movement for Markdown projects without making every local edit depend on a hosted backend.

GitHub sync is useful when Markdown work needs to move into repository collaboration, review, or publishing workflows. MdWrk keeps that path explicit so local authoring remains understandable before content crosses a network boundary.

This feature page frames GitHub as an integration rather than a default dependency. Authors can write, preview, and organize locally, then choose repository operations when the project needs versioned collaboration.

The portable lander extraction keeps this claim in MdWrk content. Other products can reuse the same lander packages without inheriting GitHub-specific positioning.

Frequently Asked Questions

Does MdWrk support GitHub-oriented workflows?

MdWrk documents GitHub-oriented sync and repository workflows as optional integration paths.

Is GitHub the default storage layer?

No. MdWrk's normal authoring story remains local-first, with GitHub as an explicit integration.