Search Knowledge Base Articles

Page Builder

🌐 Page Builder

Overview

The Page Builder module allows you to create and manage single frontend pages on your App Dashboard domain or subdomain.

This is useful when you want to publish a simple standalone page outside of your main website, such as:

  • an app landing page
  • an app download / install page
  • an app promotion page
  • a campaign page
  • a single branded information page
  • any other app-specific custom page

These pages are hosted on your dashboard domain or subdomain and can be linked to from your main website, emails, social media, QR codes, or other marketing materials.

Where to find it

→ Page Builder

What this section does

From the Page Builder page, you can:

  • create a new page
  • choose a starting template
  • organise pages into folders
  • edit page settings and SEO details
  • choose which page acts as your landing page
  • open a page in the visual page builder
  • upload template ZIP files
  • manage allowed external domains for embedded content
  • control whether logged-in dashboard users are redirected into the dashboard instead of seeing public pages

How Page Builder works

Page Builder stores and serves HTML pages from your dashboard installation.

In simple terms:

  • you create a page
  • edit its content in the visual builder
  • save it
  • the page becomes available on your dashboard domain/subdomain

This means the module is ideal for single-page experiences rather than full websites with complex navigation.

It is especially useful for:

  • App landing pages used on a client’s main website
  • App-only campaign pages
  • temporary promotional pages
  • custom information pages specific to the app

Main Page Builder screen

When you open Page Builder, you will see the page manager with three main buttons at the top:

  • New Page
  • Upload Template
  • Settings

Below this is a list/tree of your existing pages and folders.

1. New Page

Click New Page to create a new page.

Fields on the New Page form

Template

This lets you choose the starting file/template for the new page.

Options include:

  • Blank Template for a page built from scratch
  • any other available starter templates already in the system

Use this when:

  • you want a totally custom page from scratch
  • you want to start from an existing layout or example page

File Name

This is the actual filename of your page.

Example:

  • app-landing.html
  • special-offer.html
  • download-app.html

Best practice for File Name

  • always use lowercase
  • use hyphens instead of spaces
  • keep it short and descriptive
  • include .html at the end

Good examples:

  • app-landing.html
  • spring-promo.html
  • loyalty-page.html

Avoid:

  • spaces
  • special characters
  • very long names
  • vague names like page1.html

Save to Folder

This lets you place the page inside a folder.

Example:

  • /
  • campaigns
  • app-pages

This helps keep your pages organised.

For example:

  • campaigns/summer-sale.html
  • app-pages/install-guide.html

Tips

Use folders when you expect to create several pages over time, for example:

  • campaigns
  • offers
  • downloads
  • support

If you leave the folder blank, the page will be saved in the main pages area.

2. Edit Page

Each page can be edited from the page manager.

The edit option allows you to control the page filename and metadata.

Fields in Edit Page

File Name

This lets you rename the page file.

Be careful when changing this, because if the page has already been linked from your website, emails, QR codes, or ads, the old link may stop working.

Set as Landing Page

Choose Yes if this page should become the main landing page for the root of your dashboard domain/subdomain.

This is useful when you want visitors to reach a specific public-facing page as soon as they visit the Page Builder area.

For example, you may want your dashboard subdomain to open directly to:

  • your app landing page
  • your app promotion page
  • a branded welcome page

Only set this for the page you want as the main public entry page.

Layout Template for Rendering

This controls the wrapper/layout used when the page is displayed.

The available options are:

  • Bootstrap
  • Vanilla

In most cases, Bootstrap will be the safer choice unless you specifically need a simpler/plain rendering approach.

SEO and metadata fields

The edit form also includes a set of metadata fields.

These can include:

  • Title
  • Meta Description
  • Meta Keywords
  • Meta Author
  • Robots
  • Canonical
  • Open Graph Image URL
  • Custom CSS
  • Favicon URL

What these fields are for

Title

This is the browser/page title and is important for SEO and sharing.

Use a clear, branded title such as:

  • Download the Redpost Equestrian App
  • App Offers and Rewards
  • Install Our App Today

Meta Description

A short description of the page for search engines and sharing previews.

Keep it concise and clear.

Meta Keywords

This is an older SEO field and is less important than it once was, but can still be filled in sensibly.

Meta Author

The content/page author.

Robots

This tells search engines how to treat the page.

Examples:

  • index, follow
  • noindex, nofollow

Use noindex, nofollow for pages you do not want appearing in search results.

Canonical

Use this if the page content is duplicated elsewhere and you want to point search engines to the preferred version.

Open Graph Image URL

This controls the image used when the page is shared on some social platforms or messaging apps.

Custom CSS

Use this for page-specific styling adjustments.

Only use this if you are confident making styling changes.

Favicon URL

Lets you set the small icon shown in the browser tab for that page.

3. Duplicate Page

The duplicate option allows you to create a copy of an existing page.

This is useful when you want to:

  • reuse an existing layout
  • create seasonal variants of the same page
  • test multiple versions of a landing page
  • speed up production of campaign pages

When duplicating, enter a new file name so the copied page is saved separately.

Example:

  • original: app-landing.html
  • duplicate: app-landing-spring.html

4. Build Page

The Build Page option opens the page in a visual page editor.

This module supports visual editors such as:

  • Vvveb
  • GrapeJS

Depending on your installation, one or both may be available.

What the builder is for

The builder lets you visually design the page content, such as:

  • text blocks
  • headings
  • images
  • buttons
  • sections
  • layouts
  • spacing and styling
  • basic landing page structure

This is where the actual page design is created and updated.

Best practice when building a page

Keep standalone pages focused on a single purpose, for example:

  • install the app
  • learn about app features
  • access app-only offers
  • join a loyalty programme
  • read campaign information

A strong page usually includes:

  • a clear heading
  • a short explanation
  • one main call to action
  • app store/download buttons if relevant
  • branding that matches your business

5. Upload Template

The Upload Template option lets you upload a ZIP file containing a page template.

Fields

Name

Give the template a clear internal name.

Template File

Upload a .zip file containing the template.

When to use this

This is useful if:

  • Hoofpick/Apparati supplies you with a prebuilt page template
  • you want to import a prepared landing page structure
  • you want to reuse a design across multiple pages

This feature is more advanced and is generally best used with support or a prepared template file.

6. Settings

The Settings option controls global Page Builder behaviour.

Redirect to Dashboard

This controls whether logged-in users should be redirected to the dashboard instead of seeing public-facing pages.

In most cases, this should remain enabled.

This helps ensure that:

  • clients and staff who log in go straight to the working dashboard
  • public pages remain for visitors, customers, or prospects

Whitelist Domains

This is an important setting.

It controls which external domains are allowed for certain embedded content such as media or iframes.

For example, this may be relevant when embedding content from trusted services.

Enter domains separated by commas, for example:

youtube.com,vimeo.com,google.com

Only add trusted domains that you genuinely need.

OpenAI settings

The settings screen also includes AI-related fields such as API key, model, and token settings.

These are technical options linked to builder features and will normally only be relevant if specifically configured for your installation.

If you are unsure, leave these settings as provided by Hoofpick/Apparati.

Using Page Builder for an app landing page

One of the most common uses of this module is to create a custom app landing page.

This can be used as a page that:

  • explains the benefits of the app
  • links to the App Store / Google Play
  • promotes app-only discounts or rewards
  • gives users a branded app introduction
  • acts as the destination for website buttons such as Download our app

A good app landing page often includes:

  • app logo or branding
  • a headline explaining the benefit of the app
  • screenshots or visual sections
  • a short list of key benefits
  • download/install links
  • optional QR code
  • optional promotion or welcome offer

Typical client use cases

You may use Page Builder for:

App landing pages

A standalone branded page linked from your main website.

Campaign pages

A temporary page for an app-only campaign, promotion, or event.

Download pages

A simple page with store badges, QR codes, and install instructions.

App support pages

A page explaining app login, account access, or app-only features.

Offer pages

A page promoting app rewards, loyalty offers, or subscriber benefits.

Best practice tips

Keep each page focused

Each page should have one clear purpose rather than trying to do too much.

Use clear file names

Choose names that make sense later when you return to manage the pages.

Be careful when renaming live pages

If a page URL has already been shared, renaming the file may break that link.

Use landing page status carefully

Only mark a page as the landing page if you want it to be the main default public page.

Organise pages into folders

This helps keep your page list tidy as more pages are added.

Keep SEO fields sensible

Complete the page title and meta description for any page that may be publicly shared or indexed.

Only whitelist trusted domains

Do not add unnecessary third-party domains.

Things to be aware of

  • Page Builder is designed for single frontend pages, not a full website CMS.
  • These pages live on your dashboard domain/subdomain, not your main website unless specifically linked or proxied.
  • The module can serve public pages directly from your dashboard subdomain.
  • Logged-in users can be redirected back into the dashboard depending on settings.
  • Template upload and some advanced settings are more technical and may be best handled with Hoofpick/Apparati support.

Recommended use for most clients

For most app dashboard users, the simplest and most effective use of Page Builder is:

  1. create a single app landing page
  2. design it in the visual builder
  3. set it as the landing page if needed
  4. link to it from your main website

This gives you a quick, flexible way to publish app-related content without needing changes on your main website.

Summary

The Page Builder module gives you a simple way to create and publish standalone frontend pages on your App Dashboard domain or subdomain.

It is especially useful for:

  • custom app landing pages
  • app promotion pages
  • campaign pages
  • app-specific information pages

For most clients, this module is best used as a lightweight page tool for app-related marketing and support content.

Did you find this article useful?