A prototype becomes more useful when it can be opened by someone else. That is why I like keeping the deployment path short.
For this portfolio, the site is a static Astro build served through Cloudflare Workers Static Assets. The local command builds the site into dist, and Wrangler deploys that directory to Workers.
The Deployment Shape
The setup is intentionally small:
- Astro outputs static HTML, CSS, and JavaScript
- Bun runs the scripts and dependency workflow
- Wrangler deploys the static assets
- Cloudflare Workers serves the live site
There is no custom Worker script yet because the site does not need runtime logic. That can change later if the product adds server-side routes, form handling, AI endpoints, or authenticated features.
What I Check Before Shipping
Before calling something done, I want proof from the actual artifact:
- the production build passes
- the expected routes exist
- metadata is present for SEO and sharing
- the live Workers URL opens correctly
- the UI has no obvious console errors
That verification habit matters more as the stack becomes more AI-assisted. Fast shipping only works when the feedback loop is real.
AI-assisted summary compiled from the sources above, reviewed by a human before publishing.