Overview
Add your own modules, plugins, generated file conventions, and scope-aware behavior on top of the same extension points QUESTPIE uses internally.
QUESTPIE treats framework features and userland features the same way: a module contributes runtime state, and a plugin teaches codegen how to discover and type new files. Use this section when you are packaging reusable behavior, adding custom conventions, or shaping an app around scopes and tenants.
Pages
| Page | What it covers |
|---|---|
| Modules | Static module objects, module merging, bundled plugins, and how packages contribute runtime features. |
| Building a plugin | The authoring loop for reusable codegen-aware packages. |
| Codegen | File discovery, generated factories, registries, and the CodegenPlugin API. |
| Multi-tenancy | Scope derivation, access-rule enforcement, scoped globals, and the admin scope picker. |
Related
- Configuration - where modules and config files are wired.
- Adapters - the infrastructure contracts your modules can use or replace.
- Admin - the largest built-in example of a module plus codegen plugin.
Audit
Add durable admin audit logs, inspect the audit collection, and write custom audit events.
Modules
A module is a plain, static data object that contributes collections, globals, jobs, routes, services, config, and even codegen plugins to your app, the unit QUESTPIE uses to ship batteries (admin, OpenAPI) and the unit you publish to share your own.