nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Multi country/language URL naming conventions

ivanho

I want to create the URL to cater for multiple country / languages.

http://www.mydomain.com/site/US/en/home.html
http://www.mydomain.com/site/UK/en/home.html
http://www.mydomain.com/site/CN/cn/home.html

Does anyone has any idea how do we define it in the workarea structure and what need to be set to come out with this ?

Find more posts tagged with

Comments

curiousmaverick

I'd suggest that you go for independent branch structure, where for each site you'll have a separate branch.

However if you want to have the same branch and different workareas you can do that as well by maintaining respective site specific folders outside templatedata.

Regarding seting up these urls, you deploy the site specific folders to your web servers by using OD, and then need to configure the IIS to map these folders.

Adam Stoller

I want to create the URL to cater for multiple country / languages.

http://www.mydomain.com/site/US/en/home.html
http://www.mydomain.com/site/UK/en/home.html
http://www.mydomain.com/site/CN/cn/home.html

Does anyone has any idea how do we define it in the workarea structure and what need to be set to come out with this ?

It would probably help if you provided a bit more context to the question.
Is this a question about working within TeamSite? Working within SitePublisher/LiveSite? Working with OpenDeploy? Something else?

My guess would be SitePublisher/LiveSite and/or OpenDeploy - but still, the more context you can provide about what you're trying to do, the better chance you have of getting a reasonable response.

GmDevnet

I'd suggest that you go for independent branch structure, where for each site you'll have a separate branch.

However if you want to have the same branch and different workareas you can do that as well by maintaining respective site specific folders outside templatedata.

Regarding seting up these urls, you deploy the site specific folders to your web servers by using OD, and then need to configure the IIS to map these folders.

Just wondering how you did this ?