Thank you Dan for the tips!
Right now I think the discussion of documentation is centralized in educational practice inside academic environment. I had contact with the Pd in this environment but now I see a lot of people having contact with Pd inside free workshops, which brought other ways to search for information.
An example is here in Brazil, I noticed that the English language has been a big obstacle in the tool's learning path. Even for teachers who teach classes to teenagers. So I have been thinking about ways to alleviate the difficulties, which inevitably involves supporting multiple languages in the documentation. There is a
discussion about this in the list.
There are various insights about efforts to provide support to multi-language patches inside Pd, move the focus of objects reference to html files to be opened on browser and called from Pd patch. There are to
references about Processing and OpenFrameworks docs and a draft survey of possibilities to provide a platform that allows the inclusion of content tutorials regarding synthesis techniques and everything else.
Personally I believe we have a lot of work done using this information and the help patch models done in Pd-extended. Would be great if we can find this documented.
To point some examples of things already done in regard to better documentation:
- Porres' ELSE documentation and the Live Electronics Tutorial are good because of the care to register and create patches that are visually unified, that show a concern with good practices of patches creation.
I started to asking about in Pd patch repo, telegram Pd group, discord and Facebook, and there at this moment people sent:
-
https://gridflow.ca/help/ - which I see interesting the use of colors in the patch which is more apelative to the eyes. But to go in this way mapping the audience is required.
Another very blowing mind in my view, which amplify the scope of the problem in my point of view is the
mscotthouston post on github related issue, he reach at github issue from a call I did in pd discord channel.
Please, disagree, propose and take a stand. This way, it will be possible to map a little of what the pd community needs in new documentation.