Get in touchAdobe Edge Delivery Services
Sites that load before people finish deciding to leave.
Edge Delivery Services is content infrastructure with the ceremony removed: pages that are mostly static, authoring in documents, deploys without a committee. I build the content model, the blocks and the budget that keeps speed real after the twentieth campaign.
100
Lighthouse target
0
page builders
<1s
LCP ambition
Who it's for
- Marketing teams that publish weekly and shouldn't need a developer for it.
- Companies stepping away from a heavyweight CMS.
- Multi-brand systems where every brand reuses the same blocks.
- Sites that keep failing Core Web Vitals no matter how often they're rebuilt.
What I bring
06 deliverablesDocuments authors get
(01)Tables, blocks and variants mapped to how your team already writes — not to how the CMS thinks.
A block library, not a theme
(02)Each block isolated, versioned and styled with scoped CSS; the site stays fast as it grows.
A performance budget with teeth
(03)Lighthouse near 100, honest Core Web Vitals, disciplined images — measured on every release.
Authoring that keeps up
(04)Document authoring or Universal Editor, tuned so campaigns don't wait for sprints.
SEO from the first block
(05)Static HTML, metadata, structured data and redirects designed in, not patched later.
The whole pipeline
(06)Preview, publish, revalidation and monitoring connected from day one.
What work is covered
- New EDS sites, boilerplate to launch
- Moves from AEM Sites, WordPress and home-grown CMSs
- Document authoring (DA) and Universal Editor projects
- Block libraries and design systems built for EDS
- Core Web Vitals and Lighthouse cleanup
- SEO, structured data and redirect maps
How it works
4 steps- 01
You bring the mess
Half a spec, a bug list, or a migration that stalled — all valid starting points.
- 02
I cut the first slice
One small piece with real value, agreed in writing before anything else moves.
- 03
Ship in the open
Working software every week, reviewed with your team — not a reveal at the end.
- 04
Hand over the keys
Code, docs and conventions stay with you; I stay reachable if you want that.
Questions
Does EDS mean leaving AEM?
Not necessarily. Many setups run EDS for public content and keep AEM for workflows and apps — a hybrid that's often the cheapest path.
Can our editors learn it?
Yes, and quickly: authoring works in documents they already know. I run a session and leave a one-page guide rather than a manual nobody opens.
How long does a build take?
First blocks in days; a campaign site usually in a few weeks, gated by content decisions and reviews rather than code. The pipeline comes first.
Will it match our design system?
Blocks consume your tokens and primitives, and the library is documented so the next designer doesn't reinvent it.
What about SEO?
Every page is static HTML with metadata, canonicals, sitemaps and structured data. Crawlers get the full page, not a hydration promise.
Brief
Send the
brief.
A half-formed problem works. Pick the closest reason and write three sentences — you get the smallest useful first step back.
Why are you reaching out?
Fast sites, author-friendly content. What's the plan?