Mobile internet usage has skyrocketed to overtake desktop as the most used digital platform. That means making your website responsive is integral to your digital strategy. Web developers resorted to options like media queries, fluid grids and adaptive images to cater to the needs of mobile browsing. But how do we tackle the ever increasing list of mobile devices, their sizes, input modes and browsers? In this article, we talk about how Adobe Experience Manager (AEM)’s responsive layout editor comes to the rescue.
How Far We’ve Come: Then vs. Now
In the past, building a responsive website was far from easy. It started by defining which devices and view ports to support, deciding on the layout for each device, then creating unique stylesheets for each. At any point (or with any new device release), changes to those layouts would require more custom programming and a new software release—a time-consuming effort.
Things have changed with AEM 6.1. With a new Responsive Layout Container, developers are no longer the lynch-pin in the process. Instead, new devices can be added with a few configurations and layout changes are made easily through content authoring.
Big, Time-Saving Advantages
The new Responsive layout editor in AEM offers numerous advantages when authoring responsive pages. Here are a few important ones:
- It eliminates the need for frequent development cycles and code releases.
- It’s easier to support a broader range of breakpoints.
- It offers faster time-to-market new devices.
- It gives more granular control over page behavior than traditional systems (e.g., Bootstrap).
How Does It Work?
Responsiveness is achieved through grid-based layouts with options for floating, nesting and hiding various content components, based on the needs of the responsive experience. It’s all possible through a “responsive parsys” (an extension of the regular parsys with the same capabilities of drag and drop, etc.). . Responsive parsys also known as the layout container along with the layouting mode and emulator provides options for content authors to create various layouts and breakpoints, and also to test them out. All of these features are available to be configured for landscape and portrait modes.
Responsiveness can be defined at either the page template level or the page level. If done at the page level, the responsiveness will be automatically inherited to all the child pages, which is another huge time-saver. Also, Multi Site Manager and live copy relationships can be established across various sections of pages to establish responsive behavior.
With Adobe Experience Manager 6.1, you can create device groups and different sections of the website can be supported for specific device groups as per business needs. You can create as many devices, with specific height and width specifications and add them to device groups on the fly. These device groups can then be assigned for specific sections of the website. This becomes particular helpful when the content and audience are significantly different.
8 Steps to Creating a Responsive Experience
Now that you know how AEM helps you achieve responsiveness using the Responsive layout editor, here’s a glimpse of the high-level steps you will follow:
- Enable a responsive grid by adding a layout container to the page.
- Enable layouting mode.
- Set up responsive editing.
- Include a responsive stylesheet.
- Configure break points.
- Create device groups.
- Configure the emulator.
- Authors are now enabled to create responsive experiences, as needed.
Curious to learn more? Stay tuned for our next blog with more details on the process.
Interested to see a live demo of this or a POC on a page from your website? Reach out to us today.