Layout Management

Agility offers a wide array of robust authoring tools, but one of the most powerful features is our built-in Layout Management which delivers a best-in-class Editor Experience (EX).

Benefits of Layout Management

Using Layout Management, you can empower editors to create and manage layouts for your digital solutions using re-usable building blocks (i.e. components & layout models).

Editors can manage your site's page tree, layout-level SEO properties, and determine what content and functionality will be in each layout.

As a developer and architect, you still have full control over what layout models are available to the editor, where they can place components within the layout, and what the components can do.

  • Empowered editors who can do more without a developer
  • Happier developers who can focus on new functionality and enhancements, and less time responding to new content requirements
  • Increased productivity
  • Fewer resources/expenses required

Why do you need Layout Management in Headless CMS?

Here's a few scenarios showcasing situations editors and/or developers may have experienced:

  • I need to create a new landing page specifically for the press. It will have the exact same content layout as the home page, but just different content.
  • I need to be able to set the SEO properties for each page such as Meta Tags and Meta Descriptions.
  • On the home page, we want the YoutTube video to be BELOW the Main Rich Text, but on our press page, we want the YouTube video to remain ABOVE the Main Rich Text.
  • Our CEO doesn't like it, can we have the YouTube video ABOVE the Main Rich Text area on the homepage again?

In the scenarios above, you can see that the editor's needs are impossible to predict. It's not their fault, it's just the nature of the game. Managing content comes with a lot of changes.

Not taking advantage of Layout Management for your digital solution means it's not flexible for editors, so developers spend most of their time taking orders, tinkering with existing code to support content requirements, and wishing they were doing something else! Content changes should not have to involve developers.

So what does this ultimately mean?

  • Editors cannot create/manage layouts on their own without a developer
  • Editors cannot control which components are in each layout
  • Developers get bored or burnt out
  • More development resources/expenses requiredProductivity on the website suffers

And, who's at fault in this? I'll give you a hint, it's not the editor, and it's not the developer... It's the architecture!