Public hub, built to grow

Home projects with a steadier shape.

Fireoak is where Daniel collects practical software projects, Cloudflare-native experiments, and the kinds of personal builds that start as a quiet itch and end up worth sharing.

Curated first

The homepage leads with a small number of projects that are ready to be understood quickly.

Subdomains with intent

Bigger apps can move onto their own surfaces later without turning the apex site into a maze.

Private tools later

Home and personal utilities stay off the public surface until they belong behind Access.

Highlights

A few projects worth the first click.

The public hub should make the interesting work easy to spot without forcing visitors through every experiment first.

Bot coordination flow
active public
Featured build

AI Enabled Chat Bot

A Discord-first running-group bot that uses Cloudflare Workers, D1, and Workers AI to handle schedules, reminders, and in-channel chat.

Cloudflare WorkersD1DiscordWorkers AI
Modernization routing map
prototype public
Featured plan

Pack 162 Modernization

A Cloudflare-first modernization plan for a Cub Scouts site, using an edge proxy and progressive migration instead of a risky full rewrite.

Cloudflare WorkersPagesHTMLRewriterArchitecture
Domain layout blueprint
active public
Featured build

Fireoak Hub

The public front door for personal projects: a curated homepage, lightweight project pages, and a domain structure built to grow without becoming messy.

Cloudflare PagesStatic SiteContent Architecture
Domain Layout

Apex for clarity, subdomains for depth.

The root site stays readable and lightweight, while the domain keeps reserved space for polished apps, experiments, and private tools.

@

Public Fireoak hub with Home, Projects, and About.

www

Redirect to the apex domain to keep the public entrypoint canonical.

lab

Shared sandbox for fast experiments and lower-stakes demos.

private

Future home and personal tools behind Cloudflare Access.

Version one stays small on purpose.

Fireoak launches with Home, Projects, and About. That is enough to explain the work, route people into the good stuff, and keep the main domain feeling intentional instead of busy.

What grows later

Project-specific subdomains, a shared lab. sandbox, and a private. surface for home tools can all arrive later without tearing up the public hub.