[epo-core] List of supported projects

[J. Shirley]

On Mon, Sep 15, 2008 at 10:14 AM, Jesse Vincent <jesse at fsck.com> wrote:
>>
>> I would propose development of a pod-book system.  I hacked up a proof
>> of concept that simply parsed a YAML file to establish relations
>> between pod, and generate out a tree, it was incredibly ugly and not
>> quite finished but easy enough to work on.  Uses TT to render from
>> Pod::POM, pretty basic.
>
> It's called PseudoPod and was developed by O'Reilly.
> http://search.cpan.org/dist/Pod-PseudoPod/ is, as far as I know, pretty
> recent.
>

Sorry, I think there's been some misunderstanding (but it happens a
lot, I think I don't explain it well, or perhaps focus on the wrong
points first).

To try again, my work is not around formatting instead around cohesive
structure.  The PseudoPod work is more targeting my comment about Pod
itself being a good reference format by expanding the offerings to
have singular pages have more substance beyond reference lists.  It
doesn't address the notion that Pod documents are single documents and
there is no way to cohesively bind multiple pod documents together
outside of pod documents.

The idea that it is Pod could be substitutes for any other format,
really.  Pod::POM or PseudoPod are irrelevant, I just want something
that injects nodes in the rendering bit that creates a work flow
through the documents.  As far as I know, even with PseudoPod, the
only way to do that is to put the data directly in the Pod itself.  I
read PseudoPod's pod again, and didn't see any other top level
structural bits that do what I'm aiming for.

-J