Closed regisphilibert closed 5 months ago
I like this idea a lot and I think this is what I was originally hoping for. So the layout would take some data feed (in yaml format if need be, otherwise maybe json or csv). Each card layout would take parameters from the data feed. Then we could filter by specified fields in the data feed.
Well currently the data structure is very different from one source to the next... So we have to know what keys goes where (eg: currently the Workshop title is their venue
in the feed while Lessons uses name
from the data file) which makes each "feed to filter" solution not quiet reusable among different content types.
If the sources (data or feed) were consistently structured eg: expecting a title
, subtitle
, desription
, metas
(for tags with icon and filters) etc... We woudn't need the "transformer" step and could build something reusable to populate both the cards on the page and the filters.
Currently we need to set the feed (doable in front-matter) and the transformer partial, which is also doable in front-matter but a bit overhead and error prone.
We could have data match a standardized format. We'd ensure that any transformations needed happened outside of the website build (in the process of building our own data feeds).
See in #68 and later the blog
Currently the filters really revolves around workshops, we should make this layout agnostic. It should take a feed parameter and maybe a list of filters. not sure.