Review the landing page

[coreation]

Currently portals with 200-ish datasets are no longer an exception, perhaps we should think about the following:

• AJAX calls for filtering
• Introducing tag/key-words
• Switching between landing page views (list, grid based on keywords, ...)
• Filtering that takes the tag into account

Feel free to add your thoughts about the best UX we can provide to quickly give an overview of the available datasets.

[coreation]

I think we should see the broader picture and think about how meta-data (dcat, tags, ...) can be identified (using groups e.g. as we're doing now?) and used in the UI/API. It would also be handy that lists (e.g. languages) can be declared in the model itself because not all option lists will be accessible via URI (e.g. draft/published)

[pietercolpaert]

+1

[coreation]

Implemented by #395