ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Sulu's declarative webspace configuration lets one installation serve multiple brands and languages. Here's how portals, localizations, and fallback chains work — plus the honest trade-offs.
Weblate's REST API handles CI automation well, but token scoping, plural-form validation, and batch limits trip up first integrations. Here's what actually works.
Architecture note for integrating Weblate's Git branching and pull-request workflow into CI/CD: minimal design, trust boundaries, operational checks, failure modes, and redesign triggers with a concrete GitHub Actions example.
Weblate’s translation memory automatically suggests fuzzy matches for repetitive strings, cutting translator effort while preserving consistency.
A decision guide for engineering teams adopting self-hosted Weblate: compare direct-push vs. pull-request write-back, merge-style trade-offs, and a staging validation plan.
Step-by-step guide to configuring multi-language content structures, webspace routing, locale detection, and cache invalidation in Sulu CMS 2.x.
Stop the 'commit storm' in your Git history. Learn how to use dedicated branches and component mapping to balance continuous localization with a clean repository.
Learn how Weblate’s component linking and shared translation memory let teams translate common UI strings once and propagate them across multiple projects, reducing duplicate work while preserving per‑component controls.
weblate