Victoria James

What she covers

The guides deal with the structural side of multilingual websites: how language versions are organised, linked, announced to search engines, designed for longer and right-to-left text, formatted for each locale and kept current. They are written for people in Swiss organisations who commission, manage or build websites, rather than for translators or search specialists.

Victoria James does not write about how to translate, does not give legal advice, and does not write about search rankings. Where a guide touches on Swiss rules, such as price display or data protection, it quotes official summaries and points to an adviser.

How she works

Every technical statement in a guide is checked against the documentation that defines it: Google's own search documentation ¹, the W3C's internationalisation articles ² and accessibility guidelines ³, federal law as published on Fedlex ⁴, and the Confederation's own offices for statistics ⁵, tax ⁶ and small-business rules ⁷. A secondary or commercial source appears only where a primary one could not be used, and each source list labels it.

Figures are quoted with their source and year, and never estimated. Where a guide gives a recommendation rather than a rule, it says so and shows the reasoning. The full rules are in the editorial policy.

The guides

• Hreflang explained: what the annotation says, how to write Swiss codes such as de-CH, and why every version must list every other.
• Choosing a URL structure: language folders, subdomains or separate domains, using the trade-offs in Google's own table.
• Language switcher design: placement, naming each language in itself, why flags mislead, and markup for screen readers.
• Choosing Swiss languages: deciding between German, French, Italian, Romansh and English from tasks, figures and upkeep.
• Translation handover: freezing the source, export formats, glossary, context and review in the layout.
• Right-to-left basics: the dir attribute, mirroring, logical CSS, mixed-direction text and forms.
• Text expansion: how much translations grow, according to the figures the W3C cites, and how layouts can absorb it.
• Swiss locale formats: dates, separators, CHF prices with VAT, phone numbers and addresses across locales.
• Automatic redirects: why guessing language from IP address or browser settings causes problems, and what to do instead.
• Multilingual website costs: one-off and repeating budget lines, and how to keep each proportionate.

She also writes the explanations on the four tool pages: the hreflang planner, the locale QA checklist, the project planner and the language demo.

Why a pen name

Lingravelix is a small publication. A pen name keeps the editor's private details off the site while still giving readers a consistent byline to hold to account. It does not hide who is responsible for the content: the publisher is, and corrections and complaints go through the contact page.

The pen name is not used to suggest credentials, a team or experience that the site cannot show. The guides stand on their sources, which every reader can check.

Corrections

Found a mistake in a guide? Tell us on the contact page, naming the guide and the sentence concerned. The editorial policy explains how corrections are assessed and recorded.