Problem
Mission-driven organizations need dependable public systems, but production reliability and accessibility often get treated as separate concerns instead of one delivery problem.
Production case study
Production platform and delivery stack supporting a nonprofit serving the visually impaired community.
At a glance
Delivery stage
Production
Current state
Production
My role
Sole engineer for architecture, frontend, infrastructure, and deployment
Mission-driven organizations need dependable public systems, but production reliability and accessibility often get treated as separate concerns instead of one delivery problem.
Built as an accessibility-first web platform deployed on AWS Lightsail with host-level Nginx, Dockerized frontend delivery, SSL automation, scheduled maintenance, and CI-driven image publishing. The system supports real nonprofit operations instead of acting like a brochure site.
Production site serving VIFG nonprofit since 2020, deployed on AWS Lightsail with automated CI/CD and TLS termination
This section shows the operational logic behind the build, not just the user-facing surface.
Core constraint
Accessibility as a system constraint: screen reader compatibility, keyboard navigation, and contrast requirements treated as first-class delivery requirements
This page separates what is already visible from what is still being prepared, so the proof layer can grow without pretending unfinished artifacts already exist.
Real artifacts stay visible. Missing artifacts are labeled directly so this page stays honest and ready for stronger proof later.
This is the clearest public proof on the site because both the public surface and the delivery stack are visible.
The deployment diagram on this page shows the infrastructure and release path that make the system believable.
The project includes real production surfaces beyond the public pages themselves.
This project already has the strongest current evidence set in the portfolio.
This system also has a live public surface, which matters because delivery only counts when the software is actually in use.