Problem
Mission-driven organizations need dependable public systems, but production reliability and accessibility often get treated as separate concerns instead of one delivery problem.
Public Production Proof
VIFG Nonprofit Platform
Production platform and delivery stack supporting a nonprofit serving the visually impaired community.
At a glance
Context
Public Production Proof
Current state
Production
Role
Sole engineer for architecture, frontend, infrastructure, and deployment
Core Constraint
Accessibility as a system constraint: screen reader compatibility, keyboard navigation, and contrast requirements treated as first-class delivery requirements
Solution / What I Built
I build and maintain the React application and its delivery path on AWS Lightsail. Nginx handles incoming traffic and TLS, Docker packages the frontend, and GitHub Actions supports repeatable releases. Accessibility review and infrastructure maintenance remain part of the same engineering responsibility.
Results
Production site serving VIFG nonprofit since 2020, deployed on AWS Lightsail with automated CI/CD and TLS termination
Architecture
The pipeline is shown as explicit stages so the system boundary is inspectable.
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.
Technical Stack
ReactTypeScriptViteDockerAWS LightsailNginx
Applied Relevance
Where the pattern matters
- Accessible public services for a nonprofit community.
- Repeatable application releases on a maintained cloud host.
- Ongoing ownership of application, deployment, and infrastructure changes.
Implementation and evidence
Implementation details and the artifacts available for review.
Live nonprofit website
Linked artifactsThe public website is the visitor-facing part of the platform I build and maintain for VIFG.
- The engagement spans application development, infrastructure, and releases.
- Screen-reader compatibility, keyboard navigation, and contrast are delivery requirements for the community it serves.
Deployment architecture
Linked artifactsThe diagram shows the request path and how application changes reach the AWS host.
- Nginx terminates TLS and forwards traffic to the Dockerized frontend on Lightsail.
- GitHub Actions supports the image-publishing and deployment path.
- The diagram describes the architecture; it is not a monitoring report.
Ongoing delivery responsibilities
Implementation notesMy role continues beyond the application code into the infrastructure and release process.
- Maintain host-level web serving and TLS configuration.
- Keep Docker packaging and the release workflow aligned with application changes.
- Review accessibility issues alongside feature work and maintenance.
Scope and limitations
Interpreting this work
- The live website and deployment diagram show the public surface and architecture. This page does not publish an uptime measurement or an independent accessibility audit.
- Serving the nonprofit since 2020 describes the engagement history, not a measured availability percentage.
Live Proof
Visit the public website to review the delivered experience.
Related Case Studies
More portfolio context.
PilotBeta Pilot
DealerFlow
Pilot platform that automates inventory alerts, buyer matching, and seller workflows for wholesale vehicle activity.
NestJSBullMQPostgreSQLPrisma
Read case studyR&DActive Build
DGM
Workflow orchestration layer in active development for managing state, decision flow, and human review inside StormIQ.
PythonFastAPIWorkflow GraphsQueue-backed Jobs
Read case study