<?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 Koen Van Eeghem on Medium]]></title>
        <description><![CDATA[Stories by Koen Van Eeghem on Medium]]></description>
        <link>https://medium.com/@koen_?source=rss-904903549781------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*wz688bnuzTZk7P4Tk-vNUA.jpeg</url>
            <title>Stories by Koen Van Eeghem on Medium</title>
            <link>https://medium.com/@koen_?source=rss-904903549781------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 21:16:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@koen_/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[Boost your AEM author’s experience]]></title>
            <link>https://medium.com/@koen_/boost-your-aem-authors-experience-85b2aef04422?source=rss-904903549781------2</link>
            <guid isPermaLink="false">https://medium.com/p/85b2aef04422</guid>
            <category><![CDATA[aem-dialog]]></category>
            <category><![CDATA[aem]]></category>
            <category><![CDATA[aem-developer]]></category>
            <category><![CDATA[adobe-experience-manager]]></category>
            <dc:creator><![CDATA[Koen Van Eeghem]]></dc:creator>
            <pubDate>Sat, 27 Feb 2021 20:11:46 GMT</pubDate>
            <atom:updated>2021-02-27T20:11:46.522Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IB-Z-CZS72IM_CqqUTUfdg.jpeg" /></figure><p>Authoring a component in Adobe Experience Manager can quickly become a tedious job. There’s component styles, checkboxes, dropdowns, … — you’d call something complex for less. There’s however a whole bunch of simple things you can do to make your author’s life easier.</p><p>I’ve listed two of them here, that I’ve been using on almost all of my projects.</p><h3>Configure your inline editors… correctly.</h3><p>That AEM has some of the most advanced editing capabilities of all the content management systems out there is widely known. That their inline editors are actually really powerful too, gets overlooked all too quickly. This partially has to do with <a href="https://experienceleague.adobe.com/docs/experience-manager-64/developing/extending-aem/customizing-page-authoring-touch.html?lang=en#code-sample-2">the documentation</a>, which is cryptic on how to configure inline editors.</p><p>For example, when you configure your rich text editor as shown in the tutorials, you will get a white overlay in which you edit your text:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*8lWrmZwfITd5S5hv_SJOXA.gif" /></figure><p>Not only that, but it can get very buggy very quickly. However, this is really easy to solve: just add the <em>editElementQuery</em> property to your inplace editor. That way, AEM knows which HTML element to target, and you will be editing your property visually in your component!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*yA6kPbFchqYGyJfZ-SURIg.gif" /></figure><p>A quick rundown on how the inline editor works:</p><ul><li><em>editorType=</em>”<em>hybrid”</em>: allows you to combine multiple in-place editors on 1 component</li><li><em>name=”./name”</em>: refers to the child editor node under <em>cq:childEditors</em></li><li><em>textPropertyName=”./property”</em>: refers to the property in the JCR where you store the value</li><li><em>editElementQuery=”css.selector”</em>: the CSS selector in the eventual HTML that contains the text this property populates</li><li><strong>note</strong>: there’s two types of text inline editors — <em>text</em> and <em>plaintext</em>, so by default it uses a rich text!</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9924cdde608df5a090622207141350f6/href">https://medium.com/media/9924cdde608df5a090622207141350f6/href</a></iframe><h3>Not using a property? Then hide it!</h3><p>We always try to keep our dialogs as simple as possible, however sometimes business requirements get so funky you just have to add a lot of scenario’s in your dialog. Core components does a really great job of handling this: they hide what you don’t need, based on the selection you make. This results in your dialog dynamically changing based on the selections you make.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*hsasm1_KPzTYtqVK_mTFRA.gif" /></figure><p><a href="https://adobe-consulting-services.github.io/acs-aem-commons/">ACS Commons</a> makes it really easy for you to use it too. By adding a few extra properties, you can hide properties you shouldn’t be using.</p><ul><li>Start by adding <em>extraClientlibs=”[acs-commons.widgets.showhidedialogfields]”</em> to your dialog. This ensures the javascript that handles the showing/hiding is called.</li><li>Add a <em>granite:data</em> node to your select, with on one hand <em>acs-cq-dialog-dropdown-checkbox-showhide=”” </em>(this will add a data attribute, letting the JS know this element controls the show-hiding) and on the other hand <em>acs-cq-dialog-dropdown-checkbox-showhide-target=”.type-of-list-showhide”</em> (which lets the JS know which elements are impacted by the changes on this element).</li><li>On the element that shows/hides based on changes in the dropdown, add a <em>granite:class</em> property containing the CSS class you defined earlier (i.e. type-of-list-showhide).</li><li>Then, add <em>granite:data</em> node with a property <em>acs-dropdownshowhidetargetvalue </em>set to the value in the select it needs to show for. Then, also add the class hide so it’s hidden by default.</li><li><strong>Tip:</strong> Add all elements that need to be shown/hidden together in a well. That way, the JS needs to show/hide less elements, which makes sure your dialog doesn’t get laggy.</li><li><strong>Caution! </strong>You cannot show/hide mandatory properties, this can lead to some really weird dialog validation bugs that make some time to troubleshoot.</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/07b0577a15537a6f4f835fb3b3dfc109/href">https://medium.com/media/07b0577a15537a6f4f835fb3b3dfc109/href</a></iframe><h3>Wrapping up</h3><p>Of course, there’s more than just these two things that contribute to a great editor experience, but I decided it would be better to keep things short so I could keep a hold of your attention 😉</p><p>Are these tips useful? Are there things you would like to see explained? Let us know in the comments and who knows we’ll pick it up for a next edition!</p><h3>Capgemini Belgium Customer Experience</h3><p>We are at the forefront of web development.</p><p>Are you interested in a career in Web Development at Capgemini? Do you have what it takes to join our team of experts? Reach out to us!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85b2aef04422" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AEM Editable templates demystified.]]></title>
            <link>https://medium.com/@koen_/aem-editable-templates-demystified-66b1cdec7889?source=rss-904903549781------2</link>
            <guid isPermaLink="false">https://medium.com/p/66b1cdec7889</guid>
            <category><![CDATA[aem]]></category>
            <category><![CDATA[adobe-experience-manager]]></category>
            <category><![CDATA[aem-features]]></category>
            <dc:creator><![CDATA[Koen Van Eeghem]]></dc:creator>
            <pubDate>Mon, 15 Feb 2021 15:45:56 GMT</pubDate>
            <atom:updated>2021-02-15T15:45:56.278Z</atom:updated>
            <content:encoded><![CDATA[<h3>AEM Editable templates demystified</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6jJgfXIyqv2mNhjzBzFzWA.jpeg" /></figure><p>During my five years implementing Adobe Experience Manager at Capgemini Belgium, I’ve seen a lot of new developers joining our ever-growing team. One of the topics that almost all of these developers had a problem with, was the editable templates in AEM.</p><p>There’s a few reasons why there’s so many people struggling with getting these editable templates right: there’s multiple locations to configure your template, you have those mysterious policies to worry about, … . <strong>Let’s start at the beginning: what does a template consist of?</strong></p><h3>What does a template consist of?</h3><p>First of all, you have the three subfolders of your template: <strong>initial, policies and structure.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/520/1*aW8I2cvkWl1xERET8PwqQA.png" /><figcaption>The structure of an editable template in AEM.</figcaption></figure><h3>The template structure</h3><p><strong>In structure, you include all the immutable content of your template</strong>. Good examples of this are your header and footer experience fragment, your containers where editors can add content, … .<strong> When updating the structure of your template, all pages using that template will be impacted.</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2ff617ebaa1c32b71c14743c3d2da16d/href">https://medium.com/media/2ff617ebaa1c32b71c14743c3d2da16d/href</a></iframe><p>See that property <em>editable</em> on the responsivegrid? This means the editor can edit this component on pages created with this template. Whatever they edit will be only visible on the page itself, not on all pages with the same template — to add components to your responsivegrid, it of course needs to be editable. This property maps to the “locking” of components in the template editor itself.</p><p>Furthermore you also include the breakpoints that will be used for layouting (the <em>cq:responsive</em> subnode) and the devices that can be used in the device emulator (the <em>cq:deviceGroups</em> property). These can all be customized — see <a href="https://levelup.gitconnected.com/aem-customize-emulators-in-layout-mode-288f951d96c5">this interesting story</a> for more information.</p><h3>The initial content of your page</h3><p><strong>In initial, you include all content that needs to be added automatically upon page creation.</strong> You can for example give some page properties default values, or add some components in your responsivegrid by default. This makes your editors’ life a bit easier. <strong>Only pages created after updating the inital content of your template will be impacted.</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/555dbd8b0f906d6d0d558a2a7a27e875/href">https://medium.com/media/555dbd8b0f906d6d0d558a2a7a27e875/href</a></iframe><p>Logically, everything you defined in your template structure needs to be present in the initial content of your page. Then, you can add additional things: in this example we set the description to “This is my default description” for every newly created page. <br>We also add a title component on every new page. Unlike in the structure, you don’t have to specify whether it’s editable or not: it is expected that everything you add in your responsivegrid is editable — because you specified this in your template structure.</p><h3>The policies mapped to your template</h3><p><strong>Finally, in policies, you map the components on your page to a certain policy</strong>. Changing these policies will affect which functionalities are available for your component at runtime.</p><p>To fully understand what happens in the above example, you first have to fully grasp what a policy is. <strong>Policies allow you to change a component’s behavior at runtime.</strong> Sample use cases are the AEM style system, allowed components in a container, … but you can also add your custom properties — but that’s a story for another time.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5a327ed199087494f7339ea8828693d5/href">https://medium.com/media/5a327ed199087494f7339ea8828693d5/href</a></iframe><p>Before mapping these policies, you of course need to create them. They are stored under <em>/conf/your-project/settings/wcm/policies</em>. As a best practice, we then follow the resource type of the component you’re creating a policy for, even though this is not enforced.</p><p>So how do you map these policies to your template? There’s two different ways:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/010b883f9f6fb253dd5332887bbf5fb5/href">https://medium.com/media/010b883f9f6fb253dd5332887bbf5fb5/href</a></iframe><ul><li><strong>by absolute path</strong>: following the page structure in your policies node, map specific nodes to a specific policy (e.g. “jcr:content/root/responsivegrid”)</li><li><strong>by resource type</strong>: within a container (any component with the <em>cq:isContainer</em> property set to <em>true</em>), you can opt to follow the relative resource type of a component. In this case, all components within this container and subcontainers will apply this policy. (e.g. “examples/components/content/product-sheet”)</li></ul><p>Regardless of which way of mapping you choose, the way of working is always the same: on the node where you want to map (hence the resource type “mapping”), you add a <em>cq:policy</em> with the path of the policy you want to map to, relative to <em>/conf/your-project/settings/wcm/policies</em>.</p><h3>Summarised</h3><p>Wrapping up, you can see that in fact these dreaded editable templates aren’t all that complicated: you have a <strong>structure</strong> for all pages using your template, you can provide <strong>initial</strong> content for new pages and define <strong>policies</strong> to allow flexible behaviour of your components depending on where they are used.</p><p>Now, go and spread the word: static templates are dead, long live the editable templates!</p><h3>Capgemini Belgium Customer Experience</h3><p>We are at the forefront of web development.</p><p>Are you interested in a career in Web Development at Capgemini? Do you have what it takes to join our team of experts? Reach out to us!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66b1cdec7889" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>