- People have acquired the instinct to delete anything long that comes into their mailbox as a result of filling out a "sign me up" web form. So, I'd like to argue that this doc should be as lean, and as to the point, as possible. Don't try to explain or point out everything; that's an unreasonable goal for this sort of auto-sent welcome message. If a better introduction is needed, then maybe the PM FAQ or other doc pages should be revised.
Or else, as perigeeV suggests, maybe it should be the page that pops up after creating a new user; label it "New Monk Info Page" and stick in the right column under
"Information". Or even situate the link somewhere at the top of the home node of all users during their first 2 levels.
- Item #12 should top the whole list. Also, note that the first link under #12 makes all of item #3 redundant. Item #3 is fairly confusing in this context anyway.
- After #12 should come #9, followed by a combined list of links to FAQs and manpages under a generic and brief, "If you're looking for help, have you tried any of these sites yet?"
- After all
the hubbub, you just can't leave out http://learn.perl.org!
- The formatting on the links is a little mixed up in places. (I assume that you won't be sending HTML-format mail?) Here's what I'd recommend:
name of URL, indented slightly (no tabs):
full URL, indented slightly more,
maybe surrounded by one species of bracket or another
(if that won't break an HTML-based reader)
This especially includes the Perlmonks node links that you've included.
- Is "have you read the man pages" really necessary? I'd have thought that Perlmonks was relatively obscure enough that to have found it, you'd already know about the existence of man pages. However, one thing that I have found to be obscure to some novices is the perldoc command;
you should touch very briefly on this along with the FAQ/man stuff. (Even just a hint to try typing 'perldoc perldoc' would be great.)
- "Generating its own *superior* FAQ"...I don't want to knock Hubris, but I think this will come off as too smarmy for a greeting message.
- "At the risk of being branded a heretic" - I don't know if that's just your own parenthetical comment, but this should probably be dropped from the final message.
- I second the emotion: drop #13. Either completely, or replace it with a Saints link. Let them explore the Monastery in their own sweet time; if it matters to them, they'll come to know the Saints and their home nodes soon enough, and if it doesn't, it's just more noise in the message, drowning out signal.
I hope this doesn't come off as too harsh. This is a good idea, but I just think it should be lean & mean; otherwise, most people won't give it the full attention it deserves. In fact, the more I think about it, the more it makes sense to have this as a web page rather than (or in addition to) an email; that way, people can bookmark it (rather than losing it to the depths of their inbox, or automatically hitting the 'd' key), and people can merrily click away to browse all of those Perl/Perlmonks documentation sites before they jump into posting.
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.