Hi all,
I'm very excited and motivated to help on this/these projects. I want to share this resource for thinking about documentation: https://documentation.divio.com/
Basically, we could think of our documentation as split between four different things: Tutorials and Explanations (which are maybe more useful for beginners, students) and How-To Guides and Reference (maybe more useful for advanced users, developers, and so on).
In thinking about what goes where, whether that be internal documentation, PD's HTML manual, FLOSS manuals, resources on puredata.info, etc., we should be thinking about the above four-part division. Or at least, something along those lines.
A book like Kreidler's loadbang is a great example of Tutorial and Explanation. The FLOSS manuals lean more towards How-To Guides. The internal help files are closer to Reference. We don't have to follow these exact distinctions, but I think that making *some* distinctions will help us as we sort where different kinds of information need to go.
Alexandre--I'm happy to put all this into an issue on the github, or add it on to an existing one, if you think that would help.
Best, Matt
On Mon, Nov 22, 2021 at 8:36 AM Alexandre Torres Porres porres@gmail.com wrote:
Em seg., 22 de nov. de 2021 às 11:14, ub ub@xdv.org escreveu:
a manual living on the www would be internet-searchengine-findable!
Pd's actual manual actually already lives on the internet: http://msp.ucsd.edu/Pd_documentation/index.htm _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list