TechnicalCollectible prompt
Multiple languages with a switcher and hreflang
Make my {{tech_stack}} site available in {{languages}}. Read the existing code first and show me a short plan before changing files.
Structure:
- Each language gets its own URL path, with the default language at the root
- The correct language attribute on every page
- A switcher that names each language in itself, such as Español, without flags, keeping visitors on the same page
- Remember the visitor's choice; suggest a language from browser settings with a dismissible note, but never force a redirect
Text and content:
- Every interface string moved into one message file per language, using the i18n library that suits my stack
- Plurals and variables handled by the library, never by joining strings
- Dates, numbers and prices formatted for each locale
- For database content, propose how to store translations, falling back to the default language when one is missing
Search:
- Translated page titles, meta descriptions and share tags
- Hreflang links between every version of each page, plus x-default, and every language in the sitemap
Leave room for text that runs 30 percent longer, and support right-to-left layout if any language needs it.
When you're done, list the files changed, the strings still to translate, and anything you assumed.
Technicalnvoka.com/library/nvoka-multilingual-website-with-hreflangScan to open
Technical
Multiple languages with a switcher and hreflang
Offer your site in several languages, with language URLs, a switcher and translated SEO tags.
Curated by Nvoka
Claude CodeCodexCursor
Make it yours
Fill in the blanks and change any word. Only your copy changes, never the card.
Fill in the blanks
0 of 2 filledYour prompt
Make my {{tech_stack}} site available in {{languages}}. Read the existing code first and show me a short plan before changing files.
Structure:
- Each language gets its own URL path, with the default language at the root
- The correct language attribute on every page
- A switcher that names each language in itself, such as Español, without flags, keeping visitors on the same page
- Remember the visitor's choice; suggest a language from browser settings with a dismissible note, but never force a redirect
Text and content:
- Every interface string moved into one message file per language, using the i18n library that suits my stack
- Plurals and variables handled by the library, never by joining strings
- Dates, numbers and prices formatted for each locale
- For database content, propose how to store translations, falling back to the default language when one is missing
Search:
- Translated page titles, meta descriptions and share tags
- Hreflang links between every version of each page, plus x-default, and every language in the sitemap
Leave room for text that runs 30 percent longer, and support right-to-left layout if any language needs it.
When you're done, list the files changed, the strings still to translate, and anything you assumed.