Technology
Notes from running a bilingual city guide on two subdomains
Source: Dev Community|
3 min read
Danang Plus is a small independent guide to Da Nang, Vietnam. It has two editions: Vietnamese at danang.plus and English at en.danang.plus. The English edition is a static site built with Astro. This post collects a few practical notes from keeping two language editions of the same guide in shape, in case they help someone planning a similar project. Why two subdomains instead of /en/ folders Both options work. Subdomains made sense here because the two editions are written separately rather than machine-translated, they have different editorial priorities, and they could be deployed independently. The trade-off is that each subdomain is treated as its own property in search tools, so you verify and monitor both, and you submit two sitemaps. Write for the reader, not as a translation A visitor reading in English usually needs different information from a local reader. An English page about renting in Da Nang has to explain deposits, contracts and temporary residence registration, things a Vietnamese reader already knows. A Vietnamese page on the same topic can skip that and go straight to neighbourhoods and prices. Treating each edition as its own content plan, rather than a one-to-one copy, produced more useful pages on both sides. Keep facts that change in one place Prices, opening hours, ticket costs and transport fares go out of date quickly. Pages such as the cost of living in Da Nang list where each figure came from and when it was checked. Keeping a "last checked" date next to volatile facts makes it obvious which pages need review first, and it tells readers how much to trust a number. Sitemaps per content type The English sitemap index splits into posts, pages, categories and authors. That makes it easy to see in a search console which type of page is or is not getting indexed, and to re-submit only the part that changed. Small things that pay off Use one canonical URL per page and stick to a trailing-slash convention. Link related guides to each other in the text, for example from a beach guide to where to stay in Da Nang, so readers and crawlers can move through the site. Keep images compressed and sized for the layout; a static build makes this easy to automate. Put the date a guide was last updated near the top. Wrapping up None of this is complicated, but writing each language edition for its own readers, and making the date on every changing fact visible, did more for the guide than any single technical trick. If you are curious how it turned out, the English edition is at en.danang.plus.