In Getting to Super Search, I mentioned that I felt a strong search was essential to the success of PerlMonks as an archived resources
(okay, I didn't say it so elegantly).
Today, I thought I remembered something from the infamous "running with scissors" thread, so
I went to find it. A super search for: running with scissors
gave me a bunch of perlman pages (why?) and the code Running with Scissors (Listing "1 word matched" ???)
but not "running with scissors".
So I think we should put some effort into improving Super Search. What kinds of features would be good to add?
- I'd like to see results sorted by Rep. (Regardless of whether I know the rep, lets not go there again).
- I'd also like to be able to search posts by author. (If, for example, I remember that chromatic made a good post about typeglobs that had something I specifically wanted, but I don't remember that it was Re: Validating a Code Reference, and I don't want to go through the listing of his 600 nodes, and everyone talks about typeglobs, so a general search isn't as helpful. This happens more often then you think, although that node is a bad example, because it's easy to find)
- I'd like to not have all the perlman pages show up so often
Comments?
-
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.
|
