Workspace Repository Sync

Why Repository Sync?

Many technical teams write blog content in markdown, stored in a GitHub repository alongside their codebase or documentation. Engineering blogs, changelog posts, developer tutorials, and open-source project updates all commonly follow this pattern.

Without repository sync, publishing this content requires: 1. Copy-pasting from the markdown file into a CMS editor 2. Re-formatting headings, code blocks, and images manually 3. Re-entering SEO metadata that was already in the frontmatter 4. Repeating this across every platform you publish to

Workspace Repository Sync eliminates all of this. Connect your repository once, and the platform reads your markdown files, parses the frontmatter, converts images to properly hosted URLs, and creates articles in your publishing queue automatically, ready to review, schedule, and publish to any connected CMS.

How the Sync Works

Once connected, the sync engine monitors your repository for file changes:

1. 1When a markdown file is added or updated in the configured directory (e.g., /posts/ or /blog/), the platform detects the change via a GitHub webhook.
2. 2The file is parsed: frontmatter metadata is extracted and the markdown body is converted to clean HTML.
3. 3Any relative image links in the markdown (e.g., ![cover](./images/cover.png)) are fetched and re-hosted on the platform's media CDN, so images load reliably regardless of where the article is published.
4. 4A new article draft is created in your publishing queue, pre-filled with the extracted metadata and content.
5. 5The article appears in your editorial pipeline at Draft state, ready for review, SEO optimization, and publishing.

Markdown Frontmatter Format

The platform reads frontmatter using standard YAML formatting at the top of each markdown file:

---
title: "How We Scaled to 1 Million Users on a Single Server"
slug: "scaling-to-1-million-users"
category: "Engineering"
date: "2026-06-01"
meta_description: "A deep dive into the architecture choices that let us scale from 10,000 to 1 million users without a full rewrite."
focus_keyword: "scaling web applications"
tags: ["backend", "architecture", "performance"]
featured_image: "./images/scaling-cover.png"
---

Your article body starts here...

All frontmatter fields are optional except title. Missing fields can be filled in manually inside the platform's editor before publishing.

Connecting Your Repository

1. 1Navigate to Workspace Settings → Integrations → GitHub Repository.
2. 2Authorize the platform to access your GitHub account (read-only access to the selected repository is sufficient).
3. 3Select the repository and the branch you want to sync (typically main or master).
4. 4Specify the directory path where your markdown files live (e.g., posts/, content/blog/).
5. 5The platform installs a webhook on the repository and performs an initial sync of all existing markdown files.

After the initial sync, all future pushes to the configured branch and directory are picked up automatically within seconds.

Frequently Asked Questions