Skip to main content
M
MoonTech
Communication

Content Management

Portal pages, widgets and dynamic content

9
Sections
2
Panels
Club PanelUser Portal
Service Overview

Content in Club Panel lets managers build static portal pages — about us, terms, campaigns — using a section-based editor similar in spirit to App Builder but focused on club website-style pages rather than the full app shell. Pages can be draft or published; widgets include text, images, and embeds.

Use Content for legal pages, help centers, and marketing landings that should appear in the portal drawer without rebuilding the entire app home in App Builder.

1
Section 1 of 9

Core concepts

ConceptMeaning
**Page**URL slug with title and ordered sections.
**Section / widget**Block of content on a page.
**Draft**Visible only in panel preview — not live for members.
**Published**Live for members with link in drawer if configured.
**Slug**URL path segment — e.g. `about-us`.
Previous sectionNext section
2
Club PanelSection 2 of 9

Content hub

**Menu:** Club Panel → Community → Content

Entry point — list all pages, filter by status, create new.

Prerequisites

  1. Content option on club subscription.
  2. Editor role with content create/update permission.
  3. For drawer links, App Builder or portal navigation must expose published slugs.

Page layout

  • Page list: title, slug, status, last updated, actions (edit, preview, delete).
  • New page button.
  • Search by title or slug.

Step-by-step — first-time setup

  1. Open Community → Content.
  2. Create Terms of use and Privacy as drafts.
  3. Legal review offline → publish when approved.
  4. Add drawer link via App Builder dynamic page or portal nav settings.
  5. Create About us and FAQ for member trust.
Previous sectionNext section
3
Section 3 of 9

View & create pages

**Menu:** Club Panel → Content → page editor**

Page form fields

FieldPurpose
**Title**Display heading and browser title
**Slug**Unique URL path — lowercase, hyphens
**Status**Draft / Published / Archived
**Show in drawer**Adds link to portal hamburger menu
**Meta description**SEO / sharing snippet if supported

Step-by-step

  1. New page — enter title; slug auto-suggests from title.
  2. Add sections from widget palette (see below).
  3. Reorder sections via drag handle.
  4. Preview in panel before publish.
  5. Set Published and save.
  6. Test on portal logged in as member.
Previous sectionNext section
4
Section 4 of 9

Widget types

Common section types available in the content editor:

WidgetUse caseKey settings
**Hero**Top banner with title and CTABackground image, button link
**Text block**Paragraph contentRich or plain text
**Rich text**Formatted HTML contentWYSIWYG editor
**Image**Full-width or inline imageUpload, alt text, link
**Image gallery**Multiple photosGrid columns, captions
**Video embed**YouTube / hosted videoURL, aspect ratio
**FAQ accordion**Expandable Q&AQuestion/answer pairs
**CTA banner**Call to action stripText, button, internal page link
**Divider / spacer**Layout spacingHeight or line style
**Embed form**Link to App Builder formSelect form by code

Step-by-step — add widget

  1. In page editor, click Add section.
  2. Pick widget type from modal.
  3. Fill content tab in right panel.
  4. Set optional click action (internal page or external URL — use menu names in docs to members).
  5. Save page.
Previous sectionNext section
5
Section 5 of 9

Publish & draft

Workflow

Draft → Preview → Published → (optional) Archived

Step-by-step

  1. Keep work in Draft until stakeholders approve.
  2. Use Preview URL or panel simulator if available.
  3. Switch to Published — immediate for members after cache refresh.
  4. Archived hides page but keeps history; use instead of delete for old campaigns.

Tips

  • Do not change slug after publishing — bookmarks break.
  • Unpublish by reverting to Draft if urgent takedown needed.
  • Drawer visibility requires both Published and Show in drawer checked.
Previous sectionNext section
6
Section 6 of 9

Rich text editor

**Content editor → Rich text widget**

Features

  • Headings, bold, lists, links, tables (if enabled).
  • Paste from Word — review formatting cleanup.
  • Link to other content pages by slug.

Step-by-step

  1. Select rich text widget.
  2. Write in editor; use heading hierarchy for accessibility.
  3. Insert links to portal pages using internal picker.
  4. Avoid pasting raw HTML from unknown sources — security risk.

Tips

  • Keep line length readable — break long policy text with headings.
  • Mobile preview: images should be responsive uploads.
Previous sectionNext section
7
Section 7 of 9

Example: About us page

  1. Hero — club name, tagline, hero image.
  2. Rich text — mission paragraph.
  3. Features grid or Image gallery — team or office photos.
  4. FAQ accordion — top 5 member questions with links to Support.
  5. CTA banner — “Join now” linking to registration or App Builder form.

Step-by-step

  1. New page — title “About us”, slug about-us.
  2. Add sections in order above.
  3. Publish and enable Show in drawer.
  4. Link from App Builder home quick action for visibility.
Previous sectionNext section
8
Section 8 of 9

Content vs App Builder

AspectContent moduleApp Builder
ScopeStandalone pagesFull app + home + tabs
NavigationDrawer / direct URLTabs, drawer, actions
Best forLegal, about, campaignsProductized member UX
Previous sectionNext section
9
Section 9 of 9

Summary for support

  • Content pages = slug + widgets + publish state.
  • Members see only Published pages with drawer flag or direct link.
  • Legal and FAQ content belongs here; interactive flows belong in App Builder Forms.
Previous sectionNext section