A recruiter usually spends very little time on a first pass. That means your project page needs to answer a few questions quickly: what did you build, why did it matter, what decisions did you make, and what happened because of it.
I structure case studies around problem, role, approach, stack, tradeoffs, and results. That order works because it mirrors how hiring teams evaluate practical ability and ownership.
The biggest mistake is treating a project like a feature dump. Instead of listing everything you used, highlight the few choices that prove judgment. Clear writing often signals seniority even before deep technical review begins.