<?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 PelinHangisi on Medium]]></title>
        <description><![CDATA[Stories by PelinHangisi on Medium]]></description>
        <link>https://medium.com/@pelinhangisi?source=rss-d051be460c83------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*pNtasGMxZ_SOc31ukZBfqQ.png</url>
            <title>Stories by PelinHangisi on Medium</title>
            <link>https://medium.com/@pelinhangisi?source=rss-d051be460c83------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 08:58:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pelinhangisi/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[What Is an Experience Fragment (XF) in AEM?]]></title>
            <link>https://medium.com/@pelinhangisi/what-is-an-experience-fragment-xf-in-aem-b1f355497d4f?source=rss-d051be460c83------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1f355497d4f</guid>
            <category><![CDATA[aem-developer]]></category>
            <category><![CDATA[aem-experience-fragment]]></category>
            <category><![CDATA[adobe-experience-manager]]></category>
            <category><![CDATA[aem]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[PelinHangisi]]></dc:creator>
            <pubDate>Sun, 11 Jan 2026 14:46:05 GMT</pubDate>
            <atom:updated>2026-01-11T14:46:05.071Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A Beginner-Friendly Explanation</em></p><p>If you start learning Adobe Experience Manager (AEM), one of the concepts you’ll encounter quite early is <strong>Experience Fragment (XF)</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0MpXMiYzUuMR2d7Ph47GdQ.png" /></figure><p>At first, it usually feels confusing:</p><ul><li>Is it a page?</li><li>Is it a component?</li><li>Is it just copy–paste content?</li></ul><p>In this article, I’ll explain Experience Fragments <strong>from scratch</strong>, step by step, in a clear and simple way.</p><h3>The Simplest Definition</h3><p>An <strong>Experience Fragment (XF)</strong> is:</p><blockquote><em>A reusable content block made up of multiple components<br> that can be used consistently across different pages.</em></blockquote><p>In other words:</p><ul><li>You create it once</li><li>You reuse it on many pages</li><li>When you update it, it updates everywhere</li></ul><h3>A Real-Life Example</h3><p>Imagine you have a website where these sections are the same on many pages:</p><ul><li>Header</li><li>Footer</li><li>Campaign banner</li><li>Login or promotion popup</li></ul><p>If you add these manually to every page:</p><ul><li>Updating them is painful</li><li>Maintenance becomes harder</li><li>The risk of mistakes increases</li></ul><p>This is where <strong>Experience Fragments</strong> come in.</p><blockquote><em>“Create once, manage centrally, reuse everywhere.”</em></blockquote><h3>An Experience Fragment Is NOT a Page (Very Important)</h3><p>An XF:</p><ul><li>❌ Is not a regular AEM page</li><li>❌ Does not have its own URL</li><li>❌ Does not behave like a page with page properties</li></ul><p>But:</p><ul><li>✔ It contains components</li><li>✔ It has layout and styling</li><li>✔ It is editable by authors</li></ul><p>So think of it like this:</p><blockquote><em>An XF looks like a page, but it is not a page.</em></blockquote><h3>Where Do Experience Fragments Live?</h3><p>Experience Fragments are stored in a dedicated location in AEM:</p><pre>/content/experience-fragments/</pre><p>They live <strong>outside</strong> the normal page structure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Wk6UbrBzcq33LRybdCsOg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xIxHd0mK9oKp4zDJfo2Xhw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hbZF45Wo8tG8BSMcJV8oZQ.png" /></figure><p>This separation is intentional:</p><ul><li>Pages manage navigation and flow</li><li>Experience Fragments manage shared content</li></ul><h3>What Can an Experience Fragment Contain?</h3><p>Inside an XF, you can place:</p><ul><li>Text</li><li>Images</li><li>Buttons</li><li>Containers</li><li>Custom components</li></ul><p>Basically:</p><blockquote><em>Anything you can place on a page, you can also place inside an XF.</em></blockquote><p>The key difference is purpose:</p><ul><li>Pages are standalone</li><li>XFs are designed to be reused</li></ul><h3>What Is a Variation?</h3><p>When you create an Experience Fragment, you’ll always see <strong>Variations</strong>.</p><p>A variation is:</p><ul><li>A version of the same Experience Fragment</li></ul><p>Examples:</p><ul><li>Desktop banner</li><li>Mobile banner</li><li>Different language or campaign versions</li></ul><p>When adding an XF to a page:</p><ul><li>You select the XF</li><li>Then you select <strong>which variation</strong> to render</li></ul><blockquote><em>Pages render variations, not the XF root itself.</em></blockquote><h3>How Do You Add an XF to a Page?</h3><p>The most common way:</p><ol><li>Add the <strong>Experience Fragment Component</strong> to the page</li><li>Select the Experience Fragment</li><li>Choose the variation</li></ol><p>That’s it.</p><p>One important detail though 👇<br> The XF is rendered <em>inside</em> the page — it doesn’t live separately in the UI.</p><h3>Common Beginner Mistakes</h3><h3>1️⃣ Using XF for Everything</h3><p>Experience Fragments are powerful, but:</p><ul><li>Not every piece of content should be an XF</li></ul><p>Single-use content usually doesn’t need one.</p><h3>2️⃣ Treating an XF Like a Page</h3><p>Inside an XF:</p><ul><li>Page-based logic</li><li>currentPage conditions</li></ul><p>may not behave as expected.</p><p>An XF is <strong>independent content</strong>, not a page.</p><h3>3️⃣ Expecting Frontend JavaScript to “Just Work”</h3><p>Sometimes an XF renders, but:</p><ul><li>JavaScript doesn’t run</li><li>Interactions don’t work</li></ul><p>Common reason:</p><ul><li>JS is only loaded in the page template</li><li>XF is reused elsewhere</li></ul><blockquote><em>If you use XFs, your frontend setup must support them.</em></blockquote><h3>4️⃣ XF Is Empty on Publish</h3><p>A classic XF problem 😄</p><p>Usually caused by:</p><ul><li>XF not published</li><li>Child components not published</li><li>Broken references</li></ul><p>Remember:</p><blockquote><strong><em>Experience Fragments are reference-based<br> Every referenced piece must be published.</em></strong></blockquote><h3>When Should You Use Experience Fragments?</h3><h3>✅ Good Use Cases</h3><ul><li>Shared content across many pages</li><li>Frequently updated marketing content</li><li>Centrally managed UI blocks</li></ul><h3>❌ Bad Use Cases</h3><ul><li>Page-specific, one-off content</li><li>Heavy backend-driven logic</li></ul><h3>Final Thoughts</h3><p>Experience Fragments:</p><ul><li>Reduce content duplication</li><li>Improve manageability</li><li>Become essential in large AEM projects</li></ul><p>But:</p><ul><li>Used incorrectly, they introduce complexity</li></ul><p>The best way to think about an XF is:</p><blockquote><em>“A centrally managed, reusable content block.”</em></blockquote><p>You can also check this articles 👇</p><ul><li>➤ <strong>Experience Fragments — Adobe Docs (Cloud Service)</strong><br><a href="https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/sites/authoring/fragments/experience-fragments"> https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/sites/authoring/fragments/experience-fragments</a></li><li>➤ <strong>Experience Fragments — Adobe Docs (AEM 6.5)</strong><br><a href="https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/authoring/authoring/experience-fragments"> https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/authoring/authoring/experience-fragments</a></li><li>➤ <strong>Core Component: Experience Fragment Component</strong><br> <a href="https://experienceleague.adobe.com/en/docs/experience-manager-core-components/using/wcm-components/experience-fragment">https://experienceleague.adobe.com/en/docs/experience-manager-core-components/using/wcm-components/experience-fragment</a></li><li>➤ <strong>Further Overview of Experience Fragments (Authoring + Rendering)</strong><br><a href="https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/configuring-and-extending/experience-fragments">https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/configuring-and-extending/experience-fragments</a></li></ul><p>👏 If you found this helpful, leave a clap and share it with your team.</p><h3>Contact With Me</h3><ul><li><a href="https://www.linkedin.com/in/pelinhangisi/">LinkedIn</a></li><li><a href="https://github.com/pelinhangisi">Github</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1f355497d4f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Building a CMS Approval Flow in AEM]]></title>
            <link>https://medium.com/@pelinhangisi/building-a-cms-approval-flow-in-aem-cbe1bbfb657f?source=rss-d051be460c83------2</link>
            <guid isPermaLink="false">https://medium.com/p/cbe1bbfb657f</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[aem-architect]]></category>
            <category><![CDATA[aem]]></category>
            <category><![CDATA[aem-developer]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[PelinHangisi]]></dc:creator>
            <pubDate>Wed, 05 Nov 2025 18:12:24 GMT</pubDate>
            <atom:updated>2025-11-05T18:12:24.320Z</atom:updated>
            <content:encoded><![CDATA[<h3>Making Your Content Publishing Process Secure and Controlled</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WnD4tqK6zvHs6bVEcfkOCQ.png" /></figure><h3>🎯 Introduction</h3><p>Publishing a page may look like a simple click — but in reality, it’s one of the most critical moments in any content lifecycle.<br> Without a proper approval system, unreviewed or incomplete content might go live, causing brand or compliance issues.</p><p>Adobe Experience Manager (AEM) provides a robust <strong>workflow engine</strong> that allows you to define approval flows for content publishing.<br> In this guide, you’ll learn how to design an <strong>approval workflow</strong> step by step in AEM, ensuring that every piece of content passes the right checks before it’s published.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*AwvfNQ6Mw-Ktq0FC.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*ttuFmYTrVTjEDjqY" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*F5a1B5NQ9diNsfqk.jpg" /></figure><h3>🧠 1. Why an Approval Flow Matters</h3><p>✅ <strong>Content Quality:</strong> Ensures each asset or page is reviewed before publishing.</p><p>👥 <strong>Role-Based Control:</strong> Separates Authors, Reviewers, and Admins with distinct permissions.</p><p>🕒 <strong>Traceability:</strong> Tracks who approved or rejected, and when.</p><p>⚙️ <strong>Automation:</strong> Reduces manual steps and makes the process consistent.</p><p>An approval flow doesn’t slow down your team — it safeguards your content.</p><h3>🧭 2. Creating the Workflow Model</h3><p>In AEM, approval flows are implemented through <strong>Workflow Models</strong>.</p><p><strong>Steps to set up:</strong></p><ol><li>Navigate to <strong>Tools → Workflow → Models</strong> in AEM Author.</li><li>Create a new model (for example, “Content Approval Flow”).</li><li>Add these workflow steps:</li></ol><ul><li>🟢 <strong>Start</strong></li><li>👤 <strong>Participant Step (Review)</strong></li><li>⚖️ <strong>OR Split (Approve / Reject)</strong></li><li>🚀 <strong>Publish Step (if approved)</strong></li><li>📩 <strong>Notification Step (if rejected)</strong></li><li>🔚 <strong>End</strong></li></ul><p>All of this can be built using AEM’s drag-and-drop <strong>Workflow Model Editor</strong>.</p><h3>👤 3. Participant Step — Assigning Reviewers</h3><p>The Participant Step defines <em>who</em> reviews and approves the content.</p><ol><li>Add a <strong>Participant Step</strong> to your model.</li><li>In the <strong>User/Group</strong> field, assign your reviewers group (e.g., content-approvers).</li><li>Optionally, enable “Notify via email” to send approval tasks directly to inboxes.</li><li>Add a description like</li></ol><ul><li>“In this step, the reviewer checks the content and approves or rejects it.”</li></ul><p>💡 <em>Tip:</em> If you want admins to skip the approval step, you can add a <strong>Dynamic Participant Chooser</strong> (explained below).</p><h3>⚙️ 4. Admin Bypass with a Dynamic Participant Chooser</h3><p>In many enterprise setups, admin users should be able to publish directly without waiting for approval.<br> You can implement this with a <strong>Participant Chooser Class</strong> in AEM.</p><pre>package com.example.workflow;<br><br>import com.adobe.granite.workflow.exec.ParticipantStepChooser;<br>import com.adobe.granite.workflow.exec.WorkItem;<br>import com.adobe.granite.workflow.WorkflowSession;<br>import com.adobe.granite.workflow.metadata.MetaDataMap;<br><br>public class AdminBypassParticipantChooser implements ParticipantStepChooser {<br>    @Override<br>    public String getParticipant(WorkItem item,<br>                                 WorkflowSession session,<br>                                 MetaDataMap metaDataMap) {<br>        String currentUser = session.getUser().getID();<br>        if (&quot;admin&quot;.equals(currentUser)) {<br>            // Admin can skip approval and publish directly<br>            return &quot;admin&quot;;<br>        }<br>        // All other users require approval<br>        return &quot;content-approvers&quot;;<br>    }<br>}</pre><p>📍 Deploy this class under /apps/.../workflow/scripts/<br> and in the Participant Step, set <strong>Chooser Class</strong> to<br> com.example.workflow.AdminBypassParticipantChooser.</p><h3>⚖️ 5. OR Split — Approve or Reject</h3><p>After the review step, the workflow splits into two branches:</p><ul><li>✅ <strong>Approve</strong> → moves to the <strong>Publish Step</strong></li><li>❌ <strong>Reject</strong> → triggers the <strong>Notification Step</strong></li></ul><p>The <strong>OR Split</strong> node handles this decision and ensures the flow continues in the correct direction automatically.</p><h3>🚀 6. Publish Step</h3><p>Once approved, content can be published in two ways:</p><ul><li><strong>Manual Publish:</strong> Reviewer approves, and an admin publishes manually.</li><li><strong>Auto Publish:</strong> The workflow automatically activates the content after approval.</li></ul><p>Example implementation:</p><pre>public class AutoPublishProcess implements WorkflowProcess {<br>    @Override<br>    public void execute(WorkItem item,<br>                        WorkflowSession session,<br>                        MetaDataMap args) throws WorkflowException {<br>        String path = item.getWorkflowData().getPayload().toString();<br>        Replicator replicator = session.adaptTo(Replicator.class);<br>        Session jcrSession = session.adaptTo(Session.class);<br><br>        replicator.replicate(jcrSession,<br>                              ReplicationActionType.ACTIVATE,<br>                              path);<br>    }<br>}</pre><blockquote><em>💡 </em>Tip:<em> Use manual publishing for production and auto-publish for pre-prod or test environments.</em></blockquote><h3>📩 7. Reject Path — Sending Notifications</h3><p>If the content is rejected:</p><ul><li>The <strong>Notification Step</strong> (or a custom process) notifies the author.</li><li>Example message:</li></ul><p><strong>“Your content has been rejected. Please revise and resubmit.”</strong></p><ul><li>The author can make updates and re-submit for approval.</li></ul><p>Notifications can be sent via email, inbox tasks, or logs.</p><h3>🧱 8. Workflow Model Example (XML)</h3><pre>&lt;workflow-model xmlns:cq=&quot;http://www.day.com/jcr/cq/1.0&quot;&gt;<br>  &lt;step id=&quot;participant&quot; type=&quot;Participant&quot;&gt;<br>    &lt;metaData&gt;<br>      &lt;chooserClass&gt;com.example.workflow.AdminBypassParticipantChooser&lt;/chooserClass&gt;<br>      &lt;participant&gt;content-approvers&lt;/participant&gt;<br>    &lt;/metaData&gt;<br>  &lt;/step&gt;<br><br>  &lt;step id=&quot;orSplit&quot; type=&quot;ORSplit&quot;/&gt;<br>  &lt;step id=&quot;approve&quot; type=&quot;Process&quot;&gt;<br>    &lt;processClass&gt;com.example.workflow.AutoPublishProcess&lt;/processClass&gt;<br>  &lt;/step&gt;<br>  &lt;step id=&quot;reject&quot; type=&quot;Process&quot;&gt;<br>    &lt;processClass&gt;com.example.workflow.RejectNotificationProcess&lt;/processClass&gt;<br>  &lt;/step&gt;<br>&lt;/workflow-model&gt;</pre><p>This is a simplified view of the model as it appears in CRX.</p><h3>✅ Final Thoughts</h3><p>With this setup:</p><ul><li>The <strong>Author</strong> creates the content and submits it for approval.</li><li>The <strong>Reviewer</strong> checks and approves or rejects it.</li><li>The <strong>Admin</strong> can either publish directly or monitor the flow.</li><li>Notifications ensure transparency at every step.</li></ul><p>An approval flow isn’t just about permissions — it’s about maintaining <strong>content integrity</strong> and <strong>workflow discipline</strong> within your organization.</p><h3>✨ Conclusion</h3><p>When configured properly, AEM’s workflow system transforms content publishing into a <strong>structured, trackable, and secure process</strong>.<br> Publishing becomes not just a button — but a <strong>quality checkpoint</strong>.</p><p>💬</p><blockquote><em>“Publishing content isn’t just a technical action — <br> it’s a reflection of trust and responsibility.”</em></blockquote><p>👏 If you found this helpful, leave a clap and share it with your team.</p><h3>Contact With Me</h3><ul><li><a href="https://www.linkedin.com/in/pelinhangisi/">LinkedIn</a></li><li><a href="https://github.com/pelinhangisi">Github</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cbe1bbfb657f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[⚙️ Tekrar Başlamak Cesaret İster: Her Yeni Teknolojiyle Yeniden Öğrenmek]]></title>
            <link>https://medium.com/@pelinhangisi/%EF%B8%8F-tekrar-ba%C5%9Flamak-cesaret-i%CC%87ster-her-yeni-teknolojiyle-yeniden-%C3%B6%C4%9Frenmek-cbf6ae095de4?source=rss-d051be460c83------2</link>
            <guid isPermaLink="false">https://medium.com/p/cbf6ae095de4</guid>
            <category><![CDATA[keep-going]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[PelinHangisi]]></dc:creator>
            <pubDate>Mon, 20 Oct 2025 21:39:04 GMT</pubDate>
            <atom:updated>2025-10-20T21:45:47.887Z</atom:updated>
            <content:encoded><![CDATA[<h3>Her Zaman Öğrenmeye Hazır Ol: Geliştiricinin Altın Kuralı</h3><blockquote><em>“Bir yazılımcı asla gerçekten sıfırdan başlamaz — sadece versiyon günceller.”</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JuXscwc8mt9c1yz3bQ4lfQ.png" /></figure><p>Yazılım dünyasında hiçbir şey sabit kalmaz.<br>Bugün ustası olduğun framework, yarın deprecated olabilir. Dün ezbere bildiğin yapılar, bugün bambaşka bir yaklaşımla yeniden tanımlanır.</p><p>Ama bu, moral bozucu bir durum değil — tam tersine, <strong>her yeni teknoloji yeniden başlamak için bir fırsattır.</strong></p><p>Ve evet, tekrar başlamak cesaret ister.<br>Ama sıfırdan değil… deneyimle, farkındalıkla, merakla yeniden başladığında, artık bambaşka bir seviyedesindir.</p><h3>🔁 Başlamak değil, güncellenmek</h3><p>Bir yazılımcının kariyeri düz bir çizgi değildir — sürekli commit’lenen, bazen revert edilen, ama hep ilerleyen bir branch gibidir.</p><p>Yeni bir dil, framework ya da paradigma öğrenmek demek; eski alışkanlıkları sorgulamak, yeni bakış açıları kazanmak ve bazen de “bunu neden böyle yapmışım?” demektir.</p><p>Spring Boot, AEM, şimdi React…<br>Her biri aynı hedefe farklı bir yoldan gider. Ve her yeni başlangıç, seni sadece teknik olarak değil, <strong>düşünme biçimi olarak da geliştirir.</strong></p><p>Yeni bir teknolojiye başladığında dokümantasyonlar arasında kaybolmak, ilk build hatasında paniklemek, Stack Overflow sekmesini 12 kez yenilemek… çok normal.</p><p>Ama işte tam da orada büyüyorsun.<br> O anlar, sabrını değil, <strong>öğrenme kasını</strong> güçlendiriyor.</p><blockquote>“Bir yazılımcının en güçlü yönü, bildikleri değil; bilmedikleriyle kurduğu ilişkidir.”</blockquote><p>Yeniden başlamak, hatırlamakla unutmak arasında gidip gelmek gibi. Zorlayıcı, ama sonunda özgüven kazandıran bir döngü.</p><h3>🚀 Konfor alanı ≠ gelişim alanı</h3><p>Kendini fazla rahat hissediyorsan, büyük ihtimalle gelişmiyorsundur.<br>Yeni bir teknolojiye başlamak, çoğu zaman konfor alanını kırmak anlamına gelir — ama tam da o kırılma anı, <strong>en hızlı büyüdüğün andır.</strong></p><p>Yeni bir syntax, yeni bir ekosistem, yeni bir topluluk…<br>Hepsi seni biraz daha esnek, biraz daha açık fikirli yapar.</p><p>Ve bir noktada fark edersin:<br>Artık korkmuyorsun, çünkü <strong><em>öğrenmeyi öğrenmişsindir.</em></strong></p><h3>🔧 Küçük başla, sürekli ilerle</h3><p>Hiçbir framework bir gecede öğrenilmez.<br> Ama her gün 30 dakika dokümantasyon okumak, bir component yazmak, bir servisi debug etmek…<br> Hepsi birer küçük commit’tir.</p><p>Ve o küçük commit’ler, uzun vadede seni bambaşka bir seviyeye taşır.</p><blockquote><em>“Bir zamanlar HTML yazmayı bile bilmiyordum. Şimdi neden bunu öğrenemeyeyim?”</em></blockquote><p>Bu cümleyi kendine sık sık hatırlat. Çünkü öğrenme, hep o ilk satırın cesaretiyle başlar.</p><h3>✨ Sonuç</h3><p>Yazılımda “yeniden başlamak”, kaybetmek değil; <strong>güncel kalmanın doğal bedeli.</strong><br>Her yeni teknoloji, her yeni bilgi, seni bir adım daha donanımlı, bir adım daha farkında yapar.</p><p>O yüzden korkma.<br>Yeni bir dokümantasyon sekmesi açarken, bilinmezlik değil; <strong>gelişim</strong> başlıyor olabilir.</p><h3>Contact With Me</h3><ul><li><a href="https://www.linkedin.com/in/pelinhangisi/">LinkedIn</a></li><li><a href="https://github.com/pelinhangisi">Github</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cbf6ae095de4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ AEM Dispatcher Advanced: Techniques, Performance Tips, and Common Pitfalls]]></title>
            <link>https://medium.com/@pelinhangisi/aem-dispatcher-advanced-techniques-performance-tips-and-common-pitfalls-aa55c0dacecb?source=rss-d051be460c83------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa55c0dacecb</guid>
            <category><![CDATA[aem-dispatcher]]></category>
            <category><![CDATA[aem-developer]]></category>
            <category><![CDATA[dispatcher]]></category>
            <category><![CDATA[aem]]></category>
            <category><![CDATA[aem-features]]></category>
            <dc:creator><![CDATA[PelinHangisi]]></dc:creator>
            <pubDate>Tue, 30 Sep 2025 20:45:14 GMT</pubDate>
            <atom:updated>2025-09-30T21:06:05.100Z</atom:updated>
            <content:encoded><![CDATA[<p>Adobe Experience Manager (AEM) Dispatcher is not just a caching layer; it’s the security guard, accelerator, and traffic manager of your site. Without the Dispatcher, AEM sites would rely directly on publish instances, leading to <strong>high infrastructure costs</strong> and <strong>serious security vulnerabilities</strong>.</p><p>In my previous article, I introduced the basics of Dispatcher. This time, let’s go deeper into <strong>advanced configuration techniques, performance optimizations, security headers, flush strategies, load balancing, and real-world troubleshooting cases</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FRaDtBokQI1iudkCC3NUAQ.png" /></figure><h3>🔹 1. Introduction: Why Dispatcher Shouldn’t Be Underestimated</h3><p>Dispatcher is often described as a “simple caching proxy.” In reality, it’s much more:</p><ul><li><strong>Performance layer</strong> → reduces up to 80% of publish requests.</li><li><strong>Security layer</strong> → blocks unwanted endpoints before they hit AEM.</li><li><strong>Control layer</strong> → manages failover, load balancing, and cache invalidation.</li></ul><p>👉 Think of Dispatcher as the <strong>gatekeeper</strong> of every AEM project.</p><h3>🔹 2. Filter Rules: Fine-Grained Security</h3><p>Dispatcher filters define <strong>who can access what</strong> on your site.</p><h3>2.1 Rule Order</h3><ul><li>Always start with deny *.</li><li>Add specific allow rules afterwards.</li><li>End with critical denies (e.g., .json, /system).</li></ul><h3>2.2 JSON Variants</h3><ul><li>.infinity.json → dumps entire content trees, <strong>major security risk</strong>.</li><li>.1.json, .2.json → partial dumps, should also be blocked.</li><li>.tidy.json → useful for developers, dangerous in production.</li></ul><h3>2.3 Example Advanced Filter Configuration</h3><pre>/filters<br>  {<br>  # Default: block everything<br>  /0001 { /type &quot;deny&quot; /glob &quot;*&quot; }<br><br>  # Allow HTML pages<br>  /0002 { /type &quot;allow&quot; /glob &quot;/content/mysite/*.html&quot; }<br>  /0003 { /type &quot;allow&quot; /glob &quot;/content/mysite/en/*&quot; }<br><br>  # Deny JSON variants<br>  /0004 { /type &quot;deny&quot; /glob &quot;*.infinity.json&quot; }<br>  /0005 { /type &quot;deny&quot; /glob &quot;*.tidy.json&quot; }<br>  /0006 { /type &quot;deny&quot; /glob &quot;*.1.json&quot; }<br>  /0007 { /type &quot;deny&quot; /glob &quot;*.2.json&quot; }<br><br>  # Deny system endpoints<br>  /0008 { /type &quot;deny&quot; /glob &quot;/system/*&quot; }<br>  /0009 { /type &quot;deny&quot; /glob &quot;*/services/*&quot; }<br>  }</pre><p>✅ Best Practice: Deny everything first, only allow what’s necessary.</p><h3>🔹 3. Cache Management: The Heart of Performance</h3><p>Cache misconfiguration is one of the most common performance killers.</p><h3>3.1 statfileslevel</h3><ul><li>0 → all cache tied to one statfile (bad for large sites).</li><li>2 or 3 → recommended for medium/large websites.</li></ul><h3>3.2 gracePeriod</h3><ul><li>Keeps serving old cache while new cache is being generated.</li><li>Prevents blank pages during traffic spikes.</li></ul><h3>3.3 Parameter Handling</h3><ul><li>Analytics params (utm_*, gclid) → should not break cache.</li><li>Session-based params (sessionId, token) → must bypass cache.</li></ul><h3>3.4 Cache Directory Hygiene</h3><ul><li>Regularly validate invalidation rules.</li><li>Prevent oversized cache folders and redundant assets.</li></ul><h4>Example Cache Configuration</h4><pre>/cache<br>  {<br>  /docroot &quot;/var/www/html/cache&quot;<br>  /statfileslevel &quot;2&quot;<br>  /invalidate<br>    {<br>      /0001 { /glob &quot;*.html&quot; }<br>      /0002 { /glob &quot;*.json&quot; }<br>    }<br>  /allowedClients<br>    {<br>      /0001 { /glob &quot;127.0.0.1&quot; }<br>      /0002 { /glob &quot;10.0.*.*&quot; }<br>    }<br>  /gracePeriod &quot;600&quot;<br>  }</pre><h3>🔹 4. Security Headers</h3><p>Dispatcher can enforce security through HTTP response headers.</p><h3>4.1 Must-Have Headers</h3><ul><li>X-Frame-Options: SAMEORIGIN → prevents clickjacking.</li><li>Content-Security-Policy → restricts scripts, styles, and iframes.</li><li>X-Content-Type-Options: nosniff → stops MIME spoofing.</li><li>Strict-Transport-Security → forces HTTPS.</li></ul><h3>4.2 Common Mistake</h3><ul><li>Configuring headers only in AEM but <strong>not enforcing them at the Dispatcher</strong>.</li><li>CDNs or load balancers may strip headers.</li><li>Result: policies silently fail in production.</li></ul><h3>🔹 5. Load Balancing &amp; Failover</h3><p>Dispatcher distributes traffic across multiple publish instances.</p><h3>5.1 Sticky vs Stateless</h3><ul><li><strong>Sticky session</strong>: User always hits the same publish (session continuity).</li><li><strong>Stateless</strong>: User may hit any publish (better load balancing).</li></ul><h3>5.2 Health Check</h3><ul><li>Downed publishes must be detected quickly.</li><li>Tune retryDelay and failover for your SLA.</li></ul><h3>5.3 Failover Risk</h3><ul><li>Without proper cache invalidation sync → users may see inconsistent content.</li></ul><h4>Example Load Balancing Config</h4><pre>/renders<br>  {<br>  /publish1 { /hostname &quot;10.0.0.21&quot; /port &quot;4503&quot; /timeout &quot;0&quot; }<br>  /publish2 { /hostname &quot;10.0.0.22&quot; /port &quot;4503&quot; /timeout &quot;0&quot; }<br>  }</pre><h3>🔹 6. Flush &amp; Invalidation</h3><p>Keeping cache fresh is just as important as serving it fast.</p><h3>6.1 Flush Agents</h3><ul><li>Replication agents must be enabled and tested.</li><li>Most common mistake: leaving them disabled in test/stage.</li></ul><h3>6.2 CDN Integration</h3><ul><li>When using Akamai, CloudFront, etc. → invalidate both Dispatcher + CDN.</li><li>Otherwise, Dispatcher updates but CDN keeps stale cache.</li></ul><h3>6.3 Manual Flush Example</h3><pre>rm -rf /dispatcher/cache/content/mysite/*<br>touch /dispatcher/cache/.stat</pre><h3>🔹 7. Real-World Case Studies</h3><h3>Case 1: Cache Not Flushing</h3><ul><li><strong>Cause</strong>: Wrong statfileslevel.</li><li><strong>Fix</strong>: Adjust to directory structure.</li></ul><h3>Case 2: JSON Endpoint Leak</h3><ul><li><strong>Cause</strong>: .infinity.json not denied.</li><li><strong>Fix</strong>: Add deny rule in filters.</li></ul><h3>Case 3: Mobile WebView Login Failures</h3><ul><li><strong>Cause</strong>: Missing Authorization in client headers.</li><li><strong>Fix</strong>: Add it to /clientheaders.</li></ul><pre>/clientheaders<br>  {<br>  &quot;Host&quot;<br>  &quot;User-Agent&quot;<br>  &quot;Referer&quot;<br>  &quot;Authorization&quot;<br>  &quot;Cookie&quot;<br>  &quot;X-Forwarded-For&quot;<br>  }</pre><h3>Case 4: CDN Serving Old Content</h3><ul><li><strong>Cause</strong>: CDN purge not triggered after Dispatcher flush.</li><li><strong>Fix</strong>: Integrate Dispatcher flush with CDN API purge.</li></ul><h4>8.1 Logging</h4><ul><li>Temporarily set dispatcher.log to DEBUG during troubleshooting.</li><li>Look for cache-hit and cache-miss logs to analyze performance.</li></ul><h4>8.2 Monitoring Tools</h4><ul><li>Integrate Dispatcher logs with Dynatrace, Kibana, or Splunk.</li><li>Identify the most requested paths and tune filters accordingly.</li></ul><h3>🔹 9. Dispatcher Request Flow (Diagram)</h3><pre>[ User Request ]<br>        |<br>        v<br>[ Dispatcher ]<br>   |     |     \<br>   |     |      \<br>   |     |       -&gt; [Filter Rules] --&gt; (403 or 404 response)<br>   |     |<br>   |     v<br>   |  [Cache Control]<br>   |     |   \<br>   |     |    -&gt; Cache Hit -&gt; [Static Content] -&gt; User Response<br>   |     |<br>   |     v<br>   |  Cache Miss<br>   |     |<br>   v     v<br>[ Publish Instance ]<br>        |<br>        v<br> [ Response returns to Dispatcher ]<br>        |<br>        v<br> [ Written to Cache ]<br>        |<br>        v<br> [ Response to User ]</pre><h3>🔹 10. Best Practices Recap</h3><ul><li>Deny everything, allow only what’s required.</li><li>Block all .json variants in production.</li><li>Maintain separate configs per environment.</li><li>Always test Dispatcher + CDN flush together.</li><li>Monitor and log aggressively to catch anomalies.</li></ul><h3>🎯 Conclusion</h3><p>Dispatcher is the <strong>invisible hero</strong> of every AEM project. Misconfigured, it becomes the source of performance bottlenecks and security leaks. Properly tuned, it delivers:</p><ul><li>Up to <strong>70–80% reduction in publish load</strong>.</li><li>Stronger protection against data leaks and attacks.</li><li>A smooth, consistent user experience.</li></ul><p>👉 Treat Dispatcher as more than a cache: it’s your <strong>security shield and performance accelerator</strong>.</p><p>👏 If you found this helpful, leave a clap and share it with your team.</p><h3>Contact With Me</h3><ul><li><a href="https://www.linkedin.com/in/pelinhangisi/">LinkedIn</a></li><li><a href="https://github.com/pelinhangisi">Github</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa55c0dacecb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Yazılımcıların Sessiz Mücadelesi: Umut Her Zaman Yanında]]></title>
            <link>https://medium.com/@pelinhangisi/yaz%C4%B1l%C4%B1mc%C4%B1lar%C4%B1n-sessiz-m%C3%BCcadelesi-umut-her-zaman-yan%C4%B1nda-944b83176caf?source=rss-d051be460c83------2</link>
            <guid isPermaLink="false">https://medium.com/p/944b83176caf</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[jobs]]></category>
            <dc:creator><![CDATA[PelinHangisi]]></dc:creator>
            <pubDate>Mon, 22 Sep 2025 00:55:02 GMT</pubDate>
            <atom:updated>2025-09-22T00:56:25.254Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*giO4BS0pa-BIIYJi2uRhpw.png" /></figure><p>Son zamanlarda çevremde iş bulma sürecinde olan, sık sık umutsuzluğa kapılan ve “artık olmuyor” diyerek isyan eden çok fazla kişi görüyorum. Ben şu an çalışıyor olsam da, onların verdiği bu mücadelenin ne kadar zor olduğunu yakından hissediyorum. İşte bu yazıyı da tam olarak bu yüzden kaleme almak istedim: Biraz olsun destek olabilmek, bu yolda yürüyenlere “yalnız değilsiniz” diyebilmek için. 🌱</p><p>Çünkü yazılım dünyasında iş aramak bazen görünmez bir savaş gibidir. Başvurular yapılır, cevaplar beklenir, bazen hiç dönülmez… O sessizlik bile insanın kulağına bir reddediş gibi çınlar. Hele ki bu mesleği tutkuyla seçmiş, saatlerini öğrenmeye ve kendini geliştirmeye adamış kişiler için bu durum çok daha ağırdır.</p><p>Ama bil ki bu yolculukta yalnız değilsin. Bugün iş bulmakta zorlanan binlerce kişi aynı anda seninle birlikte aynı mücadelenin içinde. Ve bu, senin yetersizliğinin değil; piyasanın zorlu koşullarının, artan rekabetin ve değişen dengelerin bir sonucu.</p><h3>Görünmeyen Yük: Psikolojik Mücadele</h3><p>İş arama sürecinin en yorucu kısmı aslında reddedilmek değil, <strong>belirsizliktir</strong>. “Acaba yeterince iyi miyim?” sorusu her olumsuz dönüşle biraz daha ağır gelir. Bu da özgüveni kemiren görünmez bir savaşa dönüşür.</p><p>Ama unutma: Bu duygular yalnızca senin değil. Hepimiz bu süreçten geçiyoruz, hepimiz aynı kaygıları taşıyoruz. Ve unutmaman gereken şey şu: bugünkü çaban, yarının fırsatlarını hazırlıyor.</p><h3>Network, Torpil ve Çaban</h3><p>Evet, sektörde sık sık şu sözleri duyuyoruz: <em>“Network çok önemli.”</em> Doğru, çevre bazen kapıları hızla açabiliyor. Torpilin konuşulduğu yerler de var. Ama bu resmin tamamı değil.</p><p>Gerçek anlamda seni ileri taşıyacak olan şey, <strong>çaban ve sabrın</strong>. Her gün öğrendiğin yeni bir teknoloji, geliştirdiğin küçük bir proje, çözdüğün bir hata… Bunların hepsi görünmeyen bir yatırım. Belki bugün fark edilmiyor, ama yarın bir fırsat anında seni öne çıkaracak.</p><p>Unutma: Torpil ya da network tek başına yeterli değil. Senin emeğin, tutkuyla ortaya koyduğun çalışmalar ve öğrenme isteğin her şeyden daha güçlü bir referans. 🌱</p><h3>“Hep Tecrübe Arıyorlar” Sözü</h3><p>İlanlara bakarken gözümüze hep aynı cümle çarpıyor: <em>“En az 3 yıl, 5 yıl tecrübe.”</em> Bu durum özellikle yeni başlayanlar için moral bozucu olabiliyor. Ama şunu bil: Her şirket böyle değil. Az da olsa, yeni başlayanlara şans tanıyan, potansiyeli gören ve öğrenme isteğine değer veren yerler var.</p><p>Bu şirketler, senin çabanı devam ettirmen için uzanan bir ipin ucu gibidir. Belki sayıları çok değil, ama varlar. Ve o fırsatı yakaladığında, bugüne kadar verdiğin emek seni yukarı çekecek.</p><h3>Umudu Diri Tutmak İçin</h3><p>✨ <strong>Dayanışma</strong>: Hikayeni paylaş, başkalarının hikayelerini dinle. Bu süreçte yalnız değilsin.<br> ✨ <strong>Küçük Zaferler</strong>: Her yeni bilgi, her küçük proje, ilerlemenin işaretidir.<br> ✨ <strong>Sabır ve Süreklilik</strong>: İş bulmak kısa bir sprint değil, uzun bir maraton. Her adım, seni biraz daha yaklaştırır.</p><p>Evet, piyasa zor, rekabet çok, enflasyon da cabası… Ama yazılım hala geleceğin dili. Ve sen bu dili öğrenmek, geliştirmek ve dönüştürmek için çaba veriyorsun.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=944b83176caf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Runmodes in AEM: Secure Configuration Management from Local to Production]]></title>
            <link>https://medium.com/@pelinhangisi/runmodes-in-aem-secure-configuration-management-from-local-to-production-ce6fed2103f1?source=rss-d051be460c83------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce6fed2103f1</guid>
            <category><![CDATA[aem-developer]]></category>
            <category><![CDATA[osgi]]></category>
            <category><![CDATA[adobe-experience-manager]]></category>
            <category><![CDATA[aem]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[PelinHangisi]]></dc:creator>
            <pubDate>Tue, 16 Sep 2025 18:20:40 GMT</pubDate>
            <atom:updated>2025-09-16T18:20:40.011Z</atom:updated>
            <content:encoded><![CDATA[<p>In Adobe Experience Manager (AEM) projects, one of the most common pitfalls is having the same code behave differently across environments (local, dev, stage, prod). <strong>Runmodes</strong> are the key mechanism to solve this problem.</p><p>In this article, I’ll explain why runmodes are essential — especially in local development — how to structure OSGi configurations properly, common mistakes, and best practices for smooth environment management.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ncYiCnvGMxfSbFtmuxF4fg.png" /></figure><h3>Why Runmodes Matter</h3><ul><li><strong>Security:</strong> Prevents test keys, sandbox endpoints, and debug logs from leaking into production.</li><li><strong>Stability:</strong> Each environment runs with its own configuration (timeouts, cache, CDN, analytics etc.).</li><li><strong>Efficiency:</strong> Local setups can disable heavy services and only keep what’s necessary for development.</li><li><strong>Transparency:</strong> Configurations remain code-independent, file-based, and version-controlled.</li></ul><p>In short, a well-defined runmode ensures you don’t end up with <em>“works locally, breaks in prod”</em> scenarios.</p><h3>How Runmodes Work</h3><p>AEM loads OSGi configurations based on the <strong>active runmode set</strong>.</p><p>Example folder structure:</p><pre>/apps/my-site/config/                      # Common for all environments<br>/apps/my-site/config.dev/                  # Dev only<br>/apps/my-site/config.stage/                # Stage only<br>/apps/my-site/config.prod/                 # Prod only<br>/apps/my-site/config.author/               # Author only<br>/apps/my-site/config.publish/              # Publish only<br>/apps/my-site/config.dev.author/           # Combination: dev + author<br>/apps/my-site/config.local/                # Local development</pre><p>👉 The directory name must exactly match the active runmode set.<br> For example, if you start AEM with dev.author, it will read from config.dev.author, not from config.dev.</p><h3>Setting Runmodes in Local Development</h3><p>When starting AEM SDK/Quickstart:</p><pre>java -jar aem-author-p4502.jar -r author,local,dev</pre><p>Or via sling.options.file:</p><pre>sling.run.modes=author,local,dev</pre><p>💡 <strong>Tip:</strong> For local author instances, author,local,dev is usually enough.<br> If you’re running a publish instance locally, use publish,local,dev.</p><h3>Environment-Specific OSGi Configurations</h3><p><strong>Local/Dev (sandbox)</strong></p><pre>/apps/my-site/config.local/com.company.integration.HttpClient.cfg.json<br>{<br>  &quot;socketTimeout&quot;: 5000,<br>  &quot;connectTimeout&quot;: 3000,<br>  &quot;baseUrl&quot;: &quot;https://sandbox-api.example.com&quot;,<br>  &quot;apiKey&quot;: &quot;dev-XXXX&quot;<br>}</pre><p>Stage</p><pre>/apps/my-site/config.stage/com.company.integration.HttpClient.cfg.json<br>{<br>  &quot;socketTimeout&quot;: 7000,<br>  &quot;connectTimeout&quot;: 4000,<br>  &quot;baseUrl&quot;: &quot;https://stage-api.example.com&quot;,<br>  &quot;apiKey&quot;: &quot;stage-XXXX&quot;<br>}</pre><p>Prod</p><pre>/apps/my-site/config.prod/com.company.integration.HttpClient.cfg.json<br>{<br>  &quot;socketTimeout&quot;: 10000,<br>  &quot;connectTimeout&quot;: 6000,<br>  &quot;baseUrl&quot;: &quot;https://api.example.com&quot;,<br>  &quot;apiKey&quot;: &quot;$[secret:api/prod-key]&quot;<br>}</pre><p>✅ This way, the <strong>same codebase</strong> behaves differently in each environment, without code changes.</p><h4>Accessing Runmodes from Code (If Needed)</h4><p>Although configuration files should do most of the work, sometimes code needs to know the runmode.</p><pre>import org.apache.sling.settings.SlingSettingsService;<br><br>@Reference<br>private SlingSettingsService slingSettings;<br><br>public boolean isLocal() {<br>    return slingSettings.getRunModes().contains(&quot;local&quot;);<br>}<br><br>public boolean isProd() {<br>    return slingSettings.getRunModes().contains(&quot;prod&quot;);<br>}</pre><p>⚠️ <strong>Best practice:</strong> Keep logic in configs. Only query runmodes in code as a last resort.</p><h3>Frontend/HTL Considerations</h3><p>Don’t check runmodes directly in HTL. Instead, expose values from your model/service and pass them as attributes.</p><pre>html<br><br>&lt;div id=&quot;env-flags&quot;<br>     data-is-local=&quot;${model.isLocal}&quot;<br>     data-api-base=&quot;${model.apiBase}&quot;&gt;&lt;/div&gt;</pre><pre>js<br>const el = document.getElementById(&#39;env-flags&#39;);<br>const isLocal = el?.dataset.isLocal === &#39;true&#39;;<br>const apiBase = el?.dataset.apiBase;</pre><p>This keeps frontend logic clean and environment-aware without hardcoding conditions.</p><h3>Dispatcher and Runmodes</h3><p>Dispatcher rules (cache, headers, rewrites) may also vary by environment.</p><ul><li><strong>Prod:</strong> strict security (CSP, cookies, headers).</li><li><strong>Local/Dev:</strong> loosen restrictions for testing.</li></ul><p>Runmodes help ensure the AEM side is aligned with the dispatcher’s environment-specific settings.</p><h3>Anti-Patterns to Avoid</h3><p>❌ Hardcoding secrets/URLs in code with if (isProd) blocks.<br> ❌ Placing the same PID in multiple runmode directories (creates conflicts).<br> ❌ Connecting local dev instances to production services.<br> ❌ Using inconsistent runmode names (dev-local, localdev instead of local,dev).</p><h3>Troubleshooting Checklist</h3><ul><li><strong>Config not loaded?</strong> Make sure the folder name matches the exact runmode set (dev.author vs. author.dev).</li><li><strong>Prod calling stage URLs?</strong> Verify the instance actually started with the prod runmode.</li><li><strong>Value missing in HTL?</strong> Expose it via the model; don’t read directly in HTL.</li></ul><h3>Real-World Example</h3><blockquote><em>“When switching environments in Dispatcher, we used to update test links in code — not anymore.”</em></blockquote><p>With proper runmodes, environment links and endpoints are controlled via config files, not code.<br> Changing environment means simply activating a different runmode set. The code remains untouched.</p><h3>Final Checklist (Local Verification in 5 Minutes)</h3><ol><li>Start AEM with author,local,dev.</li><li>Check /system/console/status-slingsettings for active runmodes.</li><li>Place configs under config.local (or config.dev.author).</li><li>Ensure secrets are managed securely, not in repo.</li><li>Pass environment values to HTL/JS through models.</li><li>Confirm prod has no leftover debug logs or test links.</li></ol><h3>Conclusion</h3><p>Runmodes are the foundation of <strong>secure, efficient, and reliable environment management</strong> in AEM.<br> With proper setup in local development, you prevent surprises in production: no leaked test endpoints, no misplaced debug logs, and consistent behavior across environments.</p><p>🔑 <strong>Remember:</strong> <em>“No runmodes, more problems.”</em></p><p><a href="https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/configuring/configure-runmodes">https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/configuring/configure-runmodes</a></p><h3>Contact With Me</h3><ul><li><a href="https://www.linkedin.com/in/pelinhangisi/">LinkedIn</a></li><li><a href="https://github.com/pelinhangisi">Github</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce6fed2103f1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[✨ Full Stack Development with React + Spring Boot — Part 4: Sending Email]]></title>
            <link>https://medium.com/@pelinhangisi/full-stack-development-with-react-spring-boot-part-4-sending-email-680496396481?source=rss-d051be460c83------2</link>
            <guid isPermaLink="false">https://medium.com/p/680496396481</guid>
            <category><![CDATA[java]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[email-sender]]></category>
            <category><![CDATA[spring-boot]]></category>
            <dc:creator><![CDATA[PelinHangisi]]></dc:creator>
            <pubDate>Mon, 04 Aug 2025 20:53:12 GMT</pubDate>
            <atom:updated>2025-08-04T20:54:26.843Z</atom:updated>
            <content:encoded><![CDATA[<h3>✨ Full Stack Development with React + Spring Boot — Part 4: Sending Email</h3><p>Sending an email after user registration is a common need in most modern applications. In this article, we’ll walk through a real-world implementation of sending activation emails using Spring Boot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lIR1p62tx05nOom-GGZ7Sw.png" /></figure><h3>🔧 Key Annotations and Tools Used</h3><p>We leveraged several powerful annotations and configurations from the Spring ecosystem:</p><ul><li>@Service: Marks the class as a service layer component in Spring’s context.</li><li>@Transactional: Manages transactions across database operations. If any step fails, the entire process is rolled back.</li><li>@PostConstruct: Executes logic after the Spring bean is initialized.</li><li>@Configuration: Indicates a class that contains Spring bean definitions.</li><li>@ConfigurationProperties: Binds properties from application.properties to a POJO.</li><li>@JsonInclude: Controls which fields are included in the JSON response.</li></ul><p>Spring Validation annotations were also used to secure input:</p><ul><li>@Email, @NotBlank, @Size, @Pattern, and a custom @UniqueEmail.</li></ul><h3>🗂 Capturing User Input with a DTO</h3><p>A DTO (Data Transfer Object) is a design pattern used to transfer data between processes or layers in an application. By using a DTO, we can decouple the structure of data in our service layer from the entities or models in the database. This helps us apply validations, sanitize inputs, and map data cleanly without exposing internal representations to the client.</p><p>The frontend sends the user data to our backend as a DTO. We use a Java record for concise structure:</p><pre>public record UserCreate(<br>    @NotBlank(message = &quot;{hangisip.constraint.username.notblank}&quot;) @Size(min = 4, max = 255) String username,<br>    @NotBlank @Email @UniqueEmail String email,<br>    @Pattern(regexp = &quot;^(?=.*[a-z])(?=.*[A-Z])(?=.*\\d).*$&quot;, message = &quot;{hangisip.constraint.password.pattern}&quot;) @Size(min = 8, max = 255) String password<br>) {<br>    public User toUser() {<br>        User user = new User();<br>        user.setEmail(email);<br>        user.setUsername(username);<br>        user.setPassword(password);<br>        return user;<br>    }<br>}</pre><p>We define a password policy with @Pattern, and @UniqueEmail ensures the email isn&#39;t already registered.</p><h3>🔁 User Save and Email Logic (Transactional Management)</h3><p>We want both the user registration and email delivery to succeed together — or fail together. Hence, the logic is wrapped in a transactional block.</p><pre>@Transactional(rollbackOn = MailException.class)<br>public void save(User user) {<br>    try {<br>        user.setPassword(passwordEncoder.encode(user.getPassword()));<br>        user.setActivationToken(UUID.randomUUID().toString());<br>        userRepository.saveAndFlush(user);<br>        emailService.sendActivationEmail(user.getEmail(), user.getActivationToken());<br>    } catch (DataIntegrityViolationException ex) {<br>        throw new NotUniqueEmailException();<br>    } catch (MailException ex) {<br>        throw new ActivationNotificationException();<br>    }<br>}</pre><h3>Understanding @Transactional:</h3><ul><li>rollbackOn = MailException.class: If email delivery fails, we rollback the DB operation as well.</li><li>Optional parameters like:</li><li>readOnly: True if no data is being modified.</li><li>propagation: Controls how nested transactions behave.</li><li>isolation: Defines how transaction visibility works.</li><li>timeout: Limits transaction lifespan.</li></ul><h3>Why saveAndFlush()?</h3><p>Calling saveAndFlush() ensures that the data (like activation token) is physically written to the database before trying to send the email.</p><h3>📧 JavaMailSender Configuration in EmailService</h3><p>Email sending is a responsibility on its own and should be isolated from other business logic. By extracting it into a dedicated EmailService, we follow the Single Responsibility Principle, keeping our code modular, maintainable, and easier to test. This approach ensures each service is only responsible for one thing, making the application architecture cleaner and more scalable.</p><p>Spring’s JavaMailSender makes email handling easy. Here&#39;s our implementation:</p><pre>@Service<br>public class EmailService {<br>    JavaMailSenderImpl mailSender;<br><br>    @Autowired<br>    HangisipProperties hangisipProperties;<br><br>    @Autowired<br>    MessageSource messageSource;<br><br>    @PostConstruct<br>    public void initialize() {<br>        this.mailSender = new JavaMailSenderImpl();<br>        mailSender.setHost(hangisipProperties.getEmail().host());<br>        mailSender.setPort(hangisipProperties.getEmail().port());<br>        mailSender.setUsername(hangisipProperties.getEmail().username());<br>        mailSender.setPassword(hangisipProperties.getEmail().password());<br><br>        Properties properties = mailSender.getJavaMailProperties();<br>        properties.put(&quot;mail.smtp.starttls.enable&quot;, &quot;true&quot;);<br>    }<br><br>    String activationEmail = &quot;&quot;&quot;<br>        &lt;html&gt;<br>         &lt;head&gt;<br>            &lt;meta charset=\&quot;UTF-8\&quot;&gt;<br>         &lt;/head&gt;<br>            &lt;body&gt;<br>            &lt;h1&gt;${title}&lt;/h1&gt;<br>            &lt;a href=\&quot;${url}\&quot;&gt;${clickHere}&lt;/a&gt;<br>            &lt;/body&gt;<br>        &lt;/html&gt;<br>        &quot;&quot;&quot;;<br><br>    public void sendActivationEmail(String email, String activationToken) {<br>        var activationUrl = hangisipProperties.getClient().host() + &quot;/activation/&quot; + activationToken;<br>        var title = messageSource.getMessage(&quot;hangisip.mail.user.creted.title&quot;, null, LocaleContextHolder.getLocale());<br>        var clickHere = messageSource.getMessage(&quot;hangisip.mail.click.here&quot;, null, LocaleContextHolder.getLocale());<br><br>        var mailBody = activationEmail<br>                .replace(&quot;${url}&quot;, activationUrl)<br>                .replace(&quot;${title}&quot;, title)<br>                .replace(&quot;${clickHere}&quot;, clickHere);<br><br>        MimeMessage mimeMessage = mailSender.createMimeMessage();<br>        try {<br>            MimeMessageHelper message = new MimeMessageHelper(mimeMessage, false, &quot;UTF-8&quot;);<br>            message.setFrom(hangisipProperties.getEmail().from());<br>            message.setTo(email);<br>            message.setSubject(title);<br>            message.setText(mailBody, true);<br>        } catch (MessagingException e) {<br>            e.printStackTrace();<br>        }<br><br>        this.mailSender.send(mimeMessage);<br>    }<br>}</pre><h3>@PostConstruct</h3><p>Used to configure the mail sender right after Spring creates the bean.</p><h3>MimeMessage &amp; MimeMessageHelper</h3><p>These are used to build and send HTML email. Declaring UTF-8 is essential for language-specific characters.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yJ-CoJ8fCJenXbGz61PJCw.png" /></figure><h3>⚙️ application.properties for Environment Config</h3><pre>spring.messages.basename=messages<br>spring.messages.encoding=UTF-8<br>hangisip.email.username=...<br>hangisip.email.password=...</pre><p>We inject these into a POJO via @ConfigurationProperties:</p><pre>@Configuration<br>@ConfigurationProperties(prefix = &quot;hangisip&quot;)<br>public record HangisipProperties(...) { ... }</pre><h3>Spring Boot Configuration Processor</h3><p>The spring-boot-configuration-processor dependency enables auto-complete and metadata support in IDEs.</p><pre>&lt;dependency&gt;<br>   &lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;<br>   &lt;artifactId&gt;spring-boot-configuration-processor&lt;/artifactId&gt;<br>   &lt;scope&gt;annotationProcessor&lt;/scope&gt;<br>  &lt;/dependency&gt;</pre><h3>🌐 Internationalization Support</h3><p>Spring’s MessageSource helps deliver multilingual email content:</p><pre>var title = messageSource.getMessage(&quot;hangisip.mail.user.creted.title&quot;, null, LocaleContextHolder.getLocale());</pre><p>This retrieves the translation depending on the user’s locale, like messages_en.properties, messages_tr.properties, etc.</p><h3>🧠 Handling Errors on the Frontend (React + Axios)</h3><p>Here’s how we catch backend validation or email errors on the frontend:</p><pre>if (axiosError.response?.data) {<br>  if (axiosError.response.data.status === 400) {<br>    setErrors(axiosError.response.data.validationErrors);<br>  } else {<br>    setGeneralError(axiosError.response.data.message);<br>  }<br>} else {<br>  setGeneralError(t(&#39;genericError&#39;));<br>}</pre><p>This enables controlled UX feedback depending on error type.</p><h3>🌍 Using Ethereal for Email Testing</h3><p>During development, we don’t want to send real emails. Instead, <a href="https://ethereal.email/">Ethereal</a> provides a fake SMTP service to preview test emails safely.</p><p>This article showed how to send multilingual transactional emails using Spring Boot, along with transactional consistency and frontend error handling. Feel free to share your questions or experience in the comments! 🚀</p><h3>🔜 What’s Next?</h3><p>In the next part of our series — <br>✨ <strong>Full Stack Development with React + Spring Boot — Part 5: Account Activation</strong><br>we’ll focus on how to handle account activation from both the frontend and backend:</p><ul><li>Creating activation routes using <strong>React Router</strong></li><li>Designing the <strong>Activation Page UI</strong></li><li>Implementing token-based activation in <strong>Spring Boot</strong></li><li>Sending the activation request from <strong>React</strong></li><li>Error handling and success feedback</li></ul><p>Stay tuned for the next article to complete the full authentication flow! 🔐</p><h3>📁 Code Repository</h3><p>👉 <a href="https://github.com/pelinhangisi/springboot-react">https://github.com/pelinhangisi/springboot-react</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=680496396481" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[️ What is AEM Dispatcher? A Complete Guide for Building Secure and High-Performance Sites]]></title>
            <link>https://medium.com/@pelinhangisi/%EF%B8%8F-what-is-aem-dispatcher-a-complete-guide-for-building-secure-and-high-performance-sites-52ebc7c6ff2b?source=rss-d051be460c83------2</link>
            <guid isPermaLink="false">https://medium.com/p/52ebc7c6ff2b</guid>
            <category><![CDATA[adobe-experience-manager]]></category>
            <category><![CDATA[aem-developer]]></category>
            <category><![CDATA[aem]]></category>
            <category><![CDATA[dispatcher]]></category>
            <dc:creator><![CDATA[PelinHangisi]]></dc:creator>
            <pubDate>Wed, 16 Jul 2025 02:11:37 GMT</pubDate>
            <atom:updated>2025-07-16T02:11:37.889Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’re working with Adobe Experience Manager, you’ll inevitably encounter <strong>Dispatcher</strong>. But Dispatcher isn’t just a caching layer — it’s the invisible gatekeeper that keeps your website fast and secure.</p><p>In this article, I’ll walk you through what Dispatcher is, how it works, how to configure it, and share <strong>real production issues and lessons learned</strong> from my own experience — from beginner to intermediate level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zi66pwcHHc7v8cJTufsQlQ.png" /></figure><p>🔄 <em>AEM Dispatcher: The Gateway Between Users and AEM</em></p><pre>User Browser<br>     |<br>     v<br>+-----------------+<br>|  Dispatcher     |   ← Reverse Proxy, Cache, Filter<br>+-----------------+<br>     |<br>     v<br>+------------------+        +------------------+<br>|  Publish Server 1|        |  Publish Server 2|<br>+------------------+        +------------------+</pre><h3>🚀 What is Dispatcher?</h3><p>Dispatcher is a module that runs on Apache HTTP Server (or IIS) and sits in front of your AEM publish servers. It acts as:</p><ul><li>A <strong>reverse proxy</strong></li><li>A <strong>caching layer</strong></li><li>And a <strong>security filter</strong></li></ul><h3>Dispatcher Has Two Primary Goals:</h3><ol><li><strong>Caching:</strong> Improve performance and reduce page load times</li><li><strong>Filtering:</strong> Block access to sensitive endpoints and paths</li></ol><p>In short, every user request first hits the Dispatcher. If the content is cached, Dispatcher returns it immediately. If not, it fetches it from the AEM publish server, caches the result, and serves it.</p><h3>📁 Understanding the dispatcher.any File</h3><p>The heart of Dispatcher is the configuration file: dispatcher.any.</p><h3>Core Sections:</h3><pre>/cache<br>/filters<br>/vanity_urls<br>/farms</pre><h4>Explanation:</h4><ul><li>/cache: Defines what content should be cached</li><li>/filters: Controls which URLs are allowed or blocked</li><li>/vanity_urls: Handles vanity URL resolution</li><li>/farms: Defines AEM publish instances and routing</li></ul><h3>🔐 Security Configurations You Must Not Skip</h3><p>Dispatcher is critical not only for performance but also for <strong>security</strong>. Many vulnerabilities come from misconfigured Dispatcher rules.</p><h3>Common Security Pitfalls:</h3><ul><li>Leaving paths like /libs, /apps, /system, and /bin exposed</li><li>Allowing access to endpoints like *.json or .infinity.json</li><li>Not blocking unsafe HTTP methods (e.g., POST, PUT, DELETE)</li></ul><h3>Sample Filter Rules:</h3><pre>/filters {<br>  /0001 { /type &quot;deny&quot; /url &quot;/libs/*&quot; }<br>  /0002 { /type &quot;deny&quot; /url &quot;*.json&quot; }<br>  /0003 { /type &quot;allow&quot; /url &quot;/content/mysite/*.json&quot; }<br>  /0004 { /type &quot;allow&quot; /url &quot;/content/mysite/*&quot; }<br>}</pre><h3>⚡ Performance Settings: statfileslevel and ignoreUrlParams</h3><h3>🔁 statfileslevel</h3><p>Determines from which folder level cached content should be invalidated.</p><pre>/statfileslevel &quot;3&quot;</pre><p>This means if /content/mysite/page1/subpage1 is updated, everything under page1 will be invalidated.</p><h3>❓ ignoreUrlParams</h3><p>Use this to prevent certain query parameters (like utm_*) from affecting the cache:</p><pre>/ignoreUrlParams {<br>  /0001 { /glob &quot;*&quot; /type &quot;deny&quot; }<br>  /0002 { /glob &quot;utm_*&quot; /type &quot;allow&quot; }<br>}</pre><h3>🧪 Real-Life Dispatcher Issues and Solutions</h3><h3>💥 1. JSON Endpoint Exposure</h3><p><strong>Issue:</strong><br> Users could access full content structure via .model.json, .1.json, etc.</p><p><strong>Fix:</strong></p><ul><li>Added a deny rule for *.json requests</li><li>Only allowed specific paths with structured JSON as needed</li></ul><h3>💥 2. Cache Not Refreshing (statfileslevel Misconfiguration)</h3><p><strong>Issue:</strong><br> Updated content was not being reflected due to a low statfileslevel setting.</p><p><strong>Fix:</strong></p><ul><li>Increased statfileslevel from 2 to 3</li><li>Verified flush agent setup and cache invalidation triggers</li></ul><h3>💥 3. Author Environment Blocked</h3><p><strong>Issue:</strong><br> Global deny filters unintentionally blocked access to editor.html in the author instance.</p><p><strong>Fix:</strong></p><ul><li>Added isAuthor check via backend or JavaScript</li><li>Scoped deny rules to apply only in the publish environment</li></ul><h3>💥 4. Inconsistent Content Between Publish Instances</h3><p><strong>Issue:</strong><br> Some users saw the new version of an image, while others saw the old one.</p><p><strong>Root Cause:</strong><br> One publish server had the updated asset, while another had the old version. Dispatcher cached the asset from the outdated publish instance.</p><p><strong>Fix:</strong></p><ul><li>Ensured all publish nodes were fully synchronized (via rsync, AEM replication, or pipeline)</li><li>Implemented <strong>cache busting</strong> by appending version query strings to assets (e.g., logo.png?v=3)</li></ul><h3>💥 5. One Dispatcher Node Was Down (Failover Problem)</h3><p><strong>Issue:</strong><br> One Dispatcher node was offline, but the Apache load balancer continued routing requests to it, causing intermittent site failures.</p><p><strong>Fix:</strong></p><p>Added health check logic in Apache config:</p><pre>&lt;Proxy &quot;balancer://aem_cluster&quot;&gt;<br>  BalancerMember http://publish1.internal:4503 route=publish1<br>  BalancerMember http://publish2.internal:4503 route=publish2 status=+H<br>&lt;/Proxy&gt;</pre><p>✅ This ensured requests were only routed to healthy, active Dispatcher nodes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rNmauFcIxUU4vU4ba711fQ.png" /></figure><h3>🎯 Final Thoughts</h3><p>When properly configured, AEM Dispatcher drastically improves your website’s speed and security. But remember:</p><blockquote><em>Dispatcher is not just a configuration file — it’s an architectural discipline.</em></blockquote><p>It involves filtering, caching, infrastructure, and coordination between frontend and backend teams.</p><h3>📚 Further Resources</h3><ul><li>🔗 <a href="https://experienceleague.adobe.com/docs/experience-manager-dispatcher.html">Adobe Dispatcher Official Docs</a></li><li>🧰 <a href="https://github.com/adobe/aem-dispatcher-optimizer-tool">Dispatcher Optimizer Tool (GitHub)</a></li><li>🛡️ <a href="https://experienceleague.adobe.com/docs/experience-manager-65/administering/security/security-checklist.html">AEM Security Checklist</a></li></ul><p>👏 If you found this helpful, leave a clap and share it with your team.<br> Got Dispatcher questions or want more advanced topics? Let me know in the comments!</p><h3>Contact With Me</h3><ul><li><a href="https://www.linkedin.com/in/pelinhangisi/">LinkedIn</a></li><li><a href="https://github.com/pelinhangisi">Github</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52ebc7c6ff2b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[✨ Full Stack Development with React + Spring Boot — Part 3: Internationalization]]></title>
            <link>https://medium.com/@pelinhangisi/full-stack-development-with-react-spring-boot-part-3-internationalization-d8fc076712cf?source=rss-d051be460c83------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8fc076712cf</guid>
            <category><![CDATA[localization]]></category>
            <category><![CDATA[spring-boot]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[internalitonalization]]></category>
            <category><![CDATA[i18n]]></category>
            <dc:creator><![CDATA[PelinHangisi]]></dc:creator>
            <pubDate>Sun, 06 Jul 2025 12:05:51 GMT</pubDate>
            <atom:updated>2025-07-06T13:48:55.723Z</atom:updated>
            <content:encoded><![CDATA[<h3>✨ Full Stack Development with React + Spring Boot — Part 3: Internationalization</h3><h3>🌍 Internationalization (i18n): Building a Multilingual Application</h3><p>In the third part of our series, we’re enabling <strong>multilingual support</strong> in our application. We’ll walk through how to set up internationalization (i18n) in both the <strong>backend (Spring Boot)</strong> and the <strong>frontend (React)</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7xE7Qyoe-haXlSJngke1NQ.png" /></figure><h3>🔹 Spring Boot — Language Support</h3><p>Instead of using MessageSource, we’ve taken a simpler approach for loading localized properties using Java’s built-in ResourceBundle.</p><p>We created a utility class called Messages:</p><pre>public class Messages {<br>    public static String getMessageForLocale(String messageKey, Locale locale) {<br>        return ResourceBundle.getBundle(&quot;messages&quot;, locale).getString(messageKey);<br>    }<br>}</pre><pre>hangisip.constraint.email.notunique = E-mail in use<br>hangisip.create.user.success.message = User is created<br>hangisip.error.validation = Validation error</pre><p>This way, anywhere in your backend code, you can get a localized message like this</p><pre>String message = Messages.getMessageForLocale(&quot;greeting.message&quot;, new Locale(&quot;tr&quot;));</pre><p>The properties file should be placed under resources/ and named like messages.properties, messages_tr.properties, etc.</p><pre>hangisip.constraint.username.notblank = Username can not be blank<br>hangisip.constraint.email.notunique = E-mail in use<br>hangisip.constraint.password.pattern = Must have uppercase, lowercase letters and number</pre><h3>🔹 Validation Messages</h3><p>You can also create localized messages for validation errors using the same messages_xx.properties files and return them manually in your response:</p><pre>public Map&lt;String, String&gt; getValidationErrors() {<br>        return Collections.singletonMap(&quot;email&quot;,<br>                Messages.getMessageForLocale(&quot;hangisip.constraint.emain.notunique&quot;, LocaleContextHolder.getLocale()));<br>    }</pre><h3>🔹 What is ResourceBundle.getBundle?</h3><p>We use ResourceBundle.getBundle(&quot;messages&quot;, locale) to load the correct language file based on the Locale. This is part of the Java standard library and works well in smaller or utility-driven setups.</p><h3>🔹 Collections.singletonMap Usage</h3><p>For returning a simple response with a single key-value pair:</p><pre>return Collections.singletonMap(&quot;message&quot;, Messages.getMessageForLocale(&quot;success.message&quot;, locale));</pre><p>This keeps your controller response structure clean and minimal.</p><h3>🔸 React — Language Support with react-i18next</h3><p>On the frontend, we use the react-i18next library to handle multilingual content. We configure it using an i18n.js file:</p><pre>i18n<br>  .use(initReactI18next) // passes i18n down to react-i18next<br>  .init({<br>    // the translations<br>    // (tip move them in a JSON file and import them,<br>    // or even better, manage them via a UI: https://react.i18next.com/guides/multiple-translation-files#manage-your-translations-with-a-management-gui)<br>    resources: {<br>      en: {<br>        translation: {<br>          &quot;Welcome to React&quot;: &quot;Welcome to React and react-i18next&quot;<br>        }<br>      }<br>    },<br>    lng: &quot;en&quot;, // if you&#39;re using a language detector, do not define the lng option<br>    fallbackLng: &quot;en&quot;,<br><br>    interpolation: {<br>      escapeValue: false // react already safes from xss =&gt; https://www.i18next.com/translation-function/interpolation#unescape<br>    }<br>  });</pre><h3>📌 Documentation</h3><p>You can explore advanced usage in the official docs:</p><p><a href="https://react.i18next.com/getting-started">react-i18next documentation</a>.</p><h4>🔸 Country Flags with FlagCDN</h4><p>To show flags based on language selection, we use <a href="https://flagcdn.com/">flagcdn.com</a>:</p><pre>&lt;img<br>        src=&quot;https://flagcdn.com/24x18/tr.png&quot;<br>        role=&quot;button&quot;<br>        width=&quot;16&quot;<br>        height=&quot;12&quot;<br>        alt=&quot;Türkçe&quot;<br>        onClick={() =&gt; onSelectLanguage(&#39;tr&#39;)}&gt;&lt;/img&gt;</pre><h3>🔸 Browser Language Detection + localStorage</h3><p>We detect the browser language using navigator.language, store it in localStorage, and initialize i18n accordingly:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Il3bloFlZMWPWR9W0Ravw.png" /></figure><p>This allows users to stay in their preferred language even after refresh or relaunch.</p><h3>🧩 Bonus: Refactoring Tips</h3><p>We recommend collecting all translation keys in JSON files, organizing them by feature or module, and using useTranslation wisely for performance:</p><p>en.json:</p><pre>{<br>  &quot;signUp&quot;: &quot;Sign Up&quot;,<br>  &quot;username&quot;: &quot;Username&quot;,<br>  &quot;email&quot;: &quot;E-mail&quot;,<br>  &quot;password&quot;: &quot;Password&quot;,<br>  &quot;passwordRepeat&quot;: &quot;Password Repeat&quot;,<br>  &quot;passwordMismatch&quot;: &quot;Password mismatch&quot;,<br>  &quot;genericError&quot;: &quot;Unexpected error occured. Please try again&quot;<br>}</pre><p>tr.json</p><pre>{<br>  &quot;signUp&quot;: &quot;Kayıt Ol&quot;,<br>  &quot;username&quot;: &quot;Kullanıcı Adı&quot;,<br>  &quot;email&quot;: &quot;E-Posta&quot;,<br>  &quot;password&quot;: &quot;Şifre&quot;,<br>  &quot;passwordRepeat&quot;: &quot;Şifre Tekrarı&quot;,<br>  &quot;passwordMismatch&quot;: &quot;Şifreler eşleşmiyor.&quot;,<br>  &quot;genericError&quot;: &quot;Beklenmedik bir hata oluştu. Lütfen tekrar deneyin&quot;<br>}</pre><h3>🎯 Conclusion</h3><p>With this update, our app supports multiple languages using a custom Messages class in the backend and react-i18next on the frontend. The structure is now simpler, modular, and easier to maintain.</p><h3>In the next part of our series — <br> <strong>✨ Full Stack Development with React + Spring Boot — Part 4: Sending E-mail</strong></h3><p>We’ll dive into how to send emails using Spring Boot, covering key backend topics focused on email functionality:</p><ul><li>➡️ Sending e-mails using Spring</li><li>➡️ Managing transactional rollbacks</li><li>➡️ Solving post-transactional issues</li><li>➡️ Handling e-mail sending errors</li><li>➡️ Application-level configuration</li><li>➡️ Securing sensitive data</li><li>➡️ Working with Spring profiles</li><li>➡️ Adding i18n (language support) inside e-mail content</li></ul><p>By the end of Part 4, you’ll be able to integrate email functionality into your application with reliability, flexibility, and multilingual support.</p><p><strong>Stay tuned! 🚀</strong></p><h3>📁 Code Repository</h3><p>👉 <a href="https://github.com/pelinhangisi/springboot-react">https://github.com/pelinhangisi/springboot-react</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8fc076712cf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Neyi Arıyorsun?]]></title>
            <link>https://medium.com/@pelinhangisi/neyi-ar%C4%B1yorsun-f7b2e9988c79?source=rss-d051be460c83------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7b2e9988c79</guid>
            <category><![CDATA[farkındalık]]></category>
            <dc:creator><![CDATA[PelinHangisi]]></dc:creator>
            <pubDate>Sun, 22 Jun 2025 06:08:26 GMT</pubDate>
            <atom:updated>2025-06-22T06:22:45.511Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Öz farkındalıkla kendine yapılan bir yolculuk üzerine..</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AC3BjZ25Shh9DxcmfxjxtA.png" /></figure><p>Bazı sorular vardır, cevabını bilmezsin ama sormaktan da hiç vazgeçemezsin.<br> “Neyi arıyorum ben?”<br> Bu soru, kulağa basit bir merak gibi gelir ilk başta.<br> Ama zamanla fark edersin ki, bu bir merak değil, bir <strong>uyanış</strong> çağrısıdır.</p><h3>Şu anla mı ilgili? Yoksa geçmişle mi?</h3><p>Kimi sabahlar uyanırsın, içinde tarifsiz bir huzursuzluk.<br> Her şey yolunda gibi görünürken neden eksik hissedersin?<br> Bir işin vardır, bir çevren, bir düzenin…<br> Ama hala bir şeylerin dışındasındır.<br> <strong>Bir “sen” var içerde</strong>, tanımadığın, unuttuğun ya da hiç bakmadığın.</p><p>Şu anla mı ilgili bu eksiklik?<br> Yoksa geçmişte kalan bir “sen”in hâlâ bugüne yansıması mı?<br> Bazı duygular zamanla geçmez, sadece şekil değiştirir.<br> Ve bazı sorular zamanla anlam kazanır.</p><h3>Mesele tamamlanmak değil. Eksik olanı fark etmek.</h3><p>Bir şeylerin eksik olduğunu hissettiğimizde panik yaparız.<br> Doldurmaya çalışırız, hızla.<br> Yeni hedefler koyarız.<br> Daha çok çalışır, daha çok sever, daha çok unuturuz.<br> Ama belki de mesele dolmak değil.<br> <strong>Boşluğun ne olduğunu fark etmektir.</strong><br> Eksik olan şeye alan açmak… onu bastırmadan, anlamaya çalışmak.</p><p>Çünkü gelişmek bazen ileri gitmek değil,<br> <strong>durup kendi içine bakabilmektir.</strong><br> Zihin de böyle büyür.<br> Doyurmaya çalıştığın şeyin aslında neye ihtiyacı olduğunu anlamaya başladığında,<br> işte o zaman gerçek dönüşüm başlar.</p><h3>Kendinle karşılaşmaya hazır mısın?</h3><p>Zihninle ilişkin ne kadar sağlıklı?<br> Onu her gün neyle besliyorsun?<br> Sosyal medya akışlarıyla mı, başkalarının hayatlarıyla mı…<br> yoksa kendi iç sesinle mi?</p><p><strong>Kendini izleyebiliyor musun?</strong><br> Hangi anlarda savruluyorsun?<br> Hangi anlarda kendin gibi hissetmiyorsun?<br> Ve bunu fark ettiğinde ne yapıyorsun?</p><p>İşte <strong>öz farkındalık</strong>, tam burada başlıyor.<br> Yargılamadan, bastırmadan, değiştirmeye çalışmadan önce…<br> <strong>Sadece gözlemleyerek.</strong></p><h3>Galaksiler, yıldızlar ve… sen</h3><p>Hayatın anlamını gökyüzünde ararız çoğu zaman.<br> Yıldızlarda, gezegenlerde, evrende…<br> Ama bazen mesele ne galaksilerde ne de ayda.<br> <strong>Mesele sensin.</strong><br> Senin seçimlerin, senin yönelişlerin, senin kırılma anların.</p><p>Her gün verdiğin küçük kararlar…<br> Uyandığında yaptığın ilk hareket, kendinle kurduğun ilk cümle…<br> İşte onlar seni şekillendiriyor.<br> Ve sen bu şekillenmenin farkında mısın?</p><h3>Peki, gerçekten neyi arıyorsun?</h3><p>Belki bir “evet”,<br> belki bir “hayır”,<br> belki de geç kalmış bir “seni seviyorum”.</p><p>Ama belki de tüm bunlardan öte,<br> <strong>“Ben kimim?”</strong> sorusunun cevabını…<br> ve cevabın içinde <strong>kendinle barışmayı</strong> arıyorsun.</p><p>Çünkü bazen hayat;<br> bir yayın akışında küçük bir kesinti,<br> bir duraksama,<br> bir “şu an” anıdır.</p><p>Ve işte o anda fark edersin:<br> <strong>Sen, zaten aradığın şeysin.</strong><br> Ama kendini yeniden hatırlamak için bazen tüm bu yolculuğu yapman gerekir.</p><h3>Kapanış:</h3><p>Bu yazıyı okuyan sen,<br> belki bu sabah kendine “neden böyle hissediyorum?” diye sordun.<br> Ve cevabı hemen bulamadın.<br> Ama bu yazı, sana küçük bir hatırlatma olsun:<br> <strong>Aramak da bir yolculuktur.<br> Ve her yolculukta en önemli durak, kendinsin.</strong></p><p>Peki…<br> <strong>Sen bugün neyi arıyorsun?</strong></p><p>Xinobi — Searching For şarkısından yola çıkarak derlenmiştir..</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7b2e9988c79" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>