← All projects & work

Software / 2026

Post of Joy

Collaborative full-stack development for Post of Joy, a nonprofit website. The work included a responsive interface, persistent user-generated content, and cloud deployment.

My role
Collaborative full-stack development
Current status
Deployed
Technology & tools
Python · Flask · HTML / CSS / JS · Firestore · Google Cloud Run · DNS
Post of Joy homepage with birthday-card artwork and the headline Every Birthday Deserves to Be Celebrated
Live homepage · desktop capture, October 2026Explore screenshots

Context

The problem

Turn stakeholder needs into a useful, responsive website that supports user-generated content and can be reached through the nonprofit’s own domain.

How it fits together

Architecture & approach

The work combines product decisions, persistent data, and deployment. Public screenshots and examples must respect the nonprofit’s permission and the privacy of people whose content appears on the site.

System overviewConceptual
  1. VisitorResponsive UI
  2. FlaskApplication
  3. FirestorePersistent data
  4. Cloud RunDeployment
Conceptual component map. Cloud Run hosts the application; the map is not a request sequence.

My contribution

What I worked on

  • Worked with nonprofit stakeholders and incorporated their feedback.
  • Developed the Flask application and responsive HTML, CSS, and JavaScript interface, with Firestore for persistent content.
  • Deployed the website on Google Cloud Run and configured its custom domain and DNS.

Technical choices

The choices behind the work

A managed database and cloud runtime reduce the infrastructure the project needs to own, but the application still needs clear rules for user content and data access.

Looking back

Results & current status

The website is live at postofjoy.org. This was a collaborative project.

Testing and evidence

Stakeholder feedback informed iterations. No formal accessibility audit, load-test figures, or user study results were supplied for the nonprofit application.

What I learned & what comes next

Deployment is part of the product story. A useful follow-up artifact would connect one specific stakeholder request to the resulting interface change and explain the responsibility for ongoing maintenance.

Keep exploring

More engineering work.

All projects