Skip to main content
Version: v1 (Current)

Apps, Portals & Widgets

This guide covers how to assemble an attendee experience by adding plugin pages, widgets, and themes to a portal.

Adding a Page to a Project​

When you install a plugin page into a project, GXP creates a ProjectPage instance — a copy of the plugin template pinned to a specific version.

  1. Navigate to Project Dashboard → Pages
  2. Click Add Page
  3. Browse or search available plugin pages
  4. Select the plugin and version to install
  5. Configure the page's settings (each plugin exposes its own configuration form)

The ProjectPage stores:

  • The pinned plugin version
  • Resolved dependency values (model references for API access)
  • Custom settings, language overrides, and style overrides

Binding Pages to a Portal​

A page becomes accessible to attendees when you bind it to a portal. This creates a ProjectPortalPage with a URL slug.

  1. Navigate to Project Dashboard → Portals → [Your Portal]
  2. Click Add Page
  3. Select from your project's installed pages
  4. Configure the portal page:
SettingPurpose
URL SlugThe page's URL path (e.g., /schedule, /register)
TitleDisplay title in portal navigation
Sort OrderPosition in the navigation menu
Requires AuthenticationWhether attendees must log in to view
Access CodeOptional access code gate for the page

Each portal page automatically receives its own Sanctum API token, which is used by the plugin frontend to make authorized API calls scoped to the page's declared dependencies.

Configuring Pages​

Portal pages support three layers of customization that override plugin defaults:

Custom Settings​

Behavioral configuration exposed by the plugin developer. Each plugin defines its own settings schema — project admins configure values through the dashboard form builder.

Language Overrides​

Override any translatable string defined by the plugin. Useful for localization or customizing labels and messages.

Style Overrides​

CSS overrides applied on top of the plugin's default styles and the portal theme.

Adding Widgets​

Widgets are global components injected into every portal page. They're designed for persistent functionality like analytics, chat, and notifications.

  1. Navigate to Project Dashboard → Portals → [Your Portal]
  2. Click Add Widget
  3. Select and configure the widget

Widgets operate independently from pages — each widget gets its own API token and declares its own dependencies. Common widget types:

  • Head scripts — analytics trackers, tag managers (injected into <head>)
  • Floating overlays — chat bubbles, help buttons, notification bells
  • Banners — cookie consent, announcements

Applying a Theme​

Themes control the visual shell of a portal — layout, branding, colors, and fonts.

  1. Navigate to Project Dashboard → Portals → [Your Portal] → Theme
  2. Select a theme and version
  3. Configure theme settings (colors, branding, fonts)

A theme provides three layout templates:

  • Public — for unauthenticated pages (login, registration)
  • Private — for authenticated pages
  • System — for system pages (errors, access code entry)

Adding Tiles to the Dashboard​

Tiles are admin-facing analytics displays that appear on the project dashboard overview.

  1. Navigate to Project Dashboard → Overview
  2. Click Add Tile
  3. Select a tile plugin and configure it

Tiles render custom visualizations — attendance counters, registration charts, revenue breakdowns, real-time maps, and more.

Portal Domains and Activation​

Each portal is served on one or more custom domains:

  • Wildcard domains (e.g., *.customer.com) — shared across projects at the team level
  • Single domains (e.g., event.customer.com) — assigned to one portal

To activate a portal:

  1. Configure at least one domain
  2. Ensure DNS records point to the GXP platform (CNAME)
  3. SSL certificates are automatically provisioned

See Portal Architecture for the full domain resolution and authentication flow.

Next Steps​