Testing Story Print Mech

We support a process of collective story telling supported by a gardenof lived experiences. New with version 0.1.35

One individual's story is told in a sequence of pages specified by an additional page that list them in order as References. Once identified, we can WALK this sequence and notice what additional pages provide the support.

It has been suggested that my way is to make "the simplest thing that could possibly work and then milk the possibilities for a long time before adding on." when in fact I have many ways.

CLICK FROM code.fed.wiki.org/the-ward-way NEIGHBORS code WALK 2 clicks PREVIEW synopsis graph

We expect the reader to willingly depart from the story to ramble briefly through the garden. The page one click from the story is the "gateway" and has important context setting responsibility. One can assume a limit to how far a reader will stray. Possible routes become larger as clicks grow so SOLO provides more managed browsing of the possibilities.

CLICK FROM code.fed.wiki.org/the-ward-way NEIGHBORS code WALK 3 clicks CLICK SOLO

We soon wonder what this content will look like on paper. Here PRINT recognizes both story and garden and will produce a single downloadable file that can be saved as PDF for offline reading and further downstream publishing.

CLICK FROM code.fed.wiki.org/the-ward-way NEIGHBORS code WALK 3 clicks CLICK PRINT outline CLICK PRINT draft CLICK PREVIEW synopsis items

When PRINT completes it downloads a single file named print-story.html. Open this from the browser and choose As PDF in the print dialog.

PRINT records applicable conversion statistics a items available to PREVIEW. PRINT outline notices Sourced Sites, Missing Pages, and Omitted Links. PRINT draft further notices Unusual Plugins and Program Errors.