-
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.
-
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.
-
General, Layout, Content Sections, Tab Bar, Add Item: per-screen sub-tabs
Editing a screen splits its settings across up to five sub-tabs — General, Layout, Content Sections, Tab Bar, Add Item — each one controlling a different layer.
-
How a list-with-detail feature is assembled (geodirectory reference architecture)
How mam-geodirectory assembles a list-with-detail feature: one content class drives list/map/calendar surfaces, content sections, tab-bar buttons, forms, and notifications.
-
How a MAM app is structured: tabs, screens, buttons, and content classes
The mental model behind every MAM app: a tab bar and left menu made of buttons, each one backed by a content class that renders a single screen.
Knowledge Base Categories
Need Support?
Can't find the answer you're looking for? Don't worry we're here to help!
