Project Browser Localizer

PB Localizer: Bridging the Language Barrier for Global Drupal Adoption

The PB Localizer (Project Browser Localizer) translates the core experience of the Project Browser into your native language. While the Project Browser is a fantastic decoupled tool that fetches real-time metadata from Drupal.org, that data is currently English-only. This creates a hurdle for non-English speaking site builders and clients.

PB Localizer 2.0 solves this by acting as a high-performance client for a central PB Translation Hub. It intercepts JSON-based project descriptions and overlays them with live, community-driven or AI-assisted translations. This ensures a localized, high-quality "App Store" experience for your customers, building confidence within their own site's administration.

Core Philosophy: "Language is Trust"

Research from the influential study "Can't Read, Won't Buy: Why Language Matters on Global Websites" proves that language is a pivotal factor in adoption decisions. This is especially true for the Project Browser, which serves as the primary gateway for new users to explore the Drupal ecosystem.

Originally conducted by CSA Research, this study quantified how language influences user behavior:

• Preference: 72.4% of users are more likely to engage with a product if information is available in their native language.
• Necessity: 52.4% of global users buy only at websites presented in their own language.
• Trust & Quality: 67% of consumers consider localized product information essential when making decisions.
• Value over Price: 56.2% of users value having information in their own language more than a lower price point.

Key Features & Technical Architecture

• The "Shadow API" Proxy: Transparently intercepts JSON:API requests from your site to Drupal.org and merges live metadata with translations from a Translation Hub without hacking Drupal core.
• Global Translation Hub Support: Connects to a central server (like pb.drupaltutorials.de) where modules are translated by the community and AI (Gemini/DeepL).
• Dynamic UI Localization: Uses a MutationObserver to localize hardcoded UI elements (like "X sites report using this module") directly in the Project Browser interface.
• Visual Indicators: Displays language flags on translated modules so site builders know exactly which content has been localized.
• Cache Integrity: Advanced cache isolation prevents cross-language leakage in multilingual environments.

Configuration & Setup

Once installed, PB Localizer acts as the bridge to your chosen Translation Hub.

Configuration Path:

• Settings: /admin/config/services/pb-localizer to define your Hub URL, Port, and UI display options.

Requirements

• Drupal Core: ^10.4 || ^11
• Dependency: Project Browser module
• The Gap: While Drupal Core handles interface localization (.po files), project metadata on Drupal.org remains English-only. PB Localizer provides the missing translation overlay for this dynamic data.

For Drupal CMS (Starshot), which aims for maximum user-friendliness, this localization is the key to global success by meeting users in their own language.