>PDF conversion would be pretty cool... Anyone feel like >coming up with a >sheet to generate XSL:FO? =) Good idea, we should find help on xml.apache.org. >> If someone is scared of XML, they can submit it to us in >text format and >> we can go add tags (as time permits), but we're all >developers here, so >> I don't think that's an issue. > >With the (hopeful ;) abundance of docs we'll put in there ourselves, >there'll be plenty of sample 'code' to work with. As well, >the closer we >stick to HTML, the easier it'll be... > >> I. Standalone Installation Guide >> II. Installation Behind a Web Server Guide >> III. Deploying and Configuring, or Tomcat Administrator's Guide >> IV. Performance Tuning Guide >> V. Tomcat Developer's Guide (writing code for Tomcat itself) >> >> I and II may merge, as may III and IV, but I think we're >looking at at >> least three major parts. Seems natural that they'd be in separate >> subdirectories. But... I feel that I and II shouldn't merge. It will confuse users with Apache .conf, and server.xml. Also many time, it will be only the Admin/WebMaster of a site which will read the part II. May be more fluent in Apache config that Tomcat server.xml... >> My vote is -1 for a separate mailing list at this point, at >least until >> we prove that we're not going to peter out like every other >> documentation effort so far. :-) I agree with you. Just prefix your mail with [J-T-D] and it will help developpers follow your works and questions :)
