NF3L Software & Games
Mission Control

Operations Console

ALL SYSTEMS LIVE Jim Chookagian
Projects3live
Source of truthGitHub
Clock · UTC
Clock · Local
01

Projects

version stamp shows on each live site — compare to your zip
PFH
Pennridge Field Hockey — Sub Planner
v1.0.02026-07-03
Livepfh.nf3l.com
Repopfh-sub-planner
Pagespfh-sub-planner
Supabasecucdovxsnhhjisdbcasm
Auth Cloud sync Backups Keep-alive RLS
NF3L
nf3l.com — Public site & web games
v1.0.02026-06-30
Livenf3l.com + www
Reponf3l-site
Pagesnf3l-site
Supabasewspnyfiljtdckmarzbsl · demo
Git-versioned Auth Backend Gate
CFCSQ
Membership DB · Coopersburg Fire Co. Social Quarters — ~1,500 members
v1.0.02026-06-27
Repocfcsq-membership
Pagescfcsq-git
Supabaseunykwebzlmvadvnutgvi
Auth Access gate · 3 emails RLS · 24 policies Recovery kit
02

Live status · CFCSQ

connecting…
🗄️ Cloud (Supabase)
📦 Dropbox
💻 Local Download

Members by status

Loading…
03

Games · nf3l.com

opens in a new tab
04

Operations

Deploy workflow

The same five moves for any site. No command line.

1Edit the files in your local repo folder.
2Bump the version — the stamp in the file (and tell Claude to, on any build).
3In GitHub Desktop: write a summary → Commit.
4Click Push origin. Cloudflare Pages auto-deploys in seconds.
5Verify: open the live site — the version stamp should match your new build.

Versioning rule

Bump on every change. Name it PROJECT_vX.Y.Z_YYYY-MM-DD

PATCHv1.0.1 — a small fix or copy tweak (last digit +1).
MINORv1.1.0 — a new feature added (middle digit +1).
MAJORv2.0.0 — a big overhaul (first digit +1).
05

Working with Claude

tap copy, paste into chat

Hand these to Claude to keep builds clean and versioned. Fill in the teal parts.

Update [PFH / NF3L / CFCSQ]: [what to change]. Bump the version and give me a properly named build.
Give me the current master zip for [project], version-stamped and named to standard.
What version is live on [project], and does it match my latest zip?
Walk me through [task] one step at a time — this is a mission-critical system.
06

Consoles

07

Recovery & backup

Every version lives in 4 places

Sweep the repo folder to USB, then Google Drive, whenever you change something.

1Your computer the working repo folders
2GitHub full history + one-click rollback — the source of truth
3USB drive copy the whole folder (incl. hidden .git)
4Google Drive keep private — the CFCSQ kit holds admin emails

CFCSQ recovery kit

Three layers — files alone won't rebuild it. All captured.

App files · repo cfcsq-membership
Access gate · access app + policy JSON
Supabase RLS · cfcsq-rls-2026-06-27.sql
Index · CFCSQ-RECOVERY-KIT.md
Versions & project names are editable — changes save in this browser.
Copied