Modules Overview
Modules are the building blocks of your site. They are the pieces you place on pages, templates, global layout areas, and even inside articles to show scores, standings, editorial content, navigation, promotions, or social elements.
A module can be as simple as a divider or as rich as a full livescore block, a league table, a hero section, or a bookmaker CTA.
Modules can also be arranged inside Grid containers when you want 2-column or 3-column sections in pages or articles.
Where modules can be used
You can use modules in four main places:
| Place | Best for | Typical examples |
|---|---|---|
| Pages and templates | Content that belongs to a specific page or route | Homepage blocks, match page layout, league sidebar, contact page sections |
| Global layout slots | Content that should appear across the site | Top bar notices, live ticker, newsletter above footer, legal notices |
| Inside article bodies | Editorial content mixed directly into a story | Match summary between paragraphs, standings table in an analysis, video or CTA inside a feature |
| Article template | Content that should wrap every article | news-post, author box, related news, newsletter, share buttons |
See Using Modules for the full workflow.
What modules let you do
Modules are used for three broad jobs:
- Show sports data such as livescores, fixtures, standings, lineups, stats, odds, and player or team information
- Build editorial layouts such as heroes, FAQs, galleries, timelines, reviews, comparison tables, and CTAs
- Add site structure such as menus, breadcrumbs, social links, taxonomies, banners, and notices
That means the same site can mix live data, editorial storytelling, navigation, and monetization without custom development for each page.
How to think about modules
For normal day-to-day work, the easiest rule is:
- Use a page or template module when the block should stay in the layout
- Use a global layout module when it should appear on many pages automatically
- Use an article module when it belongs to one specific story and should sit between paragraphs
Examples:
- A homepage livescore strip belongs on the homepage layout
- A newsletter signup used everywhere belongs in a global layout slot
- A match stats block used only in one article belongs inside the article body
Main module families
| Family | What it is for | Common examples |
|---|---|---|
| Sports | Detailed match, team, league, and player data | match-header, league-standings, team-players, player-stats |
| Livescore & discovery | Browsing and real-time score coverage | livescore, live-ticker, featured-matches, top-leagues |
| Content | Editorial presentation and structured content | hero, callout, faq, timeline, comparison-table |
| News | Article lists and article-related navigation | news-feed, context-news, news-taxonomy |
| Navigation & social | Site structure and sharing | breadcrumb, menu, share-buttons, social-links |
| Monetization | Commercial and partner content | bookmaker-cta, broadcast-list, banner-slot |
Modules on dynamic templates
On match, team, league, and player templates, many sports modules understand the current page automatically.
In practice, this means:
- A standings module on a league template can show that league without extra setup
- A team fixtures module on a team template can show that team automatically
- A context-news module on an entity page can surface related articles from that context
This is why templates are the best place for repeated sports layouts.
Modules inside articles
Articles are not limited to text and images. In the news editor, the Modules button inserts a shortcode for you, and the public site renders it as a real module inside the story.
This is especially useful for:
- Match summaries inside recaps
- Standings tables inside league analysis
- Team or player stats inside features
- Video, poll, CTA, newsletter, or promo blocks inside long-form content
You do not need to type shortcodes manually. The editor provides a searchable module picker grouped by category.
Module presentation options
Most modules can also be styled at the instance level with wrapper settings such as:
- Title
- Subtitle
- Card style
- Padding
- Radius
- Background, border, and text colors
- Split mode
- Desktop/mobile visibility
These settings change how the module is presented, not what data it shows.
Some editorial and monetization modules also expose module-level visual tokens such as density, prominence, box colors, and button colors. Use those when the module's own internal layout should become denser, more prominent, or more conversion-focused.
For details, see Module Wrapper.
Plan restrictions
Some modules depend on plan features. For example:
- Odds modules need odds access
- Bookmaker modules need bookmaker features enabled
- Broadcast modules need broadcast features enabled
- News modules need the editorial/news feature enabled
If a required feature is not active, the module may still be configurable in the CMS but it will not render on the live site.