GearHead

A social network for those who live and breathe cars

An online community where car enthusiasts share their vehicles, meetups, modifications and stories. Feed, profiles, virtual garage and events by region.

Platforms
Web · WebApp
Year
2026
Status
In development
Role
Full stack — API and front

GearHead is a social network for people who live and breathe cars. Everyone builds a virtual garage with their cars, trims, horsepower and mods, posts project updates, joins clubs by style and RSVPs to meetups and track days in their region.

The project started as two parallel applications hitting the same database. It was reorganized into a monorepo with clear responsibilities: the Laravel API with JWT is the only thing that talks to PostgreSQL, and the plain PHP front end, with its own router and Portuguese, English and Spanish translations, consumes everything over HTTP.

What the system does

  1. Virtual garage

    Cars with make, model, year, trim, color, horsepower and a list of mods, with a main car on the profile.

  2. Community feed

    Posts with images, likes and comments, in the main feed or inside a club.

  3. Clubs by style

    JDM, Muscle, Euro, Off-Road, Classic and Track Day, with owner, admins, members and their own wall.

  4. Meetups and events

    Meetups, track days and trails with date, place, attendee limit and RSVP, filterable by type and period.

  5. Friends and messages

    Friend requests and private conversations between members.

  6. Three languages

    Interface in Portuguese, English and Spanish, with language and time-format preferences per user.

How it was built

Frontend
PHP puroRoteador próprioi18n pt/en/es
Backend
Laravel 12JWT (tymon/jwt-auth)
Data
PostgreSQL

Technical challenges

  1. Decoupling the front end from the database

    The front end read and wrote PostgreSQL directly with PDO, alongside an API nobody used. The migration moved every read and write to API endpoints and completely removed direct access and the legacy SQL.

  2. Authentication across two applications

    The JWT is obtained at login and kept in the front end's PHP session, which still handles session, CSRF and flash messages. The API doesn't know the session; the front end doesn't know the database.

  3. Consistent counters

    Club members and event attendees are shown in long lists, so they're denormalized and must be updated together with every join, leave and RSVP.

Need something
like this?

Tell me the idea or the problem. I help shape the solution and build it from the API to the app.

Let's talk