Bill Moseley wrote:
Here's a quick mock-up of what I was suggesting.

   http://hank.org:5000/about/about.html

The first paragraph has a more >> link to a very short example.  That short
example has a link to the real details.  (The wording needs to be improved,
but hey, it's late.)

Then at the bottom of the About page it links to Stas' new mod_perl in
three lines.

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_Script

What doesn't work is the [prev] button on the tips/registry.html.  I must
not understand how to link into docset correctly.  I just added this to
config.cfg:

     chapters => [
         qw(
            about/about.html
            about/tips/registry.html
           )
     ],

But that was a wild guess.

That's correct.

It all works, you just need to use -f when you add new docs or remove them, or move around. The caching is imperfect and cannot handle these now. I need to improve it.

In any case we should probably move the about docs into a separate docset if we have more than one doc. like the rest of the pages.

__________________________________________________________________
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