Git static blog

For file-based static blogs where each post is a Markdown file in a Git repo (a common Astro or Next.js content-collection setup). There's no database and no admin panel — so Vireloop publishes the way you already do: it commits a new .md file to your GitHub repo. The push triggers your host's rebuild (e.g. Vercel or Netlify), and the static page regenerates with the new post.

How it works

1. The pipeline finishes an article and produces the canonical output (title, meta, Markdown body, featured image, FAQ, keyword).
2. The connector turns it into a Markdown file with frontmatter that matches your blog's format, then commits it to <contentDir>/<slug>.md via the GitHub API.
3. Your Git host sees the push and rebuilds the site. The post is live once the build finishes (usually a minute or two).

Images are referenced by their URL — the featured image is placed as the first inline image in the body, and in-body images stay inline too, all hosted on Vireloop's CDN exactly like a post that hotlinks a remote image. Nothing is written into your repo except the Markdown file, and because the body is plain Markdown you don't need to allowlist the image host in your build config.

1. Create a GitHub token

In GitHub → Settings → Developer settings → Fine-grained personal access tokens, create a token scoped to just the site's repo with Repository permissions → Contents: Read and write. Copy it — Vireloop stores it encrypted in Vault and never shows it again.

2. Connect the site

1. Onboarding Integration step (or a site's Connection page) → Git static blog.
2. Enter the owner/org, repository, branch (usually main), content directory (e.g. src/content/blog), and file type (.md or .mdx).
3. Optionally set an author name (written into frontmatter) and your public blog URL (used for the published link).
4. Paste the GitHub token and Test connection — it verifies the repo is reachable with write access.

3. What gets committed

Each post is written with frontmatter mapped from the article, followed by the Markdown body:

---
title: "How to Use AI in WordPress: A Practical 2026 Guide"
description: "A hands-on guide to using AI in WordPress in 2026…"
date: "2026-08-04"
updated: "2026-08-04"
author: "The Acme team"
keywords:
  - how to use ai in wordpress
faq:
  - q: "What is the best AI plugin for WordPress?"
    a: "There's no single winner — it depends on the job…"
draft: true            # only present when the article is a draft
---

![Person using AI tools in WordPress](https://<project>.supabase.co/storage/v1/…/cover.png)

**The best AI tool for WordPress depends on the job…**

## How AI tools break down in 2026
…full Markdown body (in-body images embedded inline)…

Drafts (when auto-publish is off, or a test publish) are committed with draft: true— filter those out of your production build so they don't appear until approved. Approving a draft in Review re-commits the same file without the flag.

Notes

• The file name is the slug. Re-publishing the same slug updates the existing file (it commits over it), so edits and improvements land on the same post.
• Publishing isn't instant— it's as fast as your Git host's build. That's the trade-off for keeping the blog fully static with no database.
• The featured image goes inline at the top of the body (your posts have no cover-image frontmatter field). If you'd rather it map to a frontmatter key like cover or image, tell us and we'll match your schema.

Other connectors: WordPress · Next.js Blog (B1) · API Webhook (B2)