Website Handoff · Prepared by Vivere Web Development

Mimi's Sweet Treats

Everything you own, what is in it, and how to run it yourself — on Cloudflare or anywhere else.

PreparedAugust 16, 2026

Hosting projectmimis-sweet-treats

Codebase192 files · 84.1 MB

01 What you own

This document accompanies the complete source code for Mimi's Sweet Treats. The code, the content, the images and the design are yours. Nothing here depends on Vivere Web Development continuing to be involved.

33web pages

192total files

84.1 MBcodebase size

141recorded changes

The codebase is under Git version control — 141 recorded changes on branch master. Every change is reversible, and the full history can be handed to you or to any developer you hire.

Scope of these figures. The counts above describe your website. Our own working material for this project — drafts, research, marketing files and archives, 670 files in _docs, _workspaces — sits alongside it in our system and is deliberately excluded here and from the code archive. It is not part of your site and does not need to travel with it.

You do not need permission to move it, change it, hire someone else to work on it, or host it somewhere else. Sections 5 and 6 explain exactly how.

02 What is in the codebase

The top-level folders:

Folder	Contains
`admin-hub\`	Administrative pages
`assets\`	Images, video and downloadable files used by the site
`functions\`	Server-side code — see section 4

By file type

Type	What it is	Files	Size
`.webp`	Images (modern format)	69	4.8 MB
`.html`	Web pages	33	959 KB
`.jpg`	Images	30	8.7 MB
`.js`	Browser code	27	129 KB
`.mp4`	Video	18	67.1 MB
`.txt`	Text	3	138 KB
`(none)`	Other	2	1 KB
`.heic`	Images (Apple format)	2	2.1 MB
`.css`	Styling	2	159 KB
`.png`	Images	2	29 KB

03 How it is hosted today

The site runs on Cloudflare Pages, a website hosting service. The project is named mimis-sweet-treats and answers on mimissweettreats.com.

How updates reach the site: A build step produces a dist\ folder, and only that folder is uploaded. Source files stay private.

Host-specific files

_headers — security and caching rules. Cloudflare- and Netlify-specific. Other hosts configure this differently.
_redirects — URL forwarding rules. Cloudflare and Netlify read this file; most other hosts do not.

04 Part of this site is server-side code

This site is not purely static. 26 server-side file(s) live in functions/ — _middleware.js, auth.js, closing-checklist-get.js, closing-checklist-set.js, clover.js, clover-menu-setup.js, clover-sync.js, doordash-menu.js, doordash-push.js, flavors-get.js, flavors-set.js, homebase.js, media-proxy.js, menu-get.js, menu-set.js, plaid.js, plaid-exchange.js, plaid-link.js, qb-authorize.js, qb-callback.js, quickbooks.js, replenish-list-get.js, replenish-list-set.js, staff-pins.js, summary.js, upload-pl.js. On Cloudflare these run automatically as Pages Functions.

It also uses KV storage (key-value database). That data lives in your Cloudflare account rather than in the code, so moving hosts means moving or rebuilding it too.

What this means if you move hosts: the pages will still load and look correct, but anything those functions power — order forms, quote requests, contact submissions, saved data — stops working until it is rebuilt for the new host. Netlify Functions, Vercel Functions and AWS Lambda all do the same job, but the code must be adapted. It is not a copy-and-paste move.

The simplest path is to stay on Cloudflare Pages and take ownership of the account. Section 5 covers that, and everything keeps working exactly as it does today.

05 Taking over the hosting on Cloudflare

This is the simplest option, and it keeps every feature working. Cloudflare Pages has a free tier that covers a site of this size comfortably.

Create a free Cloudflare account at dash.cloudflare.com/sign-up.
Have the project transferred to you, or create a new Pages project under your own account and upload the site. Transferring keeps the existing address and settings; a fresh project is a clean start under your own billing.
Publish the site. Install Node.js, then from inside dist\:
```
npx wrangler login
npx wrangler pages deploy dist --project-name mimis-sweet-treats
```
Cloudflare returns a one-off preview address. Check that one first — the main address can take a minute to catch up, and checking it too early shows you the old version.
Point your domain at it. In the Pages project open Custom domains and add mimissweettreats.com. Cloudflare walks you through the DNS records.
Confirm it works — load the site, click through the navigation, and submit any forms before considering the move done.

06 Moving to a different host

You are not tied to Cloudflare. Read section 4 first — the server-side features need rebuilding on any other host.

Host	Good for	What to know
Netlify	Closest equivalent	Reads `_headers` and `_redirects` the same way. Functions must be rewritten for Netlify Functions.
Vercel	Strong developer tooling	Uses its own configuration format. Functions must be rewritten for Vercel Functions.
GitHub Pages	Free and simple, static only	Not suitable — cannot run this site’s server-side features.
Traditional web hosting	Bundling with existing services	Upload the files over FTP. Server-side features will not work without a rebuild.

Whatever you choose, keep a copy of the code somewhere you control — a private GitHub repository or a backup drive. The host is replaceable. The code is the asset.

07 Your domain

Your site answers on mimissweettreats.com. The domain is registered and paid for separately from the hosting — they are two different things, and you can change one without touching the other.

Confirm you are the registered owner. Whoever controls the domain registration controls the address. If it is not currently in an account you own, have it transferred before anything else — it is the one piece that is genuinely hard to replace.

08 Keeping it running

Nothing expires on its own. The site keeps serving without maintenance. A static site does not need the constant security patching a WordPress install does.
Renew your domain. This is the one thing that will take the site offline if it lapses. Turn on auto-renew.
Keep a backup of the code somewhere that is not the hosting account.
Editing content means editing HTML files. Any web developer can do it — there is no proprietary system to learn and no licence to buy.
Watch the server-side features. Cloudflare’s free tier is generous, but a very busy site may eventually need a paid plan for the functions in section 4.

09 What is not included

The code is complete. These sit outside it and need their own handover:

Accounts and logins — the Cloudflare account, the domain registrar, and any third-party service the site connects to. Ask for each to be transferred to an account you own.
Anything with its own login — analytics, email, booking or payment tools are separate services with separate billing.
Stored data — this site uses KV storage (key-value database). That data lives in the Cloudflare account rather than in the code, and has to be transferred or exported separately.
Photography and fonts — where these were licensed rather than original, the licence terms carry over. Ask if you are unsure about a specific image.