The 21 content-type handlers that drive what the mobile app can render. Each represents one type of mobile UI element (Login, Map, Web URL, etc.). Covers the duck-typed interface, the…

The Login content class — renders the app’s primary auth button and owns the login-related per-button settings. Backed by the user-roles login flow and the legacy mam_user_roles_cred_handler AJAX action.

The Logout content class — clears app session state and triggers the mam_logout / mam_update_current_user actions. Mirrors the Login button; only renders for authenticated users.

The kernel of the MAM Suite: it builds the JSON that drives every app screen and owns the app-settings registry, notification dispatcher, push credentials, user roles, cron, and Gravity Forms…

How mam-main is organized: 22 subsystems, 4-phase phone-data pipeline, notification dispatcher, settings cascade, and the cross-cutting infrastructure (MAM_Current_Request, MAM_Account_Code_Manager, MAM_Migration_Tasks, repositories) that every feature relies on.