Side project · 2024–present
Zabiro
A CMS I designed and built so a small team can update its own site without a developer.
By Sabina Nordell, Senior UX/UI Designer
Start
Start page
5 sections4 active1 inactive
#1Untitled sectionHero
A large opening with a title.
#2A lighthouse puzzle for two playersHero
A large opening with a title.
#3What you getSplit
Text beside an image or video.
#4Release dateArticle
A column of text.
#5Join the playtestSplit
Text beside an image or video.
- Role
- Design and build, solo
- Tools
- Svelte 5, SvelteKit, Zabi Components, TypeScript
The problem
I had built sites for a few game teams, and every content change came back to me. A new screenshot, a changed release date, a different call to action. None of it needed a developer.
Before
- The team
- A message to me
- A code change
- A deploy
- The live site
With Zabiro
- The team
- The editor
- The live site
What shaped it
The editors aren’t developers, so nothing can require markup or a deploy. Each team must only ever see its own site.
I built it alone, in my spare time, so the scope had to stay small.
What it does
A visual section editor and drag-and-drop calls to action, so a page can be restructured without touching markup.
Every section also has move up and move down buttons, so reordering never depends on dragging.
Sign-in is by emailed link, GitHub or Google, and each editor can change only their own site.
Built on my own library
The whole interface is built from Zabi Components. When Zabiro needed something the library couldn’t do, I fixed it in the library.
Where it is now
The game teams update their own sites. Content changes no longer come back to me.
What I’d do differently
I’d watch editors use it sooner. I built what I assumed they needed before I had seen anyone try it.
I’d design light and dark mode together. I started with dark, and light mode caused problems later.
About the author
I’m Sabina Nordell, a Senior UX/UI Designer in Stockholm. Want to talk about this project, or one of your own?