// S-04
LWC libraries
Shared, accessible components a team can build on.
// what it is
A shared Lightning Web Component library gives a team one set of well-built, accessible components to assemble features from, so the same UI is not rebuilt in every project.
// when a team needs it
- Teams keep rebuilding similar components.
- Existing components are complex, slow or hard to extend.
- Accessibility needs to be built in from the start.
- New developers take too long to become productive.
// what you get
- Shared, reusable Lightning Web Components built to best-practice accessibility standards.
- Rewrites of complex components, with simpler messaging and caching for faster data fetches.
- New components built from scratch, including search and lazy loading.
- Patterns the team can follow to extend the library themselves.
// where I've done this
- Hargreaves LansdownBuilt a suite of shared, reusable UI components that reduced developer training time and sped up delivery of new features.
- CertiniaRewrote the entire PSA skills flow for one of Certinia's largest customers in LWC, to best-practice accessibility standards, with reusable shared components now serving tens of thousands of users daily.
- CertiniaRewrote a complex Lightning Web Component to follow best practices, simplifying messaging channels and adding caching for faster data fetches.
- CertiniaBuilt a new LWC from scratch for contact work-history tracking, using Bryntum and Lightning components to support search and lazy loading.
// contact
Available for contract work alongside a full-time role.
UK / Remote