StommePoes:

I'd definitely keep DBI, as that's what I use. (I intend to try DBIx::Class and others sometime, but haven't had the need to do so yet.) For new users, the more recent packages may be preferable, so you might want to put DBI later in the list, so they can pick up on the newer ones.

As for your question about what else to put in the databases section, I'd probably point them at DBD::SQLite for small database jobs, as it's self contained. Oracle, Access, SQL Server and mySQL seem to get a lot of questions, so it seems worthwhile to point them at appropriate drivers. It may be worth while pointing them at specific perlmonks nodes (e.g. DBI Recipes, tutorial articles and CUFP articles on databases.)

Under your tutorials and articles section, you may want a subsection for "frequently encountered gotchas", like:

• Why it's stupid to `use a variable as a variable name', pt 1
• Why it's stupid to `use a variable as a variable name', pt 2
• Why it's stupid to `use a variable as a variable name', pt 3
• Far More Than Everything You've Ever Wanted to Know about Prototypes in Perl
• Perl Idioms Explained (A page of links to specific idioms...)
• Using Look-ahead and Look-behind (regex goodness)
• Coping with Scoping
• Yes, even you can use CPAN
• And many others ... (I've been grabbing these from my home page, and I'm sure other monks home pages have useful links.

...roboticus