EditandoIdeas

Specialized practice

Specialists to build, stabilize, and modernize Adobe Experience Manager.

Development, architecture, Cloud Service, headless, Edge Delivery Services, and support for the teams already running the platform.

See engagement models

AEM is not one line in our catalog.

It is a practice with architectural judgment. The difference shows up in the decisions nobody sees: how template policies are structured, where a component ends and a fragment begins, and what you pay in maintenance three years from now for a call made today.

Capabilities

What we cover.

  • Sites

    Components, editable templates, policies, content structure, and the authoring model. The priority is a content team that can work without filing a ticket for every change.

  • Assets and DAM

    Repository structure, metadata, processing profiles, renditions, and approval flows. Integrated with the systems that produce or consume the assets.

  • Headless

    Content Fragments, content models, GraphQL, and consumption from external applications. When headless is worth it — and when it is a complication that buys you nothing.

  • Integrations

    Internal services, third-party APIs, identity, search, and business systems. With explicit boundaries: what belongs inside AEM and what should not.

  • Delivery and operations

    Cloud Manager pipelines, code quality, environment management, deployments, and support for QA and DevOps teams.

Technical depth

Exactly where we work.

This list exists so a technical lead can decide in thirty seconds whether talking to us makes sense.

Development

  • Components in HTL with composition patterns that survive contact with reality.
  • Sling Models, OSGi services, and per-environment configuration.
  • Dialogs, design dialogs, and authoring validation.
  • Editable templates, policies, and page structure.
  • Clientlibs, frontend architecture, and a real performance budget.
  • Workflows and process steps when the editorial model genuinely needs them.

Content and reuse

  • Content Fragments and editorial domain modeling.
  • Experience Fragments and reuse across channels.
  • GraphQL: persisted queries, caching, and schema versioning.
  • Translation and multilingual structure.

Platform

  • AEM as a Cloud Service: architecture and adoption.
  • AEM 6.5 and the modernization path to cloud.
  • CI/CD with Cloud Manager and code quality gates.
  • Dispatcher, caching, and invalidation.
  • Security: permissions, groups, service users, and environment separation.

Edge Delivery Services

  • Fit assessment: what the project gains and what it gives up.
  • Frontend modernization and performance budget.
  • Coexistence with an existing Sites implementation.

Scenarios

When teams usually call us.

  • The backlog grows faster than the team

    The work is defined and approved, but nobody is free to take it. A specialist or a cell joins the process you already run.

  • The platform keeps breaking

    Fragile deployments, recurring incidents, or authors blocked. Diagnose first, stabilize second, and only then add features.

  • Migrating from 6.5 to Cloud Service

    Inventory of customizations, compatibility assessment, a phased plan, and execution. Without promising everything lifts and shifts unchanged — it almost never does.

  • Nobody knows how it was built

    The person who designed it has left. Audit, documentation, contribution standards, and technical governance so the knowledge stops being one person’s dependency.

  • You won the project and have no bench

    For consultancies and integrators: a cell that works inside your process, and under your brand if you prefer.

Engagement

How to hire us.

From the smallest intervention to the most committed one.

  • Audit

    An independent diagnosis of the implementation, with prioritized findings and a plan. It ends in a document, not a sales proposal.

  • Scoped sprint

    One concrete objective with a date: stabilize a flow, unblock a migration, or build a module.

  • Embedded specialist

    An AEM engineer inside your team, your process, and your ceremonies.

  • Fractional tech lead or architect

    Technical judgment and decision review by the hour or for a defined period, without a full-time hire.

  • Dedicated cell

    A team with agreed capacity and shared responsibility for delivery.

The family

What is actually inside Adobe Experience Manager.

AEM is not one product but a set you buy in parts. Knowing which ones you need moves the budget more than any technical decision that comes after.

AEM Sites

Page management, editable templates, components, and multi-site publishing. This is the module most people mean when they say "AEM".

AEM Assets

Digital asset management: metadata, renditions, approval workflows, and distribution to whatever channel consumes the image.

AEM Forms

Adaptive forms, interactive communications, and signature flows. Of the three, this is the one with the longest buying cycle.

Edge Delivery Services

Adobe's newest publishing route, built around performance measured in the field. It changes the authoring model, not just delivery.

Cloud Manager

CI/CD managed by Adobe: pipelines, quality gates, and promotion between environments. On Cloud Service it is not optional — it is the only path to production.

Headless and fragments

Content Fragments served over GraphQL or the delivery APIs, for applications that render on their own.

Editions

Cloud Service, 6.5 LTS, and on-premise are not the same conversation.

The edition decides who updates, how you deploy, and what you are allowed to customize. It is the first question on any AEM project and the one that moves the most budget.

DimensionAEM as a Cloud ServiceAEM 6.5 LTSAEM 6.5 on-premise or AMS
UpdatesContinuous, handled by AdobeService packs on a stable extended-support basePlanned by you, with your own window and risk
DeploymentCloud Manager only, with mandatory quality gatesCloud Manager or your own pipeline, depending on hostingYour own pipeline against the instances you administer
Room to customizeBounded: some APIs and practices are no longer availableWide, with the debt that creates when you migrate laterMaximum, and maximum responsibility for whatever you touch
Asset processingAdobe microservices, off the instanceOn the instance, unless you wire up external servicesOn the instance, sized by you
What getting here involvesRefactoring what is incompatible and adopting Cloud ManagerA major upgrade with a dependency reviewNothing new if you already run this way

If you do not know which edition you are on, that surfaces in the first half hour of an audit — and it is worth having before you ask anyone for a quote.

Vocabulary

The terms that show up in every AEM proposal.

Publishing these is not a lesson: it is so you can read any vendor proposal — ours included — and know what you are being quoted.

JCR
The content repository. In AEM everything is a node: pages, configuration, and assets all live in the same tree.
Apache Sling
Resolves which code serves each URL from the resource type rather than a route table. It is why the content path is what matters in AEM.
OSGi
The service container. It lets modules deploy and reconfigure without restarting the instance, and it holds per-environment configuration.
HTL
AEM's templating language. It replaced JSP and deliberately limits the logic you can write in the view.
Dispatcher
The caching and filtering layer in front of AEM. Most of the performance and security problems we find in audits live here.
Core Components
The component library Adobe maintains. Starting from it instead of writing your own is the decision that avoids the most maintenance.
Editable templates
Templates an author can configure without a code deployment. Their policies decide what can go on each page for years.
Content Fragments
Structured content independent of any page, meant to be consumed by API from any channel.
Experience Fragments
Laid-out, reusable blocks shared across pages or exported to other channels. Often confused with the above; not the same thing.
Universal Editor
The visual editor Adobe uses for decoupled authoring, including Edge Delivery Services.

Official resources

Learn AEM on your own, free, straight from Adobe.

Adobe publishes its full training on Experience League at no cost. We link what actually gets used: if after this you decide you do not need anyone, the page did its job.

See for yourself

Put us to the test before you hire us.

Forty-five minutes with the person who would do the work says more than any credentials page. Bring your implementation and leave with judgment, whether you hire us or not.

  • We review what you already have, live: template structure, components, Dispatcher, and pipeline.
  • We tell you what is well solved and what will cost you dearly two years from now.
  • You get specifics: versions, deprecated APIs, and decisions worth reversing.
  • If the problem is not AEM, we say that too.
  • What we see of your platform stays there: we do not publish client projects.

Adobe, the Adobe logo, Adobe Experience Manager, Adobe Experience Cloud, and Adobe Experience League are registered trademarks or trademarks of Adobe in the United States and other countries. Editando Ideas is an independent service provider.

Let's talk about your AEM implementation.

A technical conversation with the person who would do the work, not with an account executive.

Talk to an AEM specialistRequest talent