<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: AEM Configuration for muli site project (editable templates) in Adobe Experience Manager Questions</title>
    <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-configuration-for-muli-site-project-editable-templates/m-p/436260#M124539</link>
    <description>&lt;P&gt;Cool, thanks for the article. We were thinking about a solution similar to the one described here (but with templates dedicated to each brand to allow easy changes on brand level).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this also Adobe recommendation ?&lt;/P&gt;</description>
    <pubDate>Wed, 05 Jan 2022 10:55:01 GMT</pubDate>
    <dc:creator>bartek_887</dc:creator>
    <dc:date>2022-01-05T10:55:01Z</dc:date>
    <item>
      <title>AEM Configuration for muli site project (editable templates)</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-configuration-for-muli-site-project-editable-templates/m-p/436030#M124459</link>
      <description>&lt;P&gt;Hello, I am working on a AEM project with multiple sites&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;/content
   /siteA
     /pl/pl
     /pl/en

   /siteB
     /us/en
     /us/pl

   /siteX
     /../..&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The project started with the first siteA and now we are planning to migrate next siteB. For now we had one configuration `conf/project-name` with all editable templates and content fragment models. New sites will be quite similar to the siteA and I wonder what is the best practice for configuration management here?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&amp;nbsp;Should we create separate configuration for each site ?&amp;nbsp;&amp;nbsp;&lt;OL&gt;&lt;LI&gt;&lt;EM&gt;/conf/siteB, conf/siteC -&amp;nbsp;&lt;/EM&gt;this will force us to copy all policies, templates and content fragment models, we will migrate at least 20+ sites with will be a lot of duplication&lt;/LI&gt;&lt;/OL&gt;&lt;/LI&gt;&lt;LI&gt;Should we just add new templates to the existing conf&lt;OL&gt;&lt;LI&gt;only templates will be duplicated (most will be almost identical, with only difference in header and footer config, some will probably be changed a bit)&lt;/LI&gt;&lt;LI&gt;With 20+ sites we will get around 100-150 templates in our conf, policies will also grow as I imagine new sites will require some customizations there&lt;/LI&gt;&lt;/OL&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;I could not find clear instructions on how to approach this in&amp;nbsp;&lt;A href="https://experienceleague.adobe.com/docs/experience-manager-65/administering/introduction/configurations.html?lang=en" target="_blank"&gt;https://experienceleague.adobe.com/docs/experience-manager-65/administering/introduction/configurations.html?lang=en&lt;/A&gt;&amp;nbsp;- if you see some more documentation on that matter please let me know as well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your help &lt;img class="lia-deferred-image lia-image-emoji" src="https://experienceleaguecommunities.adobe.com/html/@31B4D6D7B3510763F3CBB2AAB7997408/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jan 2022 11:03:28 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-configuration-for-muli-site-project-editable-templates/m-p/436030#M124459</guid>
      <dc:creator>bartek_887</dc:creator>
      <dc:date>2022-01-03T11:03:28Z</dc:date>
    </item>
    <item>
      <title>Re: AEM Configuration for muli site project (editable templates)</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-configuration-for-muli-site-project-editable-templates/m-p/436044#M124464</link>
      <description>&lt;P&gt;&lt;LI-USER uid="17468940"&gt;&lt;/LI-USER&gt;&amp;nbsp;Please check below article if that helps:&lt;/P&gt;&lt;P&gt;&lt;A href="https://medium.com/tech-learnings/how-to-reuse-editable-template-with-multiple-sites-adobe-experience-manager-aem-a2bd9637a05" target="_blank"&gt;https://medium.com/tech-learnings/how-to-reuse-editable-template-with-multiple-sites-adobe-experience-manager-aem-a2bd9637a05&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jan 2022 13:51:55 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-configuration-for-muli-site-project-editable-templates/m-p/436044#M124464</guid>
      <dc:creator>Bhuwan_B</dc:creator>
      <dc:date>2022-01-03T13:51:55Z</dc:date>
    </item>
    <item>
      <title>Re: AEM Configuration for muli site project (editable templates)</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-configuration-for-muli-site-project-editable-templates/m-p/436260#M124539</link>
      <description>&lt;P&gt;Cool, thanks for the article. We were thinking about a solution similar to the one described here (but with templates dedicated to each brand to allow easy changes on brand level).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this also Adobe recommendation ?&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jan 2022 10:55:01 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-configuration-for-muli-site-project-editable-templates/m-p/436260#M124539</guid>
      <dc:creator>bartek_887</dc:creator>
      <dc:date>2022-01-05T10:55:01Z</dc:date>
    </item>
  </channel>
</rss>

