Page

Page Settings for GoHighLevel

One optional block that sets the page up. Name your brand colors and every color picker in every element offers them; an element that uses one follows it from then on, so changing a brand color here repaints the whole page. It also sets what "Page headline font" and "Page body font" mean, the border new elements start with, and how the page scrolls: a styled or hidden scrollbar, smooth scrolling to linked sections, an eased mouse wheel, a scroll progress bar and the text selection color.

Variants shown
2
Dependencies
None
Variants

2 ways to run it

Every one of these is the real element with different settings. Press play again to watch any of them from the start.

the card on the canvas
a fuller brand
What you can control

Controls, grouped the way you build

  • Brand colors
  • Page fonts
  • New element defaults
  • Scrollbar
  • Smooth scrolling
  • Scroll progress bar
  • Text selection
  • On the canvas

Everything it does

  • up to 24 named brand colors, linked live to any element
  • page headline and body fonts, including a custom family
  • the border and corners new elements start with
  • styled or hidden scrollbar with handle, hover and track colors
  • smooth scrolling to linked sections, with an offset for a sticky navbar
  • eased mouse-wheel scrolling
  • scroll progress bar, top or bottom, solid or two-color
  • text selection color
  • card label on the builder canvas
Worth knowing

How it actually behaves

Brand colors are links, not copies: the element paints one custom property per color onto the page, and a linked setting carries the color it was picked from as its fallback. Delete the block, or the color, and every element keeps painting that fallback. Nothing depends on it.

It renders nothing for visitors. On the builder canvas it shows a card naming what it controls, and it warns there if a second one is on the page.

Canvas and WebGL elements cannot read a custom property, so their colors resolve through the runtime instead, without ever adding a node to the page.

Setup

How to add Page Settings to a GoHighLevel page

  1. 01

    Open the element panel

    In the page builder, click the + button to add a new element.

  2. 02

    Go to Widget Marketplace

    In the left menu, select Widget Marketplace.

  3. 03

    Find Animated Elements

    Locate the Animated Elements widget by Funnelslayer in the installed apps list.

  4. 04

    Drag and drop it into the page

    Drop the widget where you want it. The Web Widget Settings modal opens on the element gallery: "Select an element to start with".

  5. 05

    Select an element and continue

    Choose an element (Animated Counter, Typing Animation, and more), then click Continue. Search by name or by what it does, or use the category rail on the left to narrow the list. You can switch elements later without losing your settings.

  6. 06

    Customize it

    Use the element's settings to customize everything to match your brand. The live preview updates as you go, with separate desktop and mobile views.

  7. 07

    Set the page up once

    Add the Page Settings element once, near the top of the page. It holds your brand colors, the page fonts, the border new elements start with, and how the page scrolls: a styled or hidden scrollbar, smooth scrolling to linked sections, an eased mouse wheel, a scroll progress bar and the text selection color. Every other element can link its colors to a brand color, so changing one repaints the whole page. It renders nothing for visitors, and it is optional: without it, every element keeps the colors it was given.

Questions

Common questions

What happens if I delete Page Settings later?
Nothing breaks. A linked setting carries the color it was picked from as its fallback, so every element keeps painting that color. Nothing on the page depends on the block being there.
Does it add anything visible to the page?
No. It renders nothing for visitors. The card you see is on the builder canvas only, so the block stays selectable.
Do brand colors work on the canvas and WebGL backgrounds?
Yes. Those elements cannot read a CSS variable, so their colors resolve through the runtime instead, without adding anything to the page.