What this site demonstrates
Four capability areas, each visible on the very pages you're browsing. Nothing here is theoretical.
Interface design
A consistent design system applied across five pages: shared tokens, cards, buttons, and a layout rhythm that survives content changes.
- Design tokens via CSS custom properties
- Dark and light themes from one palette
- Reusable card, chip and step components
Front-end engineering
Vanilla JavaScript doing real work: navigation state, scroll animations, counters, filtering and form validation — guarded so missing pieces fail soft.
- Progressive enhancement patterns
- IntersectionObserver-based reveals
- Client-side validation with clear errors
Performance & accessibility
No framework runtime to download, no external requests, semantic HTML throughout, and motion that respects user preferences.
- Keyboard navigable, skip links included
- prefers-reduced-motion respected
- aria labels and states on controls
Deployment & operations
The invisible half of the work: containerized build, enforced CPU and memory limits, automatic TLS, and commit-triggered redeploys.
- Git-backed deploys with audit trail
- Resource limits verified at deploy time
- Same-URL updates, no rebuild churn
How a real build runs
Scope
Describe the outcome in a sentence or two. The stack and page structure follow from it.
Build
Source written file by file, with shared assets kept genuinely shared.
Ship
One deploy call: repository, build, HTTPS verification, done.
Iterate
Feedback becomes commits; commits become redeploys on the same URL.
Fair questions, straight answers
Is this a real, publicly accessible website?
Yes. It's served over HTTPS on a live domain, verified at deploy time. Anyone with the URL can visit it.
Where does the contact form data go?
Nowhere — by design, for this demo. The form validates input in your browser and shows a success state without transmitting anything.
Could this site have a real backend?
Yes. The same pipeline supports FastAPI APIs, background workers, Redis queues and databases. Static was chosen here for speed and simplicity.
Who maintains it after launch?
AIMY does — via a commit-and-auto-deploy loop. Every change is a reviewed commit pushed to the connected repository.