Instead you should just make a homepage for your module somewhere (where you have complete control over the layout) and provide a link for that in your POD.

I only check the original intended target: manual pages. If it looks good in 'pod2man Foo.pm | nroff -man | less' on a 80 character window, I'm ready to ship it.

I'd do that too, but pod2html is far less prone to typing error :-D ... and of course, pod2html has the distinct advantage of platform neutrality.
A user level that continues to overstate my experience :-))

I beg to differ about "not caring". Using the exact style sheet as CPAN probably isn't important, but making sure you have an idea of how the pod is being parsed is important.

It isn't so easy to read the text version of the pod file and be certain that you have all of your pod tags in the right place and properly formatted. Looking at an HTML rendering provides important and easy to assess visual feedback on your pod tagging. I make mistakes all the time, especially when I'm nesting tags, using unfamiliar pod syntax, or linking to external material. The documentation of pod syntax also isn't always 100% and it is necessary to experiment a bit before one has the right syntax. Broken links are another matter that is hard to assess merely by reading the pod file.

You can get a rough idea of how the HTML will look by using the pod2html program. At the minimum it will help you identify syntax errors, misplaced tags, and broken links.

Best, beth

True. But it also helps to use Test::Pod and Perl::Critic with Pod::Spell.

I tend to only use pod2html if I'm interested in how the end result will/might look - to use it to parse and validate the POD is, IMO, overkill since you need to run the program and then (re-)load the generated page in your browser.

Whereas, whilst developing/writing the pod, I simply run perldoc over the module/script/pod file under development - much easier and quicker.

A user level that continues to overstate my experience :-))

    #!/usr/bin/perl -w

    use strict;
    use Pod::Simple::HTML;

    my $parser = Pod::Simple::HTML->new();

    if (defined $ARGV[0]) {
        open IN, $ARGV[0]  or die "Couldn't open $ARGV[0]: $!\n";
    } else {
        *IN = *STDIN;
    }

    if (defined $ARGV[1]) {
        open OUT, ">$ARGV[1]" or die "Couldn't open $ARGV[1]: $!\n";
    } else {
        *OUT = *STDOUT;
    }

    $parser->index(1);
    $parser->html_css('http://search.cpan.org/s/style.css');

    $parser->output_fh(*OUT);
    $parser->parse_file(*IN);

    __END__
[download]

    perl pod2cpanhtml.pl Module.pm > module.html
[download]

Update: This utility is now available on CPAN as pod2cpanhtml which is installed as part of App::Pod2CpanHtml.

--
John.

thanks , this is exactly what I needed and I'm using it now :)

actually now that I think of it, I could've just injected the css ... it's funny

I do care, that's why I posted.

Upload straight html?