Petrucio recently introduced the capability to apply Cascading Style Sheets (CSS) to PerlMonks, in his We Stylin'! node. Rich36 suggested a node for sample CSS files, and I've taken it upon myself to create a node dedicated to just that. although it cannot be linked directly to user pages, it should serve as a repository for everyone's creations.

But im curious, is it my browser that makes it ignore whitspace in pre blocks? All the code blocks are unindented. Im using Ie5.5... (Oh, just checked under ie6 as well, and it does the same thing too...)

Yves / DeMerphq
---
Writing a good benchmark isnt as easy as it might look.

For a demo, just go to my homenode, which force-injects my stylesheet for all visitors. (Thanks to jeffa for the inspiration. :-) )

If your browser supports CSS Level 2, the look will be consistent. Mozilla is compliant; IE5 is broken and IE6 probably is too. Otherwise a number of elements that have no class of their own will remain in the theme's default darker blue.

Changelog

2007-04-16

Updated to get rid of the various px font sizes; all font sizes are now relative. Also removed the font-size: smaller bits from various rules. They were there for the benefit of IE6, but made things look worse in other browsers. Added rules hiding behind the Holly hack to fix IE6 font size. No idea what IE7 does.

2004-06-06

Added rules to widen the textarea in post/edit forms. The rule required for the reply form will need a second look as it has name="node", which also appears on the search field on the top of the page.

2004-02-20

Fixed huge fonts for the title on section frontpages as per jarich's reply, and bolded the section title while I was at it.

2004-01-11

I grew out of the Arial look. Now using Georgia for some large, prominent bits, but the default Bitstream Vera Sans everywhere else. Also deitalicized and right-aligned nodelet headers and removed the font-size: 1.1em on them.

2004-01-10

Upon closer inspection, a lot of the HTML at PerlMonks has changed. Unfortunately, that includes handy CSS classes that were removed.. I made rather extensive changes, mostly dropping now useless classes but also adding some other bits. Also, added Bitstream Vera in one class I had overlooked before.

2004-01-09

Now preferring the Bitstream Vera Fonts for those who have them installed. Updated the selector for the input box in the approval nodelet to reflect the (not so) new CSS id and class situation. Also added note to introductory text about implementing this stylesheet easily.

Changed selector for consideration reason textinput in response to a recent class change.

2003-01-04

The <h3 class="0"> is not there any longer. Submitted a patch to have a class applied to the heading in these cases and adjusted the stylesheet for them. Decided I didn't like white-space: nowrap on the title - too often, the node titles are too large to fit.

2002-12-30

A whole lot of work, I like it quite a bit more now.

Got rid of the ugly fixed ##pt size definitions all over the place which overrode things like <small> tags - most annoying when people with large sigs courteously used such tags to reduce the screen real estate consumed, but also in other cases.

Added a [class="0"] specifier to the h3 and added a h3.superdoc style in order to affect only the node's title shown at the top but not other h3s throughout the page.

Restructured the text in this node. The <strike>s were getting messy. Found out (duh) the blue theme is still compulsory: the bgcolor selectors for the classless boxes only work when the colour is indeed #000066, which isn't the case with other themes.

2002-12-20

Removed the width property from the the .code class. It caused pages with code posted in deep replies to have a horizontal scrollbar. I'm not sure you need to use the blue theme as a base at all anymore, but too lazy to check, and it doesn't hurt at any rate.

Unknown

Applied a [bgcolor="#000066"] selector as defined by CSS Level 2 for otherwise classless tables, so their default darker blue can be overridden too.

Unknown

Added a definition so that the input box in the consideration nodelet will appear with a pale red background, as long as your browser supports CSS2. No mistaking it for the chatterbox input that way.

Thanks for tracking that one down! I had numerous reports about it from people, but have only been here very occasionally in the past 2 months or so and haven't had the tuits to look into it. There's also a number of other minor niggles I've been made aware of, but none of them is as much of an issue — nevertheless of course I hope to get to them sometime soon.

I've adapted your CSS with some additional support for things like Recently Active Threads and various pmdev stuff as well. I took most of it from you with some stuff from mdillon and some of my own. Its pretty similar to yours but for a white box the main content and less fancy stuff. Thanks a lot your stuff made for a great foundation (both here and on your home node). Ill keep this updated as I go.

Ever since I wrote this node I have been meaning to make a PerlMonks light yellow theme... well here it is :) I used Aristotle's theme as a basis and worked from there. I originally intended to use it with the default theme but found it looks really good with the red theme.

It still needs a little work - the page width barfs occaisionaly resulting in a need to use the horizontal scroll bar and I haven't managed to change the background colour for the body of sub nodes without breaking everything. All in all I find it usable and soft on the eyes :) Not too bad for a complete CSS novice any-way... /msg me or reply if you have any clues/ideas for fixes.

(no <STYLE> wrapper since this is just verbatim from my "On-Site
CSS Markup" ... Warning:
if you once try this you will never go back. It is that
soothing and clear (to some; others will hate it, personal taste
being what it is).)

Seeing this node linked on grinders homepage reminded me: The following is a report generated by looking for class and id tag code in the PM source code, the first shows what the item is and where its located, the second what source code nodes have what tag information. Its done from a fairly naive scan so there are minor glitches, but it may be useful to some of you CSS folks. (Note the readmore is large)

UPDATE: In an attempt to fix a rendering problem I deleted a bit of the table, but this is a bad plan when rowspan is involved. So ill have to regen when I can.

When putting a smiley right before a closing parenthesis, do you:

Use two parentheses: (Like this: :) )
Use one parenthesis: (Like this: :)
Reverse direction of the smiley: (Like this: (: )
Use angle/square brackets instead of parentheses
Use C-style commenting to set the smiley off from the closing parenthesis
Make the smiley a dunce: (:>
I disapprove of emoticons
Other