1
Blog Name
2
Cloudflare
3
GitHub
4
Options
5
Deploy

Choose Your Blog Name

This will be used for your subdomains and repository names.

Lowercase letters, numbers, and hyphens only

Your URLs will be:

Editor: my-blog-editor.pages.dev
Blog: my-blog.pages.dev
API: my-blog-api.workers.dev

Connect to Cloudflare

We'll deploy your blog infrastructure on Cloudflare's free tier.

🔗

Click below to authenticate with Cloudflare

What This Does:

  • Creates Cloudflare Worker for your publishing API
  • Sets up two KV namespaces (subscribers & auth)
  • Deploys editor and blog to Cloudflare Pages
  • All within Cloudflare's generous free tier

Don't have a Cloudflare account? Create one for free

Connect to GitHub

We'll create repositories to store your blog content and code.

🔗

Click below to authenticate with GitHub

What This Creates:

  • omni-blogger-editor - Editor app code (public or private)
  • omni-blogger-worker - Publishing API code (public or private)
  • my-blog - Your blog content (private)

All repositories will be created in your GitHub account and you'll have full control.

Don't have a GitHub account? Create one for free

Configure Options

Optional settings you can configure now or later.

Custom Domain

Use your own domain instead of *.pages.dev subdomains

Email Subscriptions

Allow readers to subscribe and receive new post notifications

Repository Visibility

Review & Deploy

Check everything and start deployment.

Configuration Summary

Blog Name: -
Editor URL: -
Blog URL: -
API URL: -
Cloudflare: ✓ Connected
GitHub: ✓ Connected
Custom Domain: Not configured
Email Subscriptions: Not configured

⏱️ Deployment Time: 10-15 minutes

The wizard will:

  • Create 3 GitHub repositories
  • Deploy Cloudflare Worker with KV namespaces
  • Deploy editor to Cloudflare Pages
  • Deploy blog to Cloudflare Pages
  • Configure all secrets and environment variables

Keep this tab open during deployment.