Maintaining Consistency in Multi-Language Portfolios

The Problem

When managing a personal portfolio that supports multiple languages, keeping static information synchronized across translation files can become a chore. A simple change—like updating a professional title—often requires manual intervention in every locale file, increasing the risk of drift or missed updates.

The Approach

In the my-portfolio project, I recently addressed a consistency issue where the "hero" section role was out of sync across our localized configuration files. To ensure that the brand identity remains uniform regardless of the visitor's language, I standardized the role attribute globally.

Standardizing Configuration

Instead of managing translated strings directly inside component logic, we utilize a centralized configuration object. This pattern ensures that when a core identity attribute like a job title changes, it propagates automatically through the localization service.

// Example structure of our localization config
interface PortfolioConfig {
  role: string;
  bio: string;
}

const heroConfig: Record<string, PortfolioConfig> = {
  'en': {
    role: "Frontend Developer",
    bio: "Crafting digital experiences."
  },
  'fr': {
    role: "Frontend Developer",
    bio: "Création d'expériences numériques."
  }
};

By ensuring the role field remains identical across all language definitions in the schema, we eliminate discrepancies that might arise from manual editing.

Implementation Strategy

To prevent these issues from recurring, we treat identity-defining strings as "Global Constants" that are injected into the translation layer rather than translated as individual prose. This separation of concerns allows us to maintain the integrity of professional titles while still allowing for the translation of descriptive content.

Key Insight

Maintainability is just as important as extensibility in portfolio design. By centralizing core professional identity attributes, you reduce the surface area for bugs and simplify your content update workflow significantly. If you are handling multi-language support, look for the data that should remain constant and move it into a shared, non-localized configuration block.

Generated with Gitvlg.com