Adding a New Page - Standard

Standard pages are custom pages whose content lives inside Fanmaker. Build them at Design & Content › Custom Pages in the admin.

1. Click New Page. That opens the New Custom Page form — the same form you get when you edit a page later, so you can build the whole thing in one pass.

2. At the top of the first card is the Page type toggle. Leave it on Standard page — content you write here. (Outbound link is the other half of the toggle, for a page that just sends fans to another site.)

3. Title. Shown as the page heading in the app.

4. Link text. What fans tap in the menu or footer — normally an abbreviated version of the Title. Leave it blank and the Title is used.

5. Page address. Your site's own web address is printed in front of the box, so you only fill in the path — start with a "/", for example "/tickets" for a page about tickets. Pick something related to your Title, and don't use spaces.

The address has to be unique within your program, and a handful of paths are reserved by Fanmaker: /tasks, /store, /leaderboard, /faq, /accounts and /terms. If you pick one of those, or one that's already taken, you'll see an error explaining which rule you hit.

6. Page content. This is where you build the content of the page, in a rich-text editor. Write one responsive block — fans see it on every screen size. The Title is placed at the top of the page automatically, so you don't need to repeat it here.

Visibility

The narrow card beside the page details holds three settings:

Published — the page is live. It starts unticked, so a page only goes out when you say so. With it off the app won't serve the page at all: its links disappear and its address stops working, even for someone who has it saved.

Show in footer — adds its link to the footer row at the bottom of the app's menu, where Privacy Policy and Terms sit.

Logged-in only — saved, but the apps don't act on it yet, so the page stays reachable to signed-out fans either way. Use Published when you actually need a page down.

Note: there's no checkbox here for the main menu, and that's deliberate — adding a page to the menu is done on the Menu page. The form links you straight there.

Restricting who sees the page

Allow users by tag. Tick this and add Allow list tags. The page is then available to any member carrying at least one of those tags; members without one won't see it.

Block users by tag. Tick this and add Block list tags. The page won't be shown to any member carrying one of those tags. The block list beats the allow list — a member with both an allowed and a blocked tag won't see the page.

Membership levels (none = all). Add the levels that should have access. Leave it empty and the page is open to all levels.

Note: tag rules and the footer don't mix. The footer link list skips any page with an allow or block list on it, for every fan — so adding tags to a page that shows in the footer removes its footer link entirely rather than targeting it. Its menu link and direct address still work, and the admin tells you on screen when this is happening.

7. Click Create Page.

Note: Creating a page doesn't put it in your menu. To give fans a way to reach it, add a menu item under Design & Content › Menu, choose Internal (custom page) and pick this page from the dropdown.

Tip: Position in the list is set by dragging rows on the Custom Pages table, not by a number on the form. Clear any search or filters first — reordering is only available on the full list.