Goal

Use this when you have one piece of content that doesn’t change much — an “About Us” page, a welcome message, a policy, a how-to — and you’d rather send users straight to it than make them browse a list first. Tap the button, and the app renders that single WordPress Post as a full detail screen.

You pick the post once, while you’re building the app, and the button stays bound to it from then on. The app loads that post’s body — its stored content, normalized to plain ASCII — and shows the featured image too, if the post has one.

Want a list instead, something users browse and tap into? Use WP Post Category for the list, and let it hand off to this content type for the detail screen. See Related below.

Prerequisites

• MAM Suite installed and activated, with mam-main active.
• At least one published WordPress Post. Drafts, pending, and private posts are not offered for selection — the picker only lists posts with status publish.
• Admin access to the Mobile App Manager in WordPress, where you assemble your app’s buttons and screens.

One thing worth knowing up front: this content type only lists WordPress Posts. If what you want to show actually lives on a Page, reach for the WP Content content type instead — that’s the page/post detail renderer built for that case.

Steps

1. Open your app’s button layout.
   Head to Mobile App Manager in WordPress admin and open whichever screen holds the buttons you’re arranging — the main tab bar, the home grid, or the left menu, wherever you want this button to live.

2. Add a new button (or edit an empty slot).
   Drop a button into the layout. Every button has a content source — this is where you tell it what to actually show.

3. Set the content source to “WordPress Post Content.”
   In the content-source selector, choose the WordPress Post Content type. That tells the button it’s rendering a single post; the next step is picking which one.

4. Pick the post from the dropdown.
   A second dropdown appears, starting on “Select WordPress Post…”. It lists your published posts alphabetically by title — pick the one you want this button to open.

   • The dropdown can hold up to several hundred posts. Very long titles get shortened there (hover to see the full title), but whichever one you pick, the button still binds to the whole post.
   • Don’t see your post? Confirm it is published (not a draft or scheduled) and is a Post (not a Page).

5. Give the button a label and icon.
   Set a display name and icon so users know what they’re tapping before they tap it — same as any other button in your layout.

6. Save the layout.
   Save your changes in Mobile App Manager — this writes the button’s configuration into your app’s button data.

7. Verify in a running app.
   Now see it live: open your app (or a build/preview that points at this site) and tap the button. You should see the post’s full body, plus its featured image if one is set in WordPress. If the post has no featured image, no problem — the screen just shows the body on its own.

What you’ll see on the screen

Here’s what makes up the detail screen, built from the post you selected:

• Body — the post’s stored content, normalized to plain ASCII. It’s sent as the raw post content rather than fully re-rendered through WordPress’s the_content display filters, so shortcodes and embeds may not expand the way they do on your website, and a few typographic characters like curly quotes and em dashes get simplified along the way.
• Featured image — if the post has a WordPress featured image, the app pulls it in and displays it. With no featured image, the image area is simply left out.

Because the post is resolved fresh each time the app fetches its data, editing the post in WordPress updates what the app shows on the next refresh automatically — you don’t need to re-pick the post in Mobile App Manager just to publish a content edit.

Troubleshooting

• My post isn’t in the dropdown. It has to be published and a Post — drafts, scheduled, private, and trashed posts are all excluded, and Pages never appear here (use WP Content for a Page).
• The button is empty / shows nothing. Double-check step 4 — the content type needs an actual post selected, not left on “Select WordPress Post…”. Re-save the layout once you’ve picked one.
• No image shows. This content type only displays the post’s featured image. Images placed inline in the post body still render fine as part of the body, but the dedicated image slot is driven solely by the WordPress featured image, so set one on the post if you want it to show here.
• A content edit isn’t showing up. The app caches its data between fetches, so give it a nudge — trigger a refresh in the app, or wait for the next data pull.

Related

• Content class: WP Post Content — the reference article for the content type behind this button (settings, payload shape, and gotchas).
• Show a list of posts from a category / Content class: WP Post Category — for a browsable list that drills into post detail screens.
• Content class: WP Content — render a single WordPress Page (or post) by this alternate renderer.
• Content classes overview — how buttons map to the things your app can render.