GitHub integration
Edward AI SEOon GitHub.
Edward commits each post — and its images — straight to your GitHub repo as Markdown/MDX. Your existing Vercel (or any git) deploy takes it live. No CMS, no copy-paste.
Works with any git-deployed site. Commit to a branch, or open a pull request.
Publishing as a commit.
A commit per post.
Each article lands as a Markdown/MDX file under content/blog/, with clean frontmatter — reviewable, editable, and revertable like any change.
Images come along.
Covers and in-body images are committed beside the post and served from your own site, so next/image just works — nothing hotlinked.
Live on your next deploy.
Vercel (or Netlify, Cloudflare Pages, a GitHub Action) picks up the commit and ships it. Edward never touches your hosting.
Why GitHub + Edward
Plenty of sites are just a git repo on Vercel — no CMS to publish into. Edward treats the repo as the CMS: it commits search-ready posts as MDX, your build does the rest, and every post is an auditable commit you own.
How it works
Connect in three steps.
01
Create a token.
A fine-grained GitHub token scoped to your repo with Contents: Read and write.
02
Pick your repo.
Paste owner/repo, the branch, and where posts should live (defaults to content/blog).
03
Publish.
Edward commits each article and your deploy takes it live — or opens a PR if you want to review first.
FAQ
Questions, answered.
- Do I need to install an app?
- Not for the token path — create a fine-grained GitHub token with Contents: Read and write, paste it into Edward, and choose your repo. A one-click GitHub App is on the way.
- What exactly does Edward commit?
- One Markdown/MDX file per post under content/blog/<slug>, plus its images under public/blog/<slug>/. Both land in a single commit, so it's one clean deploy.
- Will it work with my blog?
- If your site reads MDX from a content folder, yes. If you don't have a blog yet, the setup page includes a one-paste prompt that scaffolds a compatible one.
- Can I review posts before they go live?
- Yes. Choose “Open a pull request” and every post arrives as a PR against your branch — merge when you're happy.
