WryteGit-native content workspace

Your CMS shouldn'tfight your repo.

Write in a real markdown editor, organize on a board, and publish straight to GitHub as clean commits. No database to sync, no webhooks to babysit, no lock-in — your repo stays the source of truth.

Start Writing

Open Source · MIT · BYO keys · No credit card

maindiff --staged
content/posts/shipping-faster.md
1 ---
2 title: "Shipping Faster with Wryte"
3-status: draft # stuck in a CMS database
4-exported_at: null # waiting on a webhook
5+date: 2026-04-07
6+tags: [devtools, workflow]
7+draft: false
8 ---
9
10-# Copy-paste from another tool, then commit by hand
11+# Write here. Publish. It's already a commit.
Published to main · commit a3f8b2c

Everything you ship is a commit

a3f8b2cfeat: add getting-started guide
9d41e07content: refresh api-reference
1f6c5a9post: shipping faster with wryte
7b20de4fix: frontmatter date format
c4e9f13chore: schedule v0.20 changelog
e81a6d2post: the developer content problem
5a7c0b8content: bulk-publish 4 drafts
2db93f1feat: tag taxonomy cleanup
a3f8b2cfeat: add getting-started guide
9d41e07content: refresh api-reference
1f6c5a9post: shipping faster with wryte
7b20de4fix: frontmatter date format
c4e9f13chore: schedule v0.20 changelog
e81a6d2post: the developer content problem
5a7c0b8content: bulk-publish 4 drafts
2db93f1feat: tag taxonomy cleanup

Write

A real editor — not a form with a rich-text box

Markdown with live preview, schema-driven frontmatter, and AI polish on your own keys. The kind of editor you'd actually choose to write in.

shipping-faster.md● live preview
# The Developer Content Problem
 
Most developers write in markdown — but
publishing still means committing, pushing,
and waiting on a deploy to finish.
 
**Wryte changes that.**
One click from editor to your repo.
markdownUTF-8312 words⌘S to publish

Organize

Your whole pipeline on one board

Every article is a card. Drag it from Draft to Published, schedule it for later, edit tags inline — and move through it all with vim-style keys.

Draft3

API Reference

/api-referencedocs1.2k

Migration Guide

/migration-guide840
drop here
Review2

Getting Started

/getting-startedguide2.1k
drop here
Scheduled1

Shipping Faster

/shipping-faster1.6k
drop here
Published4

Changelog v0.19

/changelog-v019420
drop here
j / k navigateh / l switch columnsm + 1–9 move card⇧ + click to multi-select

How it fits together

One workspace, one source of truth

The editor, the board, and the scheduler all feed a single publish engine. It writes plain markdown straight into your repo — so GitHub, not Wryte, owns your content.

01

Editor

Markdown + live preview. Auto-save on every keystroke.

02

Board

Kanban columns track status. Drag, tag, schedule.

03

Publish engine

Durable scheduling, diff-before-sync, conflict detection.

04

Your GitHub repo

The single source of truth. Real markdown, clean commits.

Wryte never becomes a place your content gets trapped. It's a writing and publishing layer on top of your repo. Delete your account tomorrow and every word still lives in GitHub as version-controlled markdown.

Diff before sync

Wryte compares against the file SHA in your repo and only writes what actually changed — no noisy commits.

Conflict detection

Edited the same file on GitHub directly? Wryte spots the drift and lets you resolve it before publishing.

Durable scheduling

Scheduled publishes run on a workflow engine with retries — they fire even if you're offline.

Where Wryte stands

Every CMS bolts git on. Wryte starts there.

Payload, Sanity, and Contentful keep your content in their own database and treat git as an export problem — so you wire up webhooks and pray they fire. TinaCMS gets closer, but you have to wrap your whole site in its config. Wryte points at any GitHub repo and writes plain markdown commits. Nothing to install in your codebase.

- the usual CMS → git dance
-Write in a proprietary editor
-Content lives in their database
-Export, or call an API at build time
-Wire up a webhook — and hope it fires
-Debug why production is out of sync
Wryte+ with Wryte
+Write markdown in a real editor
+Organize on a board, schedule if you like
+Click publish
+git commit → your repo
+Your existing CI deploys. Done.
CapabilityPayloadTinaCMSSanityContentfulWryteWryte
Source of truth
Its own database
Your git repo
Hosted dataset
Hosted cloud
Your GitHub repo
Content stored as
DB rows
Markdown / MDX
Proprietary docs
Proprietary entries
Plain .md files
Git-native workflow
None — export first
Tied to its config
None
None
Every change is a commit
Infra to run
DB + app to host
Self-host or Tina Cloud
Hosted SaaS
Hosted SaaS
Zero — commits to your repo
Works with any repo
Build around its schema
Wrap your site in Tina
Fetch via GROQ/API
Fetch via API
Point it at a repo + path
Editorial kanban board
Enterprise add-on
Built in
Scheduled publishing
Custom / plugin
Roll your own
Add-on
Native
Durable cron + retries
AI assistance (BYO keys)
Paid add-on
Paid tier
BYOK, never proxied
Vendor lock-in
Your DB, OSS app
Low–medium
High
High
None — your repo, your keys

Take Payload. It's a great code-first CMS — but you stand up a database, model collections in code, host the app, and your content lives in Postgres or Mongo. Getting it into a git-backed static site means an export step and a build hook. Wryte skips all of it: the markdown files are the content, and the commit is the publish.

Comparison reflects typical out-of-the-box setups. Every tool here is capable — Wryte just optimizes for one workflow: markdown in a repo.

Desktop App

Same Wryte. Native feel.

The full Wryte experience as a cross-platform desktop app. Built with Electron — same editor, same board, same git-native workflow. No browser tab required.

wryte.desktop● native

Install with Homebrew

One command, always up to date.

$brew install rafay99-epic/apps/wryte

Native shortcuts

Full keyboard-driven workflow. System menus.

Auto-updates

Seamless background updates. Latest features.

github.com/rafay99-epic/wryteelectron · cross-platform · oss
Wrytewryte
$git commit -m "stopped fighting my CMS"

Keep your content in git.
Let Wryte do the rest.

No credit cardGitHub loginOpen SourceBring your own keys