Repository navigation
kite 0.1.1
A studio release: the editor gives the text the whole page, a theme's settings get a page of their own with the preview beside them, and the dashboard says in a sentence how far publishing has got.
Highlights
- Write with the whole page. The panel beside the editor is gone, and an item's settings sit where a reader meets them: the cover above the title, the summary under it, and the categories, tags, address, template and pinning as chips below, each opening a small popover. Status, the publish date and deleting open from the status in the header. The sidebar folds to its icons while you write and comes back when you leave.
- Links edited where they are. A link the caret is in shows a bubble under it to change, open or remove its address, and typing inside a link no longer jumps to the toolbar.
- Theme settings, page by page. Each section of a theme has a page of its own, with the preview beside the form. The preview follows the section to the page it is about, draws the desktop layout at any window size, and outlines what a change touched. Lists are edited as rows, trees or cards by what their entries hold, and rows drag by a handle.
- One name for you. Setup and
kite initask for your name and write it as the site's author, and the studio shows it at the foot of the sidebar, with local mode as a badge beside the site's name. - Publishing at a glance. The dashboard's publishing card says whether the site is up to date and what it takes if not, marks each step as it stands, and offers the one next step.
- Settings in plain sight. Site, theme and appearance are listed in the sidebar rather than folded under Settings, and the account sits at its foot. Most pages of the studio end with a footer naming the version, with links to the docs, the source and the issue tracker, and a phone's header shows Kite's mark.
- For themes. A highlighted code block carries
data-langwith the language its fence gave, so a theme can label it, as the docs theme Vane does. A section of a theme's settings can name the page it previews withpreview:home,post,pageorposts.
Install
Download the archive for your system below, unpack it, put kite somewhere on your PATH, and run kite run in an empty folder. On macOS, xattr -d com.apple.quarantine kite lets a downloaded program run the first time.
To run a site on a server with Docker:
docker run -d --name kite --restart unless-stopped -p 127.0.0.1:1717:1717 -v kite-data:/data ghcr.io/kite-plus/kite:0.1.1Every archive can be checked against checksums.txt, and a given commit builds to the same binary on any machine.
Upgrading from 0.1.0
Replace the binary, or pull the new image. A site and its files need no change. The author's name now lives in site.author; a name an older profile kept is shown until one is saved.
Notes
Kite is in early development, and things may still change from one version to the next. The reference covers the studio, themes, plugins, configuration and deployment.
Every change in this release
Changelog
Features
- 0be2f40: feat(render): name the language of code blocks (@amigoer)
- 35b2571: feat(schema): let a section name its preview page (@amigoer)
- e6cf4ec: feat(web): close each page with a footer (@amigoer)
- 186e61c: feat(web): edit lists as rows, trees and cards (@amigoer)
- 3bf36db: feat(web): give theme settings a page of their own (@amigoer)
- 3119ea5: feat(web): list every setting in the sidebar (@amigoer)
- c1944bf: feat(web): name the account after the site author (@amigoer)
- e8f0d84: feat(web): outline each change in the preview (@amigoer)
- 83e34a8: feat(web): pin and delete without a menu (@amigoer)
- 1958141: feat(web): replace the account menus with buttons (@amigoer)
- f354983: feat(web): set an item's details where they show (@amigoer)
- d2cf383: feat(web): show local mode by the site name (@amigoer)
- 5def2ab: feat(web): show the mark on phones (@amigoer)
- 62894bb: feat(web): tell how far publishing has got (@amigoer)
- cd84bb3: feat: make your name the site's author (@amigoer)
Fixes
Refactors
Documentation
Install
Download the archive for your platform, or pin the version in a project
so that local builds and CI agree:
./kitew build
Verify a download against checksums.txt before running it.