Giving each view a role

From one resource type to the next, no overview shared the same structure. Each accumulated whatever people wanted to show, with no common rule on how information should be distributed across views.

Two examples are enough. The overview of a data product displays the full list of its datasets; that of a dataset displays its entire schema. With five hundred columns or a long list, the view loses its purpose: to identify the resource and understand whether it meets the need before exploring its details.

Rather than fixing each page, I proposed revisiting the architecture of resources from a simple rule: each view has a role.

• The overview makes it possible to identify the resource, understand what it is for and reach the relevant actions.
• Raw and exhaustive content lives in dedicated views: for a dataset, profile, schema and data preview views; for a data product, a filterable list of resources.

I propose writing this rule into the design system of the unified experience as shared page templates. Applying them must take into account the information needed to evaluate each resource type.

A rule like this cannot be imposed all at once. The obstacle is simple: applying it means reworking every resource type, a heavy undertaking. I propose two ways to make it manageable: apply the model progressively, one resource type at a time, as each evolves; and go through templates, so that each type adopts the shared structure without being redesigned from scratch.