--- Dave Newton <[EMAIL PROTECTED]> wrote:
> Hmm, that says not to use the "h1" heading, so never mind. I'll look at
> either {toc-zone} or some of the reporting stuff to see if I can be
> appeased.
{toc:...|minLevel=2} will start the TOC at h2, so that's fine.
Sorry for the noise.
d.
>
> Than
It's a working guideline, not gospel. If the toc stuff implies we
should use h1, then let's start using h1.
On Jan 25, 2008 8:49 PM, Dave Newton <[EMAIL PROTECTED]> wrote:
> Hmm, that says not to use the "h1" heading, so never mind. I'll look at
> either {toc-zone} or some of the reporting stuff t
Hmm, that says not to use the "h1" heading, so never mind. I'll look at
either {toc-zone} or some of the reporting stuff to see if I can be appeased.
Thanks,
Dave
--- Ted Husted <[EMAIL PROTECTED]> wrote:
> We might also want to keep the Style Guide and Colophon updated with
> any changes or new
We might also want to keep the Style Guide and Colophon updated with
any changes or new approaches.
* http://struts.apache.org/2.x/docs/documentation-style-guide.html
HTH, Ted.
On Jan 25, 2008 1:45 PM, Dave Newton <[EMAIL PROTECTED]> wrote:
> Howdy,
>
> I'd like to suggest that we make sure to
Howdy,
I'd like to suggest that we make sure to use the right heading levels (h1,
h2, ...) on the documentation wiki pages so that we can better use
Confluence's {toc} macro. This should help make doc navigation a bit easier
and allow jumping to target sections a bit easier.
Relatively minor, but
