The deal is: if you are a beginner with Catalyst, go to IRC IMMEDIATELY.

I'd extend that to a: And please, after your problem is solved, just put it on the wiki. There's also a SolvedIssues page on it.

I bet if enough newbies overwhelmed the channel, the documentation effort would probably accelerate dramatically ;) If the IRC channel is just treated as an answering-machine, I fear it won't. But as stated above, a simple contribution (problem/symptoms/solution) to the wiki is worth a lot. As I see it, there are three kinds of people giving Catalyst a drive:

- The "alchemysts" (those who bring new ideas, techniques and modules no one thought about before)
- The "live infantry" (those who make--sometimes heavy--use of Catalyst in production, finding edges, problems and things that need to get simpler) and
- The "players" (those who play around with it. Some of these are also likely to improve documentation when they know where it's needed, submit simple patches, etc.)

---

---

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