Website Handoff · Prepared by Vivere Web Development

Grand View Event Center

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

Live sitegveventcenter.com
PreparedAugust 16, 2026
Hosting projectgrand-view-event-center
Codebase376 files · 176.4 MB

01 What you own

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

38web pages
376total files
176.4 MBcodebase size
117recorded changes

The codebase is under Git version control — 117 recorded changes on branch landing-redesign-2026-04-29. 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, 120 files in _docs, _source, audit, Backups, marketing-materials — 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:

FolderContains
.agents\Supporting files for the site
.cursor\Supporting files for the site
.vscode\Supporting files for the site
assets\Images, video and downloadable files used by the site
config\Supporting files for the site
contact\Supporting files for the site
data\Supporting files for the site
es\Supporting files for the site
forms\Supporting files for the site
reports\Reports produced for you
scripts\Build and deploy automation

By file type

TypeWhat it isFilesSize
.mdDocumentation1221.1 MB
.webpImages (modern format)669.6 MB
.pngImages4460.8 MB
.htmlWeb pages381.2 MB
.jpgImages186.6 MB
.pyOther1786 KB
.mp4Video1294.5 MB
.pdfDocuments101.8 MB
.ps1Deploy scripts912 KB
.jsBrowser code735 KB
.jsonData / config627 KB
.txtText519 KB
.cssStyling5261 KB
.svgVector graphics35 KB
.mdcOther34 KB
.vcfOther2426 bytes

03 How it is hosted today

The site runs on Cloudflare Pages, a website hosting service. The project is named grand-view-event-center and answers on gveventcenter.com.

How updates reach the site: A deploy script copies an approved list of files to a temporary folder, uploads that, then deletes it. Source files stay private.

Host-specific files

04 Part of this site is server-side code

This site is not purely static. 24 server-side file(s) live in functions/clean.js, cmp.js, coerce.js, compare.js, compare-build.js, compare-loose.js, diff.js, eq.js, gt.js, gte.js, inc.js, lt.js, lte.js, major.js, minor.js, neq.js, parse.js, patch.js, prerelease.js, rcompare.js, rsort.js, satisfies.js, sort.js, valid.js. On Cloudflare these run automatically as Pages Functions.

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.

  1. Create a free Cloudflare account at dash.cloudflare.com/sign-up.
  2. 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.
  3. Publish the site. Install Node.js, then from inside the project folder:
    npx wrangler login
    npx wrangler pages deploy . --project-name grand-view-event-center
    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.
  4. Point your domain at it. In the Pages project open Custom domains and add gveventcenter.com. Cloudflare walks you through the DNS records.
  5. 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.

HostGood forWhat to know
NetlifyClosest equivalentReads _headers and _redirects the same way. Functions must be rewritten for Netlify Functions.
VercelStrong developer toolingUses its own configuration format. Functions must be rewritten for Vercel Functions.
GitHub PagesFree and simple, static onlyNot suitable — cannot run this site’s server-side features.
Traditional web hostingBundling with existing servicesUpload 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 gveventcenter.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

09 What is not included

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