As you all know some questions get asked here over and over again. I and I'm guessing most of you would rather code than write up documentation. So instead of forcing the same questions to be asked over and over again in the chatterbox we are now going to allow certain high-level users to create site faq-lets once and add them to a central location. That way questions can be answered once and only once saving all of us a lot of work.

The central location will be Perl Monks FAQ... I still need to code up a bit of functionality but if you want to be added to the group of users who are allowed to add these faq-lets let me know.... For starters to keep things manageable I'm going to limit the users who can add faq-lets to users at level 5 or above. If you meet that criterion and want to help /msg me.

Update: The functionality should all be there now. If you want you can check out the current members of the Site Documentation Clan and if you're above level 4 let me know if you'd like to join our ranks.

If you're a member of the clan all you need to do is go to the section you want to add a faqlet to. Click the link to do so, and then writeup your text. The ownership is then transferred to the clan so all in it can update it as necessary.

vroom | Tim Vroom | vroom@cs.hope.edu

---

---

• 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.