<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Suraj Kamdi</title>
    <description>The latest articles on DEV Community by Suraj Kamdi (@surajkamdi).</description>
    <link>https://dev.to/surajkamdi</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F225675%2Fb2a72cfe-5de5-4c23-b49d-50458a87fb79.png</url>
      <title>DEV Community: Suraj Kamdi</title>
      <link>https://dev.to/surajkamdi</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/surajkamdi"/>
    <language>en</language>
    <item>
      <title>Adding Documentation for AEM Components</title>
      <dc:creator>Suraj Kamdi</dc:creator>
      <pubDate>Tue, 22 Aug 2023 13:53:15 +0000</pubDate>
      <link>https://dev.to/surajkamdi/adding-documentation-for-aem-components-322b</link>
      <guid>https://dev.to/surajkamdi/adding-documentation-for-aem-components-322b</guid>
      <description>&lt;p&gt;Documentation is one of the important key processes when it comes to delivering any kind of software functionality. Meanwhile, It is a technical write-up that is helpful from a developer's perspective. It contains technical details like how to configure the module to show certain functionality otherwise it is difficult for the new developers to understand the whole process. Explaining the whole functionality is a time-consuming procedure instead one can share a technical document that covers actual functionality.&lt;br&gt;
Most of the time, We provide technical documentation to AEM Content Authors when it comes to authoring the component. It is helpful for AEM authors to understand &amp;amp; authoring the functionality of components. Ordinarily, we see the help (?) icon on the component dialog which contains the help path of respective component documentation. On click, it redirects to Adobe's AEM Documentation URL. But, what if we want to provide the documentation for our custom component? Most of us are not aware of how to achieve this functionality in AEM. But yes, We do have such AEM OOTB functionality for providing component documentation.&lt;/p&gt;

&lt;p&gt;Need same solution for your site then quickly jump on &lt;a href="https://medium.com/@surajkamdi/adding-documentation-for-aem-components-ab0bced28c26"&gt;https://medium.com/@surajkamdi/adding-documentation-for-aem-components-ab0bced28c26&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Adding a Color Picker to the AEM Content Fragment Model Editor</title>
      <dc:creator>Suraj Kamdi</dc:creator>
      <pubDate>Wed, 18 Nov 2020 05:09:52 +0000</pubDate>
      <link>https://dev.to/surajkamdi/adding-a-color-picker-to-the-aem-content-fragment-model-editor-3ao0</link>
      <guid>https://dev.to/surajkamdi/adding-a-color-picker-to-the-aem-content-fragment-model-editor-3ao0</guid>
      <description>&lt;p&gt;Recently, I wrote one blog related to AEM customization for content fragment models. Content Fragment Models are built with elements from various out-of-the-box data types, including single-line text, multi-line text, number, boolean (only for checkboxes), date/time, enumeration (only for static dropdown values), tags, and content reference.&lt;br&gt;
See the link here&lt;br&gt;
&lt;a href="https://blogs.perficient.com/2020/10/20/adding-a-color-picker-to-the-aem-content-fragment-model-editor/"&gt;https://blogs.perficient.com/2020/10/20/adding-a-color-picker-to-the-aem-content-fragment-model-editor/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>aem</category>
      <category>adobeexperiencemanager</category>
      <category>cq</category>
      <category>adobe</category>
    </item>
  </channel>
</rss>
