use case · static sites
Blog posts for static sites in git
If your blog is a folder of markdown files in a GitHub repo, you already have the best review tool there is: the pull request. Magic Share uses it. Press “Open PR on GitHub” on a draft you’re happy with (or, on Starter and Pro, schedule it) and the post arrives as a PR against your repo. It goes live when you merge it, the same way your own changes do.
Setting it up
In the site’s settings you give Magic Share four things:
- the repository, as owner/repo, and the base branch (blank means the default);
- the content directory the post files go in (blank means
content/blog); - your live URL pattern, such as
https://yoursite.com/blog/{slug}, so the X thread can link to the published post; - a fine-grained GitHub token with contents and pull-requests write access on that one repo.
What a pull request contains
Exactly one markdown file: YAML frontmatter (title, description, slug, date, tags and target keyword, each validated for length and shape) and the post body. The hero image is served from a stable Magic Share URL, so there’s no binary to commit.
Before the file is pushed it’s scanned for active content, so a post can’t carry a script into your repo. When Magic Share merges a scheduled post, it first re-reads the PR from GitHub and confirms it’s still one file, at the expected path, identical to the post you approved. A commit pushed after that check makes the merge fail instead of shipping.
Merge it yourself, or schedule it
Merge the PR when you’re ready, and your host’s usual build publishes it. Or, on Starter and Pro, schedule the approved post: at the time you picked Magic Share opens the PR, verifies it, merges it and, if you’ve connected X, posts the thread with the live link. Either way the decision was yours. See the approval flow.
Links that point forward, too
New posts link back to your older ones as they’re written. After a post publishes, the agent can also propose one linking sentence in up to three related older posts, as a separate PR. You read the diff and merge it or close it; it’s never merged for you.
What your generator needs
Each post lands at <content directory>/<slug>.md, and its hero image and any data cards are plain HTML <img> tags inside the markdown. So any generator that builds pages from a folder of markdown files can take the posts, as long as it reads files named by slug and lets raw HTML through. Magic Share’s own blog is published exactly this way.
- Hugo leaves raw HTML out by default, so the images won’t show until you set
markup.goldmark.renderer.unsafeto true. - Jekyll expects files in
_poststo be named with the date first (2026-10-20-my-post.md), and these files are named by slug alone, so point the content directory at a collection instead.
When it isn’t a fit
- Your repo isn’t on GitHub. Publishing talks to GitHub only. You can still download each post as markdown.
- Your template expects different frontmatter. The field names are fixed, so a theme that wants, say,
summaryinstead ofdescriptionneeds a small mapping on your side. - Your blog lives in a CMS. There’s no WordPress or Webflow connection; see the comparison with SEObot for a tool that has them.