Update pages template

[matamadio]

For RDLSv0.3 (and following versions) it would be great to adjust/improve the page template.
I will post a mockup to how it should look, but meanwhile @lydiascarf could you point me to all the files that contribute to building the dataset page?

I guess the page structure is specified by dataset.html and default.html, but what about the attributes mapping?

[lydiascarf]

@matamadio here are the key files:

• _data/schemas/rdl-03.yml is the UI schema. This won't correspond 1:1 with the data schema, but it describes the schema of the markdown YAML front matter that will be available in the page template after import.
  • some of the dataset_fields in the UI schema will refer to templates in _includes/display using the display_template. these HTML files are templates for rendering specific dataset fields and they will use Liquid just like the page templates. we can version these like so: _includes/display/project_v03.html then reference the correct template in the UI schema.
• _layouts/dataset.html is the dataset page template. to use versioned page templates, we will need to change this to be _layouts/dataset_v02.html and create a new _layouts/dataset_v03.html, then the v0.3 markdown files will need to have a new field: layout: dataset_v03 to match the new layout file. the import script can handle this for new entries and i can manually update any v0.3 entries that get merged before this is done. the older files can just default to v0.2. defaults are set in _config.yml
• finally, rdl-datasets.json is used by JavaScript files to filter and search through site.datasets. this will need to be modified a bit to accommodate multiple simultaneous schema versions. we'll need to include conditions for searchable/filterable fields that differ between schema. currently, that just includes project and creator.

[matamadio]

Ideas to improve the main dataset page:

• Geo-coverage to be more visible
  • Colored Labels for global/regional
  • More elegant for long countries list
• Use short code for licensese

[lydiascarf]

If this is also covering UI updates for the datasets page, now the landing page, I'd like to suggest we add a loading indicator to hold space while the datasets load.

[matamadio]

If this is also covering UI updates for the datasets page, now the landing page, I'd like to suggest we add a loading indicator to hold space while the datasets load.

Agree this would be nice!

[matamadio]

Proposal for the dataset index page: having colored labels on top of title for:

• geo scale (global, regional, national, subnational, urban)
• country(s) name(s)

Also:

• more compact font size and spacing, so that more dataset are seen per screen
• Use license code instead of full name. Place code on the bottom right side of the item card

Improvements:

• Coverage level as a prominent color-coded badge for quick scanning
• Country name is displayed as a clean label instead of "Geo-coverage: Country"
• Labels appear above the title for better visual hierarchy
• For global datasets, only the coverage level label is shown (no country)
• Cleaner, more modern appearance with better use of space

[matamadio]

Please see new mockup proposals for dataset index:

• Proposal 1: Friendly mockup-comparison.html

• Proposal 2: modern minimal

• Proposal 3: balanced mockup-balanced.html

[matamadio]

@pzwsk @stufraser1 please have a look and express a preference or suggest changes.

I vote for 3 - good balance in color framing, few symbols (country flags), visual clarity.

[pzwsk]

Thanks a lot Mat, looks nice. I prefer 3 as well. Let's also keep some consistency with the Risk Data Library website in terms of visual identity, colors, fonts, logo, icons, etc.

[matamadio]

Reminder: use the same footer as RDL website.

[matamadio]

New mockups!

• Revised layout
• Revised color codes, logos and footer (similar to RDL website)

mockup-dataset-page.html
mockup-index-page.html

Palette for risk components:

• Hazard: #007fc3
• Exposure: #00cbab
• Vulnerability: #ffc757
• Loss: #f3436a

[matamadio]

Would be great to get a bunch of review and comments on the mockup.
The actual implementation is postponed after:

• RDLS v1.0
• Agreement on tamplate layout and metadata fields to be shown
• JKAN functionality update (Sidebar filters shouldn't fully reload the page #57, Fix/Remove count labels from filters #76)