Dispatch 196
Week ↗

Starting a memorial site and tying up commerce flows

I started the day by tackling the most personal thing on the plate: a memorial site for KerryLee. It felt right to build something that actually holds space for memory rather than just another dashboard. I s…

Commits
8
Systems
5
Read
2min
Product capture

Unicorn Commander — admin dashboard.

I started the day by tackling the most personal thing on the plate: a memorial site for KerryLee. It felt right to build something that actually holds space for memory rather than just another dashboard. I spun up the kerrylee repo from scratch. The initial commit brought in the full admin structure, the gallery, and the photos. I loaded it with some images from the 70s and a toga party because that is exactly the kind of history that needs preserving. The codebase grew to over six thousand lines in one go. I then added the video and audio gallery features, fixed the rotation logic, and wired up the upload routes. It was a lot of files to touch, but seeing the admin panel come together with a proper lightbox and reordering system made the effort feel necessary. It is not just a website; it is an archive.

Meanwhile, the majiks-mobile app needed some serious housekeeping. The commerce flows were in a messy state. I spent a good chunk of time integrating the phase two ownership and payment logic. That meant rewriting album models, updating the library pages, and syncing the track details with the new remote repositories. I had to align the live API stubs across thirteen files just to make sure the creator insights and track ownership data were actually matching what the backend was sending. It was tedious work, but the library now correctly reflects who owns what and how the payments flow. I also polished the download workflows. The playlist handling was a bit clunky, so I streamlined the providers. The downloads now behave properly and the library pages reflect the changes without breaking the UI.

I did not ignore the documentation, because code without context is just noise. I updated the majiks-research-portal with extensive guides on Listmonk and Postiz integration. I wrote out the marketing automation deliverables, including the setup guides for social platforms and the content templates. If we are going to automate the outreach, we need clear instructions on how to do it. I also bumped the ops-center README to version 2.5.0 to reflect the new org features and the Q1 2026 changes. The uc-cloud docs got the same treatment, updated through March 2026 so everyone knows what the status is.

I spent a good chunk of time integrating the phase two ownership and payment logic.

Eight commits across five repositories. The memorial site is live and breathing. The mobile app finally has the commerce logic it has been missing for weeks. The docs are no longer a guessing game. I am tired but the work feels solid.

Also in the frame

Real product captures — click any to enlarge.

uc cloud
ops center
ops center