:: Also, I'm not a big fan of having a menu item to Take23 :: because it's an off-site link and it's one of the main menu :: items. Not to mention "[EMAIL PROTECTED]" takes you to news :: that's from last June. I think all those menu items should :: stay on-site. No reason the mod_perl site can't have it's :: own news, even if it's just a paragraph about a new story at Take23.
+1 :: Finally: Extraordinaire Technologie -- How about just :: "Success Stories" or "mod_perl in action" or something that :: says "this link will tell you about sites using mod perl, :: and stories about using it. I think mod_perl can speak for :: itself, and we don't need to boast about it in menu titles. "Case Studies"? :: - "Getting Started" (which is "tutorial" but more friendly). -1 redundancy: just make "tutorial" more friendly :: Or maybe better a little introduction that includes sub-sections: :: a) what is mod_perl? -1 I still prefer the idea of a separate advocacy/promotional site (eg: http://www.mod-perl.org/), with perl.apache.org remaining as the documentation/technical site - in which case "What is mod_perl" would obviously be on the advocacy site. :: b) a non-biased comparison with PHP and Java and other :: server solutions +0 Dodgy area this - we don't want a page that incites flame-wars and I note that you wrote "non-biased" Bill. I'd be happy to see a simple matrix with several technologies covered and the relevant ticks or crosses for each feature for each technology. :: c) a very short (two screens?) of building mod_perl (five :: lines), and :: a example of a handler (which can be done in a <perl> section) -1 redundant... surely? There's enough documentation for this already. :: d) a paper called "How to learn mod_perl" which points to :: tutorials :: and the guide and discusses getting help from mod_perl list +0 :: e) a quick overview of related projects (Mason, TT, OI, :: Embperl....) +1 :: - White Papers, which can be discussions (summaries from the :: mod_perl list) such as the eToys paper, and caching techniques. +1 _definitely_ - this would be a real plus :: I'd also like to see a short description on putting together :: a basic configuration that includes sessions, Apache::DBI, :: and the real standard building blocks that are commonly :: used. In other words, follow these ten steps and now you :: have a platform for building high-end, scalable :: applications. Just something to cut down on the TIMTOWTDI :: confusion when first starting out. +1 _definitely_ - this would be a real plus Jonathan M. Hollin - WYPUG Co-ordinator West Yorkshire Perl User Group http://wypug.pm.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
