TECHNOLOGY · ADOBE EXPERIENCE MANAGER (AEM)
On AEM the problem is rarely technical. It's about content governance.
Templates, components and the dispatcher decide what gets published and how it's served. When many teams publish, order breaks down before performance does.
Let's talk about your project- +15
- years working visibility for large brands
- +200
- projects with our own data behind them
- 48 h
- to reply, at most
Brands that have trusted Laika
Some of these situations may sound familiar
Each country or brand publishes its own way
The same components used with different criteria end up producing structures that look nothing alike.
There are duplicate pages inherited from templates
Content hierarchies grow by copying branches. Over time several live versions of the same thing exist.
The dispatcher cache hides what's happening
You see one thing in author, another in publish and another after the cache. All three need checking.
Changes depend on a long release cycle
What can be done from the author environment and what needs development are two different lists, and it pays to separate them early.
Nobody knows which component controls the metadata
Titles and descriptions are generated in different places depending on the template, and there are pages where nobody fills them in.
The scope
We review content hierarchies, templates, components and dispatcher configuration, and define publishing rules every team can follow without depending on one person.
We work on the judgement and the spec: what needs to change on Adobe Experience Manager, in which order and how it gets checked afterwards. Your team or your development partner implements it, and we review that what reaches production is what was agreed.
The areas of work
Four fronts that come up again and again on Adobe Experience Manager projects. Depending on where your project stands, some weigh more than others.
Content hierarchy and templates
Tidy up the tree so the site structure makes sense from the outside.
See the detail
- Map of branches, templates and active inheritance
- Detection of duplication from copied branches
- Target structure per market or brand
- Creation rules for new pages
Components and metadata
Make each page type generate its tags and structured data without manual work.
See the detail
- Review of how titles, descriptions and canonicals are generated
- Missing fields and sensible defaults
- Structured data per template
- Internal linking resolved from the component
Dispatcher, cache and performance
Know what a crawler actually receives, after every layer.
See the detail
- Review of cache rules, redirects and filters
- Behaviour with parameters and headers
- Performance of critical templates
- Server log analysis when access is available
Governance across teams
Keep the structure from unravelling in the next campaign.
See the detail
- Publishing guide by role and by market
- Review criteria before publishing
- Short training for content teams
- Periodic checks on what's been published
Who does it?
A small team with real hours inside Adobe Experience Manager. MJ leads the strategy and the specialist who reviews your platform is the one who explains it to you.
Why Laika?
Knowing the platform changes the conversation: you stop arguing about whether something is possible and start deciding when it ships.
We've worked on Adobe Experience Manager projects long enough to know where its real limits are and what a second pass at configuration can solve.
We've worked inside large organisations
We know that on AEM the bottleneck is usually the process, not the platform, and we plan the work accordingly.
You always talk to whoever decides
There's no management layer between you and the judgement. MJ leads the strategy and the specialist team executes.
If we're not the right fit, we say so
Even if that means there's no project for us, we'd rather say so before signing.
Frequently asked questions
Do you work with AEM as a Cloud Service and 6.5?
With both. What changes is what can be configured without development and how it deploys, and we confirm that at the start.
Does our implementation partner need to be involved?
Yes, at some point. We write what needs changing and why; they estimate and deploy it.
Can you review before a release?
That's the recommended way. We review in staging and flag whatever shouldn't ship yet.
Tell us about your project
Knowing which version you run, who develops it and what worries you is enough for us to say whether it makes sense to talk.
Shall we talk about your platform?
We look at your project before proposing anything and tell you what can move without fighting the roadmap.
We look at your project before proposing anything. Reply within two working days at most.
Let's talk about your project