We were in fact considering this exact problem yesterday. While I like your description of it, I don't like your solution. our solution would be as follows:

• Tutorials get posted to tutorials, as it should be, the author can pick a tutorial category when posting.
• The Tutorials page automagically lists ALL tutorials, according to the picked category, possibly with a section for NEW posts, or some way of identifying them.
• Tutorials can be front-paged (I can't see a reason why they shouldn't be.)
• Tutorials can be considered to be moved away from that section, and get moved by editors if need be.
• Tutorials can also be moved between categories by the editors
• Categories would be maintained by the editors, suggestions could be made via /msg editors, Editor Requests or maybe a new page for that purpose.

In my perfect world, also, each tutorial would be maintained by its author, or the editors, a little like Q&A, so corrections and updates would be made as they are needed, keeping teh the tutorial as useful as possile.

Further thought: Each tutorial should also mention which perl versions it applie(s|d) to at time of writing, and which operating systems, if appropriate.

In case you didn't know, the only real problem with the current system is, that Tutorial type nodes have to be added to the Tutorials page by hand. Thus, even if a Meditation gets 'moved' to Tutorials, all that actually happens is that its nodetype gets changed to 'perltutorial', it won't turn up on the Tutorials page unless the editor goes and does that as well. (And I'll admit, I've never added any).

C.

Update: The reason that Meditations that have been considered as 'Move to Tutorials' are getting unconsidered recently, is that we are in general, not moving Meditations to Tutorials any more. This is mostly because quite a few are getting considered that weren't intended as tutorials, and aren't very good as tutorials. (So we need to educate people that intended to write a tutorial, to post them there, even if not quite finished.. It's easy write 'under construction' on a post, and to update one)

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, 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:
	&		&
	<		&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.