A project page should explain the work without turning it into a sales pitch. The useful question is not whether the idea sounds persuasive. It is whether it helps someone understand the work, make a decision, or complete a task with less friction.
What is happening
Images show quality but not context. Long claims add context but can crowd out the evidence. A useful page balances both.
This tends to become visible at the boundary between the organization and the person encountering it for the first time. Internal familiarity hides effort that remains obvious to a customer, reader, applicant, or collaborator.
A practical response
State what the project is, what needed to become clear, how the response was shaped, and what the finished system enables.
The aim is a smaller, clearer system: one source for the record, one visible hierarchy, and one next action that behaves as expected. That approach improves the immediate page and makes later application or database work easier to add without rebuilding the public surface.