Layout & Regions
Every page in Scorecenter has a layout that determines how content is arranged horizontally, and regions that act as drop zones for modules. Understanding these is essential for building pages that work well on all screen sizes.
The 4 layout modes
| Layout | Regions available | Best for |
|---|---|---|
| None (full width) | main | Landing pages, articles, minimal designs |
| Left sidebar | sidebarLeft, main | Editorial layouts with navigation or filters on the left |
| Right sidebar | main, sidebarRight | The most common layout: content + supporting data on the right |
| Both sidebars | sidebarLeft, main, sidebarRight | Dense, portal-style pages that maximize visible information |
Choosing a layout
- No sidebars gives your content the full viewport width. Best when the main content is self-sufficient and does not need supporting context.
- Right sidebar is the most popular pattern in sports sites. Main content (scores, articles, fixtures) on the left, supporting content (standings, ads, quick links) on the right.
- Left sidebar is less common but useful for pages with navigation-heavy structures like league directories or category filters.
- Both sidebars is the densest layout. Use it sparingly -- it works on desktop but stacks into a very tall page on mobile.
Content regions
Regions are the containers where you place modules. Each region is an ordered list -- modules render top to bottom in the order you arrange them.
main
Always present regardless of layout mode. This is the primary content area and typically holds your most important modules. On mobile, this region appears first.
sidebarLeft
Available when the layout is set to Left sidebar or Both sidebars. On mobile, this region stacks above the main content.
sidebarRight
Available when the layout is set to Right sidebar or Both sidebars. On mobile, this region stacks below the main content.
Adding modules to a region
Each region has its own Add module button at the bottom. Click it to open the module library, then select a module to insert. You can drag modules to reorder them within a region or move them between regions.
Put compact module variants in sidebars -- most modules have a compact or mini variant designed for narrow spaces. Full-width modules in a sidebar will look cramped.
Sidebar width control
Sidebar widths are configured in Settings > Styles and apply globally across all pages.
| Setting | Range | Default | Description |
|---|---|---|---|
| Left sidebar width | 14% -- 30% | 22% | Percentage of the page width allocated to the left sidebar |
| Right sidebar width | 14% -- 30% | 22% | Percentage of the page width allocated to the right sidebar |
The main region takes whatever space remains. For example, with a right sidebar at 25%, the main region gets 75% of the content width.
On screens narrower than the responsive breakpoint (typically 768px), sidebars collapse and stack vertically regardless of the width setting.
Layout presets
Layout presets are quick-apply configurations that set the layout mode, sidebar widths, and recommended module placement patterns in one click.
Standard
The default configuration for most pages.
- Layout: Right sidebar
- Right sidebar width: 22%
- Optimized for: General-purpose pages that need a main content column with supporting data on the side
This is the most versatile preset. It gives main content roughly 78% of the width while leaving enough space for standings tables, ad banners, and compact news feeds in the sidebar.
Balanced
A wider sidebar for pages that need more supporting content.
- Layout: Right sidebar
- Right sidebar width: 28%
- Optimized for: Portal-style pages where sidebar content is almost as important as main content
Use this when your sidebar holds full standings tables, detailed fixtures lists, or multiple stacked modules that need breathing room.
Editorial
Designed for article and news pages.
- Layout: Right sidebar
- Right sidebar width: 18%
- Optimized for: Reading-focused pages where the main content (article body) should dominate
The narrower sidebar keeps the reading column wide and comfortable. Sidebar space is reserved for minimal supporting elements like related articles or a single ad slot.
Focus
No distractions, full-width content.
- Layout: None (no sidebars)
- Optimized for: Landing pages, match detail pages, immersive experiences
All modules go into the main region. Content stretches across the full width. Best when every module is designed to work at full viewport width.
Shell modules
Shell modules are special region slots that sit outside the page content area. They belong to the site's persistent frame -- the parts that appear on every page regardless of which page the visitor is viewing.
They are managed in Settings -> Global regions. Pages and templates are managed separately in Pages.
| Shell region | Position | Common uses |
|---|---|---|
topbar | Above the header, at the very top of the page | Announcement bar, breaking news ticker, regulatory disclaimer |
belowHeader | After the header and navigation, before page content | Horizontal ad banner, league quick-links bar, live ticker strip |
aboveFooter | After page content, before the footer | Newsletter signup, related content grid, partner logos |
bottombar | At the very bottom of the page, after the footer | Cookie consent bar, sticky ad, compliance notice |
Shell vs page modules
The key difference:
- Page modules change from page to page. Your homepage has different modules than your contact page.
- Shell modules persist across all pages. A banner in
belowHeaderappears on the homepage, on match pages, on article pages -- everywhere.
Per-page overrides
Global shell regions apply by default, but pages can override them individually from the page editor.
For each shell region, a page can:
- keep the global version
- hide it on that page
- replace it with a page-specific set of modules
This gives you global consistency by default, while still allowing exceptions where needed.
Responsive behavior
On smaller screens, Scorecenter follows a predictable stacking order:
topbar(shell)- Header and navigation
belowHeader(shell)sidebarLeft(if present, stacks above main)mainsidebarRight(if present, stacks below main)aboveFooter(shell)- Footer
bottombar(shell)
This means visitors on mobile always see the main content before the right sidebar, and the left sidebar before the main content. Plan your module order with this stacking in mind.