WEB-10 · EXPERIENCE
I build fast, dependency-light websites and web apps
I design and build marketing sites and internal web apps with Astro, Cloudflare Pages, Tailwind, and TypeScript. The goal is simple: pages that load fast, code that stays small, and a stack that does not fall over when traffic spikes or a dependency breaks. I treat every production push like an infrastructure change, with a documented plan and a rollback ready before anything goes live.
01 · What I do
The actual work
- Build marketing sites and landing pages in Astro that ship mostly static HTML and almost no client-side JavaScript.
- Develop internal web apps, tools, and dashboards backed by Cloudflare Workers, KV, and D1.
- Stand up Tailwind design systems so styling stays consistent and easy for your team to extend.
- Write everything in TypeScript so mistakes surface at build time instead of in production.
- Deploy to Cloudflare Pages with preview builds, custom domains, and edge caching.
- Wire up forms, auth, and API endpoints without dragging in a heavy framework you have to babysit.
- Tune for Core Web Vitals: image handling, font loading, and a tight asset budget.
02 · What you get
What you are left with
- A site or app that loads fast and stays cheap to host on Cloudflare's edge.
- A clean TypeScript codebase your team can actually read, extend, and maintain.
- A documented deploy and rollback path, so releases stay boring on purpose.
- Source in your own repo and your own Cloudflare account, with no lock-in to me.
03 · Tools and knowledge
What I work with here
04 · How I approach it
Planned, scoped, and owned
We start with a 30-minute scoping call, and you get a written fit assessment the same day so you know whether I am the right person before you commit anything. From there I work in small, reviewable steps: a documented change plan with a rollback before any production change, then a cutover inside a defined window, validated against clear gates with the rollback owned. Preview deploys on Cloudflare Pages mean you see real, working pages at every stage instead of waiting for one big reveal at the end.
05 · Questions
Good questions, straight answers
Why Astro instead of Next.js or WordPress?
Astro ships static HTML with almost no JavaScript by default, so pages load fast and there is less to break or patch. If a section genuinely needs interactivity, I add it there and nowhere else. WordPress works for some teams, but it carries a plugin and update burden I would rather you not own.
Can you work with my existing brand or design?
Yes. I can build from your Figma file, an existing site, or a rough brand guide, and turn it into a Tailwind setup your team can keep using after I hand it off.
Do I own the code and the hosting?
Yes. The code lives in your repo and deploys to your Cloudflare account. Nothing is tied to me, and you can hand it to another developer at any time.
06 · Related experience
Adjacent work I do
Need this handled?
Tell me what you are trying to move and where it is stuck. A few sentences is plenty to start, and it goes straight to my inbox.