For the people the site is built for

Your client edits. You stay out of it.

Kiri Studio is a desktop app for site owners. They sign in with GitHub once, change their text, fill in forms, drop in pictures, watch the real page update, and click Publish.

Download Kiri Studio Set up a site for it

Kiri Studio: the page list, a Markdown page with its header form, and the live preview — Pages by name on the left, the page's header as a form, the real page on the right.

The whole journey, and nothing more

The welcome screen with a Sign in with GitHub button

Sign in once

One "Sign in with GitHub" button. The app opens the browser with the code already copied; the owner approves and never sees it again.

Open the site

The site appears directly (a picker only shows for more than one), and keeps itself in sync while they read.

Edit by name

Pages and sections are listed by their plain names: "Team", "Blog posts". Text goes in a Markdown editor, data in a form-like editor checked against a JSON Schema. There is no Save button: every change is kept as a draft.

The live preview of a page next to the editor

See the real page

A live preview beside the editor renders the page with the site's own Kirigami engine, as it will look once online.

The image manager, with a grid of thumbnails

Drop pictures in

Pictures and documents go in a manager. Big photos are resized for them, and each one can copy the code that inserts it into a page.

Publish

One button. "Publishing…", then "Your site is online", with a link. The site's usual GitHub Pages workflow does the rest.

What owners can edit

Text

Markdown pages, with the page header (title, date, abstract, page layout) shown as a form above the text instead of raw tags.

Structured data

YAML and JSON files, with schema-aware help and smart indentation. A file's schema is found the way VS Code finds it.

Images

Drop pictures in; they are downscaled before they are committed. Copy or insert the Markdown for them, or set one as a page's image.

Documents, audio, video

PDFs and other files go in a document manager, and audio and video play inside the app. Large files can go through Git LFS.

Blog-style collections

Add and delete posts or tree-shaped pages, with default header tags filled in for each new one.

Per-page media

Optionally, each page gets its own images, videos and downloads next to it, with a panel to manage them.

Kiri Studio's image manager: a grid of thumbnails with New folder and Add images buttons — The image manager: drop pictures in, big photos are resized for you, and each one can copy the code that inserts it.

You decide what is editable

The maintainer controls it in the site's own kirigami.yaml, versioned with the site, not in the app. Without anything, the content that pages load and the site's images are editable; everything else stays out of sight.


                        studio:
                          files: src/documents          # a document manager (PDF, …)
                          exclude: [src/features/data/_stats.json]
                          labels:
                            src/features/data/_articles.yaml: Articles

The build ignores that block, so a site works the same with or without Studio. Every key is documented in the configuration reference and in Kiri Studio for maintainers.

Safe by design

No Git for the owner. The app talks to the GitHub API: no git binary, no repository on their disk.
All or nothing. A publish is one commit, applied by a single branch update. If someone published in between, the app syncs and rebuilds on the new head.
Only what is allowed. The sign-in only reaches repositories where the Kiri Studio GitHub App is installed and the owner can write.
Plain language. No commit, branch or conflict. Interface in English and French.
Windows, macOS and Linux. Installers update themselves on Windows and Linux (AppImage); they are not code-signed yet, so Windows warns on first install and macOS needs right-click, Open.

Kiri Studio is in early development. Source and releases: php-kirigami/kiri-studio.