Inspired by reading Rich Bowen's presentation: http://www.slideshare.net/rbowen/write-a-better-fm which everybody should read!
----- Original Message ----- > Due to the "it's never enough" effect I have extend the use specified > nav bar links syntax. If you add a link that has a name of "Top", > "Back", or "Next" (the auto-generated names) and a URL of '*', then > the '*' will be changed to the corresponding generated value. If the > generated value doesn't exist (e.g., you used 'Back' in the first > item) then the link item is silently discarded. I've already suggested in TS-694 to *always* add a language links, if the link would be *none* -- replace it with a Link to our wiki on how to contribute to our documentation. Now, here's a couple other items from my wish-list: The CSS needs tweaking, both amc and me are.. slightly inhibited in that regard, so we'd appreciate input, patches, etc, from everyone who has any kind of the aesthetic taste we lack :) In particular I noticed that * the definition lists which we use extensively look awful. * fonts should match the front page: http://trafficserver.apache.org/ instead of being defaults (usually something like Times New Roman) * make text (of normal content) justified? * break terribly long lines. Me and my army of monkeys are currently busy fixing the admin/ content's general markdown style, since it was just migrated by script. Both hands are tied to conducting the monkey's work, so any helping hand is more than welcome! i -- Igor Galić Tel: +43 (0) 664 886 22 883 Mail: i.ga...@brainsware.org URL: http://brainsware.org/
