I'm still a little bit puzzled by the region structure. For example something I'd like to do right now is modify the vertical margin betwen two regions but only when these two regions are definitions (type, module, val, etc.), which seems horrible to do from a css perspective (maybe the regions should be classifed, e.g. with a def class).
It's also a little bit strange that in a signature headings are in .doc .region h1 rather than .region .doc h1. This would make things much more regular in a signature. I think we should be able to come up with a simple high-level page description in one or two paragraph. Things like a module signature is a list of .region each of these .region can be one of bla bla bla.
I'm still a little bit puzzled by the region structure. For example something I'd like to do right now is modify the vertical margin betwen two regions but only when these two regions are definitions (
type,module,val, etc.), which seems horrible to do from a css perspective (maybe the regions should be classifed, e.g. with adefclass).It's also a little bit strange that in a signature headings are in
.doc .region h1rather than.region .doc h1. This would make things much more regular in a signature. I think we should be able to come up with a simple high-level page description in one or two paragraph. Things like a module signature is a list of.regioneach of these.regioncan be one of bla bla bla.