Website documentation fixes

[duffee]

This is a checklist of problems in the documentation, meaning small fixes that we need to get around to applying. Add any speeling errors, broken links or things that just don't make sense and we'll fix them.

Fixes to the documentation needed:

• the note about the implementing package being a C<> not a L<> (which wouldn't help anyway since there's no POD in there)
• https://metacpan.org/pod/PDL::Graphics::TriD#points3d says "see module doc" but there isn't any
• PDL::Graphics::TriD::Objects line 7 refers to TkTriD_demo.pm which doesn't exist

[duffee]

Improvements for the PDL book :

• text needs proof-reading
• Table of Contents indentation to reflect structure (can we put section numbers in the table?)
• TODO's collected into a project so they can be systematically tackled
• identify the missing chapters, which functions could do with some love
• fix example script locations (404 for https://pdl.perl.org/content/book/PLplot/x08.pl)
• check code still works as shown
• look into transforming source into Jupyter Notebooks and epub (requirement - code must look good on my Nook)

Resources to consider

• HeVeA is used by Allen Downey to do LaTeX to html translation

[duffee]

• Improve SEO

[duffee]

Tracking minor module perldoc corrections needed:

• PDL::Dataflow ONE-WAY This means PDL will only created directed to create

[mohawk2]

Tracking minor module perldoc corrections needed:

• PDL::Dataflow ONE-WAY This means PDL will only created directed to create

Is it not easier to just PR corrections, rather than carefully track them on a separate repo issue?

[duffee]

Is it not easier to just PR corrections, rather than carefully track them on a separate repo issue?

A PR will take me out of the headspace where I'm reading the docs. Editing an Issue requires no thought, but means I'll get to it at some point.