MACH Experts: A discussion on the role of orchestration in composability Sign Up
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).
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.
Here's a few scenarios showcasing situations editors and/or developers may have experienced:
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?
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!