Best practice: 100 projects as a pure archive without detail pages – create as pages or as a structured list?

The CMS Questions
1

I want to output a chronological project archive of ca. 100 entries in Kirby. The projects are only displayed in short form and are not clickable (no detail view, extra page). They appear on an overview page and sometimes also on the home page.

Short form of each project entry: image, title, customer, category (1×), year, description, tags (1–3×).

Now the question: What is the most best way to create these project archive?
A) As individual pages (without linked detail pages) or
B) as a structured list (e.g., structure field/YAML/JSON in a page, or otherwise as a “dataset”)?

I’m interested in best practice in Kirby: What is the most robust, easiest to maintain, and quickest to implement?

2

I’d use pages, more robust, easier to handle.

3

So these are all listed out on one page and the indvidual projects are not to be viewed directly by URL?

If thats the case i would consider implementing a little custom route that bounces a direct hit back up one level to that project in the overview list. I think you can redirct to anchor on the page.