GitHub MDX publishing for Content Engine

Content Engine can now publish Studio assets to your website's GitHub repository as MDX. Map directories in the repo to content types (for example content/blog for blog posts, content/customers for case studies), choose a strict blog format with authors, categories, and tags or a lighter generic MDX format, and publish through a pull request or a direct commit.

Every publish is validated before it reaches GitHub. Direct commits can trigger your site's deploy hook so the change goes live without extra steps, and PR publishes build when the PR is merged. Authors, categories, and tags are picked from your repo's taxonomy files, and new entries are only added when you explicitly create them.

Only the teammate who connects GitHub can change the token, repository, or directory mappings, and everyone else sees who to contact. Once a token is entered you can pick branches and click through the repo's folders instead of typing paths, and each publish is checked against the frontmatter of posts already in that folder so mismatched fields are caught before they break your site's build.