Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight
 
PerlMonks  

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

A few weeks ago cosmicperl began a discussion about the pros and cons of a newbie focused satellite site for Perl Monks. The suggestion of a new beginners only site was not particularly well received, and instead triggered a large number of suggestions about how the current Perl Monks could be improved.

This is only one of many threads where suggestions for improving PM have been offered. In the coming weeks, I hope to construct a list of some of the more recent threads. I will also be reviewing them and compiling a list of suggestions that people have made for improving PM. If anyone else is interested in working on this, please make yourself known.

This process (and this post) is an outgrowth of the discussion we had last week on the thread Process for Site Improvement. We have at present no "official" wish list or mechanism for prioritizing suggestions for site improvement. In that thread jdporter suggested that for the time being, one way to get a better understanding of what changes matter to us monks would be to compile a list of suggestions from PM discussion threads.

Some of the proposals in PerlMonks for newbies? are very specific; some simply point out general areas where improvement might be valuable. I've assembled a list (below) of the various suggestions from that post in hopes of stimulating discussion on the following questions:

  • Which, if any, of these suggestions do you feel are valuable enough to merit further discussion?
  • Do you see a consensus developing around any of the suggestions?
  • What suggestions would you add that aren't already on the list?
  • What do you value most about Perl Monks and which of these suggestions enhance or build upon that?
  • Which of these have in fact been implemented but need to be better publicized?
  • As we work through other threads and gather their suggestions what is the best format for organizing them? Do we want to see other "per-thread" summaries? What about consolidating all suggestions into a single list?
  • If more that one person is involved in compiling a list of suggestions (and I really hope there will be), what tools does PM provide to help us coordinate our work?
  • How would you prioritize these suggestions? What is the best way to keep track of a developing consensus about which suggestions are highest priority? Is there a way we could adapt the polling mechanism? Is a qualitative summary the best way? Some combination?
  • To the members of cabal, and pmdev in particular: What would it take to actually implement the more specific suggestions - both technically and in terms of support from the wider monk community?
  • What would you be willing to do to help make your favorite suggestion "happen"?
  • This thread gives examples of suggestions, some clear and some overly general. If you were to write a How (Not) to propose a site improvement tutorial, what would it include?
  • Was the format of this post helpful? What would you do to improve upon it?

If there is no objection, when this thread winds down, I will summarize the comments here and post the results so that we can continue to build on the discussion.

Best, beth

Note 1: My apologies in advance if I left out anyone's suggestion or misrepresented their views. If I have done so, please message me and I will make the correction.

Note 2:Many thanks to all those who gave suggestions privately and on the thread Process for Site Improvement about how to go about this task. They made this thread possible.

Suggestions have been grouped into one of the following categories:

Site look and feel suggestions

Site content and navigation suggestions

Community building suggestions

Site performance suggestions

Site development tool suggestions

Places to look for further inspiration


In reply to Making Perl Monks a better place for newbies (and others) by ELISHEVA

Title:
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?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others surveying the Monastery: (3)
    As of 2020-02-25 22:17 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?
      What numbers are you going to focus on primarily in 2020?










      Results (113 votes). Check out past polls.

      Notices?