Either something has substance that justifies it to be structured in a document for users to download so it can be used in their context, or has become part of the Weekandoo website that users can navigate; e.g. writing down definitions takes time, but once created, there is nothing else to say about it. The whole process from idea to final result is of little interest, expect perhaps for the prompts used, but that's one extra line of text, not worth a whole document that can be downloaded.

What is interesting is how tools got selected, how these tools are integrated, customisations made to code, workflows, explanation of why/what/how practices used, which refer to definitions of terms that are available on the website. Basically, the things that make Weekandoo work, but that users can't see; it either works in the background or is an applied practice that is proven to work, with an explanation why (e.g. psychology, management styles, org structures, etc.)

Once a work item is completed, it's moved to the done-state and added to a collection that makes it easy for users to navigate. It shows the work item definition, like estimated size (perhaps actual cost), description of the value proposition, parent-child relationships, dependencies, etc.; basically for users to use as inspiration for their own work items.

The result of a work item is either a link to the part of Weekandoo that it has updated, the result in the description (in case of definitions) or something that can be downloaded, e.g. source code, designs, guidelines, practices, in which case "add to cart" is shown.