Translate Bundle Laravel Package

Product Decisions This Supports

• Localization / i18n roadmap prioritization. Whether to ship multi-language support now, later, or never, and whether the first market expansion is a translation-only concern or a deeper content-ops problem.
• Build vs. buy for translation infrastructure. This package is a thin Symfony integration over the Weglot SaaS API — its existence is a data point that "buy" (Weglot subscription) is the default path for most teams, and the integration work itself is largely commodity plumbing rather than differentiated engineering.
• Vendor evaluation and lock-in analysis. Weglot is a paid, hosted service; the bundle sits on top. The PM decision is not really about this repo, it's about committing to a translation vendor (cost per word, page limits, SEO/URL handling, content delivery model) versus running gettext/Symfony Translator or a self-hosted pipeline.
• Use-case scoping. Useful when the product is a Symfony app with marketing/content pages that need translated variants without duplicating content in a CMS. Less useful for product-UI strings, which typically belong in Symfony's translation component with developer-managed catalogs.
• Informing maintenance/ownership decisions. An archived, near-zero-adoption wrapper is a signal that the integration layer should be either vendor-supported or owned in-house with a small adapter, not depended on as an external library.

When to Consider This Package

Consider the underlying Weglot approach (not necessarily this package) when:

• You are on Symfony and want server-side, runtime translation of rendered pages without instrumenting every template string.
• The content is dynamic/marketing-heavy and you want translated URLs (subdomains or path prefixes) handled by the vendor.
• Time-to-market for a second language matters more than per-word marginal cost or full control over translation memory.

Look elsewhere when:

• You are on Laravel. This is a Symfony bundle (weglot/translate-bundle); it will not drop into a Laravel app. The ecosystem equivalent is Weglot's own JS snippet or a community Laravel wrapper — assess those on their own merits.
• The repo being archived and ~10 stars matters to you. It does. Treat this as a reference implementation for how Weglot wires into a PHP framework, not as a dependency to install. Prefer the vendor's official SDK/integration or a small in-house adapter you control.
• Your translation needs are UI-string driven — Symfony's native translation component plus a translation-management platform (Crowdin, Lokalise, Phrase) is usually the better fit.
• You need deterministic, self-hosted, zero-vendor-cost translation — self-managed catalogs or an open-source MT pipeline will be cheaper at scale and avoid the SaaS lock-in.

How to Pitch It (Stakeholders)

To executives: We can add multi-language support to the Symfony application by integrating a hosted translation service rather than building a translation pipeline. That converts a multi-quarter engineering effort into an integration task plus a vendor subscription — faster to market, lower fixed cost, with per-word usage costs that scale with content volume. The specific open-source package in front of us is archived and barely adopted, so we should not build a dependency on it; we should evaluate the vendor directly and budget the integration as a small, owned piece of glue code.

To engineering: This is a thin Symfony bundle around Weglot — routing, locale switching, and rendering hooks. It is unmaintained and effectively unused, so treat it as documentation of the integration pattern, not a dependency. If we proceed, we own a small adapter against Weglot's current API, with tests around URL/locale handling and a defined exit path (translation catalogs remain exportable) so we are not locked in.

Bottom line for the roadmap: The capability (fast, vendor-assisted localization) is worth a spike this quarter. The package is not an adoption candidate. Decision to make: approve a vendor-evaluation spike and a bounded integration budget, or defer localization until content volume justifies it.