I first want to say that PerlMonks has become an addiction to
me. I spend my day checking for new stuff and seeing where I could
contribute something. This is very cool. Keep up the good work,
everyone!
That said, here's my list (I know, some of these have already been mentioned,
but then vroom can see we really want those things :-)
- Ability to rearrange the nodelets (up/down buttons,
or something similar)
- Ability to put the nodelets on the left ( to be able to
get easily at them when the page is too wide because of code in it)
- A separate page for the chatterbox. Maybe you could make it
have an auto-reload thing so that it gets continuously updated.
I wouldn't vote for a Java-based thing, though. Simple HTML is
probably enough.
- A page where you can see a configurable number of writeups
(from all users) sorted by reputation.
- Wider and taller boxes for typing! I think taller is more
important than wider.
- Ability to submit entire files to the code catacombs instead
of having to cut-and-paste everything.
- A link in the code catacombs for downloading the file. Similar
to the previous point.
- After editing a snippet, there is no way to see it in its new state.
You have to go through "snippets" and reselect it, or go back using the
browser's history and reload. It would be nice to have a link to your
snippet's page in the screen that appears after you edit it.
- A "null vote" button next to the "+" and "-". Sometimes I
click on one of them and then change my mind about voting for
that piece. Currently, once you click on a voting check box,
the only way to avoid voting is to reload the page.
- After you comment on a writeup, it gives you a link to
the writeup you replied to, even if that was a reply. I think
the link should be to the "top level" writeup on whose thread
you commented.
- If a search term looks like a module name (:: in its name)
and nothing is found locally, redirect the search to CPAN.
- If a search term starts with "cpan:", redirect the rest
of the term to CPAN.
- If a search term starts with "perldoc:", produce the result
of running "perldoc" on the rest of the term, on a well-loaded
Perl installation. I'm sure you have one of those :-)
- Better "getting started" documentation. Guide to the Monastery
and Perl Monk Procedures are good, but you still have to figure
out many things on your own, like:
- The special features of the search box ("perlman:blah",
for example).
- The concept that nodes can be found by their name alone.
Not all of us are familiar with The Everything Engine
when we first come here.
- That things on the front page are not necessarily the
newest nodes. You have to go look in each section (or
check the Newest nodes page) to actually see the latest
things people have entered.
This is it for now. As I think of more things, I'll post them
here.
-
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.
|
