>soren hale — frontend developer
// Case study
Ledgerline Console
Forty internal tools moved into one console, on one design system, with one way to ship.
From merge to productionfrom 14 min→to 95 s
- Client
- Ledgerline
- Year
- 2024
- Role
- Frontend architect
- Kind
- Tooling
The problem
Ledgerline's operations teams worked in forty separate tools, each with its own login, its own table component and its own idea of a date picker.
The approach
- One shell that owns routing, auth and layout; each team ships its own module into it.
- A shared component library with typed props and visual tests on every pull request.
- A build that only rebuilds what a change touches.
The result
A merge now reaches production in 95 seconds instead of 14 minutes. New tools start from a template and are usable on day two. Six teams deleted their private UI kits within the quarter.
Built with
ReactTypeScriptModule FederationTurborepo
// Case study
Ledgerline Console
Forty internal tools moved into one console, on one design system, with one way to ship.
From merge to productionfrom 14 min→to 95 s
- Client
- Ledgerline
- Year
- 2024
- Role
- Frontend architect
- Kind
- Tooling
The problem
Ledgerline's operations teams worked in forty separate tools, each with its own login, its own table component and its own idea of a date picker.
The approach
- One shell that owns routing, auth and layout; each team ships its own module into it.
- A shared component library with typed props and visual tests on every pull request.
- A build that only rebuilds what a change touches.
The result
A merge now reaches production in 95 seconds instead of 14 minutes. New tools start from a template and are usable on day two. Six teams deleted their private UI kits within the quarter.
Built with
ReactTypeScriptModule FederationTurborepo
// Case study
Ledgerline Console
Forty internal tools moved into one console, on one design system, with one way to ship.
From merge to productionfrom 14 min→to 95 s
- Client
- Ledgerline
- Year
- 2024
- Role
- Frontend architect
- Kind
- Tooling
The problem
Ledgerline's operations teams worked in forty separate tools, each with its own login, its own table component and its own idea of a date picker.
The approach
- One shell that owns routing, auth and layout; each team ships its own module into it.
- A shared component library with typed props and visual tests on every pull request.
- A build that only rebuilds what a change touches.
The result
A merge now reaches production in 95 seconds instead of 14 minutes. New tools start from a template and are usable on day two. Six teams deleted their private UI kits within the quarter.
Built with
ReactTypeScriptModule FederationTurborepo
// Start a project
Tell me what you are building.
Three quick picks so the first reply is useful. You finish the message on the contact page.
// Start a project
Tell me what you are building.
Three quick picks so the first reply is useful. You finish the message on the contact page.
// Start a project
Tell me what you are building.
Three quick picks so the first reply is useful. You finish the message on the contact page.