Build modules and themes for Bondry

The contracts a module or a theme has to follow, how the Designer is extended, how an app signs in with OAuth, and how a paid module gets its own license.

Getting started

Building for Bondry

What a module is, what a theme is, and the rules that apply to both before you write a line.

Modules

Module anatomy and module.json

The folder layout, every field of the manifest, and the lifecycle methods the kernel calls.
Independence rules

Table prefixes, uninstall behaviour, child modules and the compatibility states, in detail.
Routes, permissions and admin screens

Wiring a module into the front end, the group matrix and the admin navigation.
Widgets and surfaces

Letting the Designer place your content, and opening your screens to it, without ever depending on it.

Themes

Themes

theme.json, the template hierarchy, customizer.json, child themes and functions.php.

Designer

Designer for authors

The contracts a module or a theme uses to extend the page builder, with the schema control reference.

API

OAuth 2.1 for apps

Authorization code with PKCE, rotating refresh tokens, scopes and the endpoints an app calls.

Licensing and packaging

License API for module authors

How a paid module licenses itself: the manifest key, the activation call, the heartbeat and the degradation policy.
Packaging and release format

The signed update package, what the installer refuses, and how a release is built.