Skip to main content
prakashd8825934
prakashd8825934
Apr 11, 2017 3:55 PM UTC
Solved

Implications of not using us/en in site structure

Is it compulsion to create site structure as 

 

/content/we.retail/us/en/Experience

 

Can we directly create

 

/content/we.retail/Experience

 

We do not have different language copy sites and  international sites. We don't intend to develop in near future.

 

How will it effect the implementation(development), if we don't consider having us/en?

 

What is the better way to remove /us/en in the urls?.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    vjetty
    vjettyAccepted solution
    Level 4
    Apr 11, 2017 4:24 PM UTC

    Hi, Prakash

    It is not mandatory to create language and country nodes in your site structure thought it's good practice to have one. It's all up to your future scope of the project. It won't have any impact on your project development. 

    You can always use rewrite rules in your dispatcher to handle your urls. You can write a rule to hide /us/en from your url. 

    Here is a really good session from adobe explaining why we need to have a good site structure while you planning your project implementation. 

    https://docs.adobe.com/ddc/en/gems/aem-6-1--translation-integration-and-best-practices.html

    Site Structure  -  3:50 min - 12:00 min (timeline)

    Hope this helps.

    Thanks,

    Vamsi

    View in thread

    3 replies

    vjetty
    vjettyAccepted solution
    Level 4
    Apr 11, 2017 4:24 PM UTC

    Hi, Prakash

    It is not mandatory to create language and country nodes in your site structure thought it's good practice to have one. It's all up to your future scope of the project. It won't have any impact on your project development. 

    You can always use rewrite rules in your dispatcher to handle your urls. You can write a rule to hide /us/en from your url. 

    Here is a really good session from adobe explaining why we need to have a good site structure while you planning your project implementation. 

    https://docs.adobe.com/ddc/en/gems/aem-6-1--translation-integration-and-best-practices.html

    Site Structure  -  3:50 min - 12:00 min (timeline)

    Hope this helps.

    Thanks,

    Vamsi

    Translate
    prakashd8825934
    prakashd8825934Author
    Apr 12, 2017 5:11 PM UTC

    Thanks Vamsi, 

    Translate
    joerghoh
    Adobe Employee
    joerghohAdobe Employee
    Adobe Employee
    Apr 12, 2017 7:33 PM UTC

    Hi,

    Although you don't want to be mult-site or support multi-language in the near future, it doesn't mean, that you will never do it. Using the proposed structure makes sense, because it is extensible. If it turns out, that you don't need, you haven't lost anything. You can always ignore the country/language nodes in your application. But in case you will ever go multi-site or multi-language, you are happy that you have the chance.

    Your content hierarchy should be well thought. And base on my experience it always pay off to have a good structure. See #2 of Davids Model [1].

    Jörg

    [1] https://wiki.apache.org/jackrabbit/DavidsModel

    Translate
      Terms & ConditionsAccessibility statement

      Loading footer...