Bill Moseley wrote:
At 06:12 PM 4/20/2002 +0800, Stas Bekman wrote:


The idea, is that this gives someone that has no idea about mod_perl a path
to gently learn about it with simple text, and simple examples.

Does it work?

Well, I won't start yet another mini-guide on the site. Let's keep everything in one place, otherwise the maintenance is a nightmare and people get even more confused. Why not linking directly to the right sections in the about page as you go, including the install link


e.g. instead of tips/example, link to:
http://hank.org:5000/docs/1.0/guide/getwet.html#A_Sample_Apache__Registry_S

cript

Well, getwet didn't exist when I started ;)  That's fine.  I do like the
concept of the more>> link pointing to a very small page to demonstrate the
point on the About page in code.   But it would save some work, though I
can't imagine that the About page will need updating very often.  I just
didn't want to link into a huge section of the Guide just for an example,
and I didn't' want to add examples directly to the about.html file.

It also seems a bit weird to link to getwet from all the more>> links, then
at the bottom say Now, next read the getwet page.  But minor point.

OK, no prob. If we can make sure that it stays small it's a great idea, Bill.


Everyone: I could use some help finding some good examples for those
various About mod_perl sections -- something that exists in the current
docs or just a real life yet easily demonstrated example.

How about the modperl cookbook? Also check the getwet, I think it covers pretty much all you need. __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to