Do we have a distinct layout for datasets

Yes

Have a specific layout.

👍

No

• Just have the user choose their layout and give them components to that …

# Title

This is my awesome datasets.

<!- Here's a graph. Bonus would be to have this in backticks setup -->

<VegaLitChart data={} spec={} />

Here's the data list from the datapackage.yml

<FileList />

Pros/cons

• 👍 fully customizable
• 👎 pages don't look the same
• 👎 requires user to pollute their README with a bunch of components or backticks stuff
• 👎 doesn't work "out of the box" for people with frictionless data

Goal is always simplicity. What is the simplest user experience.

• Start writing a README.md
• Reference a data file (even one on the web)
• It just works

Why would i create a data package yaml?

• I want to reference external data
• I need to set the types of the fields

Notes 2024-02-28

Having just one layout for both datasets and stories

S:

• Two layouts: story, dataset
  • Story: just render the page as it is
  • Dataset: this is a Frictionless dataset and use a more dataset layout plus use the datapackage.json
• In the past seemed clear we wanted 2 layouts …

But why do people want a dataset layout?

What do i want when i publish a dataset?

• Description etc
• Graphs etc
• I want to see the data files

Aside: What do i want when i'm noodling around with data …

Issues with classic dataset layouts

• Very busy - see kaggle
• Overwhelmed if lots of data files

Imagine no dataset layout

• People have to create their dataset page themselves
• Have a data tab that shows content from datapackage.json

If we were doing the simplest thing possible …