don-the-imaginator.com: Why I Tore Down the Gate, Over-Built It, Then Chose Restraint
The first version of my portfolio made people create an account before they could see any work. My analytics (Firestore) told the story: about 10 visitors a month arrived from résumé links, 20% signed up, and 0% ever sent a first message. I took the gate down — then over-corrected: 5 switchable looks, an in-browser answer cache, a keep-alive script, all crammed onto one page. It proved I could build, and it overwhelmed anyone scanning fast. So V3 is restraint: a quiet editorial landing page for the 30-second scan, with the experiments — the theme engine, the graph tools, plain-English database queries — moved into /lab.
The Wake-Up Call: 1 in 5 Signed Up, None Stayed
My analytics (Firestore: page views, accounts created, first chat messages) showed exactly where it broke. About 10 visitors a month arrived from résumé links. 20% created an account. 0% ever sent a first chat message. I had told myself a gate would feel exclusive; in a hiring review, a needless signup just kills interest. The sample is small — that is the honest size of it — but a funnel where nobody finishes is a funnel that is broken.
Two Ways People Read a Portfolio — the Insight That Created /lab
The quick scan (a model reader — call her Sarah, a VP of Applied AI; not a real interviewee): 30–60 seconds. Wants to see real work and try a tool within 5 seconds, with no account. Deal-breakers: a mandatory login, a 30-second cold start.
The deep read (a model reader — Marcus, a repeat founder; also not a real interviewee): 15–30 minutes. Wants the Python APIs, the Docker setup, how the Neo4j graph is queried, and whether the site stays up. Both readers are models I built from how hiring reviews actually work — I did not interview them, and I won’t pretend otherwise.
The conflict: one page was trying to serve both — theme pickers, a chat concierge, and dashboards all fighting for attention.
Decision: split the site. The landing page (/) is quiet and editorial, for the 30-second scan. /lab is the sandbox, where reviewers can try the tools, switch the looks, and see how the in-browser answers work.
A Theme Engine With 5 Looks, Built on CSS Variables
To test how far a design system can stretch, I built a theme engine with 5 looks, using space-separated RGB values stored in root CSS variables (--theme-bg: 253 248 237). Tailwind maps via rgb(var(--theme-bg) / <alpha>).
Switching looks flips a single class on the root element, and the browser repaints at native speed. My test: 250 swaps on my machine — the layout did not shift (CLS 0) and a swap took ~16ms. That is a theme test, not a claim about every page; full checks across all 21 routes are still on my list.
General visitors need clarity, not a theme-switching demo. Keeping the experiment in /lab shows the discipline without distracting from the case studies.
Choosing Restraint: One System Across All Three Projects
Keeping Free Databases Awake: A Local Script (for Now)
Free-tier databases fall asleep when they sit idle, and the first visitor after that can hit a ~30-second cold start — or an error page. For now, a PowerShell script on my own machine pings them to keep them warm. It only works while my machine is on. It is a workaround, not a solution.
The script has logged 1,420 warm-up cycles locally. The honest next step is Google Cloud Scheduler plus paid database tiers. I am not claiming 100% uptime, or that $0 a month is some permanent achievement — today’s setup is free tiers plus a script on my desk.
On layout stability: in the 250-swap theme test, the layout shift (CLS) measured 0 and a swap took ~16ms. Full Core Web Vitals across all 21 pages are still being checked — I will publish them when they are real numbers, not targets.
{
"database": "Neo4j AuraDB (Cloud)",
"protocol": "neo4j+s / Bolt TLS",
"current": "local keep-alive script (temp workaround)",
"limitation": "requires dev machine on",
"next": "GCP Cloud Scheduler + Aura Professional",
"verified_warmup_cycles": 1420,
"monitored_surfaces": ["/ (reserved)", "/lab (experimental)"],
"infra_footprint": "serverless + free-tier + local daemon"
}Honest Outcomes: From a Signup Wall to an Open Site
1. The gate came down: The V1 numbers (Firestore): ~10 visitors a month, 20% signed up, 0% ever sent a message. Now there is no account between a visitor and the work, and the chat can be tried within seconds of landing.
2. The site split in two: Moving the 5 looks and the experiments into /lab kept the landing quiet. In testing, the in-browser cache answered 40 of 50 typical questions with no AI call and $0 cost (2,500 runs).
3. Tools do the work, the AI routes: The valuation tool answers in ~4ms typical (50 runs, my machine); a stock lookup ~10ms; weather ~23ms. Routing the question through tools instead of asking the AI to calculate cut the prompt from ~1,850 tokens to ~140.
4. Plain-English database queries: A small service turns questions into read-only queries over 45 tables. The database account can only read, the query is checked before it runs, and a failed query gets one automatic retry. Results stream into live cards with charts and CSV export.
5. The takeaway: Serve the visitor’s intent before asking for anything. Prove depth with systems people can actually try. And say the limitations out loud: the keep-alive is temporary, and the reader types are models, not interviews.