◊(Local Yarn Code "Ticket Change Details")

Overview

Artifact ID: 953b2b06728a9165857e020c88f9089fcfd29ca5dbc2edf5df01ba0780d97ef6
Ticket: f580d19482db99f2541c19f926d2a840ec4dce97
Need for “listings” functions to support series surfaces architectural problem
User & Date: joel on 2019-04-06 21:08:39
Changes

  1. icomment:
    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.
    
  2. login: "joel"
  3. mimetype: "text/x-fossil-wiki"
  4. priority changed to: "Immediate"
  5. resolution changed to: "Open"
  6. status changed to: "Review"