Details
-
Task
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
Description
Document the Device Detection module, new in Magnolia CMS 4.5. It provides the capability to detect the device requesting the site. Typical examples of device classes are desktop browser, smartphone and tablet.
Topics to cover:
- What is device detection. Why is it needed? Identifying a device's capabilities is a pre-requisite for delivering optimized content.
- Describe the mobile explosion, stress the necessity to tailor content. Provide statistics about top mobile devices used to access the Magnolia corporate website from Google Analytics.
- Default implementation uses WURFL. WURFL is quite well explained in the Mobile article (/templates/mobile). Move it here if there is too much detail in the Mobile article.
- Configuration in /modules/device-detection. The WURLF package is inside the module JAR.
- DeviceInfo object
- DeviceCapability object, for example WURFLDeviceCapability
- deviceDetection filter
- Channel. Device detection is tightly bound with channel management. Once a device has been identified, content from the appropriate channel is served. This ensures that content is served in the right format. Channel management will be a separate article but discuss the relationship here because they are inseparable.
- A typical example is optimizing the site for mobile devices. Link to the Mobile article.
- Give ideas for implementing your own device detection. A developer would start by writing a custom class that implements the DeviceDetection interface. They could examine the request headers and match the user agent against a local device database, for example.
Resources
- Magnolia CMS 4.5 Beta 5 in Nexus
- module-device-detection in Nexus. Get the Javadoc JAR so you can look at the classes and interfaces.
- Magnolia Module Device Detection concept page on the wiki
Checklists
Acceptance criteria