Translated product copy for GoCommerce

What it does

Configuration

The module has no settings of its own — translations.New() takes none. Whether it does anything is decided by the engine’s language list, set in gocommerce.Config.

The module reads its Config struct, not the environment. The variable names are the ones the package’s own example or the reference binary uses; in your own main() you choose where each value comes from. Where a setting has a panel label, the admin’s settings drawer can hold it too, and a value typed there wins over Config.

Setting it up

1. Declare the languagesSet Languages in gocommerce.Config — en, fr and de in the package’s example — with the catalogue’s own language as the default.
2. Install the modulePass translations.New() to gocommerce.New in your own main(), as below. Neither the reference binary nor examples/store installs it.
3. Write translationsPUT /api/admin/x/translations/product/{id}/{language} with fields for title, description, seo_title or seo_description. An unknown field is refused; an empty one is dropped.
4. Ask in a languageThe storefront sends ?lang=fr or an Accept-Language header on product reads, and gets French where it exists and the stored text where it does not.

import (
	"github.com/itswadesh/gocommerce/core"
	"github.com/itswadesh/gocommerce/ext/translations"
)

app, err := gocommerce.New(gocommerce.Config{
	// DBURL, Addr and the rest of your Config, then:
	Languages: []string{"en", "fr", "de"},
}, translations.New())

How it works

• Behind the engine’s port

  The module registers as the engine’s one Translator. Every public product read — the listing, a single product, a category’s or a collection’s products — asks it for overrides in the negotiated language.

• One query per page

  A page of fifty products is one lookup, not fifty: the port is batched, and the exact tag and its primary language are fetched together.

• Failure falls back

  If a lookup fails, the engine logs it and serves the stored text rather than failing the request — a shopper would rather read the default language than an error page.

• An allow-list of fields

  Only title, description, seo_title and seo_description are accepted, and anything else is refused with the list of what is. A typo is an error, not a row that silently never applies.

• Empty means absent

  Blank fields are dropped, and a write that empties every field deletes the row — so a product never claims a language it has no text in.

• Catalogue rights

  Reading translations needs catalog.read and writing them catalog.write. In the package’s words, somebody trusted to rewrite the English title is trusted to write the French.

What it does not do

Read these before an order depends on it. No store is known to run GoCommerce in production yet, so these come from the code, not from anyone’s experience.

• Products onlyCategory and collection names are not translated — the engine has no hook for them — so a French catalogue still shows its navigation in the default language. Variants are refused too.
• No admin screenTranslations are written through the admin API. The admin has no screen for them yet.
• No flag, no quick startNeither the reference binary nor examples/store installs it. Using it means a main() of your own.
• Any tag is storedThe API accepts any language tag, but only the languages in Config.Languages are ever served; a translation into an undeclared one is stored and never read.
• Not in search or feedsThe Meilisearch index and the product feeds carry the stored text. Translated copy reaches the storefront’s product reads and nothing else.
• Nothing automaticIt stores and serves text somebody wrote. There is no machine translation.