bLang Is Dead for Evo 3.x: Move to sLang Instead

Some ecosystem updates are valuable precisely because they stop people from going down the wrong path. This one did that clearly: bLang is not the multilingual package to build new Evolution CMS 3.x projects around, because its repository had effectively stopped moving years earlier and belonged to the older MODX Evolution era.

The practical takeaway was simple: if a team is planning multilingual work on Evo 3.x, sLang is the package that actually belongs to that generation of the platform. That kind of clarification matters because outdated package recommendations create wasted debugging time, false bug reports, and migration frustration that should have been avoided upfront.

Why this ecosystem note matters

• it prevents teams from building on an abandoned multilingual stack
• it redirects new Evo 3.x work toward a package designed for the current architecture
• it documents an ecosystem handoff instead of leaving developers to infer it from broken installs

Source: Telegram post, bLang on GitHub, and sLang on GitHub.