Summary

A content class represents one type of mobile UI element — a Login button, a Map, a Web URL viewer, a Favorites list, a Phone Call button, etc. There are 21 content classes in mam-main/includes/content-classes/. Adding a new content class is how you give customers a new building block to assemble screens with in the no-code builder.

Each class lives in a single file. The file:

1. Registers itself in the global $local_app_content[] array with content_type, class, and vc_type metadata.
2. Defines a class implementing the duck-typed interface below.

Class names like local_app_login_button are frozen because they appear in customer button arrays serialized into local-app-button-array*. Renaming would orphan every site’s saved instance of that button type.

The 21 content classes

The duck-typed interface

There is no formal interface declaration yet — it’s tracked as a known refactor target. Every content class is expected to implement:

A content class that omits get_data_for_app will appear in the admin UI but render nothing on the device.

Settings schema (app_settings())

Each entry describes one settings field:

array(
    'category'    => 'login',                       // matches a slug from app_settings_categories()
    'title'       => __( 'Require Login?', 'mam-suite' ),
    'variable'    => 'require_login',               // option-key suffix
    'type'        => 'yes-no',                      // input widget
    'id'          => 'tsl-require_login',           // DOM id
    'environment' => 'global',                      // 'global' = site-wide; 'per-button' = per-instance
)

Common type values: yes-no, text, textarea, select, image, color, number. The settings UI infrastructure lives in app-settings/.

How a content class fits into the pipeline

mobile request → mam_get_phone_data() → MAM_Phone_Data_Pipeline::run()
                                              │
                                              ▼
                                       phase_content
                                              │
                            For each button in the role's button array:
                                  ▼
                       resolve content_class from $local_app_content
                                  ▼
                       call $class->get_data_for_app($category)
                                  ▼
                       merge into the response

Content classes don’t typically subscribe to mam_get_phone_data_before_send directly — they’re invoked by the button-rendering loop based on button-config metadata.

Adding a new content class

1. Create includes/content-classes/local-app-<kind>-class.php.
2. Append your file to the require_once chain in content-class-manager.php.
3. Register the class in the global registry:

$local_app_content['Your Type'] = array(
    'content_type' => 'Your Button',
    'class'        => 'local_app_your_button',
    'vc_type'      => 'your_button',
);

4. Implement the 7 interface methods.
5. Optionally seed an initial instance in create_initial_buttons() so new sites get one by default.

See Recipe: Register a content class.

Frozen surface callouts

• Class names for any content class that appears in customer button arrays are frozen. Renaming local_app_login_button orphans every customer site’s saved login button. Frozen contract — do not rename without a coordinated migration of every site’s local-app-button-array*.
• content_type keys are user-facing labels in the admin UI; changing them changes what admins see.
• *`local-app-button-array`** option is itself a frozen public contract.

Gotchas

• No interface enforcement. A class can ship with a missing method and break only when that method is called.
• $local_app_content is a global populated at file-include time. Any code that reads it must run after content-class-manager.php has loaded.
• vc_type is a Visual Composer integration leftover and is mostly inert today, but downstream code still reads it — keep it set.

Related articles

• Recipe: Register a content class
• Recipe: Add a button
• Hook: mam_app_settings_get_buttons
• Hook: mam_get_phone_data_before_send
• Frozen public contracts reference
• One article per content class (see the table above)

Metadata