Cookie Consent by Free Privacy Policy Generator ๐Ÿ“Œ A modern web experience on Adobe Experience Manager with WorkBox

๐Ÿ  Team IT Security News

TSecurity.de ist eine Online-Plattform, die sich auf die Bereitstellung von Informationen,alle 15 Minuten neuste Nachrichten, Bildungsressourcen und Dienstleistungen rund um das Thema IT-Sicherheit spezialisiert hat.
Ob es sich um aktuelle Nachrichten, Fachartikel, Blogbeitrรคge, Webinare, Tutorials, oder Tipps & Tricks handelt, TSecurity.de bietet seinen Nutzern einen umfassenden รœberblick รผber die wichtigsten Aspekte der IT-Sicherheit in einer sich stรคndig verรคndernden digitalen Welt.

16.12.2023 - TIP: Wer den Cookie Consent Banner akzeptiert, kann z.B. von Englisch nach Deutsch รผbersetzen, erst Englisch auswรคhlen dann wieder Deutsch!

Google Android Playstore Download Button fรผr Team IT Security



๐Ÿ“š A modern web experience on Adobe Experience Manager with WorkBox


๐Ÿ’ก Newskategorie: Web Tipps
๐Ÿ”— Quelle: web.dev

If you are a technical lead or digital marketing analyst interested in providing a modern Web experience to your Adobe Experience Manager (AEM) web application and have been looking for your options in doing so, then you have come to the right article. This will cover what Progressive Web Apps (PWA) are and what you need to create a PWA in AEM leveraging the WorkBox library through configuration, without coding.

Why PWA? #

Progressive Web Apps leverage what the modern web can do. They are installable on your device, load quickly, with subsequent visits loading instantly. They respond to input quickly. They work well on an unreliable connection or when offline. PWAs use modern APIs to provide an engaging app-like experience with an optional full screen UI, background updating, and offline access to data.

From web app to Progressive Web App.

To enhance a web app into a Progressive Web App requires adding two artifacts:

  • A web app manifest: a JSON configuration file that defines the app's entry point URL, the icon used to represent the PWA and other configuration that describe how the application looks and behaves.
  • A service worker: a script that provides background services that enrich your PWA by defining resources your PWA uses and the strategies to access them.

What is a service worker? #

At its core, a service worker is just a script that your browser runs independently as you interact with your web application. An active service worker provides services such as smart caching using the Cache API, keeping data up to date using the Background Sync API, and integrating with push notifications. A service worker with the right caching strategy provides stable and reliable user experiences for various scenarios, returning pre-cached resources instantly, storing data in cache, and updating resources when connected to the web.

A service worker lives on the client, but proxies the network.
Workbox Logo

Service workers can be hard to write from scratch. Workbox was created to make it easier. Workbox is a set of libraries to help you write and manage service workers and caching with the Cache Storage API. Service workers and the Cache Storage API, when used together, control how assets (HTML, CSS, JS, images, etc.) are requested from the network or cache, even allowing you to return cached content when offline. With Workbox, you can quickly set up and manage both, and more, with production-ready code.

Upgrading an AEM site to a PWA #

Adobe Experience Manager (AEM) is a comprehensive content management solution for building websites, mobile apps, forms, and digital signage. It makes it easy to manage your marketing content and assets.

While AEM provides a rich library for building web applications, until now it's been difficult to build a PWA by adding a service worker and a manifest.

Adobe Experience Manager Sites is the UI building tool that is part of Adobe Experience Manager. When used with Adobe Experience Manager as a cloud service, AEM Sites makes it easy to convert any existing AEM website or single page application into an installable offline-enabled Progressive Web App with just configuration and no coding. It uses Workbox to deliver the best practices for Progressive Web Apps and abstracts the complexities of writing boilerplate manifests and service workers.

AEM supports localization of content which means you can have different branding and even different offline content for different locales. To do this build different PWA configurations for each language master.

Getting started with PWA configuration on AEM #

Log into Adobe Experience Manager as a Cloud Service and select any Adobe Experience Manager Sites page or language master and click properties. You should see a tab called Progressive Web App. (Note: if you do not see this tab, please contact Adobe to enable this feature.) You can configure the installation and the look and feel of your Progressive Web Apps with just a few clicks.

If you've completed AEM Sites tutorials you have likely seen the WKND site before. This article uses the WKND demo as the starting point. When you are done you will have updated WKND from a web app to a PWA using WorkBox.

Configure the manifest #

The web app manifest is a JSON file that contains properties that describe the look and behavior of a PWA. Adobe Experience Manager Sites provides a friendly user interface to configure the properties.

Configuring the manifest in the installable experience dialog box.
The start URL is the entry point of your PWA. When a user taps on the the PWA icon on their phone, they will be accessing the startup URL. The display mode configures whether the app is a windowed or fullscreen experience. You can also specify the screen orientation of the application. The theme color is the color of the window and toolbar while the background color is the color of the splash screen when the application is launched. The icon is the image that is shown on the devices home screen or application drawer when the application is installed on the device. The configuration shown in the image generates the manifest JSON shown below.
{
"name": "WKND Adventures and Travel",
"short_name": "WKND Adventures and Travel",
"start_url": "/content/wknd/us/en.html",
"display": "standalone",
"theme_color": "#FFDC00",
"background_color": "#FF851B",
"orientation": "any",
"icons": [
{
"src": "/content/dam/wknd/pwa-logo.png",
"type": "image/png",
"sizes": "512x512",
"purpose": "any maskable"
}
]
}

The start URL can be different from the default landing page for your domain. By changing the start_url parameter, you can send your users directly to the application experience rather than the default page a non-authenticated or new user would be presented. This provides PWA users with a smoother, more app-like experience.

AEM understands that different locales can have a different look and feel. You can configure different properties, colors, and icons for different locales or languages and then synchronize the configuration with the linked pages.

Once the PWA is accessed on the browser, you can right click and inspect to bring up DevTools and view the manifest under the Applications panel.

A PWA in the DevTools Application panel.

Configure the service worker #

You can configure the content to cache and the caching strategy to use.

If you have been using service workers you may be familiar with caching strategies. Caching strategies specify which resources to cache and whether to look for those resources in the cache first, the network first, or in the cache with a network fallback. You can then choose the resources to pre-cache when the service worker is installed. AEM Application service workers implement a warm cache strategy which means user's experience will not break even if you specify a missing or broken path.

Configuring the service worker using the Cache Management (Advanced) dialog box.

In AEM, the term "clientlibs" refers to client-side Libraries: the combination of related JavaScript, CSS, and static resources that have been added to your project that are served to and utilized by the client web browser. You can easily set your client-side libraries to be used offline by specifying those libraries in the user interface.

The client side libraries dialog box.

You can also include third-party resources such as fonts. This offline cache configuration provides configuration information to a service worker that is generated for your application that internally uses workbox. That is pretty much all there is to make your application installable. Once installed, the application icon will show up on your mobile device home screen just like a platform app. Clicking the icon will access the wknd site.

Please note that you can change your content or these settings at any time. When you publish your changes, the service worker will be updated at the client by the browser and a message will be presented to the user that a newer version of the PWA is available. The user can click the message to reload the application and get the latest updates. You can open the browser developer tools and applications panel to view the service worker details.

The DevTools service worker panel.

You can expand cache storage to view the content that has been cached locally:

The cache storage view in DevTools.

The results #

It's time to look at the results of your hard work. With just configuration and without coding you have just enhanced your AEM site to become a Progressive Web App.

An AEM site as a Progressive Web App.

Chrome developer tools provide a lighthouse audit that lets you check how compliant your web application and configuration is with Progressive Web App standards.

A lighthouse audit.

Conclusion #

Progressive Web Apps provide an app-like experience for your website, that uses the cross platform and open nature of the web at a lower cost of development and maintenance while providing control over distribution. This enhances engagement, retention, and most importantly, drives higher conversion rates. AEM in conjunction with Workbox makes it easy to enhance your existing site into a PWA with just configuration and no coding.

References #

...



๐Ÿ“Œ A modern web experience on Adobe Experience Manager with WorkBox


๐Ÿ“ˆ 67.57 Punkte

๐Ÿ“Œ Atlassian Confluence bis 6.2.0 Workbox Notification Comment Information Disclosure


๐Ÿ“ˆ 32.07 Punkte

๐Ÿ“Œ Atlassian Confluence up to 6.2.0 Workbox Notification Comment information disclosure


๐Ÿ“ˆ 32.07 Punkte

๐Ÿ“Œ Extending Workbox: Custom strategies and plugins


๐Ÿ“ˆ 32.07 Punkte

๐Ÿ“Œ Adobe Released Another Patch โ€“ This Time For Adobe Experience Manager


๐Ÿ“ˆ 22.32 Punkte

๐Ÿ“Œ Adobe Fixes 82 Vulnerabilities in Adobe Acrobat and Reader, Experience & Downloader Manager


๐Ÿ“ˆ 22.32 Punkte

๐Ÿ“Œ Adobe fixes critical flaws in Adobe InDesign, Framemaker, and Experience Manager


๐Ÿ“ˆ 22.32 Punkte

๐Ÿ“Œ Bugtraq: CVE-2015-0955 - Stored XSS in Adobe Experience Manager (AEM)


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Vuln: Adobe Experience Manager CVE-2016-4169 Information Disclosure Vulnerability


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Vuln: Adobe Experience Manager CVE-2016-4253 Information Disclosure Vulnerability


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Vuln: Adobe Experience Manager CVE-2016-4170 Cross Site Scripting Vulnerability


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Vuln: Adobe Experience Manager and LiveCycle Multiple Cross Site Scripting Vulnerabilities


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Vuln: Adobe Experience Manager Multiple Cross Site Scripting Vulnerabilities


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Bugtraq: CVE-2015-0955 - Stored XSS in Adobe Experience Manager (AEM)


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Adobe Experience Manager 5.6.1/6.0.0/6.1.0 Java Object Handler unbekannte Schwachstelle


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Vuln: Adobe Experience Manager CVE-2016-4169 Information Disclosure Vulnerability


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Vuln: Adobe Experience Manager CVE-2016-4253 Information Disclosure Vulnerability


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Adobe Experience Manager 5.6.1/6.0.0/6.1.0 Apple Sling Information Disclosure


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Vuln: Adobe Experience Manager CVE-2016-4170 Cross Site Scripting Vulnerability


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Vuln: Adobe Experience Manager and LiveCycle Multiple Cross Site Scripting Vulnerabilities


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Vuln: Adobe Experience Manager Multiple Cross Site Scripting Vulnerabilities


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Vuln: Adobe Experience Manager CVE-2017-3108 Arbitrary Code Execution Vulnerability


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Vuln: Adobe Experience Manager CVE-2017-3109 Cross Site Scripting Vulnerability


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Vuln: Adobe Experience Manager CVE-2017-3111 Information Disclosure Vulnerability


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Low CVE-2017-3109: Adobe Experience manager


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Low CVE-2017-11296: Adobe Experience manager


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Medium CVE-2017-3111: Adobe Experience manager


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Adobe Experience Manager 5.6.1/6.0.0/6.1.0 Dispatcher Filter erweiterte Rechte


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Adobe Patches Flaws in Flash Player, Experience Manager


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Low CVE-2018-4876: Adobe Experience manager


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Low CVE-2018-4876: Adobe Experience manager


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Adobe Experience Manager 5.6.1/6.0.0/6.1.0 Cross Site Scripting


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Adobe Patches Information Disclosure Flaws in Experience Manager


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Adobe Issues Unscheduled Updates for Experience Manager Platform


๐Ÿ“ˆ 16.93 Punkte

๐Ÿ“Œ Low CVE-2019-7129: Adobe Experience manager forms


๐Ÿ“ˆ 16.93 Punkte











matomo