Primary responsibility
Renders a single WordPress page or post inside the app. The post body is filtered through standard the_content. Below the body, mam-suite content sections (featured image, social-media row, etc.) can be appended.
Settings
| Setting |
Type |
Environment |
Purpose |
post_id |
number |
per-button |
The post id to render |
show_featured_image |
yes-no |
per-button |
Render the post’s featured image above the body |
show_title |
yes-no |
per-button |
Render the post title |
show_author |
yes-no |
per-button |
Render author byline |
show_date |
yes-no |
per-button |
Render publish date |
style_* |
various |
per-button |
Typography colors |
Hooks involved
| Hook |
Type |
Role |
the_content |
Filter |
Standard WP content filter — your shortcodes, embeds, and content filters all run |
mam_main_content_class_featured_image |
Filter |
Featured-image section builder (from content-class-elements) |
mam_add_featured_image |
Filter |
Alternate featured-image hook |
Gotchas
- All standard WP content filters run. Shortcodes that produce HTML the mobile app can’t render (Flash, complex iframes) will look broken on the device.
- Embeds (oEmbed) generate HTML that depends on JavaScript. The app’s webview can render them; raw text content cannot.
- Single-post only. For a list of posts, use Content class: WP Post Category. For dynamically-routed posts, use Content class: WP Post Content.
Related articles
- Content classes overview
- Content class: WP Post Content
- Content class: WP Post Category
- Content class elements reference
| Field |
Value |
| Article type |
Screen Reference |
| Plugin slug |
mam-main |
| Applies to plugin version |
2.1.11+ |
| Category |
App Settings Reference |
| Audience |
WordPress admin / PHP developer |
| Class name |
local_app_wp_content (frozen) |
| Source file |
includes/content-classes/local-app-wp-content-class.php |
| Last verified |
2026-05-02 |
