Blog admin
Write like WordPress.
Keep posts on your own GitHub.
GitPress is a blog admin. You sign in and write. The words go into your GitHub repo. On save they become a static site on GitHub Pages. gitpress.net is the remote; readers never hit our servers.
Public platform stats · refresh every 5 minutes · totals only, no personal data
- Users
- 34
- Sites
- 23
- GitHub connected
- 24
- Builtin themes
- 4
Source · exit right
If GitPress.net shuts down,
your blog stays in your repos.
Posts, images, and drafts never entered our database. Themes and the build tool are MIT. Compiles run on GitHub Actions, not our machines. The control plane is source-available (PolyForm Shield): self-host for yourself, don’t run a public competing platform. If we disappear, keep building with the same repos and Action. You are not migrating. You already have the files.
Main repo · the site you click
tap6/GitPress.net
WordPress-style admin: sign in, create repos, write, save. This is the control plane, not your article library. Source-available, PolyForm Shield.
Open on GitHub →
Themes and conventions
tap6/gitpress
How a blog looks, how Markdown is written, the data-repo template. Switching or authoring a theme follows this spec.
Open on GitHub →
Compiler
tap6/build-action
Reads the private data repo, builds a static site, pushes the public site repo. You can run the same Action in your own workflows.
Open on GitHub →
What the three pieces do: What is this?. What the control plane keeps: Privacy.
Live in three steps
No server, database, or WordPress plugins to maintain. GitHub is the backend.
- 1
Sign in and authorize GitHub
Use Google, GitHub, or another provider, install the GitPress App, and let us create repos for you.
- 2
Pick a theme and write
Fill in site details, choose a builtin Astro theme, then write, upload media, and manage categories.
- 3
Build and go live
Every save triggers Actions. Compiled output is pushed to the public site repo. Pages is live.
Two repos, clear jobs
Content and the website are split. Everything you write in the admin goes into the private data repo. Only compiled HTML/CSS/assets enter the public site repo for Pages.
- Data repo (private) — content/, media/, gitpress.json
- Site repo (public) — Astro output; rebuild anytime to change theme
- GitHub Actions — push triggers the build; our servers stay idle
# Typical site layout
alice-blog-data/ ← private, includes drafts
content/posts/*.md
media/*.jpg · *.mp4
gitpress.json
alice-blog/ ← public, compiled output only
index.html · posts/ · media/
→ GitHub Pages / custom domain
Why GitPress
The writing stays yours
Posts, images, and drafts live only in your private GitHub repo. GitPress.net is not a content library. Uninstall the App and we cannot read your prose.
Content and site are separate
One repo for posts and drafts, one for compiled pages. Changing theme is a config change. You don’t lose a word.
Zero-server builds
GitHub Actions compiles. GitHub Pages or Vercel hosts for free. There is no day the box won’t boot.
A familiar admin
WordPress-style: dashboard, posts, media, appearance, settings. Almost no learning curve.
Make your own theme with AI
You don’t need a design system. Copy our first prompt, let your AI ask questions, then generate an Astro theme GitPress can import.
Copy the prompt
Open “Make a theme with AI” in Help and send the full prompt as the first message.
Answer questions
The AI asks about style, layout, logo, and options. It writes code only after you answer.
Import and use
Push the theme to a public GitHub repo and paste the URL under Appearance. A store is coming.
Ready for a blog you actually own?
Free to sign up. The prose is on your GitHub, not on GitPress.net servers. 34 users and 23 sites already.
Start free