ToME WikiMayLith: This thought came to me while I was tweaking the Level Feelings page.
That page currently has a subheading named "changing level feelings" which talks about coding issues related to level feelings. (And actually, coding is mentioned in at least one other place, i.e. the DESC flag.)
I think it makes sense to incorporate coding information this way (evolving yet another tree just for code seem ridiculous), but I wonder if we should evolve some sort of standardized subheading format(s) so that:
- the general, non-coding user can tell at a glance that certain portions of the TOC will not be of interest to him/her
- if you *are* after code information, you'll know exactly what part of the TOC to go to
- searching might be easier (?)
Example of headings and subheadings:
Spoilers/Level Feelings = Level feelings = = Level ratings = = Option auto_scum = = Non-standard level feelings = = Code information = == Changing level feelings == == The DESC flag ==
In the example page, the brief mention of the DESC flag could then be footnoted to the coding section. Likewise, the code section could footnote (probably via anchors so as not to cause confusion) back to the main body.
Also, it might be useful to distinguish between actual game code and LUA, e.g.
= Code information = == Game code == === Changing level feelings === == LUA == === The DESC flag === (I have no idea if it's a LUA flag or not, this is just for the sake of the example)
Maybe I'm making a mountain out of a molehill here.... Thoughts?