I like it. I looked at the source and was gladly surprised to see the cleanliness and clarity of the markup. The design is clean and clear. The colors make text legible without being glaring on a bright monitor.
I'm not personally a fan of one aspect of the markup in particular, though. The thick border between the byline and the node content followed by the thin rule between nodes reads at first as if you've used bottom attributions. It's very easy to miss that first by-line at the top and look at what is most clearly delineated. I'm not a fan in particular of bottom attributions, either, and I almost commented about that before I noticed it wasn't the intent. If you had used bottom attribution lines, that'd be merely a minor adjustment for people reading the site. I'm afraid what you have here will lead to mistakes in replies if it is implemented. Putting the whole by-line in the divider as the current design does may not look as crisp, but it is much clearer. I think an alternative would be to use quite a bit more vertical whitespace between the list items used to contain the nodes.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|