Frontend
Responsive static pages
Semantic HTML, modern CSS, and small JavaScript modules keep the first load fast across CloudFront edges.
Cloud-native web delivery
I build fast, resilient web experiences that pair thoughtful frontend craft with serverless AWS architecture and dependable deployment pipelines.
What this foundation supports
The current version is intentionally static, cache-friendly, and simple to deploy. It leaves clean room for API-driven features, authored content, and richer interactive surfaces as the site grows.
Frontend
Semantic HTML, modern CSS, and small JavaScript modules keep the first load fast across CloudFront edges.
Backend
Future dynamic features can sit behind API Gateway and Lambda without changing the static hosting model.
Delivery
GitHub Actions can publish versioned assets to S3 and invalidate CloudFront when production changes ship.
Build posture
Start with a durable static core. Add framework weight only when content modeling, component reuse, or interactive state starts paying rent.
Approach
The site should feel polished without being fragile: clear content hierarchy, compressed assets, accessible interactions, and deployment behavior that remains easy to reason about.
Production stack
AWS S3 stores the public HTML, CSS, JavaScript, images, and metadata files.
CloudFront serves cached assets globally and is invalidated by the deployment workflow.
Cloudflare remains the public proxy and SSL control point for the custom domain.
GitHub Actions owns the deploy step, so local work stays focused on source files and assets.
Next step