How Wryte works

From blank page to published content in three steps. No deploy scripts, no CLI gymnastics, no context switching.

Step 01

Write in markdown

A distraction-free editor that gets out of your way. Write the way you think — in markdown — with instant preview and auto-save.

Split preview

Live side-by-side preview updates as you type. WYSIWYG without the WYSIWYG complexity.

AI polish

Bring your own API key. Get AI-powered title suggestions, grammar fixes, and tone adjustments.

Schema-driven frontmatter

Define your blog's frontmatter schema once. Every new post auto-generates the right fields.

Keyboard-first

Customizable shortcuts for everything. Cmd+S to save, Cmd+Shift+P to publish, Cmd+K for quick actions.

getting-started.md
1---
2title:"Getting Started"
3date: 2026-05-16
4tags: [tutorial, guide]
5draft: false
6---
7
8# Welcome to Wryte
9
10Write content in **markdown**.
11Publish to GitHub with one click.
Step 02

Organize on a board

See all your content at a glance. Drag articles through your workflow — from draft to review to published.

Drag and drop

Move cards between columns to update status. Reorder within a column to set priority.

Inline tag editing

Click a tag to add, remove, or create new tags. Autocomplete from your project's existing tags.

Schedule publishing

Set a date and time. Wryte publishes automatically when the clock hits — no manual step.

Media management

Upload images to GitHub, UploadThing, or Cloudinary. Automatic compression and optimization.

Draft

API Reference

/api-reference

Migration Guide

/migration-guide

Review

Getting Started

/getting-started

Published

Changelog v2

/changelog-v2

Step 03

Publish to GitHub

One click and your content is committed to your repository. Deploy hooks fire automatically.

Git-native

Content is committed as real markdown files. Your repo stays the single source of truth.

Bulk publishing

Select multiple articles and publish them all at once. Perfect for batch content drops.

Scheduled deploys

Queue posts to go live at a specific time. Wryte commits on schedule, your CI does the rest.

Conflict detection

If someone edits the same file on GitHub, Wryte detects the conflict and lets you resolve it.

Publishing to main
Frontmatter validated
Markdown compiled
Committed to GitHub
Deploy hook triggered

Published successfully

commit a3f8b2c

Ready to start?

Sign up with GitHub and create your first project in under a minute.