Anne van Kesteren wrote:
fantasai wrote:
Also, <link rel="next/prev/toc"> generate navigation links in the
content,
so if you are writing a documentation series, you can <link> them up and
the DevMo build system will expose those links in the body HTML.
Does this mean that you are going to style these metadata elements in a
way that they become normal navigation without providing normal
navigation in the document? Or is there a template parser that looks for
LINK elements, takes over the contents and puts them in the document in
a much more appropriate UL, LI element construct?
Actually, the <link> is the much more appropriate construct. It's just not
the much more practical construct.
The wrapper code calls a function that parses <link> and <meta> elements
and hands all the metadata back to the wrapper in a useable datastruct.
The wrapper can then pull out info about the links from the datastruct
and generate appropriate HTML in the <body>. The <link> and <meta>
elements are left intact.
You can see what happens by looking at the /about/meta page: all the
<body> content before the <h1> and after the last <pre> is generated by
the wrapper.
~fantasai
_______________________________________________
mozilla-documentation mailing list
[email protected]
http://mail.mozilla.org/listinfo/mozilla-documentation
