gregjones.io

A personal command interface for Greg Jones — CEO of a single family office and SWS Venture Capital. Not a portfolio. An operating system for a modern capital allocator.

Building systems that compound.

Bloomberg Terminal × Apple minimalism × private family office. Dark, minimal, high-status. Static-first, near-zero JavaScript, no tracking, no stock imagery.

---

Stack

• Astro — static-first, ships almost no JS by default
• Vanilla ES module for the terminal engine (public/terminal.js) — zero runtime dependencies
• One data file (src/data/content.js) is the single source of truth for all copy, status metrics, and the Ask Greg knowledge base
• Deploys cleanly to Cloudflare Pages

src/
  data/content.js      # ← edit copy, metrics, AI answers here
  layouts/Base.astro   # head, meta, OG tags
  pages/index.astro    # boot screen + terminal markup + scoped styles
  styles/global.css    # design tokens (palette, type)
public/
  terminal.js          # terminal engine (commands, status, Ask Greg)
  _headers             # Cloudflare security + cache headers
  favicon.svg, robots.txt, sitemap.xml

---

Local development

Requires Node 18.20+ (Node 20 recommended — see .nvmrc).

npm install
npm run dev        # http://localhost:4321
npm run build      # outputs to ./dist
npm run preview    # serve the production build locally
npm run lint       # astro check

---

Deploy to Cloudflare Pages

1. Push to GitHub

git init
git add .
git commit -m "Initial commit — gregjones.io"
git branch -M main
git remote add origin https://github.com/<you>/gregjones-io.git
git push -u origin main

2. Create the Pages project

1. Cloudflare dashboard → Workers & Pages → Create → Pages → Connect to Git.
2. Select the gregjones-io repository.
3. Build settings:

Setting	Value
Framework preset	Astro
Build command	npm run build
Build output directory	dist
Node version	20 (set env var NODE_VERSION=20 if needed)

4. Save and Deploy. Every push to main redeploys automatically; pull requests get preview URLs.

3. Custom domain

Pages project → Custom domains → add gregjones.io (and www). If the domain is on Cloudflare, DNS is configured for you. Otherwise point a CNAME at the *.pages.dev target.

Environment variables

None are required for Phase 1 — the site is fully static. Variables are only needed if you wire real data (below). Set them under Pages → Settings → Environment variables.

---

Editing content

Everything visitor-facing lives in src/data/content.js:

• identity — name, tagline, pillars, email
• commands — the command menu (order = display order)
• sections — about / automation / capital / principles / contact copy
• status — dashboard metrics
• askGreg — curated Q&A knowledge base

Change a value, commit, push — Cloudflare redeploys. No code changes needed for routine copy edits.

---

Connecting real data (Phase 2)

Status dashboard → live metrics

The dashboard is simulated locally but already wired to go live. In src/data/content.js:

export const status = {
  source: '/api/status',   // ← set to your endpoint (was null)
  ...
};

terminal.js will fetch(status.source) on the /status command and fall back to the simulated values if the request fails. Expected JSON shape:

{
  "metrics": {
    "automations_running": 51,
    "hours_reclaimed": 4310,
    "documents_processed": 320145,
    "signals_monitored": 1290,
    "active_workflows": 64,
    "uptime": 99.99
  }
}

A natural backend is a Cloudflare Pages Function at functions/api/status.js (or a Worker) that reads from n8n / Zapier / a database and returns the JSON above.

Ask Greg → live model

Phase 1 is intentionally constrained: curated answers, no API, no keys — it never pretends to be autonomous. To upgrade, add a Pages Function (e.g. functions/api/ask.js) that calls a model provider with a tight system prompt, and point runAsk() in terminal.js at it (keep the curated set as the fallback). Store the API key as a Cloudflare environment variable — never in the repo.

---

Continuous improvement

See SITE_REVIEW.md for the 60-day review process, changelog, and backlog. A scheduled GitHub Action (.github/workflows/site-review.yml) opens a review issue every 60 days and runs dependency/build checks.

---

Performance & quality

• Static HTML, CSS inlined where small, single ~10KB JS module
• Semantic HTML, prefers-reduced-motion respected, keyboard-navigable, no-JS fallback
• Security headers via public/_headers
• No external fonts, images, analytics, or trackers

License

Private. © Greg Jones.