Jacques Carette
Jacques Carette
Thank you -- this is exactly what I was asking for you to dig up. We should standardize this! @smiths , your turn!
We want each table to be readable on its own. And redundancy / duplication of information in user-facing documents is **good**.
Right, now I remember why GlassBR is different: the information to present in that section really is 'different', and organizing it the way it is leads to a better presentation....
Hmm, I don't think changing `ConceptChunk`, at least for this purpose, is the right thing. This seems closer to a display issue, not a structuring one. One possibility is to...
Should go in a 0.3.0 milestone.
The longer term may be this summer. I think this is a great example for illustrating "what this sentence means" kind of knowledge capture. I'll assign this to myself right...
I'm not sure I fully understand, so what I propose here might not fit. I think that all sections should have a 'parent' field, indicating what it is a sub-section...
Yes, adding parents by `UID` is probably a good idea. A quick hack for nesting would be to build a Rose Tree (of DocSection) as the input. The tree would...
Yes to first creating a tree data structure. You might as well use https://hackage.haskell.org/package/rose-trees-0.0.4.5 instead of creating a new one. Not sure I understand the "in that case", but let...
Why not reuse the one from the package I linked? That would give you quite a few functions "for free" at the same time. Furthermore, you should build 'smart' constructors...