What belongs in a project card?

A project card should answer three questions quickly: what is this, why might it matter, and where can I inspect it?

That is why a useful card needs more than a screenshot and a title. A short description gives the work a point of view. A small stack label sets expectations. Separate links for source code and a live preview let a visitor choose the depth of exploration.

The visual treatment should support that information rather than hide it. Images can create the first impression, but text and labels are what make a project credible after the first second.