Code Pornography
Ok, that title is a bit of a teaser. But I do think that code should be sexy. In this full-color high-definition world, we've come to expect things to actually look attractive.
I'd love to see pretty logos or icons for each module on MetaCPAN. Perhaps we could add a new attribute to the META spec that points to an image file inside the distribution, or a URL somewhere.
Hacker, speaker, author, dad.
You can already use `=for html` directives to add html only pod inclusions. I see this sometimes for travis-ci build status images. Definitely an under-used feature of pod.
For example Chart::Clicker has some embedded images.
Like a favicon for modules? Or should it be for dists? Probably both: specifying a cpanicon for a dist would be the same as specifying it for all modules, but then you might want to have a generic one for the dist, and a couple of specific ones for the "public facing modules".
One potential problem with this idea is that it might give a slight advantage to module authors who are design / graphically talented (unlike myself, for example).
> Like a favicon for modules?
Exactly! Imagine if MetaCPAN looked a bit like an AppStore -- a rich and beautiful showcase of all the excellent work we do.
> it might give a slight advantage to module authors who are design / graphically talented
I don't see why that is a "problem"?
Think "booth babes," but with much lower cost and importance.