Docs.

Most of the help is right where you need it: inside the editor, beside your code. This page shows you where everything is.

a In the editor

First game: Nine steps to a game where a ship collects stars and dodges a rock. Each step shows the whole file with the new lines marked.
How do I…: 38 recipes: move with the buttons, stay on the screen, fall and land, jump, keep score, lives as hearts, a countdown, a best score that's kept, game over and play again, a camera that follows, a shaking screen, two players nearby…
Reference: Every command, with what it takes and an example, in Lua and in Python. Hover over a name in your code to see the same thing.

b By what you want to do

All you need is Berglet and a browser. Start at Make, with the real starter code and how saving works.

Learn shows the order ideas arrive in, and what's ready for classrooms.

One set of commands in C, two ways to ship it: in its own safe space, or with the whole machine. Overview on Go deeper.

Players, translators and live reloading: Go deeper.

The spec sheet, pins and case: Hardware.

Brand & press has the logo files and the short rules.

c For developers

Full developer guides

Detailed guides for people who want to build on Berglet will be published here. Join the list to hear when they're out.

System: How the library, players and games fit together; the memory card's layout; the game package format
Game kit: Every command for Lua and Python, and how a running game is updated when you save
C and WebAssembly: Building, packaging and signing games written in C or compiled to WebAssembly
Hardware: Every pin, the button matrix, power and the battery reading