comment on

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

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.


XP is just a number
	PerlMonks