Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much

Comment on

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

Your tutorial was automatically, not deliberately dropped from the list. As you noticed, new tutorials are automatically listed in a section called "Tutorials added in the last week." This section is automatically added to the end of the existing Tutorials page when served by the PM engine.

Currently, the general process for getting a Tutorial added to the permanent list involves Consideration. Generally, a monk with consideration powers will notice the new tutorial, consider it with a reason similar to "Promote to Tutorials? (Edit eq Yes, Keep eq No)"1 and wait to see what other monks feel about making the new item a permanent part of the tutorials list.

After a decent period of time, e.g. long enough for a janitor to get a sense of how the promotion voting is going, the node will be added to the Tutorials source or removed from Consideration without further action.

It's not a formal review process by any means and, like many other editorial decisions on the site, is based more on the experience of the janitor in question than any hard and fast rule. As with other nodes, we try to err on the side of generosity than elitism. Sometimes, simple mistakes get made.

In your case, it appears that no one considered your node for promotion2 or that I made an error when recently revamping the Tutorials page. If it was the latter, then I apologize.

I promoted jeffa's tutorial after only a few days primarily because the promotion voting was clearly going in the that direction and it it had a high enough reputation that it was clearly valued by the community at large. (Also, his tutorial was intended to replace an earlier one based on a now deprecated module; thus, his was more of an updated tutorial than brand new material.)

So, no. You do not have to be a high level monk to get a tutorial listed permanently; however, some general advice for all would-be tutorial writers might include:

  • Make sure your tutorial is well written and clear.

  • Make sure you choose your examples carefully. They have to be simple enough to grok quickly, but they must be more interesting than "hello, foo."

  • Write tutorials that include information beyond the friendly manual.

  • If you must re-write an existing tutorial, then please make sure your final work is clearly needed (e.g. it replaces out-of-date information) or is clearly superior in clarity, coverage, and/or content.

  • Please do *not* include unnecessary HTML formatting. Case in point, I spent about two hours trying to rewite the formatting of a certain tutorial during the recent revamp primarily because the original author posted an entire HTML document, instead of just the rendered <body> content.

  • Remember Hanlon's Razor


Update: P.S. Looks like VSarkiss types more quickly than I do. And more concisely. ;-)


1 - Yes, it's a hack. We may change that at some point. If there's time and we manage to get everything else done that we need/want to do.

2 - This has now been corrected. We'll see how the promotion voting goes.


In reply to Re: Tutorial Acceptance Policy by footpad
in thread Tutorial Acceptance Policy by hiseldl

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 all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others having an uproarious good time at the Monastery: (4)
    As of 2017-12-16 15:59 GMT
    Find Nodes?
      Voting Booth?
      What programming language do you hate the most?

      Results (455 votes). Check out past polls.