view release on metacpan or  search on metacpan

lib/App/Pods2Site/Args.pod  view on Meta::CPAN

first and then add a '--group :std' for automatically filling in all the others. For a bit more control, each of the
groups in ':std' can be used separately, e.g. as ':std-core'. If this is not sufficient, customize all options with
help from below.
 
The groups will maintain the order given.

Available internal groups:

=over

=item * :std-core

The pods in the 'pods::' namespace.

Corresponds to the query:

  type.eq(corepod)

=item * :std-scripts

All pods found in the bin directories, plus the 'pp' module as it documents the 'pp' script.

Corresponds to the query:

  type.eq(bin) || name.eq(pp)

=item * :std-pragmas

All pods starting with a lowercase letter (but not any selected by the other groups).

Corresponds to the query:

  type.eq(lib) &&
    name.regexp{^[a-z]} &&
    NOT name.eq(pp)

=item * :std-modules

All pods not selected by the other groups.

Corresponds to the query:

  NOT
    (
    	type.eq(bin) ||
    	type.eq(corepod) ||
        name.eq(pp) ||
        name.regexp{^[a-z]}
    )

=item * :std

All of the above in the order: :std-core, :std-scripts, :std-pragmas, :std-modules.

=back

=back

=item B<sitedirectory> or B<:std>

This is where the site should be created or updated. If the path doesn't exist, the full site will be created.

If the path exists, it must contain a site created by this tool, and will then be updated efficiently
(e.g. only new/updated pods will be written as necessary).
In this case however, the listed L<"Sticky options"> above are not allowed on the command line.
Instead they will be read from the site and reused as they were when the site was created.

Use C<:std> for the sitedir 'pods2site' inside the Perl tree (will only work if you have write permissions
there).
 
=back

=head1 MORE HELP

For full information on Pods2Site, see the L<manual|App::Pods2Site>, or use I<--manual>
or run I<perldoc App::Pods2Site> to see the manual page.

=cut