Addie Wu

I add a rose tree data structure in ``Langauge/Drasil/Document.hs``. ```data SecTree a = Node a [SecTree a]``` And I was thinking to build a ``SecTree DocSection`` in each example, which...

I don't think ``refsec`` is defined in Drasil. Or do you mean ``refSec`` in ``DPLate``? The type of all section variables is like ``RefSec -> DocSection``; it should take parameters...

I don't think we have that in the current code. The one we have is the original definition in ``Core.hs``, which is ```newtype RefSec = RefProg Contents```; however, we export...

Also, I would like to define the ``TableOfContents`` like this: ```haskell newtype TableOfContents = ToCProg (Tree DocSection) ``` The ``DocSection`` here is the one defines in ``Core.hs``. In ``DocDecl.hs``, we...

> The main message is that I'd like each (sub)section to exist as an independent `DocSection`-valued Haskell named entity (whichever version of `DocSection` is the 'right' one for the job)....

`mkSRS` is the original one that exists now, the only change I made is the first line ```TableOfContents $ ToCProg tocTree,``` to build the section. Besides, I found a problem/technical...

I see. So we should stay with the tree approach and adjust the current language and structure for it, right? However, I still finished the code of the nested section...

Yes, the "i" is part of the symbol. I was thinking about the pattern matching, but we actually don't know whether the superscript is part of a symbol or an...

I think it is able to check if we define them differently since they both fall into the "Sup" category now.  When it encounters a superscript, the second expression...

@balacij Some of these changes are in another branch. I'm currently cleaning up my code, and I will delete this branch (all my branches) after I have merged everything into...