explanation
-
App settings vs plugin settings: where each knob lives and why
Why MAM splits your settings into two families — app settings that ship to the phone and plugin settings that stay on the server — and how the app-settings side…
-
Add a button: the content-type picker explained
Every button in your app is backed by a content class — here’s what that means, and how to reason about which of the 19 types to pick.
-
App images explained: where they live, sizing, and the image pipeline
How MAM stores, resizes, and serves your app’s images — the branding art generated when you publish, and the content images served straight from WordPress.
-
The content-class interface: the six methods every button type implements
Why MAM’s button types share a duck-typed six-method contract, what each method does, and how the methods split between the admin builder and the device payload.
-
What you need before you start (prerequisites checklist)
Before you onboard to MAM Suite, get three things ready: a supported WordPress site, a directory or content plugin with real content in it, and a publishing plan.
Knowledge Base Categories
Need Support?
Can't find the answer you're looking for? Don't worry we're here to help!
