<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Timothy Lavelle on Medium]]></title>
        <description><![CDATA[Stories by Timothy Lavelle on Medium]]></description>
        <link>https://medium.com/@timothylavelle?source=rss-95a94ca8f627------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Wt6CxPOOOlyy05vaJU0Tog.jpeg</url>
            <title>Stories by Timothy Lavelle on Medium</title>
            <link>https://medium.com/@timothylavelle?source=rss-95a94ca8f627------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 21:10:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@timothylavelle/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Going to the Edge — The Mental Shift Teams Need]]></title>
            <link>https://timothylavelle.medium.com/going-to-the-edge-the-mental-shift-teams-need-9f0e113ebd60?source=rss-95a94ca8f627------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f0e113ebd60</guid>
            <category><![CDATA[adobe-cloud-service]]></category>
            <category><![CDATA[edge-delivery-services]]></category>
            <category><![CDATA[adobe]]></category>
            <dc:creator><![CDATA[Timothy Lavelle]]></dc:creator>
            <pubDate>Tue, 05 Aug 2025 23:32:57 GMT</pubDate>
            <atom:updated>2025-08-06T21:24:47.069Z</atom:updated>
            <content:encoded><![CDATA[<h3>Going to the Edge — The Mental Shift Teams Need</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jdigDe6qm1fQSB2MmHTBkQ.jpeg" /><figcaption>How Adobe is helping us shift our working models and bringing back the basics to create the future</figcaption></figure><p>It’s been a while since my last article — not because I’ve run out of things to say about Adobe Edge Delivery Services (EDS), but because I’ve been busy actually delivering it. This matters because the next phase of this series isn’t conceptual anymore — it’s about what happens when real teams take Edge Delivery Services from concept to production and what it means for the business: faster campaigns 🚀, lower long-term costs 💰, and a stronger, consistent brand experience 🎨.</p><p>What we’ve learned is this: <strong>moving to the Edge is not about migrating old code. It’s about changing how we think and how we work.</strong></p><h3>Why “Greenfield” Is the Only Path Forward</h3><p>When I first introduce Edge Delivery Services to AEM development teams, the most common question is:</p><blockquote><em>Can we just port our existing components to Edge Delivery Services?</em></blockquote><p>The short answer: <strong>no. And more importantly — you shouldn’t want to.</strong></p><p>Greenfield doesn’t mean reckless reinvention. It means making a choice: drag your past forward or rebuild with intent. Edge Delivery Services lets us leave legacy debt behind — without losing our strategy, our brand, or our momentum.</p><p>Edge Delivery Services is built on a different paradigm. There are no Sling models, no TouchUI dialogs, no complex Java-based backend logic. Instead, we’re working with <strong>Blocks</strong> — self-contained pieces built using .json, .css, .js, and optional .storybook.js/.test.js files.</p><p>And that’s liberating — it’s a chance to leave years of technical debt behind 🧹 and modernise using simple, future-proof standards like native JS and CSS.</p><p>We’re not forced to drag along bloated frameworks, heavy dependencies, or complex component inheritance trees. We get to build clean, modern solutions from scratch, using the latest capabilities of native JavaScript and CSS without all the baggage.</p><p>For many teams, this was the first big mindset shift: <strong>stop trying to move everything you already have</strong>. Those old patterns were optimised for a completely different model of AEM. With Edge Delivery Services, you can finally stop over-engineering and start building for what the web has become, not what it used to be.</p><p>Greenfield doesn’t mean throwing away your entire investment. It means selectively rebuilding what doesn’t make sense in an Edge world, leaving behind technical debt while carrying forward your content, brand, and strategy.</p><h3>From Framework Addiction to Vanilla</h3><p>One of the most eye-opening changes came when teams started delivering real features in production. Many had grown dependent on frameworks like React or Vue for even basic interactivity. It’s been standard practice for years: if it’s interactive, use a framework.</p><p>But Edge Delivery Services encourages simplicity. We started building Blocks entirely with <strong>Vanilla JS and CSS</strong>, and the results were surprising, even to seasoned developers.</p><p>A perfect example was a product pricing Block we delivered. It hit every criterion we set for React:</p><ul><li>API-driven dynamic content</li><li>Multiple interactive elements</li><li>State that interacted with other Blocks</li><li>Frequent refresh requirements (every five minutes due to pricing regulations)</li></ul><p>Normally, that would be a perfect use case for a framework. But we challenged the team to keep it native — and it worked beautifully. No React, no complex build setup, no analytics patching, no conditional loading logic. Just clean, fast, lightweight JavaScript.</p><p>Why does this matter? Because <strong>frameworks age out</strong>. They require heavy upgrade cycles and can be abandoned altogether. Vanilla JS and CSS are the foundation of the web itself — they’re future-proof by design. For Blocks that don’t need deep state management, sticking with the basics makes sense, and modern browser support means we’re not sacrificing functionality.</p><p>That’s not to say frameworks are gone entirely. We established a simple rule: if a Block needs API-driven content, multiple interactive elements, and shared state between Blocks, <em>then</em> we consider React. But it’s no longer our default choice.</p><h3>Shifting the Development Workflow</h3><p>Edge Delivery Services also changes how development teams work day to day. Traditional AEM workflows often require running local author instances, compiling heavy Maven builds, coordinating front-end and back-end developers, and maintaining complex package deployments.</p><p>With Edge Delivery Services, we no longer need to split every component between a front-end and a back-end developer. <strong>Blocks can be fully built and owned by a front-end developer</strong>, including their authoring configuration, which is now just a JSON content model instead of custom Java dialogs.</p><p>Developers can still work locally, but deployment is radically faster. Push code to GitHub and within 30 seconds it’s live on a SaaS-powered preview environment ⚡. Gone are the days of building and deploying heavy packages just to see a single change.</p><p>This speed changes everything:</p><ul><li>We can deliver new Blocks faster once the team gets comfortable with the basics.</li><li>We can deploy multiple times a day instead of waiting for big release windows.</li><li>We reduce friction between roles because the development model itself is simpler.</li></ul><p>The learning curve is real, though. Some developers initially struggled because they were used to leaning on frameworks or preprocessors like SCSS for everything. With Edge Delivery Services, <strong>you need to get back to basics</strong>. That meant retraining teams not to overcomplicate things that modern JS and CSS can handle out-of-the-box.</p><p>But as developers adjusted, we started hearing something unexpected: <strong>they liked it</strong>. They liked how fast it was to work, how clean the code was, and how much easier debugging became without multiple frameworks and libraries in the way.</p><h3>Content Production: A Parallel Shift</h3><p>It’s not just developers who have to adjust, the content production teams do too.</p><p>Blocks and Universal Editor simplify authoring and empower content producers to focus entirely on content rather than layout hacks or custom design work. While it may feel like reduced freedom at first, it ensures pixel-perfect brand consistency and frees authors from technical complexity — letting them spend time where it adds the most value: crafting impactful content.</p><p>What feels like a restriction is actually a gift. <strong>Guardrails liberate authors to focus on great content, </strong>not becoming accidental designers. Sites stay on-brand, and content creators spend more time producing meaningful content instead of worrying about page design decisions.</p><p>To support this, we created onboarding materials and hands-on training sessions for both developers and content authors. We showed how to translate old component mental models into the new Block-based approach, and how Universal Editor ensures a 1:1 match with the design system. That investment in training has paid off — teams have embraced the new approach, and even skeptics now see the value.</p><h3>The Results</h3><p>The outcomes speak for themselves:</p><ul><li><strong>Core Web Vitals:</strong> Improved scores across the board thanks to lighter code and faster delivery.</li><li><strong>Complexity:</strong> Some feature sets were reduced by 50% in terms of code size and dependencies.</li><li><strong>Speed-to-market:</strong> Changes that used to take hours to package and deploy now go live in seconds.</li></ul><p>Perhaps the biggest result isn’t a metric at all — it’s the cultural shift. Teams are now building faster, cleaner, and with less technical debt, while content authors are delivering consistent, brand-aligned content more easily.</p><h3>The Mental Shift</h3><p>The real takeaway is this: <strong>Edge Delivery Services isn’t just a technical upgrade. It’s a mindset shift.</strong></p><ul><li>Don’t bring legacy baggage into Edge Delivery Services projects.</li><li>Use frameworks intentionally, not by default.</li><li>Focus on content, not design gymnastics, for authoring teams.</li><li>Embrace simplicity as a principle, not an afterthought.</li></ul><p>Edge Delivery Services is a chance to reset how we work and build a foundation for faster, lighter, and more maintainable digital experiences.</p><h3><strong>What’s Next?</strong></h3><h4>If you thought mindset shifts were fun, wait until we talk about <strong>nesting</strong>.</h4><p>Legacy AEM sites often looked like a Russian doll of deeply nested components and unstructured content — clever at first, painful forever. In my next article, <strong>“How Edge Kept All the Nesting Out,”</strong> I’ll cover:</p><ul><li>Why deeply nested content is a silent killer of site performance &amp; author experience.</li><li>How Edge Delivery Services enforces <strong>clean markup and structured content</strong>.</li><li>Why modern sites thrive when you stop letting authors build “Inception-style” page hierarchies.</li></ul><p><em>(Spoiler: once you stop nesting everything, your site — and your authors — finally breathe again.)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f0e113ebd60" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Adobe’s Universal Editor: It’s Not the Flexibility We Wanted, It’s the Flexibility We Needed]]></title>
            <link>https://timothylavelle.medium.com/adobes-universal-editor-it-s-not-the-flexibility-we-wanted-it-s-the-flexibility-we-needed-87d8c3d0882c?source=rss-95a94ca8f627------2</link>
            <guid isPermaLink="false">https://medium.com/p/87d8c3d0882c</guid>
            <category><![CDATA[adobe]]></category>
            <category><![CDATA[aem]]></category>
            <category><![CDATA[cms]]></category>
            <category><![CDATA[edge-delivery-services]]></category>
            <category><![CDATA[adobe-experience-manager]]></category>
            <dc:creator><![CDATA[Timothy Lavelle]]></dc:creator>
            <pubDate>Tue, 18 Mar 2025 20:43:09 GMT</pubDate>
            <atom:updated>2025-03-18T20:43:09.791Z</atom:updated>
            <content:encoded><![CDATA[<p>For years, content authors in Adobe Experience Manager (AEM) have been moving toward greater control over page layouts. At first, everything was dictated by developers — <strong>static templates meant that every change had to go through code deployments.</strong> Then came editable templates and Layout Mode, <strong>giving content authors the ability to structure pages however they saw fit.</strong></p><p>But now, <strong>Adobe is changing the game again</strong> with <strong>Universal Editor</strong>, and at first glance, it seems like a step backward. Layout Mode is gone. Custom column controls are no longer necessary. Content authors — who once had the power to visually structure pages — are now being told that their focus should be <strong>content-first, not layout-first</strong>.</p><p>I’ve seen the reaction firsthand. <strong>“Where did my Layout Mode go?” “Why can’t I just drop things wherever I want?”</strong> It’s a real paradigm shift. But having worked closely with a client through this transition, I can confidently say:</p><blockquote><strong>This isn’t about taking control away. It’s about removing distractions and helping content creators focus on what matters; Creating Experiences.</strong></blockquote><p>At first, people resist. But then, something clicks, so let me help you understand why.</p><h3>The Learning Curve of Layout Mode — And Why It Wasn’t as Great as We Thought</h3><p>I spent the last year working with a client who had just transitioned from static templates to editable templates. It was a <strong>welcome change</strong> for them — they finally had control over their pages without needing a developer every time they wanted to tweak something.</p><p>But with that control came something unexpected: <strong>a learning curve.</strong></p><p>I remember sitting down with their content team and walking them through <strong>the box model</strong> — how an 8–4 layout works, how to create a balanced 4–4–4 layout, and how to <strong>properly</strong> use AEM’s Layout Mode.</p><p>It took time. Developers instinctively understand <strong>CSS box models</strong>, but content authors? Not so much. They aren’t trained to think in terms of <strong>margins, padding, and div structures</strong> — they just want to put content on a page.</p><p>Eventually, they got used to it. But the process made something clear: <strong>we had given them power, but also responsibility.</strong> The more flexibility they had, the more we had to teach them <strong>not to break layouts, not to stack containers in containers, not to nest accordions inside tabs inside accordions again.</strong></p><p>And that’s exactly why Universal Editor changes things. It <strong>removes</strong> this friction, but without taking away the things that actually matter.</p><figure><img alt="Screenshot of Adobe’s Universal Editor" src="https://cdn-images-1.medium.com/max/1024/1*KjkDKBtik0rmQSYXChh7Yw.png" /></figure><p>The Universal Editor Isn’t About Removing Layouts — It’s About Removing Complexity</p><p>When Adobe introduced the <strong>Universal Editor</strong>, the first reaction from content authors was, <strong>“Wait, so I can’t use Layout Mode anymore?”</strong></p><p>Not exactly. Layout Mode isn’t gone — it’s just <strong>handled differently now</strong>.</p><p>Previously, we had <strong>unlimited control</strong> over layouts. And let’s be honest — we abused it.</p><p>We stacked <strong>layout containers inside layout containers,</strong> creating <strong>deep, unnecessary div structures.</strong> Pages got <strong>bloated.</strong> Load times <strong>increased.</strong> SEO <strong>suffered.</strong></p><p><strong>Just because we could nest endless containers didn’t mean we should.</strong></p><p>Universal Editor changes this mindset. <strong>It shifts the responsibility of layout from content authors to structured, semantic content models.</strong></p><p>Now, instead of stacking multiple containers, content authors use <strong>Blocks and the Section Block</strong> to create structured content. Instead of relying on <strong>dragging and dropping elements all over a page</strong>, they use <strong>the Properties Rail</strong> — a streamlined way to add and edit content without cluttering the UI with popups and overlays.</p><p>At first, this feels restrictive. But once you understand the <strong>why</strong>, you realise:</p><p><strong>It’s not about limiting flexibility. It’s about enforcing the right kind of flexibility.</strong></p><h3>The Properties Rail: A Cleaner, More Consistent Editing Experience</h3><p>One of the first things you’ll notice when using <strong>Universal Editor</strong> is the absence of floating dialogs, popups, and overlay menus that have been a core part of AEM’s <strong>Touch UI</strong>. If you’ve worked with AEM before, you’re probably familiar with this experience:</p><ul><li>You open a component to edit its content, and a <strong>popup window appears</strong> over the page.</li><li>You need to adjust a setting, but the configuration is buried <strong>inside a different dialog.</strong></li><li>Every component has <strong>its own custom UI</strong>, making consistency across pages a challenge.</li></ul><p>For years, <strong>this fragmented editing experience led to confusion</strong> — especially for content teams who weren’t sure where to go to make changes.</p><p>Enter <strong>The Properties Rail.</strong></p><figure><img alt="Basic screen shot of the Universal Editor Properties Rail" src="https://cdn-images-1.medium.com/max/1024/1*XTwuU_atYI8SKv1ioOeR7w.png" /></figure><p>The Properties Rail is a <strong>single, unified panel</strong> that eliminates the clutter. <strong>No more popups, no more hidden dialogs — everything you need to edit a block is in one place.</strong></p><h4>Why This Matters</h4><p>At first, this may not seem like a big deal, but here’s what it solves:</p><p>✅ <strong>Consistency Across Blocks</strong> → Every block now has a standardized editing experience. Whether it’s a hero banner, a CTA, or a text block, everything is edited in the same way.</p><p>✅ <strong>Less UI Clutter</strong> → Because editing is done in the Properties Rail, there’s no need for on-page popups that obscure the content you’re working on.</p><p>✅ <strong>Faster Editing Workflows</strong> → Authors don’t have to remember which block uses which editing interface — they always go to the <strong>same place</strong>.</p><p>✅ <strong>Better Accessibility</strong> → The new editing interface is keyboard-friendly and much easier to navigate.</p><h4>How It Changes the Way We Work</h4><p>At first, <strong>some content authors struggle with this change</strong>. They’re used to editing content <strong>inline or inside popups</strong>, and the Properties Rail feels like an extra step. But in practice, it actually <strong>reduces complexity and speeds up workflows.</strong></p><p>Previously, editing meant:</p><ul><li>Clicking a component → Opening a popup → Navigating multiple tabs → Saving changes → Closing the popup → Refreshing the page.</li></ul><p>Now, editing means:</p><ul><li>Selecting a block → Adjusting content directly in the Properties Rail → Seeing changes update instantly.</li></ul><p>Once content teams get used to it, they just won’t want to go back.</p><h3>The Section Block: How Universal Editor Brings Structure Back</h3><p>For those worried that <strong>Universal Editor removes layout control</strong>, let’s talk about the <strong>Section Block</strong> — the backbone of page structuring in the new model.</p><h4>The Problem: How Layout Mode Encouraged Bad Habits</h4><p>Before Universal Editor, <strong>AEM’s Layout Mode gave content authors complete freedom</strong>. At first, that sounded great — until we started seeing <strong>layouts inside layouts, endless nesting, and content structure getting out of control.</strong></p><p>I’ve seen it happen time and time again:</p><ul><li><strong>Authors stack layout containers inside layout containers.</strong></li><li><strong>Accordions inside tabs, inside another accordion, inside another tab.</strong></li><li><strong>Endless divs ballooning the page size, making performance suffer.</strong></li></ul><p>This was <em>technically possible</em> — but <strong>should it have been?</strong></p><p>The <strong>Section Block fixes this</strong> by enforcing <strong>a structured, semantic approach</strong> to page design.</p><h4>How the Section Block Works</h4><p>Instead of dragging layout containers everywhere, <strong>Sections define the structure of the page</strong> and <strong>Blocks are placed inside them</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/716/1*HJZ5upXBGbN_n4f7Aw1gZA.png" /></figure><p>Each <strong>Section</strong> acts as a content boundary, ensuring:</p><ul><li><strong>Proper heading structure</strong> (H1-H6 hierarchy is respected).</li><li><strong>Logical content flow</strong> (content isn’t scattered randomly).</li><li><strong>SEO benefits</strong> (structured content is easier to crawl).</li><li><strong>Better accessibility</strong> (screen readers understand the page better).</li></ul><p><strong>But wait — what about layouts?</strong></p><p>Yes, <strong>you can still have multi-column layouts</strong>, but they can be <strong>handled through class-based controls, rather than deep-nesting containers. </strong>And this is just one way, there are other ways this can be managed and that’s the <strong>flexibility Edge Delivery Services and Universal Editor give you</strong>.</p><p>For example, instead of creating a <strong>8–4 layout using three nested divs</strong>, you define a <strong>Section Block</strong> and apply a class that controls the column structure.</p><p>This keeps the <strong>markup clean, readable, and performant</strong>.</p><h4>Why I like this and why I think it’s better for Authors &amp; SEO</h4><p>✅ <strong>Encourages authors to think in sections, not arbitrary layouts.</strong><br>✅ <strong>Eliminates unnecessary nesting and div bloat.</strong><br>✅ <strong>SEO benefits from structured content &amp; heading hierarchy.</strong><br>✅ <strong>Better maintainability &amp; page speed improvements.</strong></p><p>So at first, content teams worry that they <strong>lose control over layouting</strong>, but in reality, it <strong>guides them toward better content structuring — without restricting creative freedom.</strong></p><h3>At First, It Feels Different — Then It Feels Right</h3><p>If you’re a content author who’s used to <strong>Layout Mode and full control over placement</strong>, I get it — this shift feels uncomfortable. <strong>It’s natural to resist it. Resistance is Futile after all, right? Nahh</strong></p><p>I’ve worked with teams who initially crossed their arms and said:</p><ul><li><em>“This feels more restrictive.”</em></li><li><em>“This is so much harder to use.”</em></li><li><em>“We can’t use this, we need to go back to the old AEM.”</em></li></ul><p>But then something happens.</p><p>They start working with Universal Editor for a few weeks. They <strong>get used to the Properties Rail</strong>. They <strong>realise they no longer have to manually nest containers</strong>. They <strong>see their pages are structured properly without extra effort. </strong>And then, the moment clicks.</p><p>And I’ve had a client who was <strong>resistant</strong> to the change. They had been using Layout Mode for just over a year, and <strong>the idea of not having drag-and-drop freedom over every aspect of the page frustrated them.</strong></p><p>But after <strong>a 1-hour demo </strong>of how Universal Editor works, their opinion shifted.</p><blockquote><em>“Ohh, that’s not as bad as I thought it was.”</em></blockquote><p>Once they realised they could <strong>focus entirely on content</strong> instead of spending time <strong>tweaking layout adjustments</strong>, they saw how much <strong>faster and cleaner</strong> their work will be.</p><h3>Why I Feel This Shift Matters</h3><ul><li><strong>Content authors should focus on storytelling, not page structure.</strong></li><li><strong>Developers should focus on structured content models, not fixing broken layouts.</strong></li><li><strong>SEO and accessibility should be baked into the authoring experience — not an afterthought.</strong></li></ul><p>And Universal Editor makes this <strong>the default way of working</strong>.</p><h3>To end this, Universal Editor isn’t about <strong>removing power</strong> — it’s about <strong>refining it.</strong></h3><h3>It’s not the flexibility we thought we wanted — but once we understand it, <strong>it’s exactly what we needed</strong>.</h3><h3>Looking Ahead: What’s Coming up?</h3><p>There’s <strong>so much more to explore</strong> in Universal Editor. Now that we’ve covered <strong>the mindset shift</strong>, it’s time to talk about the <strong>deeper technical aspects</strong>:</p><p>📌 <strong>The Nesting Problem in AEM: Why Deep Div Structures Are a Nightmare</strong><br> 📌 <strong>Parent/Child Block Relationships: The Right Way to Build Layouts in EDS</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87d8c3d0882c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Back to the Future with Edge Delivery Services]]></title>
            <link>https://timothylavelle.medium.com/back-to-the-future-with-edge-delivery-services-e9cdcf61939a?source=rss-95a94ca8f627------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9cdcf61939a</guid>
            <category><![CDATA[cms]]></category>
            <category><![CDATA[adobe-cloud-platform]]></category>
            <category><![CDATA[edge-delivery-services]]></category>
            <category><![CDATA[adobe-experience-manager]]></category>
            <category><![CDATA[adobe]]></category>
            <dc:creator><![CDATA[Timothy Lavelle]]></dc:creator>
            <pubDate>Wed, 12 Mar 2025 20:36:14 GMT</pubDate>
            <atom:updated>2025-03-13T00:30:31.013Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*DBvYN4mHU7Qq_g5XTBCHhQ.jpeg" /></figure><h3>The Evolution of AEM Development</h3><p>When Adobe introduced <strong>Edge Delivery Services (EDS)</strong>, many developers and IT leaders had one big question:</p><p><em>“Why is Adobe moving away from traditional AEM components and asking developers to work with Vanilla JavaScript and CSS?”</em></p><p>For years, front-end development has trended towards <strong>heavy frameworks</strong> — React, Angular, Vue — all offering component-based development, state management, and powerful build pipelines. The idea of <strong>reverting to raw HTML, JavaScript, and CSS</strong> felt like a <strong>step backward</strong> to many.</p><p>But here’s the reality — <strong>Adobe isn’t taking developers back in time. </strong>It’s <strong>cutting out unnecessary complexity</strong>, making development leaner, and letting teams <strong>focus on speed, scalability, and performance</strong>.</p><p>In this article, I’ll dive deep into what’s changing, explore real-world examples from a working Adobe Edge Delivery Services project, and break down what this means for front-end development.</p><h3>Why Adobe is Moving from Components to Blocks</h3><p>To understand <strong>why this shift is significant</strong>, we need to look at <strong>how traditional AEM component development worked</strong> versus how <strong>Blocks function in Edge Delivery Services</strong>.</p><p>For nearly a decade, <strong>AEM development followed a structured but complex model</strong>, requiring developers to work across:</p><ul><li><strong>Java</strong> for Business Logic</li><li><strong>Sling Models</strong> for Data Contracting</li><li><strong>HTL (Sightly)</strong> for templating</li><li><strong>XML</strong> for defining the AEM Author UI</li><li><strong>JUnit</strong> for Java testing</li><li><strong>Selenium or Cypress</strong> for automation</li></ul><p>This stack made <strong>AEM development highly specialised</strong>, requiring engineers to <strong>not only understand Adobe’s front-end development framework, but also be well-versed in AEM’s backend intricacies</strong>. The <strong>barrier to entry was high</strong>, and small UI updates could involve <strong>multiple teams across different layers of the tech stack</strong>.</p><p>Now, with <strong>Edge Delivery Services</strong>, Adobe has <strong>stripped away these backend dependencies</strong> and introduced a <strong>Block-based development model</strong> that is:</p><p>✅ <strong>JavaScript-first</strong> — Developers use pure JavaScript (ES6+) to manipulate markup.<br> ✅ <strong>CSS-driven</strong> — Styling is handled directly with CSS, removing the need for HTL or backend rendering.<br> ✅ <strong>JSON-powered</strong> — The Author UI is defined in JSON, enabling seamless integration with the Universal Editor.</p><p>So, what does this mean in practice?</p><p><strong>AEM development is now purely front-end-driven.</strong> No Java. No Sling Models. No XML.</p><p>Everything needed to <strong>build, test, and deploy</strong> a Block <strong>exists within the front-end layer</strong>, making it accessible to any JavaScript developer — without requiring deep knowledge of AEM internals.</p><h3>Understanding the New Project Structure</h3><p>To see <strong>how this shift works in real projects</strong>, let’s break down a real-world <strong>Adobe Edge Delivery Services project structure</strong></p><p>At first glance, you’ll notice something <strong>very different</strong> from traditional AEM projects — there’s no /apps/, no Java, no backend templates. Instead, we get a <strong>fully front-end focused architecture</strong>:</p><pre>eds-project/<br>│── .github/workflows/              # CI/CD pipelines (GitHub Actions)<br>├── .husky/                         # Git commit commands to run during merges<br>├── .storybook/                     # Storybook configuration<br>├── blocks/                         # Reusable UI blocks<br>│   ├── accordion/                  # Example block structure<br>│   │   ├── accordion.js            # Main Block JS file<br>│   │   ├── accordion.css           # Main Block CSS file<br>│   │   ├── accordion.json          # Main Block Properties Rail File<br>│   │   ├── accordion.storybook.js  # Storybook stories<br>│   │   └── accordion.test.js       # Unit tests (Jest/ViTest + Testing Library)<br>│── src/                            # Folder for common assets<br>│   ├── assets/                     # Static assets (images, fonts, icons)<br>│   │   ├── fonts/                  # Font files for project use<br>│   │   ├── icons/                  # Icons files for project use<br>├── models/                         # Core AEM Block Models for Authoring<br>├── scripts/                        # Utility functions (formatting, helpers, etc.)<br>├── tests/                          # Integration and E2E tests (Cypress, Playwright)<br>├── styles/                         # Design system tokens and global styles<br>├── .eslintrc.js                    # ESLint configuration<br>├── README.md                       # Documentation<br>├── component-definition.json       # Master Block definitions<br>├── component-filters.json          # Master Block filters and controls<br>├── component-models.json           # Master Block UI elements<br>├── cypress.config.js               # Cypress for automation testing<br>└── package.json                    # Project dependencies</pre><p>This structure reflects a modern, front-end-focused architecture, emphasising modularity and maintainability.​</p><p>Let’s now also look at how a <strong>common React project</strong> structure looks like when a CMS handles the routing and templating:</p><pre>/my-react-app<br>│── .github/workflows/            # CI/CD pipelines (GitHub Actions)<br>├── .husky/                       # Git commit commands to run during merges<br>│── .storybook/                   # Storybook configuration<br>│── public/                       # Static assets (favicons, index.html, etc.)<br>│── src/                          # Main folder for app build<br>│   ├── assets/                   # Static assets (images, fonts, icons)<br>│   │   ├── fonts/                # Font files for project use<br>│   │   ├── icons/                # Icons files for project use<br>│   ├── components/               # Reusable UI components<br>│   │   ├── Button/               # Example component structure<br>│   │   │   ├── Button.js.        # Main React JS files<br>│   │   │   ├── Button.test.js    # Unit tests (Jest + React Testing Library)<br>│   │   │   ├── Button.stories.js # Storybook stories<br>│   │   │   ├── Button.module.css # Component-specific styles<br>│   ├── styles/                   # Design system tokens and global styles<br>│   ├── hooks/                    # Custom React hooks<br>│   ├── services/                 # API calls, services, third-party integrations<br>│   ├── scripts/                  # Utility functions (formatting, helpers, etc.)<br>│   ├── context/                  # React Context API for global state management<br>│   ├── tests/                    # Integration and E2E tests (Cypress, Playwright)<br>│   ├── App.js                    # Main App component<br>│   ├── index.js                  # React entry point<br>│── cypress/                      # Cypress for automation testing<br>│── .eslint.json                  # ESLint configuration<br>│── .prettierrc                   # Prettier configuration<br>│── package.json                  # Project dependencies<br>│── README.md                     # Documentation</pre><p>Looking at these two structures independently, we may see some similarities, but if we look at a comparison, we’re going to see some surprising, and welcome characteristics:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/99e265f13387bdaaa36705cbcb5bb7b2/href">https://medium.com/media/99e265f13387bdaaa36705cbcb5bb7b2/href</a></iframe><p>The comparison between Edge Delivery Services (EDS) and a React project, or any other popular front-end framework project, is almost a 1:1 match where the only real difference is:</p><ul><li><em>Edge Delivery Services</em> uses the <strong>/blocks/</strong> folder to store reusable UI</li><li><em>React</em> uses <strong>/src/components/</strong> folder to store its reusable UI</li></ul><p>Now I wasn’t in the room when the minds behind Edge Delivery Services worked this solution up, but I do have the opportunity of speaking with Adobe engineers and Product Management and I like to think the above comparison is intentional and was the best move they’ve made in a long time.</p><h3>Some Key Takeaways from This Structure</h3><p>📌 <strong>Each Block is fully independent</strong> — Every UI element is self-contained, with its own JS, CSS, and _Block-Model.JSON Storybook and Test files<br> 📌 <strong>No Sling Models or HTL</strong> – JavaScript directly manipulates the DOM, replacing traditional templating.<br> 📌 <strong>Testing can be built-in</strong> – Cypress, Jest, or ViTest can be used for both unit and end-to-end testing.<br> 📌 <strong>Linting &amp; Formatting</strong> – ESLint, Prettier are used to maintain code consistency.</p><p>Adobe’s new model for development is <strong>lighter, faster, and easier to maintain</strong> than legacy AEM component development and I think we all can rejoice and praise Adobe for this shift.</p><h3>Common Misconceptions About This Approach</h3><p>Despite the benefits, many developers <strong>still feel skeptical about this shift</strong>. Let’s tackle some of the <strong>biggest misconceptions</strong> head-on.</p><h4>“Vanilla JavaScript? This feels like going back 10 years.”</h4><p>For years, front-end developers have <strong>relied on frameworks like React and Vue</strong> for state management and modularisation. The thought of <strong>returning to plain JavaScript</strong> can feel counterintuitive and I’ve heard this directly from some big brands, which ultimately led me to writing these articles.</p><p><strong>So let’s do a quick reality check:</strong></p><ul><li><strong>ES6+ JavaScript is fully modular</strong> — import/export syntax, async/await, and class-based structures allow for scalable development.</li><li><strong>Components are now a standard</strong> — without needing React’s virtual DOM.</li><li><strong>Performance is significantly better</strong> — no bloated JS bundles or framework dependencies.</li></ul><h4>“Without SASS or LESS, CSS will be a nightmare to manage.”</h4><p>Before CSS3, preprocessors like SASS were essential for <strong>variables, mixins, and nesting</strong>. But today, <strong>CSS3 provides these natively</strong>:</p><p><strong>Let’s do some quick fact checking here:</strong><br> ✅ <strong>CSS Custom Properties replace SASS variables</strong> — Fully supported in all browsers.<br> ✅ <strong>Native Nesting is now part of CSS</strong> — Eliminates the need for preprocessors.<br> ✅ <strong>Logical Properties &amp; Grid replace most mixin functionality</strong> — Making layouts more intuitive.</p><p>With CSS3’s advancements and browser supporting these features, there’s <strong>no need to compile styles anymore</strong> — which means <strong>faster builds and smaller file sizes</strong>.</p><h4>“Without import statements, how do we maintain UI consistency?”</h4><p>A major concern is how teams <strong>can reuse elements</strong> without standard React/Vue imports.</p><p><strong>In actuality:</strong><br> ✅ <strong>Design Systems remain intact</strong> — Blocks can be pre-defined and versioned like any other component.<br> ✅ <strong>JavaScript modules still work</strong> — Code can be structured in an ES6-friendly way, with reusable methods.</p><p>Which means instead of relying on <strong>heavy UI frameworks</strong>, Adobe is making<strong> </strong>lightweight, reusable Blocks a reality <strong>— without unnecessary complexity</strong>.</p><h3>Is there a place for React in my Edge Delivery Services Project?</h3><p>And the question which may be rummaging around your minds… can I still use React in a Edge Delivery Services project? <strong>The answer is yes!</strong> And better yet, the folder structure is almost already setup for you and later in this series, I’ll even discuss how we can create UI elements and import them into Blocks, just like we do with React atoms and components.</p><p>Which means Edge Delivery Services does not mean ReactJS is out — All it means is for CMS sites which are highly static, and a lot of them are, should use React when it’s fit for purpose, but not as default.</p><p>And don’t get me wrong… I love React and what NextJS is doing out there, but in my experience and work with global brands, use the right tool for the right job.</p><h3>Final Thoughts — The Future of CMS Development</h3><p>Edge Delivery Services <strong>isn’t just an evolution of AEM — it’s a fundamental shift </strong>in how front-end teams build for CMS-driven experiences.</p><p>✔ <strong>Decoupling UI from backend complexity</strong> makes development more accessible.<br> ✔ <strong>Simplified Blocks replace </strong>heavy component-based architectures.<br> ✔ <strong>Performance is significantly improved</strong> with <strong>less JavaScript overhead.</strong></p><p>So, hopefully we can all agree… this <strong>isn’t a step backward</strong> — it’s a streamlined, modern approach that <strong>keeps the best parts of today’s development while removing unnecessary bloat.</strong></p><p>And this isn’t a step back in time, <strong>it’s a step back into the future</strong> and I applaud the Adobe architects for giving us this DeLorean.</p><h3>Up Next: Universal Editor &amp; Headless Content Authoring</h3><p>In my next article, I’ll be diving into <strong>Adobe’s Universal Editor</strong>, exploring how it:</p><ul><li><strong>Supports both traditional Blocks &amp; Single Page Apps (SPAs).</strong></li><li><strong>Enables real-time content editing across any front-end framework.</strong></li><li><strong>Creates a truly headless CMS experience.</strong></li></ul><p><strong>Follow the series to learn more about the future of AEM &amp; Edge Delivery Services.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9cdcf61939a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Journey to the Edge — Full Article Series]]></title>
            <link>https://timothylavelle.medium.com/a-journey-to-the-edge-full-article-series-58d5e4c13b9e?source=rss-95a94ca8f627------2</link>
            <guid isPermaLink="false">https://medium.com/p/58d5e4c13b9e</guid>
            <category><![CDATA[edge-delivery-services]]></category>
            <category><![CDATA[aemasacloudservice]]></category>
            <category><![CDATA[adobe]]></category>
            <category><![CDATA[adobe-experience-manager]]></category>
            <dc:creator><![CDATA[Timothy Lavelle]]></dc:creator>
            <pubDate>Sun, 09 Mar 2025 21:34:56 GMT</pubDate>
            <atom:updated>2025-08-05T23:33:52.453Z</atom:updated>
            <content:encoded><![CDATA[<h3>A Journey to the Edge — Full Article Series</h3><figure><img alt="Image splitting the reality between two view of thought" src="https://cdn-images-1.medium.com/max/512/1*2sqzY_S54mY0OWxmINk6uA.jpeg" /></figure><p>With the 2025 Adobe Summit coming up soon and the work I’ve been doing here in Australia around Adobe’s Edge Delivery Services, I started seeing common misconceptions about it around the market. As I was drinking my coffee this morning and reading emails, I felt like I wanted to share my experience from working with brands here and working with Adobe on some exciting client transformations.</p><p>🔥 So, I’m launching a 10-part series where I’ll share and explore:</p><h3>Setting the Stage — What is Edge and Why it Matters?</h3><p>1️⃣ <a href="https://timothylavelle.medium.com/if-you-think-adobes-edge-delivery-services-is-just-client-side-rendering-you-re-missing-the-427abf08d2df"><strong>Edge and the Rendering Conundrum</strong></a> (<em>Published</em>)</p><ul><li><strong>The myth:</strong> Many assume Edge Delivery Services (EDS) is just client-side rendering.</li><li><strong>The reality:</strong> EDS uses <strong>server-side rendering (SSR)</strong> for fully structured content, decorated at the edge with CSS and JavaScript.</li><li><strong>Key topics:</strong> SSR vs. CSR, client-side decoration (CSD), SEO implications, and real-world performance metrics.</li></ul><p>2️⃣ <a href="https://timothylavelle.medium.com/back-to-the-future-with-edge-delivery-services-e9cdcf61939a"><strong>Back to the Future with Edge Delivery Services</strong></a><strong> </strong>(<em>Published</em>)</p><ul><li>Why Adobe is simplifying development by embracing JavaScript &amp; CSS again.</li><li>Why this isn’t a step backward but a move towards efficiency.</li><li>The shift away from heavy frameworks &amp; overly complex CMS development.</li></ul><p>3️⃣ <a href="https://timothylavelle.medium.com/adobes-universal-editor-it-s-not-the-flexibility-we-wanted-it-s-the-flexibility-we-needed-87d8c3d0882c"><strong>Edge and its Companion, Universal Editor</strong></a><em> (Published)</em></p><ul><li>How Universal Editor fits into Edge Delivery Services.</li><li>How it redefines content authoring &amp; previewing.</li><li>Live editing at scale with pre-rendered content.</li></ul><h3>Shifting Mindsets — How Edge Changes the Way We Work</h3><p>4️⃣ <a href="https://timothylavelle.medium.com/going-to-the-edge-the-mental-shift-teams-need-9f0e113ebd60"><strong>Going to the Edge — The Mental Shift Developers Need</strong></a><strong> </strong><em>(Publishedd)</em></p><ul><li>Why building for EDS isn’t a lift-and-shift migration — it’s a greenfield approach.</li><li>How development teams should rethink workflows &amp; frontend architecture.</li><li>Practical examples of shifting from traditional AEM to EDS.</li></ul><p>5️⃣ <strong>How Edge Kept All the Nesting Out</strong></p><ul><li>The problem with legacy AEM sites — deeply nested, unstructured content.</li><li>How EDS enforces better markup &amp; structured content.</li><li>Why modern sites benefit from strict component hierarchy &amp; constraints.</li></ul><h3>Automation &amp; Scaling on Edge</h3><p>6️⃣ <strong>Edge and the Automation Influence</strong></p><ul><li>Deploying fast = delivering quality fast.</li><li>The importance of automated testing, validation, and monitoring.</li><li>How to implement CI/CD for EDS to ensure seamless rollouts.</li></ul><p>7️⃣ <strong>At the Edge of Git Goodness — Automating Everything, Everywhere, All at Once</strong></p><ul><li>Leveraging GitHub Actions &amp; workflows for AEM Edge Delivery.</li><li>How pre-commit hooks, automated linting, and CI/CD fit into EDS.</li><li>Examples of optimised Git workflows for Edge-based deployments.</li></ul><p>8️⃣ <strong>Promoting Edge to the Edge</strong></p><ul><li>Automating deployments while ensuring quality control.</li><li>How to structure your environments for best performance.</li></ul><h3>Building on Edge — New Development Approaches</h3><p>9️⃣ <strong>Building Apps for Edge — No More Customising, Just Innovating</strong></p><ul><li>Moving away from customising AEM’s TouchUI interfaces.</li><li>Using React apps for custom integrations &amp; functionality.</li><li>How micro-frontends and modular applications fit into EDS.</li></ul><p>🔟 <strong>Edge and Your Design System — Building New Worlds</strong></p><ul><li>How design systems integrate seamlessly with Edge Delivery Services.</li><li>Automating updates &amp; ensuring consistency across experiences.</li><li>How teams can manage design assets &amp; style guides efficiently.</li></ul><h3>Each article will be packed with insights, humour, and a no-BS take on the new era of Adobe AEM development.</h3><p>If you’ve ever wondered “what is Edge Delivery Services, and why should I care?” — this series is for you.</p><p>📌 Follow me to stay updated as we push AEM to the Edge — and beyond.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=58d5e4c13b9e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[If you think Adobe’s Edge Delivery Services is just client-side rendering, you’re missing the…]]></title>
            <link>https://timothylavelle.medium.com/if-you-think-adobes-edge-delivery-services-is-just-client-side-rendering-you-re-missing-the-427abf08d2df?source=rss-95a94ca8f627------2</link>
            <guid isPermaLink="false">https://medium.com/p/427abf08d2df</guid>
            <category><![CDATA[adobe-experience-manager]]></category>
            <category><![CDATA[adobe]]></category>
            <category><![CDATA[edge-delivery-services]]></category>
            <category><![CDATA[aemasacloudservice]]></category>
            <category><![CDATA[aem]]></category>
            <dc:creator><![CDATA[Timothy Lavelle]]></dc:creator>
            <pubDate>Sun, 09 Mar 2025 21:25:22 GMT</pubDate>
            <atom:updated>2025-03-09T21:51:04.034Z</atom:updated>
            <content:encoded><![CDATA[<h3>If you think Adobe’s Edge Delivery Services is just client-side rendering, you’re missing the bigger picture.</h3><p>The Truth About AEM’s Edge Delivery Services Platform</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DTmvHWHuRC2ZZDXj7OS7-w.png" /><figcaption>Allowing our brains to think differently about Edge Delivery Services</figcaption></figure><p>Everyone thinks Adobe’s Edge Delivery Services, part of Adobe Experience Manager Sites, is just client-side rendering… but what if I told you that’s completely wrong? In fact, all your content is <strong>server-side rendered</strong> and <strong>decorated at the edge</strong> — yes, both! Confused? Buckle up, because we’re about to break this down and melt some minds!</p><p>With AEM’s Edge Delivery Services, many assume everything is rendered on the client-side. But the reality is a mix of <strong>edge computing, pre-rendering, and optimized delivery techniques</strong>. If your brain is still intact, let’s dive deeper.</p><h3>Understanding Server-Side Rendering (SSR) in Edge Delivery Services</h3><p>One of the biggest misconceptions about Adobe Edge Delivery Services is that it’s just client-side rendering. That’s a myth.</p><h3>What is Server-Side Rendering (SSR)?</h3><p>At its core, <strong>Server-Side Rendering (SSR)</strong> refers to the process where a server <strong>generates the full HTML for a page before it is sent to the client’s browser.</strong> This approach differs from <strong>Client-Side Rendering (CSR),</strong> where a browser has to download JavaScript, execute it, and then build the page dynamically.</p><p>With <strong>Edge Delivery Services</strong>, SSR works by generating clean, semantic HTML on Adobe’s cloud infrastructure <strong>before the page even reaches the browser.</strong> This means that instead of waiting for JavaScript to populate the page dynamically, a user (or a search engine crawler) gets <strong>fully structured content immediately</strong>.</p><h3>Why Does This Matter?</h3><p>SSR is crucial because for many reasons and is why development teams have turned to frameworks like ReactJS and NextJS/NestJS to give them the ability to render CMS content on the server — But these come with additional customisations, additional work, and additional frameworks to manage. Teams use these frameworks because our businesses and our online authority need:</p><ul><li><strong>Faster First Paint:</strong> Users see meaningful content almost instantly because the browser doesn’t need to run JavaScript before rendering text and images.</li><li><strong>SEO Optimisation:</strong> Since search engine crawlers index the <strong>raw HTML output</strong>, they don’t have to execute JavaScript, which improves discoverability.</li><li><strong>Lower Time to First Byte (TTFB):</strong> Content is delivered almost immediately because the heavy lifting is done before reaching the browser.</li></ul><p>Here’s a look at <strong>what web crawlers actually see</strong> before any client-side decoration takes place:</p><pre>&lt;div&gt;<br>  &lt;div class=&quot;authorable-card&quot;&gt;<br>    &lt;div&gt;<br>      &lt;div&gt;<br>        &lt;h2 id=&quot;get-started-with-experience-manager&quot;&gt;Get started with Experience Manager&lt;/h2&gt;<br>      &lt;/div&gt;<br>    &lt;/div&gt;<br>    &lt;div&gt;<br>      &lt;div&gt;Content to help you get started with your solution&lt;/div&gt;<br>    &lt;/div&gt;</pre><p>This output ensures <strong>maximum compatibility across browsers, devices, and search engines</strong> before any additional styling or interactivity is introduced.</p><p>But how can we verify this, is it all just smoke? Not at all. Adobe has provided a way for teams to view the <strong>raw, plain, undecorated page</strong> to validate what critical content is on the page for search engine crawlers. Take this example below:</p><figure><img alt="A snippet of Adobe Experience League Plain.html" src="https://cdn-images-1.medium.com/max/665/1*oQtcbYBeER7EPP3vgnLo2w.png" /><figcaption><a href="https://experienceleague.adobe.com/en/browse/experience-manager.plain.html">https://experienceleague.adobe.com/en/browse/experience-manager.plain.html</a></figcaption></figure><p>With the above, it’s pure semantic HTML with no additional clutter or Scripts to slow down the loading of the content for the search engine crawlers. This is why Adobe states they’ll give you a 100 score lighthouse site at the start and it’s on the development teams to keep that score high. <em>We’ll touch more on this later in the series.</em></p><h3>So, Where Does Client-Side Decoration Fit In?</h3><p>From my discussions with some large global brands, this is where the <strong>big misunderstanding begins</strong>.</p><p>When people hear “<em>Edge Delivery Services</em>,” they automatically assume <strong>client-side rendering</strong>. But what’s actually happening is <strong>client-side decorating</strong>. And this is where all the confusion comes from.</p><h3>Client-Side Decoration vs. Client-Side Rendering</h3><p>Client-side decoration is <strong>not</strong> the same as client-side rendering. Here’s how they differ:</p><ul><li><strong>Client-Side Rendering (CSR):</strong> The browser downloads JavaScript, runs it, and builds the page dynamically. This often results in longer load times and content delays.</li><li><strong>Client-Side Decoration:</strong> The core content is <strong>already available</strong> (from SSR), and JavaScript/CSS <strong>only enhance the visual experience</strong>.</li></ul><h3>What Happens During Client-Side Decoration?</h3><p>Once the <strong>fully structured HTML</strong> reaches the browser, JavaScript and CSS step in to:</p><ul><li>Apply <strong>styling, animations, and layouts</strong>.</li><li>Add additional<strong> mark-up, attributes</strong>, and <strong>elements</strong>.</li><li>Load <strong>interactive elements</strong> like menus, personalisation widgets, and lazy-loaded images.</li><li>Fetch <strong>dynamic content updates</strong> without reloading the page.</li></ul><p>To give an example, here’s what that <strong>earlier content looks like after decoration</strong>:</p><pre>&lt;div class=&quot;authorable-card-wrapper&quot;&gt;<br>  &lt;div class=&quot;authorable-card block browse-cards-block&quot; data-block-name=&quot;authorable-card&quot; data-block-status=&quot;loaded&quot;&gt;<br>    &lt;div class=&quot;browse-cards-block-header&quot;&gt;<br>      &lt;div class=&quot;browse-cards-block-title&quot;&gt;<br>        &lt;h2 id=&quot;get-started-with-experience-manager&quot;&gt;Get started with Experience Manager&lt;/h2&gt;<br>        &lt;div class=&quot;tooltip-placeholder&quot;&gt;<br>          &lt;div class=&quot;tooltip tooltip-right tooltip-blue&quot;&gt;<br>            &lt;span class=&quot;icon icon-info&quot;&gt;&lt;img data-icon-name=&quot;info&quot; src=&quot;/icons/info.svg&quot; alt=&quot;&quot;<br>                loading=&quot;lazy&quot;&gt;&lt;/span&gt;&lt;span class=&quot;tooltip-text&quot;&gt;Content to help you get started with your<br>              solution&lt;/span&gt;<br>          &lt;/div&gt;<br>           .... omitted dynamic loading content ....<br>        &lt;/div&gt;<br>      &lt;/div&gt;<br>    &lt;div&gt;</pre><p>As we can see, the mark-up and elements have indeed been updated and quite drastically, but without a hit to the sites Core Web Vitals.</p><p>And this is the Decorated version of the plain.html view we saw earlier:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NXwflU02bQr8KcG8UGPyAw.png" /><figcaption>Client-Side Decorated view of the section</figcaption></figure><h3>Why Is This Important?</h3><p>Client-side decoration allows:</p><ul><li><strong>Better SEO:</strong> Since the structured HTML is already available, search engines can index content immediately.</li><li><strong>Faster page loads:</strong> Users see meaningful content sooner, even if decorations load after.</li><li><strong>A smooth experience:</strong> Enhancements (like animations or personalisation) don’t block critical content.</li></ul><h3>Measuring Performance: SSR vs. CSR with Real Data</h3><p>Since skeptics will want <strong>hard evidence</strong>, I ran a performance tests on the <strong>Adobe Experience League AEM page</strong> using <strong>Google Lighthouse &amp; WebPageTest</strong> to compare <strong>SSR vs. CSR performance</strong>.</p><h3>Performance Metrics: SSR vs. CSR</h3><p>We measured key performance indicators, focusing on <strong>Time to First Byte (TTFB), Largest Contentful Paint (LCP), and Total Blocking Time (TBT).</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/92e9c7981f6ae4bac25e6c7b8e98d0ec/href">https://medium.com/media/92e9c7981f6ae4bac25e6c7b8e98d0ec/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/826/0*ATlNyX6WSrrk-2AR" /></figure><p>Both sites rank this page a 100 out of 100 for it’s performance, even though the page we’re testing is highly dynamic — which was the intention to show even with dynamic content being loaded, the site is performant.</p><p>Is it a 100 across the board, no. But it is close and those few niggling errors are easily fixable.</p><h3>Key Findings</h3><ul><li><strong>SSR drastically improves TTFB</strong> by delivering fully structured HTML before JavaScript runs.</li><li><strong>LCP (time for the largest visible element to load) is 2.5× faster</strong> in SSR, making the page feel much more responsive.</li><li><strong>Client-side decoration has minimal impact on SEO</strong> since structured HTML is available immediately.</li></ul><h3>Why TTFB and LCP Matter in Edge Delivery Services</h3><p>When evaluating web performance, <strong>Time to First Byte (TTFB)</strong> and <strong>Largest Contentful Paint (LCP)</strong> are two of the most critical Core Web Vitals. These metrics <strong>directly impact user experience, search rankings, and perceived speed.</strong></p><h4>Time to First Byte (TTFB) — The First Impression of Speed</h4><p><strong>What is TTFB?</strong><br> TTFB measures <strong>how quickly the server responds</strong> after a request is made. It’s the <strong>first indicator of whether a webpage loads fast or slow</strong>.</p><p><strong>Why Does It Matter?</strong></p><ul><li>A <strong>high TTFB</strong> means users are staring at a blank screen longer before any content appears.</li><li><strong>Search engines like Google use TTFB as a ranking factor</strong> since it reflects server efficiency.</li><li>Studies show that a <strong>TTFB under 200ms is ideal</strong>, while <strong>above 600ms can start to hurt SEO and user retention.</strong></li></ul><p><strong>How Adobe Optimised TTFB in Edge Delivery Services</strong><br> Adobe has worked very hard to <strong>fine-tune server-side response times</strong> by:</p><p>✅ <strong>Pre-rendering content at the edge</strong> to avoid unnecessary backend processing.<br>✅ <strong>Leveraging global CDN caching</strong> to serve content faster to users worldwide.<br>✅ <strong>Reducing backend dependencies</strong> by separating content rendering from dynamic API calls.</p><p><em>Our key takeaway from all of this:</em> <strong>A lower TTFB = Faster perceived performance and better SEO </strong>and Adobe Edge Delivery services has been architected and setup to help brands achieve this.</p><h4>Largest Contentful Paint (LCP) — The Real Page Load Time</h4><p><strong>What is LCP?</strong><br> LCP measures <strong>how long it takes for the largest visible element (like a hero image, H1 title, or banner) to load on the screen.</strong></p><p><strong>Why Does It Matter?</strong></p><ul><li>LCP is <strong>the moment when users feel like the page has actually loaded.</strong></li><li>A slow LCP leads to higher bounce rates — if a page <strong>takes over 3s to load, 53% of users will leave.</strong></li><li><strong>Google’s ideal LCP target is under 2.5 seconds</strong> for a good user experience.</li></ul><p><strong>How Adobe Improved LCP </strong><br> Adobe focused on <strong>optimising LCP for Edge Delivery Services by:</strong><br> ✅ <strong>Ensuring critical content is server-rendered (SSR) first,</strong> so users see meaningful content ASAP.<br> ✅ <strong>Eliminating render-blocking JavaScript</strong> that could delay LCP.<br> ✅ <strong>Prioritising above-the-fold content loading</strong> so key elements don’t wait for less important scripts.<br> ✅ <strong>Improving preloading techniques</strong> — Edge Delivery Services automatically preloads <strong>important assets and fonts</strong>.</p><p><em>Our key takeaway here:</em> <strong>A fast LCP = Users engage with the page quicker, improving retention and conversion rates </strong>and is why Adobe has also introduced their <em>E-L-D phases, which we’ll cover later in the series as wel</em>l.</p><h3>Final Wrap-Up: Edge Delivery Services = The Perfect Balance</h3><p>Modern web performance demands <strong>speed, flexibility, and search engine visibility</strong> — but historically, developers had to compromise. <strong>Go full SSR, and you get clean, fast-loading pages but at a higher cost and reduced business flexibility. Go full CSR, and you get dynamic experiences but sacrifice SEO and load times.</strong></p><p><strong>Adobe’s Edge Delivery Services eliminates that trade-off.</strong></p><p>With a <strong>server-side first approach</strong>, Edge Delivery Services delivers fully <strong>rendered, semantic HTML instantly available to search engines</strong>, ensuring that content is not only discoverable but also <strong>optimally structured for indexing</strong>. Meanwhile, <strong>client-side decoration</strong> applies <strong>CSS and JavaScript enhancements in milliseconds</strong>, maintaining interactivity, dynamic content flexibility, and a modern development experience.</p><p>This approach is the result of <strong>deep collaboration between Adobe and Google</strong>, ensuring that <strong>AEM-powered sites meet and exceed Core Web Vitals standards</strong> — delivering pages that are fast, engaging, and search-friendly. The result?<br>🔹 <strong>Content = Server-side rendered for clean SEO-friendly markup.</strong><br>🔹 <strong>CSS &amp; JavaScript = Applied client-side for design &amp; interactivity.</strong><br>🔹 <strong>Result = Fast, flexible, and fully indexable by search engines.</strong></p><p>So no — <strong>Edge Delivery Services isn’t “just client-side rendering.”</strong> It’s <strong>client-side decorating</strong> — and that’s a revolutionary shift in performance and architecture.</p><h3>What’s Next?</h3><p>This article is part of <strong>“A Journey to the Edge”</strong>, a series exploring <strong>how Adobe Experience Manager’s Edge Delivery Services redefines modern web architecture.</strong></p><p><strong>Coming up next in the series:</strong><br> 🔹 <strong>Back to the Future with Edge</strong> → Why Adobe’s return to JavaScript &amp; CSS isn’t a step backward, but the smartest move forward.<br>🔹 <strong>Edge and its Companion, Universal Editor</strong> → Understanding how the Universal Editor fits into Edge’s workflow.</p><p>📌 <strong>Follow the series</strong> to dive deeper into <strong>how Edge Delivery Services transforms performance, workflow efficiency, and development best practices.</strong></p><p>💬 Have questions or thoughts? Drop them in the comments — let’s discuss!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=427abf08d2df" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>