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
VIFG Nonprofit Platform
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
What was built
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.
Result
Production site serving VIFG nonprofit since 2020, deployed on AWS Lightsail with automated CI/CD and TLS termination
How the system was structured
This section shows the operational logic behind the build, not just the user-facing surface.
Key system pieces
Production deployment runs behind Nginx with TLS termination.
Dockerized delivery and GitHub Actions keep releases repeatable.
Accessibility is treated as a system constraint, not a post-launch fix.
Core constraint
Accessibility as a system constraint: screen reader compatibility, keyboard navigation, and contrast requirements treated as first-class delivery requirements
Stack
ReactTypeScriptViteDockerAWS LightsailNginx
Supporting proof
This project shows production ownership through deployment topology, release flow, and the public-facing system that is actually running.
Deployment diagramProduction site viewRelease artifact
Public-facing proof
This system also has a live public surface, which matters because delivery only counts when the software is actually in use.