A CMS UI for installs—front‑end on Vue 3 + TypeScript over a Rust back end.

Bridge

Experiential Content Management Systems

Bridge CMS UI showing the project tree structure.

Status

Shipped

Company

Downstream

Duration

18 Months

Role

Full Stack Developer

Tech Stack

Problem

We wanted to build an experiential content management system that wasn't a "kit of parts" solution. Instead, we wanted to have a software service that we could add new installations to via a JSON manifest. This would save thousands of dollars of man hours off of each project.

My role

  • Led front‑end development for Bridge UI
  • Migrated components from Vue 2 → Vue 3
  • Converted the app to TypeScript
  • Moved the build from Webpack to Vite
  • Read Rust code to map/validate data shapes in the UI

My Contributions

  • Adopted Vite for faster, simpler builds
  • Introduced strict typing to stabilize integration with the Rust API
  • Established patterns for component structure and data flow so future work stayed consistent

How it ended

Downstream was able to deliver a solution that dramatically cut back on the hours needed to prototype a project and start making money as an organization.

Notes

The project that seeded my belief that there's a market for experiential content management systems out there. Without this project, I wouldn't have worked at Gumband a little over a year later.

Project Gallery

A look at the scheduling in Bridge.
A look at some of the inputs used in Bridge
A look at the media library.

Impact

maintainability
developer-experience
performance

Have systems that need to work together? I can help map the problem and build the glue.

Talk details