How to separate content(markdown files) and deploy

[zhangjianrencai]

Suppose we have a scenario:
User A: responsible for write markdown files, he doesn't know technical.
User B: responsible for deploy these markdown files, he doesn't know the content of the markdown files.

How to combine these two users work automatically. for example, User A can deploy these markdown files by himself after he upload these markdown files? Is there any good practise about this?

[slorber]

User A can write the Markdon files, and User B can set up a continuous integration server to automatically deploy them on change.

There are various ways to set this up, but the easiest is probably:

• User A commits Markdown files to Git
• User B uses a CDN hosting platform such as Vercel/Netlify to deploy the Git repository automatically on new commits

User A has to be at least technical a bit, since Markdown is a markup language and MDX is even more technical than basic CommonMark (MDX is stricter, allowing JSX inside content). If commiting to Git or opening a PR is too technical for User A, then you can set up a Git-based CMS (Tina, Decap...) or use a convenient interface to edit the Git repository (GitHub interface, StackBlitz Web Publisher or something else)