I suggest that we try as much as possible to work by consensus ... if such a thing can be had ... because, even though there are a lot of “visual clods” in it (including silly-stuff, like the fact that the pictures in the top-of-screen rotation have no anti-aliasing thus “jaggies”), and some things that I wish would be changed (like Anonymous Monk and the content-evaluation system), there are many things about the site that do still work admirably well. I would like for there to be continue to be o-n-e “goto site about Perl,” and for this site to continue to be “it.” Although the site is admittedly ugly, it is functional and it contains many years’s worth of a cornucopia of information. That’s what’s important – vital – about PerlMonks, not so much its irritating warts and ugly looks. A “fork” never quite turns out right despite best intentions.
-
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.
|
