Dave Luebbert has been posting to the Frontier-user list about the way nodes that have sub-elements with types are rendered. They're not really bug reports, because the way the software works is inconsistent, and how that will be resolved is something that I want to think about.

Right now you probably shouldn't put typed nodes under typed nodes. The software will see each typed node as something it should link to -- turning the parent page into an index. If what you want is an index, you're better off using an index type node.

I got burned by this today when I was posting the transcript of conversations I had in Twitter. I expected them to be displayed as an outline because they were contained within a node with a type attribute of outline. But because they had types on them, it was displayed as an index. So I used the script I wrote the other day for Dave that removes the types and got what I wanted.

The software is confused about this because I was confused about it when I was implementing the software. I want to spend some time thinking about this before doing anything.

I've turned comments on for this worknote so if you have any questions about what I'm saying, you can ask here.