DocumentationAll sections
Everything you need to build for Luma.
From your first window to your first release. Anyone can read these docs; you don’t need an account or the developer program.
What building a Luma app means, the three Depot tiers, how publishing works, and where to start.
- 01
Getting started
Install the SDK, build a first window in Python or C, bring an existing GTK app across, and learn how a Luma project is laid out.
5 pages - 02
Tools
The luma command, the Luma Platform runtime and SDK, the LumaUI reference, Imager and Depot publishing: what each is for, how to get it, and whether it’s available yet.
1 page - 03
The stack
What a Luma app is built on, from LumaUI and GTK 4 to Flatpak and the Luma Platform runtime, and how the same app runs on other Linux distributions.
2 pages - 04
LumaUI
Luma’s toolkit, built on GTK 4: the window and its islands, components, commands and menus, adaptive layouts, semantics and actions, in Python and C.
12 pages - 05
Design guidelines
How a Luma app looks, reads and behaves: layout, spacing, type, color, icons, motion, accessibility and writing.
9 pages - 06
Permissions and privacy
Portals, the plain-language permissions Depot shows before anyone installs, and what asking for more access means at review.
1 page - 07
Publishing to Depot
How publishing on Depot works: app IDs, store pages, releases, reviews and updates. Applications to publish aren’t open yet.
8 pages - 08
Review Guidelines
The Depot Review Guidelines: what automated checks look for on every release, and what a person reviews before an app ships.
1 page - 09
The developer program and verification
Who can publish, how individual and organization verification work, and what stays private to Luma’s review staff.
1 page - 10
The
luma-app.tomlcontractEvery field in luma-app.toml, what each one promises about your app, and how the SDK checks it before you publish.
1 page - 11
Knowledge base
Common questions, and fixes for problems with running, checking and packaging an app.
2 pages