New User
joined:Oct 23, 2019
posts: 2
votes: 0
Hey guys,
Working on a potential migration. Simple site with less than 100 pages. We basically rent studio space and wish to expand into other markets at the moment we're in the UK, USA and Germany. As the content is the same I advised a language led site architecture and not country folders be used simply because there is no difference in content being served to different regions.
So for example http://example/en/name-of-folder/name-of-page
Therefore, a single language version of each page will be optimal. English can be drafted in 'international English' to cater to all markets. Implementing multiple versions of English becomes clumsy and confusing when laying out the country selector within the navigation and menu.
Now it turns out, each homepage will have content specific to that market, so is there a way I can still use the language approach without creating language/location architecture? E.g. can the http://example/en/ still cater for USA and UK users on one page or is the /en-gb/ and /en-us/ pages a better strategy. I suppose we could create content blocks on the homepage specific to each market and link to the appropriate landing page e.g. http://example/en/uk-news-and updates etc.
Let me know your thoughts guys, keen to know if I'm on the right path or not.