Skip to content
Contact

Platform architecture

Tools · Structure

A laptop on a slatted green bench showing the Classroom Champions teacher dashboard, greeting Lisa with an Almost the weekend message.

We plan the data models, permissions, integrations and hosting behind a platform around the work it has to carry, including the work it will take on after launch. We keep the result plain enough that any developer who comes after us can find their way around.

Planning the #HalfTheStory learning platform

The #HalfTheStory learning platform replaced one built for an earlier stage of the organization. The old system did the job for a while, but a school could not sign itself up, teachers had to be added by hand, and nobody could buy access without someone at #HalfTheStory processing it.

We kept content and people apart in the data. Sanity holds the lessons and the site, a Postgres database holds accounts, subscriptions and activity, and the application merges the two when it renders a page. That split lets a lesson stay public while a teacher's private notes stay tied to their login. Subscriptions belong to organizations rather than individuals, so a school buys a program once and its teachers inherit access.

#HalfTheStory's learning platform

Next.js and Sanity for content, Postgres for accounts and Stripe for subscriptions, deployed on Vercel.

Read the case study

#HalfTheStory learning platform onboarding step asking What's your role?, with a list of school roles beside an illustration of educators.

Legible to whoever comes next

We write architecture another developer can find their way around, with plain names and clear boundaries between the parts. We avoid clever indirection, because it tends to save a hundred lines and cost the next person a week of reading. On most of this work we are the ones maintaining it later.

#HalfTheStory learning platform onboarding step asking What grades do you teach?, with grade options beside an illustration of books and an apple.

What gets decided here

Architecture decides how the data is shaped, who can see what, which systems talk to each other and where everything runs. Those four answers constrain everything built afterwards, and changing any of them later is the expensive kind of change.

Selected work

  • 2026

    2026

    #HalfTheStory Learning Management System

    Platforms and applications, Portals and member experiences, Platform architecture, Data modelling, Interface design, Multilingual and multi-region systems, Accessible design, Performance and optimization

    Platforms and applications, Portals and member experiences, Platform architecture, Data modelling, Interface design, Multilingual and multi-region systems, Accessible design, Performance and optimization

  • 2024–2025

    2024–2025

    WealthCo Infinite CPA Decoupling

    Platform architecture, Platforms and applications

    Platform architecture, Platforms and applications