Before I found search.cpan.org I had started a project to build a complete CPAN module documentation site. I already had the system partly developed and still have the code kicking around.

It is easy to automatically scan through CPAN on a scheduled basis and spot new/changed modules (thank to the CPAN modules page). I don't think that detecting module version changes in real-time is necessary as most people don't upgrade modules the minute a new version comes out. If you really want to split hairs on this issue you would need to have the docs for EVERY version of EVERY module. I don't think this granularity is necessary. Modules (and their documentation) generally don't change significantly from version to version, so any recent version of the documentation for a module would be sufficient for anything but the most percise needs (not to even mention that the docs aren't always up-to-date with the code). A nightly update would be more than adequate.

I did some metrics and found that the average module had about 8 K of POD documentation throughout all of its files. There are currently about 1500 modules on CPAN. Alowing a generous buffer for added markup all the documentation should fit in under 20 MB. Not a lot of space to ask for in today's world.

Also I do not have %100 confidence in search.cpan.org as I sometimes find module documentation missing.

I would be happy to devote my time, expertise and my partially developed system to bring complete CPAN documentation on as a Perlmonks feature.