Adobe Experience Manager and RESS? | Community
Skip to main content
A
andrewk19168727
January 31, 2017
Solved

Adobe Experience Manager and RESS?

  • January 31, 2017
  • 10 replies
  • 3304 views

Does Adobe Experience Manager support RESS architecture? If yes, has anyone had any experience implementing it on enterprise websites to help optimize mobile UX and page performance?

 Pros? Cons? Issues? 

What is RESS?:

http://detector.dmolsen.com/demo/mustache/?pid=e1bd58cc186d3a2156b6ebddb558fd41 

http://blog.hebsdigital.com/responsive-web-design/ 

 

#responsivewebdesign #RWD #RESS #AdaptiveDesign 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

Hi,

If I understand you right, you don't want to display the same content on all devices, but device-optimized content. Well, I doubt that this should be a general recommendation, normally way to much work to maintain the same content for a number of different formfactors.

With AEM there's way to achieve that. You can use MSM to derive from a full-fledged page (maybe the desktop version) a mobile optimized page, which only has a fraction of content and uses smaller/optimized renditions of assets. IIRC there's even a default rollout config available for this (check the documentation) which you can extend.

Jörg

10 replies

A
andrewk19168727Author
January 31, 2017

yep.... very clear on responsive support (and adaptive for that matter), but does AEM support server side configuration of the content based on device type? 

As in... requesting device is a chrome on desktop computer (full experience - total of 12 components) or requesting device is an iphone 6 with safari (mobile optimized experience with only 4 components) making the payload for device lighter and optimizing all code and all assets delivered to the device?

check this example on desktop and then mobile safari: https://www.nd.edu/ you'll see whats delivered to the device is substantially lighter/less than what is delivered to the desktop which happens server side.

smacdonald2008
smacdonald2008
Level 10
January 31, 2017

I have not heard of AEM support RESS, Its not documented nor have i even seen this before. You can always log a feature request ticket so Product Management gets this feedback. . 

kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
February 1, 2017

Just adding this forum post here, this will certainly help you:

Link:- http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__0ufg-hi_does_aemsu.html

// It talks about AEM Responsive design Vs Adaptive design and Front-end vs back-end responsive designing.

    For server side we can implement our own logic by detecting user-agents. I have mentioned it in the Forum post

Slide :-http://www.slideshare.net/GabrielWalt/aem-responsive

// From Product manage of AEM. Here also he talks about few steps related to server side responsiveness.

Also have a look at this document on responsive layout:

Link:-https://docs.adobe.com/docs/en/aem/6-2/author/page-authoring/responsive-layout.html

~kautuk

Kautuk Sahni
A
andrewk19168727Author
February 9, 2017

Thank you @Kautuk

2 additional questions:

 

1) It is still a little fuzzy how administrators building templates or component specify what to send or not send to a device based on device sensing/user agent detection... can you point me to the AEM documentation on that particular workflow? (how I as a template creator define exactly what I want the server to send to user agent A (chrome/desktop for example) vs user agent B (safari iPhone 6 for example)?

2) How adobe plans to evolve this approach to adaptive/responsive/responsive with server side detection/configuration in version 6.3? 

Any further information you can provide will be hugely helpful.

Thank you.

A
andrewk19168727Author
February 14, 2017

hey there kautuk

just following up on this question and server side components and device detection in AEM 6.3.. any ideas for innovations coming from Adobe? and/or detail on how to manage server side components to specific devices  within AEM currently on 6.2? 

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
February 14, 2017

Hi,

If I understand you right, you don't want to display the same content on all devices, but device-optimized content. Well, I doubt that this should be a general recommendation, normally way to much work to maintain the same content for a number of different formfactors.

With AEM there's way to achieve that. You can use MSM to derive from a full-fledged page (maybe the desktop version) a mobile optimized page, which only has a fraction of content and uses smaller/optimized renditions of assets. IIRC there's even a default rollout config available for this (check the documentation) which you can extend.

Jörg

A
andrewk19168727Author
February 14, 2017

Thanks Jorg

And AEM manages whats delivered to the device from the server side (using device detection) rather than simply hiding content on the client (device) side with media queries?  Goal here is minimize the payload delivered to device especially for Geos with slow connection speeds and older/less capable devices (there are other goals as well.. but thats one of the goals).

any insights into how this evolving in AEM 6.3? 

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
February 14, 2017

If you use AEM device detection it's normally happening in the browser itself. But then you would only redirect to a page which is built for this kind of device.

Jörg

A
andrewk19168727Author
February 14, 2017

Hey Jorg - ok so MSM is not what we want to do/recommend... ideally we'd like to detect the device and have the server deliver device specific markup from the same code base to device at the page level. Specifically a responsive site with server side enhancements rather than maintaining two websites or a fully adaptive site.  

Example Notre Dame's homepage (check on desktop and then mobile): 

https://www.nd.edu/

Any innovation on this front from Adobe/the AEM team? 

Terms & ConditionsAccessibility statement

Loading footer...