adobe experience platform

Enterprise Content and Digital Asset Management with Adobe

Adobe Experience Manager (AEM) is an enterprise content management and digital asset management platform. AEM Forms handles forms. Adobe Learning Manager is a standalone Adobe product for training, and it can also connect to AEM Sites through an API. As an Adobe Partner, we help you select these products, implement them and integrate them with your existing systems.

What can the Adobe platform do?

How does an Adobe project run?

The project has four phases. This is Webtown's service process, which we apply regardless of platform.

  1. Discovery and strategy

    We understand the business goal, map the existing systems and set the direction before any development begins. The Discovery and Audit consultation gives an accurate estimate.

  2. Design and architecture

    UX design, system architecture, technical specification. We document every decision and get it approved before the first line of code is written.

  3. Development and integration

    Agile delivery with a demo every two weeks. The platform connects to existing enterprise systems and processes.

  4. Launch and support

    Load testing, phased switchover, careful go-live. The end of the project is not the end of the relationship; we define the next steps together.

Why Webtown?

  1. Adobe Partner with enterprise experience

    We have built enterprise systems for 21+ years. We have been a Liferay Partner since 2011, have worked on Ibexa since 2016, and are an Adobe Partner too.

  2. Unbiased technology choice

    Liferay, Ibexa and Adobe are all in our portfolio, so we choose the platform for the task, not for habit.

  3. Integration-first approach

    We implement the Adobe solution fitted to your existing ERP, CRM and content management systems.

When the focus is the central management of large volumes of digital assets (images, video, documents) and content-driven, multichannel delivery. If a login-based portal or case handling is also a goal, we examine this separately during Discovery.

Four questions decide the choice, and none of them is about the product's brand. Because Webtown is a Liferay, Ibexa and Adobe Partner, we can ask these questions in a platform-neutral way.

  1. How many assets need managing, and how many teams use them? This decides whether you need a standalone DAM or whether the asset handling of the content management system is enough.
  2. Is content or process the main goal? Marketing-driven, multichannel content and a login-based, case-handling portal place different requirements on the platform, so we clarify this at the start of the project.
  3. Is there an Adobe environment already? According to Adobe's documentation, adaptive forms, for example, can be connected with Adobe Analytics and Adobe Campaign. Where these already run, integrating AEM is simpler.
  4. Who operates it, and how much in-house capacity is there? The license, supervision and developer skills required differ by platform, and this shows in the total cost.

If the answer is not clear, the Discovery and Audit consultation settles it before development starts.

You do not have to decide in advance. The needs of the project decide whether we implement one or several of AEM, DAM, Forms or the LMS.

AEM Sites manages the content of websites and other channels. AEM Assets manages images, videos and documents. In one project, the two can work together.

No. It is a standalone Adobe product that connects to other systems, including AEM Sites, through an API.

Yes. An integration-first approach is a core principle of every project. We implement Adobe solutions as part of your existing ERP, CRM, and content management ecosystem.

We record these questions during Discovery, because changing them mid-implementation costs more:

  1. Existing systems. Which ERP, CRM and content management systems must exchange data with the new platform, and through which interface.
  2. Content and asset stock. How much material there is, in what quality, what can be migrated unchanged, and what is worth reworking or dropping.
  3. Content model. Which Content Fragments the content consists of, because this determines how reusable it is across channels.
  4. Approval and permissions. Who can create, who can approve, who can delete, and how the workflow reflects this.
  5. Multilingualism. How language versions are managed, who translates, and who approves the translation.
  6. Front-end approach. Headless front end or traditional page management, because this defines both the development team's tasks and the editing interface.

The cost depends on complexity. The Discovery and Audit consultation gives an accurate estimate before development starts. The license cost is a separate item.

Looking for an Adobe-Based Solution?

Let's discuss your challenges. You don't need to decide in advance which platform is the right fit.

No obligation. We respond within one business day.