Git Blog

What is Git Blog?

Git Blog is a Markdown blogging app for iPhone and iPad that lets you draft, edit, and publish blog posts directly to your GitHub repository. It’s designed for writers who want to create content on mobile while working with static site workflows, including Jekyll, Hugo, Astro, and other static site generators.

The app connects to your repository so you can manage new posts and edits to existing Markdown files, then publish changes using workflows that match Git-based branching or pull request habits.

Key Features

• Block-based Markdown editor with drag-to-reorder for arranging headings, lists, quotes, and code blocks while writing
• Camera and photo library integration, with the app processing and uploading images as part of your post
• Image layout options (full-width, half, side-by-side, and additional layout classes) to control how images appear in posts
• Flexible frontmatter templates with custom fields (including text, dropdowns, and image pickers) and support for importing frontmatter from existing repo posts
• Multiple publishing modes: push directly to the main branch, create a new branch, or open a pull request
• Repository browser for viewing your file structure, opening existing Markdown files, editing them, and republishing
• Light, dark, and system appearance modes
• Secure token storage using the device keychain

How to Use Git Blog

1. Open Git Blog on your iPhone or iPad and connect it to your GitHub repository.
2. Create a new Markdown post using the block-based editor, adding your content and inserting images as needed.
3. Use frontmatter templates to set required fields (or import frontmatter from an existing post) so the post matches your site’s structure.
4. Publish using your preferred workflow—push to main, create a branch, or open a pull request—and let the app handle the commit (including images).
5. To revise existing content, use the repository browser to open a Markdown file, edit it, and republish.

Use Cases

• Drafting a new blog post while away from a laptop, then publishing it to your GitHub-backed site in a single mobile workflow
• Editing previously published Markdown posts by browsing your repository structure, opening a file, applying updates, and republishing
• Managing posts for a static site generator that relies on frontmatter fields (such as selecting values from dropdowns or providing image pickers)
• Building and formatting technical posts that require code blocks and consistent structure, using the block-based editor and reordering blocks as you write
• Publishing changes in a team-friendly Git workflow by pushing directly to main when appropriate or creating a branch / pull request when review is needed

FAQ

• Does Git Blog support static site generators?
  Yes. It’s described as working with Jekyll, Hugo, Astro, and any static site generator.

• Can I publish changes as a pull request instead of pushing to main?
  Yes. The app supports publishing by opening a pull request, as well as pushing directly to the main branch or creating a new branch.

• How does image uploading work?
  You can snap a photo or pick from your library, and Git Blog processes and uploads images alongside your post. The app includes images as part of the commit during publishing.

• Can I edit existing Markdown files in my repo?
  Yes. Git Blog includes a repository browser to open existing Markdown files, edit them, and republish.

• What devices and OS versions does it require?
  The App Store listing indicates iOS 17.0 or later for iPhone, iPadOS 17.0 or later for iPad, macOS 14.0 or later with an Apple M1 chip or later for Mac, and visionOS 1.0 or later for Apple Vision.

Alternatives

• Markdown editors with GitHub support (desktop/mobile): These can also generate Markdown and sync to GitHub, but may rely on manual Git operations or different editing experiences than a block-based writer.
• Static site CMS tools (web-based content editors): These focus on authoring without direct Git branching/pull request workflows, which can simplify publishing but may not match a Git-centric process.
• Local static site workflows (edit Markdown and build locally): This offers full control over rendering and previews, but typically requires a computer rather than drafting and publishing directly from a phone or tablet.
• GitHub web-based editing: This keeps everything in GitHub’s interface for quick edits, but it doesn’t provide the same mobile-first Markdown block editor and frontmatter templating described for Git Blog.