Page Editor

The page editor is where you build the visible structure of a page or template. This is the place for adding modules, arranging the layout, and deciding what appears in the main area and sidebars.

What you edit here

In normal use, the page editor has three jobs:

• Set up the page basics such as title, URL, layout, and SEO
• Place modules in the correct regions
• Adjust each module so it shows the right content in the right style

Main areas of the editor

Page settings

At the top, you define the basics of the page:

• Title
• URL / slug
• Layout
• Page type
• Dynamic kind, if the page is a template
• Meta title and meta description

Content regions

These are the places where modules are added.

Depending on the layout, you will work with:

• Main
• Left sidebar
• Right sidebar

Modules are shown in order from top to bottom.

Shell regions on this page

Global shell regions are managed in Settings -> Global regions.

From the page editor, you decide how this specific page behaves relative to those global regions:

• use the global region as-is
• hide it on this page
• replace it with page-specific modules

This is useful when one page needs a cleaner shell than the rest of the site, or when a landing page needs a different promo or navigation block.

Adding a module

1. Open the page or template you want to edit
2. Go to the region where the block should appear
3. Click Add Module
4. Choose the module you want
5. Adjust its settings

If you prefer not to start from zero, apply a preset first and then refine the modules it adds.

Common module actions

Each module card lets you do the main layout tasks without leaving the page:

• Expand or collapse the module settings
• Enable or disable the module
• Drag to change the order
• Duplicate the module
• Delete the module
• Preview widget modules in the playground

Module types you will use most

Widget modules

These are the standard product modules such as:

• Livescore
• Standings
• Match header
• News feed
• Breadcrumb
• CTA
• Newsletter

Widgets are the normal choice when you want live data, structured content, or reusable design blocks.

Grid containers

If you need modules side by side inside the main content area, you can add a Grid block with 2 or 3 columns.

This is useful for:

• comparison sections
• editorial pages that mix data and text
• sponsor or CTA blocks next to supporting content
• landing pages that need tighter composition than a single vertical stack

Each column can hold its own set of modules.

Text modules

Use text modules when you want editor-style content directly on a page, without creating a separate article.

This is useful for:

• Intro text on landing pages
• Simple explanations
• Editorial notes inside a static page

HTML modules

Use HTML blocks only when you need a small custom block that does not fit a normal module.

This is useful for:

• Simple embeds
• Third-party snippets
• Small custom markup

For most content, a normal module is easier to maintain than raw HTML.

Editing module settings

Most widgets expose their options as normal fields such as:

• Layout or variant
• Display mode, when supported by the module
• Limits
• Filters
• League, category, or other content selection
• Wrapper options such as title or card style

Some modules support more than one rendering mode. For example, Match Lineups can now switch between:

• Widget — standard module layout
• Text — inline editorial prose without the normal widget card

This display choice is configured directly inside the module settings, so the same capability works in Pages, dynamic templates, and article shortcodes.

On dynamic templates, many sports modules can detect the current context automatically. That means you often do not need to fill in IDs manually when the module is placed on the matching template.

Grid containers also have a small set of layout controls:

• 2 or 3 columns
• column gap size
• independent module stacks inside each column

Wrapper options

Modules can be presented differently without changing their content.

Current wrapper controls include:

• Title
• Subtitle
• Card style
• Padding
• Radius
• Background, border, and text colors
• Split mode
• Desktop or mobile visibility

These settings help the same module fit different parts of the site.

For grouped content, use Card section when one visual card should contain multiple modules. Use Grid when the primary goal is columns.

When to use page modules vs article modules

Use the page editor when the module belongs to the layout of the page or template.

Use the article editor when the module should appear only inside one story.

Example:

• A standings block that should appear on every league page belongs in the league template
• A standings block used only in one article about the title race belongs inside that article
• A ticker that should appear on all pages belongs in the global shell regions
• A promo banner that should appear only on one landing page can replace a global shell region just for that page

See Using Modules for the full placement guide.

Good working habits

• Start with the main region before filling sidebars
• Keep sidebars compact and supportive
• Reuse templates for repeated structures instead of rebuilding them page by page
• Use presets to save time, then customise
• Keep global shell modules limited to things that deserve site-wide visibility