Marketing pages: LatAm-Spanish variants + locale-aware views - #151
Merged
Conversation
The 8 shipped marketing pages are long-form content the view owns (not string-
keyed per I18N.md), so each ships a translated sibling view:
- IndexController::postDispatch() renders index/<action>.<locale>.phtml when a
variant exists, else the English default. Uses renderScript() (NOT
setScriptAction — ZF1's inflector rewrites a dotted action "vibe.es"→"vibe-es").
- index/{index,vibe,agency,creators,developers,features,get-tiger,hosting}.es.phtml
— LatAm-Spanish (tú-form, idiomatic), mirroring the English structure exactly;
brand names, code, classes, hrefs unchanged.
So /es/vibe serves the Spanish page, /vibe stays English. Locales without a
variant (pt/de/fr/hi) fall through to English. Verified live on dev: all 8
/es/<page> render 200 with Spanish; /<page> stays English.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Merged
WebTigers
added a commit
that referenced
this pull request
Aug 20, 2026
- Lang switcher: add Hindi (🇮🇳 हिन्दी) — was falling back to globe + "HI". (#150) - Marketing pages: LatAm-Spanish variants (/es/vibe etc.) + locale-aware view resolution in IndexController (renders index/<action>.<locale>.phtml when present, else the English default). (#151) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Gives the shipped marketing pages Spanish versions, so
/es/vibe(etc.) serves Spanish instead of the English page.Approach
Marketing pages are long-form content the view owns — not string-keyed (per
I18N.md). So each ships a translated sibling view, resolved by locale:IndexController::postDispatch()rendersindex/<action>.<locale>.phtmlwhen a variant exists, else the English default. It usesrenderScript()rather thansetScriptAction()because ZF1's inflector rewrites a dotted action (vibe.es→vibe-es) and would 500.index,vibe,agency,creators,developers,features,get-tiger,hosting) —tú-form, idiomatic, adapted for the Spanish-speaking market (matching the 🇲🇽 flag). Each mirrors the English structure line-for-line; brand names, code, classes, and hrefs are unchanged.Locales without a variant (
pt/de/fr/hi) fall through to English — no breakage.Verified
Deployed to dev: all 8
/es/<page>render 200 with Spanish content, every/<page>stays English, home +/esboth 200. All 8.es.phtmllint-clean and structurally mirror their English source.🤖 Generated with Claude Code