3 ways Adobe Experience Manager can handle your content

Adobe Experience Manager can do so many things, but everyone always feels like they are a bit different from the norm. They think, “We’re special, so can AEM really be used by our company?” If you’re not sure whether AEM is the correct system for your organization’s content, then check out this infographic. It may help you decide. If you are looking for a few more details, you can also check out the longer version I wrote for our sister site, AEM Podcast. Subscribe to the blog for more information about AEM.

ways_handle_info_v5

  • We get asked the question “Can I use AEM for my content?” a lot, by companies that are evaluating whether Adobe Experience Manager is right for their organization. Most people don’t really understand what AEM is, or how it can deliver the content for their business.
  • What is AEM?
    • Adobe Experience Manager is a web content management system that lets content authors easily create, organize, and publish content to all of your customers. AEM is purpose built to address content management and content publishing.
  • Should you use it?
    • Whether Adobe Experience Manager is a good technology fit for your company centers around the content your business initiatives require. One easy way to assess whether or not to use AEM is to determine how often, and for what reason, the authoring interface will be used to control your content. If you fall under one of the following three content models, AEM will be a good fit for your organization.
  • The traditional model
    • The traditional use of AEM is to drive content to a website, or series of websites, with AEM being the primary platform for both authoring and content delivery. Authoring happens within AEM, utilizing components and page templates. The content is then delivered via AEM’s rendering engine to the website.
  • The hybrid model
    • In the hybrid model, AEM not only drives content, but also pulls in a large chunk of data from web services—data that is not available in AEM. In this model, most of the content is authored in Adobe Experience Manager, but some pieces will be created in the third-party systems where the data lives. Still all content is delivered through AEM’s rendering engine.
  • The web application model
    • In the web application model, Adobe Experience Manager will function as an authoring tool and content repository service. It will allow external systems to easily access the curated content using the RESTful interfaces of AEM. An external system acts as the rendering engine. AEM is only used to author content.
  • Conclusion
    • At its heart, Adobe Experience Manager is an engine that is focused around authoring and delivering content to your customers. How your organization chooses to use it is up to you.