Skip to content
Kedgeworks
← All workFintech2020Team

Front-end strategy across hundreds of micro-sites, and the shared component library under them.

200+micro-sites that adopted the shared component library
Radius Payment Solutions, in public figures
470,000
Organisations that Radius serves as customers
Radius, 2026
~3,000
People employed across Radius, with nearly 1,000 at its Crewe headquarters
Radius, 2026

These describe the client and the system, not our contribution. What we did is in the sections below.

The situation

Radius Payment Solutions had hundreds of front-end micro-sites, and a telematics platform with a Live Maps offering on it. We took the Head of Front End role in Crewe in 2020.

The constraint

A shared component library across hundreds of micro-sites lives or dies on adoption, and adoption is a question of what every one of those sites can agree to use.

The Live Maps offering of the telematics platform sat in the same scope.

What we did

We held the Head of Front End role and set front-end strategy for hundreds of micro-sites and a shared component library. The library was adopted across more than 200 of them.

We also worked on the Live Maps offering of the telematics platform. The stack was React, Python and AWS.

What the record supports

This was a permanent role rather than a contract, and no intermediary sits behind it.

Our record names the scope, the role and one number: the shared component library adopted across more than 200 micro-sites. It does not say what Live Maps does, what the micro-sites were for, how the library was built, who else worked on it, or what happened after 2020.

Stack
  • React
  • Python
  • AWS
Related

Working on something similar?