Good morning. I've filed a Jira for this task: http://issues.fluidproject.org/browse/FLUID-778
If anyone has spare time to suggest a style, please attach it to the Jira. I'll hopefully get around to it next iteration. - Jonathan. 2008/6/13 Allison Bloodworth <[EMAIL PROTECTED]>: > Hi all, > I did ping Jonathan about the headings, so I believe he will be looking into > that. Thanks Paul for the "How To" link! I have also found many reasons that > it would be helpful to upgrade Confluence (e.g. reordering child > pages: > http://www.nabble.com/Changing-the-order-of-child-pages--tt16993065.html#a17208242) > so here's a big thumbs up to an upgrade! +1 > Thanks Anastasia for looking into it! > Allison > On Jun 6, 2008, at 3:32 PM, Paul Zablosky wrote: > > The Confluence manual describes how we can create our own custom themes and > apply our own CSS. But before we put in too much work on our current > version of Confluence (2.5 I believe), we should look into what it would > take to upgrade to the latest release. There's a lot of new flexibility and > features that could be of use to us, particularly with navigation. > > By the way, I have often picked whatever heading size looked right on the > page, just as Daphne did, without worrying about skipping intermediate > levels. This usually doesn't cause problems. The solution to the current > problem might be a smarter {toc} macro. > > Paul > > Jess Mitchell wrote: > > Like Daphne said, anyone able to dig into the CSS of Confluence and make > bigger distinctions among our header sizes? I may be making this up in a > fog of jetlag, but I think Allison was going to ping Jonathan about this? > But if anyone else has any ideas, that'd be great. > J > On Jun 6, 2008, at 2:20 PM, Daphne Ogle wrote: > > Great, thanks Paul! > Allison, Jess and I were chatting yesterday about the minimal distinction > between headings in our current wiki look -- which is the reason I've > skipped a heading in the page. I wonder if a better solution would be to > change the format of headings? Is this even possible? > -Daphne > On Jun 5, 2008, at 3:42 PM, Paul Zablosky wrote: > > Daphne, > I did a few experiments with the {toc} macro. It appears to just set up > a fixed set of tab indents, one for each level of heading hierarchy. If you > give it a range as Anastasia suggests, it just sets them up for that range. > Since your page uses only h2 and h4 headings, you can make the toc listing > look a bit better by reducing the indent between them, say with > {toc:minLevel=2,indent=5px}. > > Paul > > Anastasia Cheetham wrote: > > On 5-Jun-08, at 11:44 AM, Daphne Ogle wrote: > > > > Here's an > example:http://wiki.fluidproject.org/display/fluid/Inline+Edit+Design+Overview > > I don't see any code that is shifted the 1st level bullets over but it > doesn't seem like that would be the default formatting. Any ideas? > > > Daphne, I tried a change that seems to improve it. > > The issues is that the headings that the ToC is generated from are > actually staring at 2nd level, not first, so they are being indented. > I set the {toc} macro to start at level 2 ({toc:minLevel=2}). This > seems to prompt it to treat these 2nd level headings as top level ToC > elements. > > > > > Daphne Ogle > Senior Interaction Designer > University of California, Berkeley > Educational Technology Services > [EMAIL PROTECTED] > cell (510)847-0308 > > > _______________________________________________ > fluid-work mailing list > [email protected] > http://fluidproject.org/mailman/listinfo/fluid-work > > > _______________________________________________ > fluid-work mailing list > [email protected] > http://fluidproject.org/mailman/listinfo/fluid-work > > Allison Bloodworth > Senior User Interaction Designer > Educational Technology Services > University of California, Berkeley > (415) 377-8243 > [EMAIL PROTECTED] > > > > > _______________________________________________ > fluid-work mailing list > [email protected] > http://fluidproject.org/mailman/listinfo/fluid-work > > -- Jonathan Hung / [EMAIL PROTECTED] University of Toronto - ATRC Tel: (416) 946-3002 _______________________________________________ fluid-work mailing list [email protected] http://fluidproject.org/mailman/listinfo/fluid-work
