Goal

Pick a published WordPress Page, point a button at it, and your app renders that page natively — body copy, featured image, all of it. Because the content comes straight from WordPress, editing the Page there is all it takes to update what your app users see; there’s no separate copy to keep in sync.

Reach for this when you’ve got a piece of relatively static, editorial content — an About Us, a Terms of Service, an FAQ, a welcome message — that already lives (or should live) on a WordPress Page. Under the hood, it’s powered by the WordPress Page Content content type (the local_app_wp_content content class in mam-main).

Pages vs. posts: this content type only lists Pages. Got a single blog post, a category of posts, or a feed in mind instead? One of the WP Post content types will serve you better — see Related at the end.

Prerequisites

• Admin access to Mobile App Manager.
• A published WordPress Page. The content selector only lists Pages whose status is Published — drafts, private, and pending pages will not appear.
• (Optional) A featured image set on that Page if you want an image rendered with the content. The featured image is pulled automatically when one is present; nothing extra is required.

Steps

1. Prepare the Page in WordPress

Head to WordPress → Pages, open (or create) the Page you want to show, and make sure it’s set to Published. Want an image too? Set the Page’s Featured image in the editor sidebar.

The app renders your page body through WordPress’s standard content filter — the same process that turns what’s in your editor into the page WordPress shows visitors — so whatever you put there is exactly what your users get. Keep it mobile-friendly: shortcodes, embeds, and HTML all run, but anything built around desktop layout or heavy scripting can look broken on a phone. Plain text, images, headings, and simple formatting are the safest bet.

2. Add a button and choose the content type

Open Mobile App Manager, head to the Buttons admin, and add a button (see Recipe: Add a button if you want the full walkthrough). When you reach the content type, choose WordPress Page Content — that’s what tells the button to pull from a Page.

3. Select the Page

With WordPress Page Content selected, the button hands you a Page selector — a dropdown that opens on “Select WordPress Page…” and lists your published Pages alphabetically by title.

Pick the Page you prepared in step 1.

Don’t see your Page? It’s almost always one of two things: it isn’t published yet, or it’s a post rather than a Page. Head back to step 1 and check.

4. Give the button a title and place it

Give the button a display title — this is the label users tap, not the Page’s own title — then place it wherever users will find it: a home-screen layout section, the left menu, or the tab bar. Placement works just like it does for any other button; see Recipe: Add a button.

5. Verify in the Previewer

Now see it live. Open the Previewer, switch to the role you set the button up for, and tap through to it. You should see:

• The Page body, rendered from the WordPress content.
• The featured image, if the Page has one set.

If the body looks off, the usual culprit is content that doesn’t translate to mobile — complex shortcodes, desktop-only embeds. Simplify the Page in WordPress and check again.

How it works (so you know what to expect)

Here’s the mechanism behind it: when the app asks for this button’s content, the WordPress Page Content class fetches the Page you picked and runs its body through WordPress’s standard the_content filter — the same pipeline that builds the Page on your website. That means your shortcodes, embeds, and content filters all fire, and any edit you make in WordPress shows up in the app with no rebuild required.

If the Page has a featured image, the class grabs the full-size version and sends it along with the content, so the image just comes along for the ride. No featured image, no problem — the content renders fine without one.

Two things worth keeping in mind:

• It’s a single Page. This content type renders one Page — not a list, not a feed.
• It’s only Pages. Posts are deliberately left out of the selector — for those, reach for the WP Post content types instead.

Related

• Recipe: Add a button — the full button-creation and placement workflow.
• Content class: WP Content — the technical reference for the WordPress Page Content type, including the content filters that run.
• Show a single blog post in your app / Content class: WP Post Content — for a single post instead of a Page.
• Show a category of posts in your app / Content class: WP Post Category — for a list/feed of posts.
• Content classes overview — the full set of content types you can attach to a button.