Skip to content

Content

Create, govern and publish content once, for every channel.

We set up how your teams create, review and publish content in Adobe Experience Manager, with content models, workflows, metadata and permissions that keep it accurate, on brand and ready for every channel.

At a glance

Adobe Content Management

How content is created, governed and published in Adobe Experience Cloud, using Adobe Experience Manager Sites and Assets.

Not sure where to start? We begin with an assessment, then implement the priorities with you.

What the platform assessment covers

Product overview

How content management works in Adobe

Adobe doesn't sell a separate content management product. In Adobe Experience Cloud, content is managed in Adobe Experience Manager: AEM Sites for pages and structured content, AEM Assets for images, video and documents. Content management is how those tools are set up and used every day, from creation to approval to publishing.

Describes Adobe's software, not a Maverick InnoGarage offering.

  • Authoring in AEM Sites

    Authors build pages from components and templates in the page editor, or edit pages and headless content visually in the Universal Editor.

  • Content Fragments for structured content

    Content Fragments hold channel-neutral content based on Content Fragment Models, so the same text and data can be reused on websites, in apps and in other channels through AEM's delivery APIs.

  • AEM Assets and Adobe Asset Link

    AEM Assets stores, tags and distributes images, video and documents. Adobe Asset Link lets designers open and save AEM assets directly from Creative Cloud apps such as Photoshop, Illustrator and InDesign.

  • Workflows, permissions and launches

    Workflows route content for review and approval, user groups and permissions control who can edit and publish, and launches let teams prepare future changes to pages without affecting the live site.

  • Metadata, tags and Content Hub

    Metadata schemas and tags make content and assets findable. Content Hub, part of AEM Assets, gives wider teams a portal to find and use brand-approved assets.

  • Language copies and multi-site rollout

    Language copies and translation projects manage content for each language, and Multi Site Manager rolls shared content out to regional or brand sites.

When teams reach out

Problems we solve

Common reasons teams bring us in for Content Management work, whether the platform is new or already live.

  • Content requests that queue behind a small group of specialists
  • No agreed review and approval path, so outdated or off-brand content gets published
  • The same content maintained separately for the website, the app and campaigns
  • Assets that are hard to find, poorly tagged or used after they should have expired
  • Regional and language teams that can't publish without central help
  • AEM in place, but authors work around it instead of with it

Services

What we deliver for Content Management

  1. Content creation and authoring

    We make it straightforward for your teams to create content in Adobe Experience Manager, with the components, templates and models they need and no developer in the loop for routine work.

    • Review of who creates which content, and where it slows down
    • Templates, components and Content Fragment Models matched to your content types
    • Authoring set up in the page editor or Universal Editor
    • Creative Cloud connection through Adobe Asset Link
    • Author guides and training
  2. Content governance

    We define and configure the rules that keep content accurate, on brand and in line with your policies, from ownership to approval to expiry.

    • Content ownership, roles and permissions
    • Review and approval workflows
    • Metadata schemas, taxonomy and tagging standards
    • Asset expiry and retirement of outdated content
    • Audit of existing content: what to keep, merge or retire
  3. Omnichannel publishing

    We structure content so it's written once and published to websites, apps, campaigns and regional sites from the same source.

    • Content models for reuse across channels
    • Headless delivery of Content Fragments to apps and front ends
    • Translation and rollout routines for language and regional sites
    • Brand-approved asset distribution through Content Hub
    • Publishing schedules and launches for planned changes

Practical applications

Content Management in practice

These are illustrative scenarios that show typical situations and approaches. They are not descriptions of specific client projects.

  • Illustrative use case

    Clearing a content request queue

    Situation
    A healthcare provider's web team handles every content change for dozens of departments, and requests wait weeks to be published.
    Approach
    Define content types and templates for department pages, set up a review and approval workflow with clear owners, and train department authors to create and submit their own updates.
    Intended outcome
    Departments update their own content, and the web team reviews instead of rebuilding every request.
  • Illustrative use case

    One source for product content

    Situation
    A manufacturer keeps product descriptions in its website, its dealer app and its campaign emails, and they often disagree.
    Approach
    Model product content as Content Fragments, agree who owns and approves each field, and publish the fragments to the website and the app through headless delivery.
    Intended outcome
    Product content is approved once and appears the same everywhere it's published.

FAQ

Content Management questions

  • Is Adobe Content Management a separate Adobe product?

    No. Adobe Content Management is how we describe our content work in Adobe Experience Cloud. The tools are Adobe Experience Manager Sites and AEM Assets, so if you already license AEM, you already have them.

  • How is this different from your Adobe Experience Manager services?

    Our Experience Manager services cover the platform: implementation, integration, multi-site setup and custom development. Content management covers how your teams use it every day: how content is created, reviewed, approved and published. Many projects include both.

  • Can you improve content governance on an existing AEM setup?

    Yes. We review how content is owned, approved and published today, then set up the roles, workflows, metadata and expiry rules that are missing, without rebuilding what already works.

  • Do you train content authors?

    Yes. Training is part of how we hand over work, so authors, approvers and asset managers can create and publish content without relying on developers for routine changes.

Related applications

  • Content

    Adobe Experience Manager

    Adobe Experience Manager is the platform behind Adobe content management. Its page covers implementation, integration and custom development.

  • Personalization

    Adobe Target

    Content Fragments and Experience Fragments governed in AEM can be exported to Target as offers for testing and personalization.

  • Analytics

    Adobe Analytics

    Analytics shows how published content performs, so teams know what to update, reuse or retire.

Insights

Related reading

All insights

Other Adobe applications

MarTech overview
Adobe Solution Partner, Bronze

Maverick InnoGarage is an Adobe Solution Partner.

We implement, integrate and support Adobe Experience Cloud applications.

Adobe, the Adobe logo and Adobe product names are either registered trademarks or trademarks of Adobe in the United States and/or other countries.

Start a conversation

Make content easier to create, govern and publish.

Tell us how your teams create and publish content today, and where it slows down. We'll scope a practical first step with you.