veta-marketing-i18n-content

What problem does it solve?

It prevents inconsistent Spanish/English marketing experiences by ensuring that public marketing pages use correct i18n content, canonical URLs, metadata, and sitemap entries across both locales.

Core Features & Use Cases

• Bilingual marketing content (ES + EN): Maintains identical namespace/key structure in src/i18n/messages/es/marketing.json and src/i18n/messages/en/marketing.json, so no marketing strings are left untranslated.
• Locale-correct routing & navigation: Ensures links use route keys from @/i18n/routing instead of hardcoded locale slugs, keeping URL formation consistent (ES without /es, EN with /en).
• SEO-ready page configuration: Requires generateMetadata with localized canonicals, alternates.languages, and Open Graph URLs aligned with the real public routes, plus sitemap coverage for both ES and EN variants.
• Slug mapping & resilience: Adds rewrites (and 301 redirects when needed) in next.config.ts when the public slug does not match the (marketing) folder name.

Quick Start

Add or update the marketing page copy and slugs by updating both ES/EN marketing.json files, wiring the page under src/app/[locale]/(marketing)/..., and ensuring generateMetadata plus src/app/sitemap.ts include both localized URLs.