Jacques Carette
Jacques Carette
I meant that the code would look like ```haskell refsec :: DocSection -- or whatever the right type is refsec = RefSec $ RefProg intro ```
So there are technical details that I may have gotten wrong from our current code base - sorry. The main message is that I'd like each (sub)section to exist as...
The part with `tocTree` makes sense. The part with `mkSRS` seems odd. It seems redundant, i.e. repeating the same information.
I was expecting that some of the higher-level routines (like `mkSRS`) would need some adjustment to keep working. "Printing" the new data-structure is going to need a bit of state...
Right. Yes, I'm fine with merging as is. Which PR?
Yes, it is too simple. I think we will need a multi-pass process that first assembles a particular "kind" of information, then transforms it (with a recipe), then adds more...
There is definitely a lot of confusion begin pointed out here. There is definitely 'disconnect' between the various pieces of code. So, starting from the top: - `ch` and its...
Great explanation. And explaining the current design is going to take more than just a few minutes, so I'll come back to this later. But quick idea: think of it...
The more I think about this, but more I feel like going to structured `UID`s is going to help. The point is that there is a single concept being captured,...
@bmaclach I think Drasil now has some features close to this. Can this be implemented now?