a) there should be clearly stated from the start of the page, that there is a special § for Apache, another one for IIS etc, that is not clear until we don't scroll to the point B. Some people could consider IIS as Apache compatible web server on Windows, and follow the instructions from the point A, instead of going to the point B for IIS.
b) in the point B, for IIS, "Step 1", it says:
start the IIS management console snap-in, select the appropriate web site and open its Properties
is not clear what web site is "appropriate", should we create a IIS web site for AWStats, or should we update the existing production web site want to install the stats on?
In the "step2"
Copy the contents of the AWStats provided cgi-bin folder, ... to your server's cgi-bin directory
the documentation is created like any site is created in perl and has a "cgi-bin" directory... I have any cgi-bin directory in my production site
the install docs on https://www.awstats.org/docs/awstats_setup.html,
a) there should be clearly stated from the start of the page, that there is a special § for Apache, another one for IIS etc, that is not clear until we don't scroll to the point B. Some people could consider IIS as Apache compatible web server on Windows, and follow the instructions from the point A, instead of going to the point B for IIS.
b) in the point B, for IIS, "Step 1", it says:
is not clear what web site is "appropriate", should we create a IIS web site for AWStats, or should we update the existing production web site want to install the stats on?
In the "step2"
the documentation is created like any site is created in perl and has a "cgi-bin" directory... I have any cgi-bin directory in my production site