The NAME section in the pod for your module(s) provides a one-line description of your module, often referred to as the abstract. Make sure all of your modules have an abstract, particularly the lead module in each distribution. And make sure it follows the convention, otherwise tools won't find it, including MetaCPAN.
Here's a well-formed abstract, taken from the pod for Type::Tiny:
=head1 NAME Type::Tiny - tiny, yet Moo(se)-compatible type constraint
It's pretty simple, but to be really safe, here's how to make sure your abstract is 'clean':
=head1followed by a single space character, then
The blank lines shouldn't even contain any spaces.
You might be thinking that surely you don't have to be quite so specific? Well, yes, I'm afraid you should.
NAME, so MetaCPAN wasn't finding the abstract (that's been fixed now though: both the module and MetaCPAN!).
NAME, so MetaCPAN isn't finding the abstract.
You should do this for all modules you release to CPAN, but in particular you should do it for the lead module in your distributions.comments powered by Disqus