phenix-ui
Nx monorepo housing all modern Angular front ends for the Phenix estate — ~35 apps (commission, VCC, dashboard, teams, copilot, theme manager, OBT, gift registry, etc.) and ~70 shared libraries.
Health score
0 to 100 across seven weighted factors; nothing is hidden. Green is 75 and above, amber 50 to 74, red below 50. How scoring works.
Facts
| Languages | typescript, javascript |
| Frameworks | Angular 20, Nx 21, NgRx 20, Jest 29, Cypress 14 |
| Runtimes | nodejs |
| Tests / CI | good / CI in place |
| Last commit | 2026-07-24 |
| Owner | Owner unknown (mapping to be curated) |
| Domain | Selling and quoting (system generated; curate in repo-owners.json to override) |
| Product area | Phenix |
| Hosted | AWS + on-prem Ships artefacts to both AWS and on-prem machines (see evidence below)
|
| Releases | 32 release pipeline(s): \commercial\accommodation\phenix-accommodation-MonoRepo; \commercial\attractions\phenix-attractions -MonoRepo; \commercial\booking-activities\phenix-booking-activities-MonoRepo; \commercial\booking-download\phenix-booking-download-MonoRepo; \commercial\carhire\phenix-carhire-ui -MonoRepo; \commercial\cruise\phenix-cruise -MonoRepo; \commercial\currency\phenix-currency-MonoRepo; \commercial\insurance\phenix-insurance-MonoRepo; \commercial\itineraries\phenix-itineraries-MonoRepo; \commercial\obt\phenix-obt-management -MonoRepo; \commercial\p2p\phenix-p2p-ui -MonoRepo; \commercial\reviews\phenix-reviews-MonoRepo; \commercial\tc-self-service\phenix-tc-self-service-MonoRepo; \commercial\tc-web-details\phenix-tc-web-details-MonoRepo; \commercial\theme-manager\phenix-theme-manager-MonoRepo; \finance\phenix\AssitantChat - MonoRepo; \finance\phenix\phenix-commission-ui -MonoRepo; \finance\phenix\phenix-commission-ui -MonoRepo - Stealth; \finance\phenix\phenix-corporate-admin-ui MonoRepo; \finance\phenix\phenix-dashboard-ui - MonoRepo; \finance\phenix\phenix-teams-ui -MonoRepo; \finance\phenix\phenix-teams-ui -MonoRepo Stealth; \finance\phenix\phenix-vcc-MonoRepo; \finance\phenix\tc-cost-savings-MonoRepo; \finance\phenix\tc-crisis-dashboard; \finance\phenix\tc-gift-registry-MonoRepo; \finance\phenix\tc-vcc-MonoRepo; \finance\tc-storybook; \flights-stream\flights\phenix-flights-admin -MonoRepo; \flights-stream\flights\phenix-flights-ui -MonoRepo; phenix-cache-management -MonoRepo; query-management-web-component |
| Integration | rest |
| Source | Open in Azure DevOps |
Dependencies in context
Entanglement
loose No binding mechanisms apply: this system needs no untangling work.
Depends on / used by
Migration playbooks
Generated from this repo's assessment data: what is feasible, what blocks it, and the steps in order. Ratings: green means actionable now, amber means sequence other work first, red means blocked, grey means not applicable.
ZDD adoption
A long roadTechnically eligible one day, but the blockers are structural: hosted WCF or SOAP contracts that cannot run two versions at once, or heavy legacy coupling. Sequence the modernisation work first. Legacy web front end: session state and framework age make mixed-version fleets risky until state is externalised.
- Adopt the four-stage discipline from the ZDD engineering standard: pre-deployment compatibility, deployment, feature activation behind a flag, post-release cleanup.
- Make every change dual-version safe: backwards-compatible APIs (new major version for breaking wire changes), expand and contract for any schema change, and consumers tolerant of unknown fields.
- Externalise any remaining session state so users can move between nodes mid-session without disruption.
- Wrap behaviour changes in feature flags so code deploys dark and release becomes a business decision, not a deployment event.
- Route deployments through the Workflow Engine's automated drain, deploy, health-check, return cycle (the path proven by the first automated production run in mid-2026).
- Verify with area-scoped regression rather than the whole-platform cycle, and watch error rates after rollout with automated rollback on alert.
SQL Server exit
Not applicableNo SQL Server dependency is recorded for this repo. Nothing to migrate.
Containerisation
Ready to containeriseModern runtime, no hosted legacy transport: this service can follow the estate's proven container path (Dockerfile, shared pipeline template, ECS via Terraform).
- Add a Dockerfile and make the app read all configuration from environment variables and the secrets manager, never from machine-local files.
- Log to stdout and expose a health check endpoint so ECS can supervise it.
- Adopt the shared ci.yml pipeline template with the container parameters (awsRegion, containerAfterBuild, ecsTerraformRepo), which is exactly how the estate's existing AWS services deploy.
- Define the service in the Terraform repo, deploy to a non-production environment, then shift traffic and disarm the deployment-group release pipeline.
Recommended actions
No specific actions for this repo. It either needs only normal maintenance, or its work is covered by an estate-level action. See the full programme.
Assessment notes
phenix-ui
Purpose
The home of all modern Angular front-end projects for the Phenix estate. An Nx monorepo containing ~35 apps (phenix-commission-ui, phenix-vcc, phenix-dashboard, tc-teams, tc-copilot, tc-user-management, theme-manager, obt-management, tc-gift-registry, quote-and-book, tc-storybook and more) and ~70 shared libraries (components, navigation, models, analytics wrappers, per-app data-access/env/ui libs).
Tech stack
TypeScript Angular 20 with Nx 21 workspace tooling, NgRx 20 state management, Jest 29 unit tests, Cypress 14 e2e projects, and yarn. Nx "affected" builds mean a single build pipeline builds only what changed, tagging builds per app to trigger the right release.
Deployment
The heaviest release fan-out in the batch: 32 release pipelines (release_count 32) across commercial, finance and flights folders — one per app (accommodation, attractions, carhire, cruise, commission, VCC, teams, dashboard, storybook, etc.) — fed by the phenix-ui and phenix-ui tc-storybook build pipelines. YAML CI (azure-pipeline.yml) using shared InternalOSS/azure-pipelines-templates with an Nx remote-cache variable group. Newer apps (tc-copilot, tc-assistant, tc-performance, phenix-dashboard, etc.) deploy to AWS CloudFront/S3 via in-repo deploy-*.yml pipelines with terraform tfvars; older apps deploy through classic release pipelines into the IIS-hosted Phenix site. Some libraries publish as private npm packages via deploy-npm-package.yml.
Dependencies
Runtime dependencies are the Phenix backend APIs the apps call over REST: phenix-components-api (api/phenixcomponents), tc-gold-api, vcc-service (api/virtual-credit-card), location service, contact API, self-service API, phenix-user-api, phenix-thememanager, vibe-api, teams-service, tc-gift-registry, plus insurance/carhire/p2p gateways. Internal npm: @tc/web-icons. External SaaS: Google Analytics, New Relic, Pendo, Mouseflow, Maze, AnnounceKit.
Data stores
None — pure front end; all state lives behind the APIs it calls.
Integration points
Outbound REST (JSON over HTTP) to the Phenix API estate; apps are embedded in the IIS Phenix shell or served from CloudFront.
Code health
Very healthy: ~1,780 Jest spec files, per-app Cypress e2e projects, an excellent README documenting the affected-build/release workflow, and daily commits (last commit 2026-07-24). Angular/Nx versions are current.
Modernisation risks
Low as a codebase — it is the modernisation target for Phenix front ends. The structural risk is blast radius: one repo feeds 32 production release pipelines, so shared-library changes can affect many apps at once, and the release process relies on humans rejecting unwanted staging approvals. The split between AWS CloudFront deployments and legacy IIS-hosted apps means two operational models coexist.