Skip to content

a folio,
in five chapters.

Illustrated portrait of Isaac Solomon in a blue beret, looking up

Frontend developer.

Nine years building commerce storefronts, custom CMS platforms and multilingual products — for the teams who have to run them after launch.

Isaac Solomon.

01

chapter one

Selected work

Client builds and side projects — each one pushed the work further than the brief required. Storefronts, content systems and a national talent platform.

Tomorrow Makers screenshot

01 · 2026 · Philanthropy · EdTech

Tomorrow Makers

National talent platform for Godrej Foundation.

Frontend developer — the public site: pathway pages, the registration hand-off, WhatsApp onboarding and the enquiry form, on SvelteKit and Cloudflare.

Four student pathways, and an aptitude assessment in 11 languages.

SvelteKit · Tailwind · Cloudflare · EdTech

read the case study
  1. SAUT screenshot

    02 · 2019 – 2023 · EdTech · LMS

    SAUT

    Learning platform for special educators teaching children with Down syndrome.

    A 65-feature roadmap shipped across six releases, through a full framework rewrite.

    Day one to handoff across four years — frontend on V1, then product manager and the person extending the design system on V2.

  2. Godrej Foundation screenshot

    03 · 2025 – 2026 · Philanthropy

    Godrej Foundation

    Website and CMS for Godrej Foundation, the philanthropic trust of the Godrej Group, founded in 1897 — built in SvelteKit and Tailwind.

    A full corporate rebrand, with zero content migration.

    Frontend developer — the whole frontend from their designs, wired to Able.do's Apex CMS and modelled for their editors.

  3. Mivi screenshot

    04 · 2018 – 2022 · E-Commerce

    Mivi

    Custom storefront for India's first audio manufacturing brand.

    100,000+ customers and 10,000+ orders managed natively after the migration.

    Frontend developer from the first build to the platform migration — storefront UI, live cart and transactional mailers.

Illustrated portrait of Isaac Solomon holding a cup of coffee
02

chapter two

About me

The part after launch is the part I am good at: a rebrand with zero content migration, a storefront built for three to four launches a day, one product carried from day one to handoff.

I'm a frontend developer at Able.do, where I have built commerce storefronts, content systems and multilingual products since 2017 — including Mivi's storefront and a national talent platform with an aptitude assessment in eleven languages.

What a team is left with matters more to me than the launch: content models that survive a rebrand, component systems a non-technical team runs without me, and scroll-driven work that is budgeted and measured like any other asset rather than bolted on at the end.

and where the years went —

  1. 2017 — Now

    Frontend Developer @ Able.do

    Nine years building and shipping client products — e-commerce platforms, custom CMS systems, component libraries and design systems. Led the frontend for Mivi, Vibrant Living and a dozen other builds from first commit to production. Since mid-2026 the work has widened into QA automation, the processes that keep delivery accountable, and technical writing.

  2. 2016 — 2017

    Developer (Intern) @ Uncommon

    Learned the craft the honest way — code reviews, broken builds and very patient mentors. Left the internship knowing why things work, not just that they do.

Since 2026 I also take freelance work part-time, alongside Able.do.

03

chapter three

What I make

  • Storefronts where product pages, carts and mailers come from one component system, so launch days do not need a rebuild.

    • Product & category pages
    • Live carts and checkout flows
    • Transactional mailers
    Mivi — built for daily product launches
05

chapter five

Photographs

Away from the screen. Photographs from the mountains, the road, and the hours in between.

All photographs (20)

A project, or a role?

let's talk.

One address for both. Say which it is, and what you already know about the scope, the team or the timing.

about a project

Send the scope, the team and the timing — that is usually enough to start.

Email about a project

about a role

Send the team and the stack. What I did on each build is on every project above.

Email about a role