Addie Wu

This seems interesting. I'll look into Ploomber and Soorgeon and see what we can get.

This is something worth discussing and might be useful in the notebook applications. I think the SRS is supposed to build in the same structure and that's why we have...

@cd155 I just noticed that the Purpose of Document Section has done something similar. It displays the contents based on the number of given elements. ```haskell - | Constructor for...

I'll fix the build failed in the next few days.

I noticed this issue when updating the GlassBR example. It builds the ``Terminology and Definitions`` section with an independent ``termsAndDesc`` subsection instead of the standard ``TermsAndDefs`` constructor. The original code...

Despite it is an enumerated list, the way this section are built is also different from the others. The point might be whether we would like to keep the grouping...

Yes, if we use the current constructor of ``TermsAndDefs``, we can't add ``[Contents]`` (i.e., grouping definitions) for each concept. I believe a ``ConceptChunk`` only allows one sentence to define the...

I'm not sure what the middle ground is supposed to be. ``TermsAndDefs`` doesn't support anything other than ``Concepts``. If we are not making changes to the section definition itself, should...

I think we do need to indicate the parent of all sections, but this might be another designs. The first thing might be adding a ``UID`` in the section representation?...

Oh, it seems to be feasible. So it would be like first creating a tree data structure in the ``drasil-lang`` (maybe?) and then build the tree explicitly in each example....