Inhabit (Bluetent)
An internal tool that non-technical people use to assemble websites. Rebuilt in a new stack without stopping the people who use it.
- Year2022–2023
- StackReact · TypeScript · Tailwind CSS · Vue.js
- RoleFrontend Developer, remote, six-person team
- ProductBluetent by Inhabit: direct-booking websites for vacation-rental companies
- ScopeComponent migration Vue → React + TypeScript + Tailwind; onboarding of two engineers
Challenge
two stacks, one tool everyone depends on
Bluetent builds direct-booking websites for vacation-rental companies, and its team assembles those sites in an internal dashboard. The dashboard was written in Vue while the rest of the stack was moving to React, so a six-person team was maintaining two worlds and every new hire had to learn both. The tool could not stop working for a day: people were publishing client sites with it.
Role
component by component, from designs to production
I joined as a frontend developer and took the migration of the dashboard’s components to React, TypeScript and Tailwind, working from designs to production and reviewing with the team. Halfway through, two new engineers joined and I onboarded them.
Insight
a migration is not a rewrite
The syntax was never the hard part. The hard part was the hidden assumptions in the old code: form state, validation, edge cases that existed because a real person had hit them. Each component had to be understood together with the people who used the tool every day before it could be rewritten as a typed, reusable React component. The migration became a conversation with the team as much as with the code.
Process
one simple component, then independence
I onboarded the two new engineers by pairing on one simple component each, then reviewing their independent work. Within two weeks both were shipping on their own. The same pattern worked for the migration itself: small, reviewable moves rather than a big switch.
Outcome
one stack
The team ended on one stack, with a typed component set instead of loose Vue components. The screenshots are not public, which is why this page has none. The dashboard belongs to the same family as the tools marketing teams use to publish pages: letting people compose a site without touching code is a problem I keep coming back to.
Next: Dosyp.pl