Website Handoff · Prepared by Vivere Web Development

Jireh Cafe and Bakery

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

PreparedAugust 16, 2026

Hosting projectjirehcafeandbakery-com

Codebase61 files · 22.3 MB

01 What you own

This document accompanies the complete source code for Jireh Cafe and Bakery. The code, the content, the images and the design are yours. Nothing here depends on Vivere Web Development continuing to be involved.

8web pages

61total files

22.3 MBcodebase size

15recorded changes

The codebase is under Git version control — 15 recorded changes on branch main. 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, 7439 files in _archive — 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
`.vscode\`	Supporting files for the site
`assets\`	Images, video and downloadable files used by the site

By file type

Type	What it is	Files	Size
`.jpg`	Images	34	17.4 MB
`.html`	Web pages	8	613 KB
`.heic`	Images (Apple format)	3	4.3 MB
`.json`	Data / config	3	10 KB
`.md`	Documentation	2	9 KB
`(none)`	Other	2	1007 bytes
`.ps1`	Deploy scripts	2	4 KB
`.js`	Browser code	2	31 KB

03 How it is hosted today

The site runs on Cloudflare Pages, a website hosting service. The project is named jirehcafeandbakery-com and answers on jirehcafeandbakery.com.

How updates reach the site: Cloudflare builds and publishes automatically whenever the GitHub repository changes.

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 This site is fully portable

Every file here is static — HTML, CSS, images and browser JavaScript. There is no server-side code and no database.

It will run on any static host, unchanged. Cloudflare Pages, Netlify, Vercel, GitHub Pages, Amazon S3, or ordinary shared hosting over FTP. Upload the files and it works. You are not locked in to any provider.

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 the project folder:
```
npx wrangler login
npx wrangler pages deploy . --project-name jirehcafeandbakery-com
```
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 jirehcafeandbakery.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. Because this site is fully static, moving is straightforward.

Host	Good for	What to know
Netlify	Closest equivalent	Reads `_headers` and `_redirects` the same way. Drag-and-drop deploy works.
Vercel	Strong developer tooling	Uses its own configuration format. Static upload works as-is.
GitHub Pages	Free and simple, static only	Works well. No server-side support, which this site does not need.
Traditional web hosting	Bundling with existing services	Upload the files over FTP. Works — it is ordinary HTML.

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 jirehcafeandbakery.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.

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.
Photography and fonts — where these were licensed rather than original, the licence terms carry over. Ask if you are unsure about a specific image.