Okay, looks like we've really got things rolling... >From the discussion so far, here's the catagories we've come up with:
* How-to -- quick and dirty for those new to Apache * How-to 2 -- advanced topics, more than you thought you'd ever need to know... * Tutorial / Overview of Apache -- glossary of terms, what apache offers, how it works (generally), why use it... * A tutorial specific for those setting up Apache on MS?? (never done it, know nothing about this...) At least I think this is everything..... I like the idea of starting from a "solid foundation", but as we're all working with these servers, we'll probably end up getting a few revisions of the how-to's here and there too. Personally, though, I'm interested in starting in on the Tutorial / Overview.... As for documentation, I also favour just plain and simple HTML. If need be I've transferred HTML to PS fairly painlessly, and from there we can go to PDF without much work. It's a question of need though; if we convert things to PDF they should be either a quick ref. card, or general overview materials (ie. materials someone may have to show a "higher-up" before moving to Apache as their server.) Jon > -----Original Message----- > From: Michele Petrovsky [SMTP:[EMAIL PROTECTED] > Sent: Wednesday, December 02, 1998 9:26 AM > To: [EMAIL PROTECTED] > Subject: RE: Case Studies > > At 11:07 AM 12/2/98 +0200, you wrote: > >On Tue, 1 Dec 1998, Michele Petrovsky wrote: > > > >> This is where questions as to structure, presentation, > >> audience etc. start to crop up. Once there's a good > >> general in-English tutorial of the type you've described, > >> a case could be made that the existing docs are sufficient > >> for all other needs (e.g., sysadmins, programmers). > >> So, should apache-docs concentrate solely on: > >> > >> * producing a tutorial > >> * broadening/facilitating access to the > >> existing docs (e.g., a document "portal" > >> as has been suggested; creating numerous > >> format versions such as PDF, SGML) > >> > >> or do we need other levels/types of documentation? > >> And if the latter, what? > > > >I'd love to see how-to type documents answering to very practical > problems > >like user wants to use SSI how do I enable it or I don't want all people > >to see my private pages how do I stop them. > >Those are for buzy (and maybe lazy) part time admins, like me. But > >tutorials would be great also covering things more in depth and paving > >path to "conventional" apache documentation use. > > I find this example particularly interesting because > it's pretty much a word-for-word description of what > the sysadmin at the college where I teach is working on > right now. Fine-tuning of various sorts might make > for a very useful category of howto docs. So here's > a question: what other specific types of howtos might > we include in such a category? > > >This is my first appearance on list so I might introduce myself a bit. My > >main job is to develop searh system with Java. I also admin departments > >apache server on solaris. I need web-server in my work so my desktop is > >Linux with apache and jserv (apache servlet module). > > >
