Highlighted

Migrating to Adobe Experience Manager: 4 Site Structure Considerations | AEM Community Seeding

Avatar

Avatar

kautuk_sahni

Community Manager

Total Posts

5.5K

Likes

955

Correct Answer

1.1K

Avatar

kautuk_sahni

Community Manager

Total Posts

5.5K

Likes

955

Correct Answer

1.1K
kautuk_sahni
Community Manager

24-04-2020

BlogImage.jpg

Migrating to Adobe Experience Manager: 4 Site Structure Considerations by searchenginejournal

Abstract

In 2019, Adobe Experience Manager (AEM) saw a substantial increase in platform uptake, with BuiltWith now estimating there are around 18,700 websites using the platform globally. Graph taken from BuiltWith on February 17, 2020, showing the number of live AEM websites globally.Graph taken from BuiltWith on February 17, 2020, showing the number of live AEM websites globally. One can assume this number is only set to increase, given Adobe’s purchase of the Magento platform. More recently, Adobe also moved the Experience Manager to be a cloud-native SaaS application – making the CMS “more scalable and secure for content management across organizations”. With uptake increasing and typical AEM implementations ranging from a few hundred thousand dollars for the license to $2 million-plus for the complete implementation, transitioning to this platform naturally inherits a lot of attention from C-suite and the wider business. This often comes with the expectation that such a substantial investment will yield improved results.

Read Full Blog

Migrating to Adobe Experience Manager: 4 Site Structure Considerations

Q&A

Please use this thread to ask the related questions.

AEM AEMEBlogSeeding Experience Manager