explanation
-
How your WordPress content reaches the app (the_content, featured images, encoding)
Why your app content looks the way it does: MAM runs your WordPress posts and pages through the_content, pulls out the featured image, and normalizes the text encoding before it…
-
In-app browser vs. external link: what a Web URL button does
Why a Web URL button shows a web page instead of native content, when that page stays inside your app versus opening the phone’s browser, and when to reach for…
-
How MAM turns your WordPress site into a native app
MAM is the WooCommerce of mobile apps — your WordPress content and plugins feed the app, and site updates show up with no rebuild.
-
How the plugins fit together: the MAM Suite integration map
How MAM Suite plugins enrich each other through hooks — the directory feeds offers, chat, reviews, geofilters, and IAP, and no single plugin ever depends on the rest.
-
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.
Knowledge Base Categories
Need Support?
Can't find the answer you're looking for? Don't worry we're here to help!
