A practical series about building Laravel localization infrastructure: route cache, logical route names, Ziggy, and Inertia SSR.
While building my own Laravel localization package, I added stable logical route names and URL generation for another locale. Everything worked without caching, but after route:cache the pages still opened while URL generation stopped working. This article explains the cause and the architectural fix.
Localized URLs do not have to make the entire application depend on locale-specific route names. This article explores an approach where Laravel keeps localized URLs while frontend and application code use stable logical route names.
Ziggy can work perfectly in the browser while still failing during SSR. This article explores how to keep one consistent routing contract across Laravel, Blade, Vue and Inertia SSR without creating separate route contexts.
I thought the SEO setup was already complete: the title, description, and canonical URL were all visible in the browser. But Google Search Console showed a different picture. That is how I realized I needed Inertia SSR.
In ICanUp, Posts and Categories use one shared slug while localized URLs differ through the locale prefix and localized content. I explain why I moved away from translated slugs, how the shared-slug model simplified routing, hreflang, sitemaps, and IndexNow, and when language-specific slugs can still be the better choice.