← Projects
Localized content site

A multilingual food content site with a custom editing model.

Overview

Bibilicious needed localization for language and location without turning the site into a brittle pile of duplicated pages. We built a content-collection CMS and localized the experience across English, Tamil, and Japanese.

Locales
3
CMS
Custom
Hosting
Netlify
Locale matrix

Language, location, and content live in the same model.

Bibilicious was built around parallel localized publishing, not a single page with translated strings bolted onto it.

01 / Tamil02 / English03 / Japanese04 / Content collections05 / Localized SEO
Localization

Language and location handled as part of the content model.

The localized pages were structured around real content needs rather than a one-size-fits-all translation layer.

  • Tamil, English, Japanese
  • Localized page structure
  • Reusable templates
CMS

Content collections gave editors structure without SaaS lock-in.

The custom CMS model keeps recipes and posts organized in code-owned content while still supporting localized publishing flows.

  • Astro content collections
  • Blog and post templates
  • Netlify deployment
Stack

The operating layers we shipped.

Each layer was chosen around ownership: the public experience, the delivery constraint, and the systems that keep the build running without rented-tool drag.

AstroAstro

Primary Astro layer for the build.

NetlifyNetlify

Primary Netlify layer for the build.

i18n

Project-specific delivery layer.

Content Collections

Project-specific delivery layer.

Results

What changed.

Next project

Evo Quest

Brand and launch system ->
Next step

Build your owned system.