Building the hub

No flying today. Two things instead.

The site

Social media gets attention. A site turns it into something durable: video, then page, then code and parts, then an email address I actually own. So this is now a site, not a portfolio. Home, Projects, Journal, Guides, About, with a newsletter form on every page and nothing behind a login, because there is nothing worth logging in for yet.

Built on Astro, deploying to Vercel, content in Markdown. The design came first as five boards, and the pages were built to match them. The flight log readout you see on the incident entry is a real component fed from real ulog data, and it will show up wherever a sequence of events is the point.

Recording plan

The master shot is me, the drone and the laptop in one wide frame, tripod, 20 m back, no cuts. A lav mic on me, Hawk’s voice captured clean from the Mac with a screen recording, a clap to sync. A friend with a second phone low on the aircraft. The Action 4 goes on the airframe for drone’s-eye B-roll only once the aircraft is cleared to fly with it, not before.

The shot list is short: take off, one move, one refusal, land. The refusal is the credibility beat. The long version gets the climb and the kill, with the log on screen. Nobody trusts a demo where nothing went wrong.

Before the next flight

Two parameters, because both address things that actually happened on the 13th: height reference to the barometer, so Hold cannot chase a drifting GPS altitude, and battery failsafe to Land, which never climbs. Then the tray repair, a healthy battery, calibration redone, and a flight on open ground once to separate “Hawk works” from “this site is hard”. The flow sensor waits until that flight says whether it is needed.