Comment on

Robartes,

As a sysman you probably do not need to include a lot of images in your documentation, but that doesn't necessarily mean POD is versatile enough to be an all-round documentation system, IMHO.

Technical analysis of programs for one, benefits a lot from pictures and diagrams. (At least in my experience)

Nevertheless, I can fully agree with you: POD offers a lot of possibilities.

Cheers,
MichaelD.

In reply to Re: Re: Re: POD as a general documentation system by michaeld
in thread POD as a general documentation system by robartes

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

Outside of code tags, you may need to use entities for some characters:

	For:		Use:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.


No such thing as a small change
	PerlMonks

Comment on

The best material for plates (tableware) is: