Payload CMS developer, UK
I build and run production sites on Payload. The largest is a charity's whole platform: five Node services with their content in Payload, edited by the charity itself.
What I do with Payload
I model the content, set up who can edit what, and build the services around it: sign-in, payments, media and email. Editors get an admin they can use without me.
In production
Solent Gay Men's Chorus is a registered charity. Everything it has online is built and run by me.
- Five Node services: main website, box office, governance, members portal and identity. Content in Payload.
- A CMS the chorus edits itself.
- One identity service for every app, with passkey sign-in and a role hierarchy.
- All five share one 2GB server behind nginx, deployed from GitHub Actions.
How I build it
Minimal technical debt. Small services with thin handlers, content as JSON, HTML rendered on the server, and nothing built on the server itself.
Questions people ask
Why Payload?
It is a headless CMS written in TypeScript that keeps its configuration in code and runs in your own Node process. Editors get a clean admin. Developers get typed JSON.
Do you work remotely?
Yes. I work with organisations anywhere in the UK, and meet face to face within about 30 miles of Portsmouth.
Work like this
-
Solent Gay Men's Chorus
Registered charity. The whole platform, built and run by me.
Tell me what you need
A few lines about the project is enough. I read every message myself. I meet people face to face within about 30 miles of Portsmouth, and work with organisations anywhere in the UK.
Or email hello@passionfruit.design, or call or WhatsApp 07385 509278.