IT / WEB INFRASTRUCTURE
This Website
The systems behind this site: the Reflex build, version control, the domain, and the hosting path from local preview to public deployment.
SITE OVERVIEW
This site is a live Reflex application served from Cloudflare Pages on the custom domain jessewilham.tech. I started learning Reflex and building this project around mid-October. It is still content-only today — the front end is exported as a static build and uploaded to Pages — but the codebase is structured so a Python backend can be added later. As of writing this page, the Python source is roughly 8,000 lines (excluding the vendored cssDOOM game.).
Deployment stack · current state
Public path
- App · Reflex 0.10READY
- Git repositoryACTIVE
- DomainACTIVE
- DNS recordsACTIVE
- HostACTIVE
- TLSACTIVE
Backend roadmap
- SQL databasePENDING
- AuthenticationPLANNED
- EmailPLANNED
- API layerPLANNED
The application
This portfolio is a Reflex application. One Python codebase defines every page and compiles into a React front end; Reflex also provides the backend the app runs on. Styling is Tailwind v4 utility classes, pages are registered by hand in app/app.py, and images, CSS, and the standalone creative works are served from assets/. The version is pinned at Reflex 0.10.0.
Build and version control
The git repository is the source of truth. Running the app compiles the project and serves a local development build on port 3000, while the production build is exported with a PowerShell script that packages the static output for Cloudflare Pages. There are no tests or CI yet, so the compile output is the current check. Every change follows the same loop: edit, compile, verify, export, upload.
Domain, hosting, and TLS
The domain jessewilham.tech is registered at Porkbun and uses Cloudflare for DNS. The site is hosted on Cloudflare Pages, which also provisions and auto-renews the TLS certificate. Traffic is proxied through Cloudflare, so the DNS A and AAAA records point at Cloudflare's edge network rather than directly at a single server.
Current host: Cloudflare Pages
Backend roadmap — planned
The site is content-only today, which is why a static front end is enough to start. The long-term plan is a real backend. Nothing below is built yet:
- A SQL database for persistent content and user data
- Authentication and login: sessions, roles, and protected admin views
- Email integration for contact forms, notifications, and account flows
- An API layer so pages can fetch and update dynamic content
These systems are what will move the site from a static portfolio to a full-stack application.
Next steps
Finishing the remaining IT subpages, add a proper CI step that runs the export script and uploads to Pages automatically. Backend work stays on hold until the front end is complete and a runtime host is needed. This in itself will be a very big project.