Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl Monk, Perl Meditation

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
I like the idea of organizing nodes by their topic (chapter) as opposed to just the type of post (question, discussion, etc). I am not convinced that there is value in adding complementary content to link nodes together, however, or in ordering them relative to one another within a section.

I think the addition of a topic/chapter nodelet could be a solution to this. I see it as a series of checkboxes with the names of various topics, from the Q&A sections of arrays and regexes to turnstep's discussion sections like voting and customization. People over a certain level would have the option of putting a post in to a topic, or of removing it. Editors would have the option of adding new topics. This would only be applicable to root-level nodes--other nodes would inherit from their parents (which means any changes to the root node's section would require cascading changes through the thread, or else some information to be stored about an entire thread rather than just a node). Naturally, these would then be searchable categories.

It would also be nice to be able to explicitly list nodes which are not categorized, so that people scouring the archives to use up votes can also sort the old posts while they're at it. ;)

Update I was thinking of the keyword nodelet when I wrote this post but commented out my thoughts on that because I couldn't think of how to tie it in. So here it is, out of comments:

Better yet, let it replace the keywords nodelet! The keywords nodelet is pretty much useless. People just add random stuff that in no way helps with searching. But even if quality content was the norm, I think the keyword nodelet would be of minimal use as a searching mechanism. Supersearch already looks for words found in the node body, and any words which aren't found in the node but would be good search terms can be included in comments, which are also searched.

In reply to (kudra: topics) Re: Lack of structure. Channeling structure by kudra
in thread Lack of structure. Channeling structure by larsen

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 pondering the Monastery: (13)
    As of 2020-11-23 16:05 GMT
    Find Nodes?
      Voting Booth?

      No recent polls found