01 — Context
A media and telecom operator ran several consumer services (streaming, karaoke, short-form video, set-top-box content), and each had its own separate admin tool. Operations, content and support staff had to switch between them.
02 — Challenge
The tools had to merge into a single dashboard without one large codebase, so each service's admin could still evolve on its own. The single build also had to be promoted across environments without rebuilding.
03 — Approach
One shell, independent modules
One host shell handles sign-in, layout, routing and module switching. Each service plugs in as an independent module package with its own internal layering.
Shared foundations without coupling
Shared UI and core packages (auth, API client, permissions, theming) keep modules consistent without coupling them.
One image for every environment
A small server serves the app, injects environment settings at runtime and proxies backend calls, so one container image moves from development to staging unchanged.
An auditable customer console
It includes a contact-centre customer console: look up a customer, see alerts, act inline. Contact changes are confirmed by one-time code and every action requires a written reason, for auditability.
04 — Outcome
Six service admins now run in one dashboard with single sign-on and a consistent design. A legacy content management tool was migrated into it as a module.