[pmwiki-users] PMWiki default documents vs search engines

Ian Barton lists at manor-farm.org
Thu Dec 14 00:35:27 CST 2006


> IMHO, the way documentation is currently distributed is ideal.  If you 
> want to block it or remove it, that is easy to do.  However, if you have 
> multiple PmWiki installations running different versions, the 
> documentation is always valid *for that version*.  You won't have the 
> situation where a user reads something on documentation linked from 
> PmWiki.org, only to find that the feature they are trying to use was 
> introduced two releases after your installation.  It is not always 
> practical or desirable to upgrade to the latest version unless there is 
> a valid security reason, so having a central documentation repository 
> might be confusing as it begins to mention features or markup not 
> available with the installed version.
> 
I totally agree. The only time I *really* need to look at pmwiki.org is 
for things like Cookbook entries.

Apart from anything else, if everyone had to look up everything on 
pmwiki.org PM's bandwidth costs would soar.

I can't see any mention of the effects of not including 
<!--HeaderText--> or <!--HTMLHeader--> in the Skin Guidelines page. 
Perhaps if we added an explanation of why this is a "good thing" skin 
authors would make sure their skin includes it.

Ian.




More information about the pmwiki-users mailing list