Using .pod as a standalone file rather than in .pm and it showing up in MetaCPAN

[rockyb]

I'd prefer to have some documentation associated with a Perl Module, but I would rather not put it inside the code or .pm file but rather its own .pod file.

The reason I'd like to do this is so that it can be shared in say a github wiki where folks can interactively edit.

Before a release though, I'd copy the wiki into the distribution.

So what are practices or best practices for having documentation showing up on search.cpan.org or metacapan.org outside of the code?

[LanX]

...where there is both a Module.pm and Module.pod perldoc will use Module.pod (same is true for metacpan.org)

[rockyb]

Thanks. This is what I was looking for.

[RonW]

As LanX said, perldoc and metacpan will show the .pod instead of the .pm if there is one.

Just checked, and it looks like cpan will, too, now.