Skip to content

Personal project · 20262 min read

This website: built and run like a production service

juasoh.com is a pre-rendered React site on Cloudflare, with a serverless contact backend on AWS defined in Terraform, CI/CD in GitHub Actions, and analytics that show where visitors come from.

Role
Designer and engineer (solo)
When
2026 – present
  • 11Pages pre-rendered to static HTML on every build
  • 17Unit tests on the contact backend
  • 0Failed Checkov security checks (121 passed)
  • ~$1Estimated AWS cost per month

The short version

Problem
A portfolio should show how I build, not just say it: fast and findable pages, a contact form that works, and infrastructure I can explain line by line.
What I did
Built the site in React and TypeScript, pre-rendered for SEO and deployed to Cloudflare from GitHub, and wrote a serverless AWS contact backend in Terraform with a tested CI/CD pipeline.
Result
Every page ships as real HTML with structured data. The contact backend's code, tests, and security scans run on every change; the backend runs on AWS at aws.juasoh.com.
  1. GitHub

    Pull request

  2. GitHub Actions

    Tests, Terraform, Checkov

  3. Cloudflare Workers

    Pre-rendered site

  4. API Gateway + Lambda

    Contact API (AWS)

  5. DynamoDB + SES

    Save, then email

My partContextThe site deploys from main to Cloudflare; the AWS contact stack deploys through GitHub Actions after a manual approval.

The problem

A portfolio that proves the work

My earlier site was a single page with a contact form that never actually sent: its email service was misconfigured. I wanted the site itself to show the platform and DevOps practices I use at work.

Approach

The front end

React 18 and TypeScript, built with Vite and styled with Tailwind CSS, with light and dark themes.

  • Every route is pre-rendered to static HTML at build time and hydrated in the browser, so search engines and link previews see real content.
  • Per-page titles, canonical URLs, Open Graph cards, JSON-LD structured data, a generated sitemap, and IndexNow submissions to Bing.
  • Accessible by keyboard and screen reader, with content that stays visible without JavaScript or with reduced motion.

Approach

Hosting and delivery

Cloudflare Workers serves the static build. Every pull request gets its own preview URL, and merging to main deploys to juasoh.com in about a minute.

My contribution

A serverless contact backend on AWS

The contact form posts to an API at aws.juasoh.com: API Gateway, then a Python Lambda that validates the message, saves it to DynamoDB, and emails it through SES. CloudWatch alarms and a budget alert watch it. All of it is defined in Terraform.

  • Least-privilege IAM: the function can write to one table and send from verified addresses, nothing else.
  • Throttling, a honeypot, and input validation instead of a login, because it's a public form.
  • Remote Terraform state in S3 with locking, and pinned provider versions.

My contribution

CI/CD and security

GitHub Actions runs the unit tests, Terraform format and validation, and a Checkov security scan on every change, and posts the Terraform plan on pull requests. Deploys use OIDC, so no AWS keys are stored anywhere, and need a manual approval.

Outcome

Where it stands

The site is live. The contact backend passes its tests and scans in CI, and it now runs on AWS at aws.juasoh.com, deployed through the approval-gated pipeline. If the API is ever unreachable, the form falls back to opening the visitor's email app, so no message is lost.

Built with

  • React 18
  • TypeScript
  • Vite
  • Tailwind CSS
  • Cloudflare Workers
  • AWS Lambda
  • API Gateway
  • DynamoDB
  • SES
  • Terraform
  • GitHub Actions
  • Checkov
  • Playwright
  • Google Analytics 4
Next case studyA GenAI chatbot for internal documentation