Skip to content

04.Services

Web Engineering & Design Systems

Web applications and sites, engineered to a reference architecture rather than assembled. I settle the decisions first: release standards, and build versus buy for the component layer. Then I build it, design the interface that serves it, and set the design system that keeps your applications consistent.

~/thelogicatelier · services/web-engineering-design-systems/

Web Engineering & Design Systems

Web applications and sites, engineered to a reference architecture rather than assembled. I settle the decisions first: release standards, and build versus buy for the component layer. Then I build it, design the interface that serves it, and set the design system that keeps your applications consistent.

A web engagement starts with the decisions that outlast the code: the reference architecture, the release standards every consuming application has to meet, and whether the component layer is bought or built. Then I engineer the application or site to that architecture, design the interface that serves it, and set the design system your other teams can adopt.

Who this is for.

You have more than one web application and no shared language between them. Your front end has become the slowest part of delivery. Or you want a web build you will still be able to change in three years.

Decisions before components.

A web build lives or dies on decisions taken before the first component: the reference architecture, the release standards every consuming application has to meet, and whether the component layer is bought or built. I settle those first, in writing.

Then comes the engineering: the application or site built to that architecture, the interfaces designed as part of building it, and a design system your other teams can adopt without the consistency drifting. I build component libraries accessibility-first, so the applications that consume them start accessible rather than being retrofitted. Design work beyond the web build is not something I offer.

On the record.

For the enterprise design system at Walgreens Boots Alliance, delivered through EY, I was design authority: the reference architecture and the release standards for every consuming application, the migration to StencilJS with native Angular and React wrappers, and the Azure DevOps pipelines behind it, with a distributed team across several countries.

For a national government department I took over the architecture of a bespoke design system and was the client's technical point of contact for the twelve applications adopting it, then set the frontend architecture and design system strategy for the department's Angular estate.

At Fidelity Investments in Ireland, the shared Nx component library I architected behind a market data application cut development redundancy by about twenty per cent, at eighty per cent unit test coverage.

What the work covers.

  • Web application and site engineering
  • Frontend architecture for estates of many applications
  • Interface design that serves the build
  • Design-system strategy, architecture and governance
  • Accessibility-first component libraries
  • Release standards and the pipelines behind them

Questions.

What is settled before the first component?

The reference architecture, the release standards every consuming application has to meet, and whether the component layer is bought or built. I put those in writing first, because they are the decisions a web estate is stuck with longest.

Does this include design work beyond the build?

No. I design the interfaces as part of building the application or site, and the design system that holds them together. Design work beyond the web build is not something I offer.

How do you handle a design system several teams consume?

As an architecture with release standards, not a library maintained in spare time. On the enterprise design system for Walgreens Boots Alliance, delivered through EY, I was design authority for the reference architecture and the release standards of every consuming application, with wrappers for the frameworks those teams already used.

Is accessibility part of the build, or an audit afterwards?

Part of the build. I build component libraries accessibility-first, so the applications that consume them start accessible rather than being retrofitted.

Start with the free assessment.

Thirty minutes, free, on a video call. You bring the challenge, I tell you where I would start and what the work would take. No obligation.

The assessment is free. Anything that follows is quoted in writing before it starts.

Book the free assessment

vi.Contact

06 · contact

Talk to me.

Talk to me.

Production AI and software architecture. Based in Dubai, working with teams in the Emirates and Ireland.

I work Dubai hours, Monday to Friday, the same week you do. Dubai is three hours ahead of Dublin in summer and four in winter, so my afternoon is your morning.

I will never sell your details, for any reason, and I never send spam.

How I use your enquiry
  • Your enquiry comes to me, Abhijit Chatterjee Chattopadhyay of The Logic Atelier. The form is handled by Formspree, which passes it to my inbox and keeps a copy in my Formspree account.
  • I use it to read your enquiry and reply. If no work follows, I delete it within 12 months, and sooner whenever you ask.
  • If Google Analytics is running on your visit, it is told that an enquiry was sent, and nothing you typed.
  • To see or delete what I hold about you, email hello@thelogicatelier.com.
  • The full detail is on the privacy page.