Sure @magdesign and @Shrinks99. I fully understand that wiki is not the best for documentation and also current method is easy for developers. I felt it is quite difficult for non-programmers to support Natron, so everything is burden of few persons. Shouldn’t of course change anything by random request if that ends up having documentation maintenance totally neglected.
And nothing official should locate in 2 places to be maintained. That would be waste of time. Also I don’t know how many Natron users there are, so maybe it is not possible to get more contributors no matter where documentation Is is located.
Documents are anyway not the most important for keeping the software project alive and I’m very happy to see that it is maintained by rodlie, although I think very much alone. And Devernay seems to be keeping all in order. Even new version was released that I haven’t downloaded yet.
Long message again, but maybe my earlier post was more for myself to remember to start following this forum again and using Natron when getting some free time.
I agree that it is hard for non-programmers to get started on things like a version control system; indeed I am myself a programmer, and I still find it intimidating to contribute to Natron’s massive codebase!
I’ve hosted a simple editable wiki here: https://hackmd.io/@4Hwha1m4Tgm-uIGs2O6kwg/SkdrzENDO/edit. It is formatted with markdown which has a really simple syntax. I can merge this periodically into the main Natron docs, and there are a plethora of markdown to rst converters out there. If you have time to, feel free to add to the docs there.
I’m starting to make screenshots for the documentation. Does anyone know if a new skin of Natron is currently worked on ? If so I would need a beta version to avoid the docs feeling outdated pretty soon.
@bonalex01 Thanks for your great work! Though syncing directly to Github would be nice, the main issue is that Natron’s docs are in RST format, while HackMD is markdown. Converting between the two formats is trivial with a bit of shell scripting and pandoc, but I want to keep the two separately and manually add the WIP docs on hackmd to Natron’s repo one at a time to ensure that the main docs are clean.
I think the hackmd.io experiment is not successful for me because:
doesn’t deal with the important step of interlinking the different pages of the documentation.
it badly renames images
as we knew it requires translation from md to rst.
My new workflow:
Visual studio code
RestructuredText VSCode extension (provides sphinx compilation)
GIT publishing tools of VSCode to send the result strait to github
if we go that route .