I happen to co-run a slash site. We started running it in the slashcode 1.x days (still using 1.x now, actually). 1.x can be a real pain to configure, otoh, it is a pretty scalable and flexible system. I've heard the Bender codebase (2.x) is a lot easier to use. As far as users submitting top-level posts/articles/stories, is this really a bad thing? You do have complete editorial control over what gets published in the slash system as a top-level content node (i.e. story/article).

I don't know if this is a factor, and I've heard it's changed in 2.x, but slashcode is a pain to virtual host.


--
"I aim for the stars. Sometimes I hit London."
~ W. von Braun

In reply to slash by volkadav
in thread Recommended Content Management System? by Jazz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.