sTask: Background Jobs and Async Workers for Evolution CMS

Once a project starts importing spreadsheets, generating reports, processing media, or synchronizing with external APIs, synchronous page requests become the wrong execution model. The user waits too long, the browser can time out, and the whole admin workflow starts feeling unreliable.

sTask matters because it addresses that problem directly for Evolution CMS. Instead of forcing every heavy operation to run inside a normal request cycle, it introduces a background-job layer designed for long-running tasks, progress tracking, worker-style execution, and operational visibility.

Why it is a meaningful ecosystem step

• it gives Evolution projects a cleaner answer for import and export workloads
• it makes media processing and external synchronization safer to run
• it opens the door to better admin UX because the interface no longer has to block on every long task

The strongest part of this update is not just the feature list. It is the direction it represents: Evolution CMS projects increasingly need serious operational tooling around asynchronous work, and packages like sTask make that possible without forcing teams to invent their own queue layer every time.

Source: Telegram post and sTask on GitHub.