Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

I'm not worried about overloading curators. And tutorials needs the tighter control because it is a special-purpose section that should only contain high-quality content, not just whatever people want to post that doesn't get rejected for being completely inappropriate.

Posters shouldn't have to wait for a curator to be around for their node to show up on their selected list. With node approval we at least have hundreds of "curators" there (and it is still enough of a problem that automatic approval is repeatedly proposed and I'm in favor of that with a few details worked out).

If the user fails to successfully pick a valid category, then a curator would need to place it for them, of course.

I don't like either of your alternatives for users selecting a list to add to. I'd have each list have an "add" link that gives a submission form with that list preselected.

Can these lists allow the viewer to select whether they want to see nodes under this keyword shown newest first or highest rep first? That seems important too.

- tye        

In reply to Re^6: Revitalize the Code Catacombs using DocLists! (fit) by tye
in thread Revitalize the Code Catacombs using DocLists! by jdporter

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others lurking in the Monastery: (4)
    As of 2021-02-28 20:00 GMT
    Find Nodes?
      Voting Booth?

      No recent polls found