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

How it works

  1. 01

    Book and send access

    Book online with your ABN or NZBN. We tell you exactly what access and material we need; the clock starts once we have it.

  2. 02

    We do the work

    An experienced employee who specialises in this task works through it, and asks before anything outside the scope.

  3. 03

    Delivered with evidence

    You get everything listed on this page, with a written account of what was done.

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

Who it's for

A team with a Svelte 5 app on another component library that wants to move to Pizzeria screen by screen while feature work carries on.

Questions

How many screens fit in a day?

It depends on your screens. A screen of average size, with a form or a table and 10 to 30 old components, takes us 45 to 75 minutes including checks and screenshots, so most days reach three to six. We finish each screen before starting the next, and the pull request lists the ones we didn't reach so you can book another day.

What if Pizzeria has no match for one of our components?

The old component stays on that screen, working as before, and goes in the day's gaps log with the reason. We don't build new components during the day, so the hours you bought go on converting screens. Building the missing pieces is The Svelte Developer Day.

Can you convert a React or Vue app?

No. Moving a React or Vue app to Svelte means rewriting every component and the way it holds its state, a much bigger job than swapping a component library. If your Svelte app is still on Svelte 4 or Tailwind 3, The Svelte Developer Day can upgrade it first, and then it qualifies.

Will the converted screens look like our brand?

They take on the Pizzeria theme your app runs: a built-in theme, one you already have, or one made by The Custom Pizzeria Theme, which puts your colours, fonts and dark mode on every Pizzeria component. Colours hard-coded in your own layout stay as they are.

What happens if our app won't run?

Two working days before your day, we follow your README on a clean machine and open each screen you listed. If something fails, we tell you that day and you have until the end of the next working day to fix it. If it still fails, we move your day to a new date instead of booking a developer who can't work, and the day you bought stays valid.

Do you use AI on our code?

Only if you choose it. In AI-assisted mode our developer uses Claude on the files of the screen in hand, after blocking environment files, keys and any secret folders you name, and reads every change before committing it. In either mode we delete our copy of your code within 24 hours of each day's pull request.

Who merges the changes, and when do you work?

You merge. We never push to your main branch, and each screen is its own commit, so you can keep some and revert others. Pizzeria is open source under the MIT licence, so the copy we add to your repository is yours to keep and change. Our developers work from India, 06:00 to 14:00 or 14:00 to 22:00 India time on weekdays, and in North America only the end of the evening shift overlaps your morning.

Often booked alongside