One project, several views
The same project can appear in a preview card, a filtered list, and a detail dialog. Copying its title, description, and repository link into each component creates several opportunities for those details to disagree.
A shared typed collection gives every view the same starting point. Updating a technology or correcting a link then becomes a single content change.
Model meaningful choices
A category can be represented as a union of supported values instead of an unrestricted string. This lets the editor catch a misspelled category before a filter quietly excludes a project.
The same principle applies to visual variants and article slugs. Types describe the choices that the interface really supports, while the UI remains responsible for presenting them clearly.
Keep structure separate from presentation
A project record should describe the project rather than prescribe every detail of its card. This leaves room for a compact listing, an expanded dialog, or a different layout without rewriting the content.
For a personal site, a small local content file can be enough. The goal is a structure that is easy to understand and maintain, with complexity added only when the site needs it.