As someone who has used Slashcode for at least three sites I can confirm there *are* drawbacks.
1) Lengthy setup time, and steep initial learning curve, even if you buy the book co-written by chromatic :-)
2) No simple way to modify the workflow (it is set up for the Slashdot.org workflow and no other)
3) Not easy to modify the layout of the main index pages
4) Does not work straight out of the box (but that is perhaps the same point as number 1)
I'd seriously looking at Squishdot (a Zope product) for my next slashcode-like site.
PS I'm Alex McLintock - not "vroom" - is this a security flaw? or is "vroom" the "Anonymous user"
-
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.
|
