<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Adobe Experience Manager &#8211; Best DevOps</title>
	<atom:link href="https://www.bestdevops.com/tag/adobe-experience-manager/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.bestdevops.com</link>
	<description>Lets Learn, Do it &#38; Share! Thats a Best DevOps!!!</description>
	<lastBuildDate>Tue, 13 Oct 2026 00:00:53 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.3</generator>
	<item>
		<title>Adobe Debuts New DevOps Capabilities in Adobe Experience Manager</title>
		<link>https://www.bestdevops.com/adobe-debuts-new-capabilities-for-devops-in-adobe-experience-manager/</link>
					<comments>https://www.bestdevops.com/adobe-debuts-new-capabilities-for-devops-in-adobe-experience-manager/#respond</comments>
		
		<dc:creator><![CDATA[anil]]></dc:creator>
		<pubDate>Thu, 27 Sep 2018 06:29:03 +0000</pubDate>
				<category><![CDATA[Continuous Delivery]]></category>
		<category><![CDATA[Continuous Integration]]></category>
		<category><![CDATA[DevOps]]></category>
		<category><![CDATA[Adobe]]></category>
		<category><![CDATA[Adobe Experience Manager]]></category>
		<guid isPermaLink="false">http://www.bestdevops.com/?p=4433</guid>

					<description><![CDATA[Adobe announced several new features for Adobe Experience Manager, including a Single Page Application Editor, Cloud Manager with CI/CD pipelines, and Smart Imaging for Dynamic Media — all aimed at improving DevOps workflows and content management agility.]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph"><em>Source: <a href="http://readitquik.com" target="_blank" rel="noopener">readitquik.com</a> (original report, 2018)</em></p>



<h2 class="wp-block-heading">Overview</h2>



<p class="wp-block-paragraph">Adobe announced a set of new capabilities for <strong>Adobe Experience Manager (AEM)</strong>, part of the broader Adobe Experience Cloud platform. The additions target three distinct pain points for DevOps and digital experience teams: editing Single Page Applications (SPAs) without breaking front-end workflows, managing cloud environments through a structured CI/CD pipeline, and optimising image delivery automatically at the edge.</p>



<h2 class="wp-block-heading">SPA Editor: Bridging Front-End Development and Content Authoring</h2>



<p class="wp-block-paragraph">Adobe introduced what it described as an industry-first <strong>Single Page Application (SPA) Editor</strong> within AEM. The feature allows front-end developers and content authors to work within the same environment simultaneously, removing the long-standing friction between JavaScript-heavy front-end codebases and CMS-driven content workflows.</p>



<p class="wp-block-paragraph">Key capabilities of the SPA Editor include:</p>



<ul class="wp-block-list">
<li><strong>In-context preview:</strong> Authors can preview an SPA exactly as it will appear to end users, without switching to a separate environment.</li>
<li><strong>JavaScript visibility:</strong> Developers can inspect the underlying JavaScript directly within the editor interface.</li>
<li><strong>Rich content editing:</strong> Text, images, and video can all be edited in-context, reducing round-trips between marketing and engineering teams.</li>
<li><strong>Framework flexibility:</strong> Developers retain the ability to use their preferred front-end frameworks and development environments, integrating SPAs into AEM without abandoning existing toolchains.</li>
</ul>



<p class="wp-block-paragraph">The practical outcome is a clearer division — and overlap — of responsibilities. Marketing teams gain autonomous control over content updates inside SPAs, while developers retain ownership of the application architecture and JavaScript logic. Both sides can co-manage all or parts of an SPA depending on the agreed governance model.</p>



<h2 class="wp-block-heading">Cloud Manager: CI/CD Pipelines for AEM Environments</h2>



<p class="wp-block-paragraph"><strong>Cloud Manager</strong> is a managed service feature for AEM that centralises the orchestration of cloud environments through a unified dashboard. For DevOps teams responsible for AEM deployments, it introduces a structured Continuous Integration / Continuous Delivery (CI/CD) workflow that covers the full path from code commit to production.</p>



<p class="wp-block-paragraph">Cloud Manager capabilities include:</p>



<ul class="wp-block-list">
<li><strong>Automated code deployment:</strong> Deployments can be triggered on-demand or scheduled, giving teams control over release cadence without requiring manual intervention at each step.</li>
<li><strong>Staging and production pipeline management:</strong> Code is promoted through discrete environments with gated transitions, reducing the risk of untested changes reaching production.</li>
<li><strong>Security validation:</strong> Security checks are built into the pipeline, surfacing vulnerabilities before deployment rather than after.</li>
<li><strong>Performance testing:</strong> Automated performance tests run as part of the pipeline, providing objective quality gates.</li>
<li><strong>Code inspection:</strong> Static code analysis helps enforce code quality standards consistently across teams.</li>
</ul>



<p class="wp-block-paragraph">For organisations running AEM at scale, Cloud Manager addresses a common operational challenge: keeping multiple environments (development, staging, production) in sync while maintaining the governance controls that enterprise content platforms require. The dashboard-driven approach lowers the operational overhead for teams that may not have dedicated AEM infrastructure specialists.</p>



<h2 class="wp-block-heading">Dynamic Media Smart Imaging: Automatic Image Optimisation</h2>



<p class="wp-block-paragraph">The third announced capability is <strong>Smart Imaging</strong>, a feature within AEM&#8217;s Dynamic Media module. Smart Imaging automatically analyses the requesting device type and the available network bandwidth, then serves an appropriately sized and compressed image — without requiring manual intervention from developers or content managers.</p>



<p class="wp-block-paragraph">The stated benefits include:</p>



<ul class="wp-block-list">
<li><strong>Reduced file sizes:</strong> Images are resized and recompressed in accordance with detected device and connection characteristics.</li>
<li><strong>Faster page loads:</strong> Smaller assets load faster, improving perceived performance particularly on mobile and low-bandwidth connections.</li>
<li><strong>Visual fidelity preserved:</strong> Compression is applied without perceptible quality loss, maintaining the intended visual experience.</li>
<li><strong>Reduced IT overhead:</strong> IT and operations teams no longer need to manually create and maintain multiple asset renditions for different device profiles.</li>
</ul>



<p class="wp-block-paragraph">For DevOps teams managing asset delivery pipelines and CDN configurations, Smart Imaging shifts a previously manual and error-prone task — maintaining device-specific image renditions — into an automated, policy-driven process.</p>



<h2 class="wp-block-heading">Summary</h2>



<figure class="wp-block-table"><table><thead><tr><th>Feature</th><th>Primary Audience</th><th>DevOps Relevance</th></tr></thead><tbody><tr><td>SPA Editor</td><td>Front-end developers, content authors</td><td>Reduces deployment friction between dev and marketing teams</td></tr><tr><td>Cloud Manager</td><td>DevOps engineers, AEM administrators</td><td>Structured CI/CD pipeline with security, performance, and code quality gates</td></tr><tr><td>Smart Imaging (Dynamic Media)</td><td>IT teams, content operations</td><td>Automates image optimisation, reduces manual rendition management</td></tr></tbody></table></figure>



<p class="wp-block-paragraph">Taken together, these three capabilities reflect Adobe&#8217;s effort to make AEM a more DevOps-native platform — one where content deployment pipelines, front-end development workflows, and asset delivery optimisation are treated as engineering problems with automated solutions, rather than manual processes managed by individual team members.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.bestdevops.com/adobe-debuts-new-capabilities-for-devops-in-adobe-experience-manager/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
