Skip to content
Know Jaden.Say hello
← All work

F3 GLOBAL / ENGINEERING

A nonprofit website its own team can maintain.

Public-facing pages, reusable interfaces, and protected publishing tools built with a 12-person team.

MY ROLE

Full-stack developer · Triton Software Engineering

WHEN

November 2025 — September 2026

STATUS

Shipped with a team

F3 GLOBAL · BUILT TO BE USEFUL

Good work deserves
a good home.

A website. A team. A little more impact.
11features delivered across six months
12people on the project team
80%less image storage after conversion

01 / THE PROCESS

The problem behind the pages

A nonprofit website serves both its visitors and the staff who keep its information current. F3 Global needed public-facing pages, but the publishing workflow mattered too: changing an FAQ should not require someone to ask a developer.

I worked as a full-stack developer on a 12-person Triton Software Engineering team. Across six months, the team delivered 11 features using React, Express, and MongoDB.

02 / THE PROCESS

Make publishing a real product feature

I engineered an authenticated FAQ service with Express and Mongoose. Validated create, read, update, and delete endpoints gave staff a way to maintain content, while role-protected admin routes kept editing separate from public reading.

An OAuth-gated admin dashboard brought those capabilities into an interface for non-engineering staff. The permission boundary was part of the feature, rather than something to add after the happy path worked.

03 / THE PROCESS

Build patterns the team can reuse

I built more than four reusable React components, including event carousels and contact forms. Shared patterns helped standardize the interface across six pages.

Reusable components were useful here because multiple pages and teammates needed the same behavior. The aim was consistency in a real team workflow, with less repeated implementation work.

04 / THE PROCESS

Pay attention to what ships over the network

I migrated 24 images to WebP, reducing their storage footprint by 80%. Smaller assets also supported the page-loading work, though I do not have a measured load-time improvement to report.

This was a concrete improvement that did not depend on adding a new service or redesigning the application. It came from examining what the website was already sending to visitors.

05 / THE PROCESS

The outcome

The team shipped the public-facing website. My contributions centered on the FAQ backend, protected administration, shared components, and image optimization.

The useful measure of this work is not just the number of pages: staff gained a publishing workflow they could use without a developer in the middle. Feature delivery was a team outcome; the technical contributions above describe my part.

SOURCES & FURTHER READING

Role and results documented in my resume ↗

Written from project documentation and my resume. Updated October 2026.

NEXT STORY

Home-Start

Turning a nonprofit’s volunteer coordination needs into a focused portal, with a migration plan that respects decades of existing records.