|Title:||Need for “listings” functions to support series surfaces architectural problem|
|Last Modified:||2019-04-07 21:14:56|
|Version Found In:|
joel added on 2019-04-06 20:58:06:
There should be tag functions available for use within the doc of a Series
joel added on 2019-04-06 21:08:39:
Re: #1 above, there are two approaches I see.
One, initialize the db connection earlier, possibly in tags-html.rkt (conditional on HTML being the current output target).
Two, define metas within a series that would govern how its child articles are displayed, and then call functions in the template based on those metas.
I’m leaning towards the first approach, because it gives author-me a lot more freedom in whether and where to put article listings. I could put them before, or between, or after other content in the series page. Or even omit them altogether, resulting in a series where you can’t see the child articles except by discovering them individually.
joel added on 2019-04-07 17:47:37:
If I do go this direction, I will need a way to protect the HTML strings from later being escaped by
Right now I am thinking of enclosing the strings in a
joel added on 2019-04-07 17:47:51:
Re: #2 above: the cache db only stores HTML right now so the listings functions can’t return anything except HTML.
Once I actually start working on the print side I can think about what the listings functions should return in that context, or whether I should just make them return empty strings.
joel added on 2019-04-07 21:14:56:
Resolved with [e493f1c6]: