Jose Gonzalez Gomez <[EMAIL PROTECTED]> writes: > Another question... is there any reason for mapping section and > subsection to h3 and h4 instead of h1 and h2?
Maven uses the style.tigris.org CSS stylesheets which were created by Todd Fahrner and co. This stylesheet defines h2 even though we don't use it over in Maven-land. h2 sections are rendered as large black text on a white background. I.e. does not have the reverse video look of h3 and h4. As a result, when I made the mapping of the style CSS to Maven's xdoc, I opted to not use h2 because I felt it didn't look as good. You can provide your own stylesheet and override the one provided by Maven if you want more control. In addition, you can also just drop HTML files in the xdocs directory and they'll be copied over as is to the final documentation directory (actually, any non-.xml file is treated in this manner). Thus, you could write your own docs in HTML and use the Maven stylesheet and have access to all of the header styles. The only drawback to the above approach is that your documents will not be automatically integrated into the site. I.e. you'll have to add the nav bar to the page, the banner, etc ... At some point, we need to re-evaluate how we generate the site documentation to be more flexible at the integration level rather than force everyone to use the inflexible xdoc format. xdoc is a great format for simple things like the reports Maven generates and simple documentation, but forcing everything to xdoc for site integration is not a good thing. I'm not proposing to get rid of xdoc, but rather find a different way of integrating the site nav bar and banner to any type of user-supplied docs. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
