1732N/AApache HTTP Server 2.0 Documentation Status File.

1732N/ALast modified: $Date: 2002/09/09 01:53:42 $

1732N/A

1732N/AIf you are interested in helping accomplish some of the tasks on this

1732N/Alist or otherwise improving the documentation, please join the

1732N/Aapache-docs mailing list by mailing to apache-docs-subscribe@apache.org

1732N/A

1732N/AFor more information on how to contribute to the Apache Documentation

1732N/AProject, please see http://httpd.apache.org/docs-project/, and

1732N/Ahttp://apache-server.com/tutorials/ATdocs-project.html for an excellent

1732N/Atutorial on how to get started with making your contribution.

1732N/A

1732N/A ------------------------------

1732N/A

1732N/A- XML

1732N/A - The xsl transformations could be greatly improved to a) look better

1732N/A and b) use proper CSS+html rather than the horrible hack that

1732N/A Joshua did (in progress).

1732N/A - Rewriting of the remainder of the manual into xml is in

1732N/A progress. See the bottom of this file for status info.

2899N/A

1732N/A- modules docs

1732N/A - mod_suexec: very little documentation

1732N/A - mod_proxy: updates for 2.0

1732N/A - mod_status: updates for 2.0

1732N/A - mod_example: updates for 2.0

1732N/A

1732N/A- man pages

1732N/A - Some of the man pages need to be updated for 2.0. At least

1732N/A the httpd man page appears to be outdated, and perhaps other.

1732N/A After this is done, the manual/programs/ versions can be

1732N/A regenerated using the program in the site-tools repository.

1732N/A

1732N/A- MPM documentation

2899N/A - Each MPM needs to have a documentation file in manual/mod/

2899N/A which lists the directives it provides, and some details

1732N/A about its operation.

1732N/A Status: Initial outlines done. Much more details need to be

1732N/A filled in.

1732N/A - Non unix/windows MPMs still need to be completed.

1732N/A - the perchild directives in threaded/worker need docs

1732N/A

1732N/A - Individual docs will need some cleanup.

1732N/A Status: What docs still need to be touched here?

2095N/A - misc/custom_errordocs.html needs to be updated to

2095N/A essentially describe how the international error

2095N/A docs included in 2.0 work

2095N/A - misc/perf-tuning.html - needs major rewrite for 2.0

2095N/A - misc/tutorials.html - mostly not relevant to 2.0

2095N/A - misc/stopping.html

2095N/A - misc/rewriteguide.html - needs cleaning in 1.3 and 2.0

1938N/A - misc/known_client_problems.html - mostly ancient

1938N/A

1732N/A- New build process.

3477N/A - install.html has had a first-pass rewrite, but many things have

3477N/A changed in the build system since it was written.

1732N/A

1732N/A- Documentation of new features.

1732N/A - This will probably require more input from new-httpd, since

1732N/A not many people here follow the development process close

1732N/A enough to know what is going on.

1732N/A

1732N/A- API documentation

1732N/A Status: Ben Laurie has written some hooks documentation

1732N/A

- Translations

There are several efforts underway to translate the documentation

into other languages. A detailed list of the currently known

translators (and the corresponding websites) can be found at

http://httpd.apache.org/docs-project/translations.html

New User documentation

======================

* Directory Handling (mod_dir/mod_autoindex/etc)

Documentation improvements

==========================

* Improving the "security docs"

- More content and better organisation.

* General cleaning and improving of module docs

* Making the directive definitions "less terse" (i.e., adding more

examples and details to the definitions of the directives)

- We'll need to audit these and find out which ones need munging, as

some of it looks ok. --jsl

* Making site-specific enhancements easier, including a documented

and robust way for 3P module docco to be added -- and have it

survive a server docco upgrade

- This could be something a simple and hackish as a manual/extra/

directory (a la the 1.3 src/modules/extra/ directory) and a

script in the support directory that scans the files there and

updates the manual indices. (We do something like that now for

httpd.conf file with apxs [LoadModule, etc.].)

* regex: We should at least document someplace what regex library we

are using and how to find more information about it

XML Conversions

===============

The following files need to be converted to XML as described at

ebcdic.html # Perhaps move to platform/

footer.html # delete after finishing manual/

header.html # delete after finishing manual/

index.html.en # leave in html?

howto/footer.html # delete after finishing howto/

howto/header.html # delete after finishing howto/

misc/custom_errordocs.html # obsolete?

misc/descriptors.html # obsolete?

misc/fin_wait_2.html # obsolete?

misc/footer.html # delete after finishing misc/

misc/header.html # delete after finishing misc/

misc/known_client_problems.html # obsolete?

misc/perf-tuning.html

misc/tutorials.html # obsolete?

mod/footer.html # delete after finishing mod/ directory

mod/header.html # delete after finishing mod/ directory

platform/footer.html # delete after finishing platform/

platform/header.html # delete after finishing platform/

ssl/footer.html # delete after finishing ssl/

ssl/header.html # delete after finishing ssl/

ssl/ssl_glossary.html # delete. replaced by ../glossary.html

vhosts/footer.html # delete after finishing vhosts/

vhosts/header.html # delete after finishing vhosts/

expand.pl # delete after finishing everything

# These will require manual.xsl changes

faq/footer.html

# Perhaps these should be left in html to allow the developers to

# play with them

# These are currently generated from nroff, but nobody is editting

# the nroff sources. Should we just convert to pure xml and forget

# about man pages?