improve content page curation strategy

[jbolda]

Currently we are "manually" entering the information to curate specific podcast episodes, and merging it with curated articles. We want to continue curating, but make it easier to enter (and less prone to error, see the article array reference).

@jorgelainfiesta, should we expect to pick specific articles and podcasts? Or are you most interested in the most recent of both? I think if we want specific articles/podcasts, we could have an array of slugs in gatsby-node.js or gatsby-config.js (a matter of preference really).

[jbolda]

In #141, I have moved some of the podcast curation data into a query to make it more dynamic. The current strategy is the "most recent 6 podcasts" effectively. The only remaining piece that isn't dynamic is the images. We have those within our repo and the paths hardcoded.

Will every podcast have an image? I imagine we will want to tie these images to the podcast more directly somehow. As of right now, if the podcast stops being featured, it will lose its image reference. @jorgelainfiesta will every podcast have an image? I suspect the answer here is "no", and this makes me think that the answer here is a curation.yml file that we use to specify the blog posts and podcasts which should be featured. In there, we can also reference images for any podcasts that have them.