The Pizzeria Conversion Day
A Svelte developer moves your app onto Pizzeria UI one screen at a time, in your order, with before-and-after screenshots of each screen and a pull request you merge.
Your Svelte app is built on one component library and you want it on Pizzeria. Your team can't pause feature work for a migration, and one huge change that touches every screen is too risky to review.
Book a day and list your screens, most important first. One of our Svelte developers swaps each screen's old components for their Pizzeria equivalents, then tries every form and dialog in your running app to check it does what it did before. Your logic, routes and data stay as they are.
Two working days before your day, we check that your app builds and send you a table of the old components in your app with their Pizzeria matches. Where Pizzeria has no match yet, the old component stays on that screen and we tell you. Each day ends with a pull request, one commit per screen, and a count of how much of the old library is left.
What's included
A full working day of a named Svelte developer on your screens, in the order you choose
Pizzeria installed with the theme you pick on your first day, if your app doesn't have it yet, with before-and-after screenshots of five screens
Each screen's components swapped for Pizzeria ones, keeping the same fields, text, actions and data, and each control tried once in your running app
Before-and-after screenshots of every converted screen at desktop and phone widths
A table of your old components and their Pizzeria matches before the day, and a log of anything left on the old library with the reason
One pull request per day with a commit per screen, so you can undo a single screen, and your own tests and build run before and after
The old library removed once no screen uses it, and a count after each day of how much of it is left
Before you order
Have these ready so we can start the moment you order. The delivery clock only runs while we have them.
A Svelte 5 app on Tailwind CSS 4 (SvelteKit, Laravel with Inertia, or Svelte with Vite) built with shadcn-svelte, Skeleton, Flowbite-Svelte, Bits UI, Melt UI, daisyUI or your own Tailwind components
Access to your GitHub, GitLab, Bitbucket or Forgejo repository for our developer's own account, with your main branch protected
A README that gets the app installed, built and running on a new machine, plus any development settings file, using test data only
Your screens in priority order, with a login for each role that sees them
Your choice of Pizzeria theme: a built-in one, the one your app already uses, or your files from The Custom Pizzeria Theme
Someone who can answer questions during the day, and your consent if you want our developer to work with Claude, our AI coding assistant
How it works
Book it — pay the fixed price and tell us the target environment. No scoping call first.
We deliver — an experienced specialist runs our standard workflow for this exact task. You can watch progress and message them in the portal.
Hand-off — you get the deliverables, the documentation, a rollback snapshot, and a walkthrough if you want one.
Who does it
A salaried Support Resort specialist with more than ten years in the field, working from a runbook we've been refining since 2003 — supervised by senior management, never a marketplace contractor. You'll see who is assigned and can message them about this task directly in your portal.
FAQ
Ask about this task
Our assistant knows the scope document and runbook behind this service. Ask what's covered, what isn't, or whether it's the right task for your situation.
Answers come from our published scope documents. Prefer a person? Switch to the "Email us" tab — a senior manager replies personally, usually the same weekday.
Related services
The Custom Pizzeria Theme
Your brand colours and fonts on all 86 Pizzeria components, in light and dark mode, delivered as files or a pull request into your app.
The Pizzeria Build Day
A developer builds your app with Pizzeria UI from your HTML prototype and written spec, one tested screen at a time, with a pull request you merge at the end of each day.
The Svelte Developer Day
One full day of a senior Svelte developer working your list, from SvelteKit features to runes migration a batch at a time, in a framework most agencies cannot staff at all.
The Front-End Developer Day
One full day of a senior front-end developer clearing the queue nobody schedules: designs built, tablet layouts repaired, and the CSS four people have patched put back in order.
The Playwright Test Suite Day
A test automation engineer spends a day turning the flows you choose into Playwright tests, written by hand or drafted with AI, and hands you a pull request of tests that passed three runs in a row.
The Customer Portal (non-Tandemity)
A portal under your own name where each of your customers signs in, sees their own records and handles routine requests, on a phone or a desktop.