This plan relies on BookStack for the feature of surfacing the same (linked) content in multiple places; we can't easily replicate that with Dokuwiki.
Printed content and online content are different use cases, and the documents need different features.
Printed content needs features to support a paginated environment:
…and an overall document design that supports readers of a physical document.
(For a fully robust solution, we'd also want an index for large collections, but that's very hard to do.)
Online content needs to support a multi-faceted, random access environment:
In both cases, we need a strong, tested organization so that readers can find what they need, quickly.
Put external-facing content on the public website:
(The class handouts are PDFs, updated as needed, etc.)
If this proves too annoying, we could try a public-facing bookstack shelf…
Put internal-facing content on an internal, member-only bookstack instance.
Shelves are for audiences:
Note that all of these shelves contain information for a particular audience.
While the internal web is not public, material on these shelves is owned by Protohaven, under an appropriate license (CC BY-NC-SA)
A separate, special shelf will hold information by members:
Each member gets a book they can use as they see fit. Members can use this area for various purposes:
All content created by members in the What We're Working On shelf is owned by the respective authors, and Protohaven makes no claim of rights over that material.
If members use this section to produce drafts of work for other sections, the ownership moves to Protohaven when the content is moved to the appropriate shelf.
Books can appear on multiple shelves. We will use the book abstraction for areas of content that may be of interest to one or more of the above audiences:
We leverage BookStack's permissions system to align access to content with need (an example policy: instructors and tech leads get access to the clearance checklists; general members do not).
Make an edit to a book in one place, and the change shows up in all of them.
With this organization, we can provide each audience type with content specific to them (hopefully reducing cognitive load), and users can also delve into other shelves as needed (as long as they have permissions to do so)
The information flow of the usage guides goes something like this (fancy diagram forthcoming):
We take a layered approach with the tool usage guides.
The single source of truth for the tool usage guides are the printed material.
For each tool, the tool usage guide has two parts: the simple version and the extended version.
The simple version is intended for learners and is used as an inclusion in the class notes handouts. The Class Notes handouts can be printed (and instructors should probably have one printed out to show students at the start of class). Most students will likely download the PDF from the public-facing website.
The extended version adds extra notes that may overload a learner, but are important to keep in the guide for shop users. Extended versions are combined into documents that can be printed and kept as physical copies on the shop floor, collecting hand-written notes. Extended versions can also be stored in BookStack, where members can make comments and annotations. These hand-written notes, comments, and annotations can periodically be collected and added to the extra notes in the extended version, which can then be redistributed to the binders, etc.
The workflow for software guides is the same as for tool usage guides above.
Lists (tools, etc.) are loaded form a single source (air table, or google sheets, or…)