000%
Ali Saad / Creative systems practiceSignal acquired
DestinationDestination
Destination / Destination11 / route handoff

All projectsW—09 / 11

Aside

Solo Ironhack final project: a MERN app for cohort discussions, shared learning resources, and traceable resource copies. Selected as the best final project in my cohort.

Open Live App
Aside
OverviewGalleryThe buildOutcome

Overview

Role
Full-Stack Developer & Product Designer (Solo)
Client
Ironhack · Solo final project
Year
2026
Frontend RepositoryBackend Repository

My contribution: I designed and built Aside independently as my final project at Ironhack, covering the product design, React frontend, Express API, MongoDB data model, authentication, file uploads, and deployment.

Aside gives a bootcamp cohort one place to discuss what they are learning and keep the resources worth returning to. The Commons contains posts, threaded comments, mentions, and a member directory. The Library holds resources with text, code, links, and files, organized into personal folders.

Members can copy a shared resource onto their own shelf through a fork. Each fork keeps a reference to its source, and a lineage view makes that relationship visible. Members can build on one another's work while preserving its origin.

The frontend uses React 19, Vite, and a custom design system built with CSS custom properties. The backend uses Express 5, Mongoose, MongoDB Atlas, JWT authentication, and Cloudinary uploads. Resource visibility is included in database read queries, covering lists, search, folders, and lineage views.

The application requires an account to access cohort content. The screenshot walkthrough covers the Library, a resource, a personal shelf, the lineage view, and The Commons. The frontend and backend repositories document the implementation and its known limitations.

The challenge +

The main engineering challenge was applying private or cohort visibility consistently across resource lists, search results, and lineage views. I built a shared visibility filter and combined it with each read query so the API returns resources within the viewer's permitted scope.

Combining filters with $and preserves separate $or conditions that could overwrite each other if merged with object spread. This keeps the search criteria and the access rules together in the database query.

A second challenge was defining what happens when related content is deleted. Folders containing resources cannot be deleted; forks remain after their source is removed, with the source reference cleared; comments and bookmarks are removed with their parent. The repositories also document that this cleanup runs outside a database transaction.

Gallery0102030405—05
Aside Library with a search field, category and tag filters, and resource cards.
Aside Library with a search field, category and tag filters, and resource cards.
Browse the shared Library
Aside member profile with a bio, skills, personal folders, and a New Folder control.
Aside member profile with a bio, skills, personal folders, and a New Folder control.
Organize a personal resource shelf
Aside Commons showing a post composer, attachment options, and a discussion feed.
Aside Commons showing a post composer, attachment options, and a discussion feed.
Keep the conversation in The Commons
Aside People directory with a search field and member profiles.
Aside People directory with a search field and member profiles.
Find people in the cohort
Project frame 5
Browse the shared LibraryOrganize a personal resource shelfKeep the conversation in The CommonsFind people in the cohortProject frame 5↓

Thebuild

01

Resource Forking & Lineage

I built a resource model that lets a cohort member copy a shared resource onto their own shelf while keeping a reference to its origin. The lineage view follows these relationships so members can see where a resource came from and what others have built from it.

Personal copies with a traceable origin

02

Query-Level Authorization

I implemented a shared visibility filter for private and cohort resources. It is combined with read queries for lists, details, search, folder contents, profile shelves, fork sources, lineage, and resource comments.

Shared visibility rules across resource read paths

03

Search with Visibility Filters

The resource search combines MongoDB text matching and the viewer's visibility filter with $and. Keeping both conditions in the query ensures that text matching uses the same access rules as the rest of the resource API.

Text matching and access rules in one query

More details (3)
04

404 Instead of 403

When a resource falls outside the viewer's visibility filter, the API returns 404. This avoids confirming its existence through a separate 403 response.

Unavailable resources return 404

05

Deliberate Relational Cleanup

MongoDB has no cascade delete, so every cleanup path is explicit and chosen by whether the child has a reason to exist alone. A folder holding resources refuses deletion; forks survive their origin with the pointer nulled; comments and bookmarks are deleted alongside their parent.

Restrict, nullify, and cascade — one per relationship

06

The Commons

The feed side carries posts with optional attachments, threaded comments, mentions, and a searchable cohort directory. Comments are two separate models with ordinary reference fields rather than one polymorphic model, so every reference points at a known collection and neither can be aimed at the wrong thing.

Posts, comments, mentions, and a member directory

Outcome

Aside was selected as the best final project in my Ironhack cohort and qualified to be presented at the Ironhack hackathon.

I delivered a deployed MERN application with cohort discussions, resource publishing, personal folders, resource forking, and a lineage view. The React frontend is hosted on Vercel and the Express API on Render.

The repositories explain the authorization model, data relationships, and deletion rules. They also document current limitations: denormalized counters, cleanup outside a transaction, stemmed-word search, and forks that preserve their origin without syncing later changes from the source.

Recognition
Best final project in the cohort
Data Model
7 Mongoose models, forks as a self-referencing graph
Access Model
Private or cohort, enforced inside every query
Authentication
Token required except signup, login, and health check
Deployment
React on Vercel, Express API on Render
Team
Solo build
Next projectW—10 / 11

WinDock

View project
WinDock
Have something worth building?Start a project
aliihsaad1@gmail.com
InstagramLinkedInGitHubFacebook
© 2026 Ali Saad