I do agree that a there should be a more exposed wiki here. I would just make a link from the front page to it, perhaps as an additional section. There are many discussions here about additional structure in PM - like better code sections, better cooperation with CPAN (reviews), etc. I believe many of them are quite usefull ideas, the problem is that they need some additional structure in the monastery, and that takes time. With an exposed wiki we could say - just start it as a wiki page, add the structure by manual intervention and see if it works. When it works and the manuall intervention is not that big problem then it can stay that way, when it works but the manual intervention is too big then one would have more arguments why to implement it as a software mechanism.
Don't build the structure for people - let people build the structure. Give them the basic mechanisms and see what happens. Now it is easy to add content to PM - make it easy to add structure.
-----------------------------------------
A generall thread about colaboration on web pages: Collaborative Media.
The original Worse is Better story.
-
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.
|