Basics of naming your areas & The area list of Elemental

This is a community-contributed tutorial. This tutorial is over a year old and may not apply to your version of Concrete CMS.
Mar 16, 2016

When you make an original theme, try to use the basic names of the area, so that you won't have to worry about switching themes.

First, let's try to use the area names of Elemental theme.

Basics of naming your areas

  • Use can use alphabet and numbers with space
  • When you enable translation interface, you can translate the area name
  • Do not overlap the Global Area and Area
    • Before and after switching the theme, try not to use the same name of area and global area
    • e.g.) "Sidebar" area was the name of area before, but the new theme has set "Sidebar" as Global Area.
  • If you want to set "Sidebar" as global area, install Concrete CMS with "Blank" starting point

The name of Global Areas in Elemental

  • Header Search
  • Header Site Title
  • Header Navigation
  • Footer Site Title
  • Footer Social
  • Footer Legal
  • Footer Navigation
  • Footer Contact

The name of Areas in Elemental

  • Page Header
  • Main
  • Page Footer
  • Sidebar
Recent Tutorials
Customize locale icons
Oct 29, 2024
By myq.

How to customize locale (language region) flags

Concrete CMS Caching Guide
Oct 16, 2024

An overview of types of caching in Concrete and considerations when using them.

Redirect all requests to HTTPS
Oct 9, 2024
By myq.

How to follow best practices for a secure web

Upgrade Concrete versions 9.3.1 and 9.3.2
Sep 10, 2024
By myq.

How to get past a bug in versions 9.3.1 and 9.3.2 that prevents upgrading the Concrete core through the Dashboard

How to use Composer with Marketplace extensions
Aug 22, 2024

Composer can be used to manage third-party extensions from the marketplace

Controlling Google Tag Manager Tags Based on Concrete CMS Edit Toolbar Visibility
Aug 13, 2024

This document provides a step-by-step guide on how to control the firing of Google Tag Manager (GTM) tags based on the visibility of the Concrete CMS edit toolbar. It explains how to create a custom JavaScript variable in GTM to detect whether the edit toolbar is present on a page and how to set up a trigger that ensures GTM tags only fire when the toolbar is not visible. This setup is particularly useful for developers and marketers who want to ensure that tracking and analytics tags are not activated during content editing sessions, thereby preserving the accuracy of data collected.

Improvements?

Let us know by posting here.