This could be an underlying facility for #40 or #41 where the source of a page could describe an API endpoint (ideally serving a JSON object) and some form of templating to display data.
each issue in issues
li= issue.name
a(href=issue.link) issue.description
This should be fairly easy with Metalsmith and the metadata plugin after an API fetch to file step, or by creating a plugin that directly consumes the API at each generation run (which could be based on the contentful or primsic metalsmith plugins which do this).
then the issue list could be transcluded from a page with :[](/issues)
then an individual issue could be transcluded with the awesome syntax :[](/issues#2) (related to #32 for transclusion of fragment blocks)
This could be an underlying facility for #40 or #41 where the source of a page could describe an API endpoint (ideally serving a JSON object) and some form of templating to display data.
For instance:
/issues/index.mdpage with:/layouts/issues.jadefile such asThis should be fairly easy with Metalsmith and the metadata plugin after an API fetch to file step, or by creating a plugin that directly consumes the API at each generation run (which could be based on the contentful or primsic metalsmith plugins which do this).
:[](/issues):[](/issues#2)(related to #32 for transclusion of fragment blocks)