At 14:30 11.05.2002, Stas Bekman wrote:
Folks, thanks to Thomas we have reshuffled a big chunk of the content. See the updated version here:
http://perl.apache.org/preview/modperl-docs/dst_html/docs/tutorials/index.html
Please verify that we didn't lose anything while moving, and that you are happy with how the docs are laid out now.
We want to freeze the docs movement, finalize the design and proceed with the preview stage. that's a release candidate modperl-docs-RC1.
Haven't found any problems yet, but I have one suggestion: instead of having a Win32 section under 1.xx, let's make it an "OS-specific instructions" section, so we could put MacOS/Cygwin/foo instructions there. If I ever get mod_perl 1.x to work on Cygwin, I'll try and write up some stuff, and I think we have enough working installations for MacOS X to get some help for that too.
Yes, we weren't sure how to do that the best. On one side it's nice to have everything in one doc to minimize dups. But if each OS specific part grows big a separate doc makes more sense. I think win32 docs are big. That's said we could move them out of win32/ and put under guide/, e.g. install_win32.pod, config_win32.pod, etc.
We have the same issue with 2.0 stuff, but here is easier: we have 2.0/install/install.pod (for generic stuff), platform specific stuff can go into 2.0/install/win32.pod, etc. What do you think?
BTW, the new docs are all nested in a separate dirs because we expect to have code and images at some point for certain chapters, so it makes sense to have them separated this way. We have done this for our book and it works very well.
__________________________________________________________________ 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]
