explanation
-
Frozen public contracts and the wrap-don’t-rename discipline
Why field-deployed mobile apps and ~2K customer sites freeze MAM Suite’s AJAX names, option keys, hooks, and tables — and how migration lets you evolve them safely.
-
The entitlement model: how plugins gate themselves on license and version
How MAM Suite sibling plugins decide whether to run: the mam_plugin_entitlement filter, an async-synced cache, fail-open behavior, and version checks.
-
The forms manager: providers, lifecycle, and why Gravity Forms is the engine
How MAM Suite turns WordPress forms into native app screens — the provider abstraction, the submission lifecycle, prefill paths, and where Gravity Forms plugs in.
-
Content classes vs. elements vs. tab-bar buttons: which extension point
MAM Suite gives you three UI-building primitives. This explains what each one is, when to reach for it, and how they compose into a list-with-detail screen.
-
Content source vs. global settings: where a button’s data comes from
Every button draws on two kinds of input: its own per-instance content source, and the site-wide global settings that style and gate it.
Knowledge Base Categories
Need Support?
Can't find the answer you're looking for? Don't worry we're here to help!
