At the moment, the content before the the first subsection is a loose collection of stuff, but it makes sense to group that into its own node.
Not only would this make selecting the whole block easier for editors that allow that sort of thing, it would also be the natural scope for ~ temp variables (which currently I have to determine by iterating children until the next subsection starts).
Example (proposed new (head …) node indicated in comments)
//(head
// title: My cool story
VAR myvar = false
~ temp mytemp = true
It was a dark and stormy knight. -> Knot
//)
== Knot ==
//(head
Hi, I'm the knot content.
* Cool.
* Not cool
//)
= Stitch
Whatever
At the moment, the content before the the first subsection is a loose collection of stuff, but it makes sense to group that into its own node.
Not only would this make selecting the whole block easier for editors that allow that sort of thing, it would also be the natural scope for
~ tempvariables (which currently I have to determine by iterating children until the next subsection starts).Example (proposed new
(head …)node indicated in comments)