Website Structure for Different Region

[webdev91]

We have a website with different regions (USA and India). All the content will be in English only so, no translation is needed. Also, the pages for both regions are different and they don't share the content either. Only, the look and feel are the same. In this case, what would be the best folder structure in "sites.html/content" for our website?

[Fanindra_Surat]

Hi @webdev91 - For determining the content structure, it is recommended to also factor in the end site urls. So to better assist you, please share the expected urls for India and US sites?

Else, to simply start with you can use something like below and map/modify it against other factors like End site URLs, Managing permissions, etc.

/content

-- /xxx (brand or company)

------ /en-us

------ /en-in

[Kiran_Vedantam]

HI @webdev91 

The hierarchy will always be /content/project-name/country/language/pages. So you can follow below structure:

1. /content/project-name/us/en
2. /content/project-name/in/en

Hope this helps!

Thanks,
Kiran Vedantam

[SantoshSai]

Hi @webdev91 

AEM is compatible by ensuring that they respect the split of mutable and immutable content.
In the repository /content is mutable area meaning they can be changed at runtime.

You can follow the recommended structure for your sites as we do have an best example from we-retail.

/content
  ++/brand
     ++/us/en/
     ++/in/en

Reference: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/develo...

Hope that helps!

Regards,
Santosh

[Kiran_Vedantam]

Hi @SantoshSai,

The concept of mutable and immutable content is for AEM as a cloud service. I don't think it is mentioned in the query asked.

Thanks,

Kiran Vedantam.

[Himanshu_Jain]

If there is no content rollout and content sync then create simple structure like

/content

-- /brand_name

     ----/us 

             --en

    ----/in

            --en

Thanks

[webdev91]

Thank you all for your quick response.

As many suggested the below structure, we have decided to go with it.

/content
   /brand
     /us/en/
     /in/en/

 Thank you again, everyone!

@Fanindra_Surat @SantoshSai @Kiran_Vedantam @Himanshu_Jain