Clear explanations and a useful set of practice problems.
Fictional preview content
A private Cal Poly Mechanical Engineering hub that turns a chapter website into a useful student product: plan the degree, understand prerequisite paths, and share course experience with the people coming next.

React
application layer
Supabase
data + auth
member sign-in
Internal
product branch
Public product preview
This small interactive screen uses fictional content to show the product loop without exposing member accounts, private records, or the internal codebase.
Cal Poly ME Hub
A limited public preview
Prerequisite flow
Engineering Statics
Dynamics
Thermodynamics
Fluid Mechanics
Personal planning
Progress
34%
12 of 35 core courses
Next recommendations
SampleShared perspective
Clear explanations and a useful set of practice problems.
Fictional preview content
Challenging material, but the course structure makes the expectations clear.
Fictional preview content
Backend architecture
The important work in this branch is not just the interface. It is the boundary between a member, their academic plan, and a shared body of course knowledge.
01
Supabase Auth establishes the member session once at the application boundary. Internal routes stay behind the same access gate instead of duplicating login checks page by page.
02
The curriculum record stores completed, in-progress, and discarded courses, planned terms, catalog mode, concentration, technical electives, and profile details for each user.
03
Members can browse and add professor reviews with ratings, difficulty, term, written feedback, and would-take-again signals. Course pages read the same records directly.
04
The internal branch changes the product surface from a public chapter site into an ME student hub while keeping the academic tools focused and member-only.
Data flow
Google OAuth returns a Supabase session.
The app fetches the signed-in member's curriculum row.
Flowchart and dashboard actions update local state immediately.
Changes are debounced and upserted back to Supabase.

Product surface
Engineering boundary
The internal branch already proves the core loop: authenticated users can change meaningful academic state and see it again later. The next layer is expanding the private member experience while keeping sensitive academic content behind the access boundary.
Private case study
Internal product / Theta Tau SLO