Depending on which (INBO) audience you would like to reach to use protocolhelper (I am not a frequent R person, and I did follow the INBO Git course at one point in time, but not recently + not a frequent user), I think you could perhaps "dumb the instructions down"?
For example, if you are someone who needs protocolhelper on an infrequent basis, there could be a section: "Returning to protocolhelper" where you describe how to open de Rproject, perhaps how to check dependencies?
Then for example the instruction below:
The instruction to do the Pull request is intuitive, however it might not be intuitive for the readers to "checkout the main branch"? I could retrace the meaning of checkout from the Git workshop notes; but still finding the correct place in the Git pane when not using it frequently, is not that intuitive. For example I had already pushed the pull button, while searching how to "checkout the main branch", while I didn't check if I was on 'main' (but I was on 'main', so I guess no harm done).
Depending on which (INBO) audience you would like to reach to use protocolhelper (I am not a frequent R person, and I did follow the INBO Git course at one point in time, but not recently + not a frequent user), I think you could perhaps "dumb the instructions down"?
For example, if you are someone who needs protocolhelper on an infrequent basis, there could be a section: "Returning to protocolhelper" where you describe how to open de Rproject, perhaps how to check dependencies?
Then for example the instruction below:
The instruction to do the Pull request is intuitive, however it might not be intuitive for the readers to "checkout the main branch"? I could retrace the meaning of checkout from the Git workshop notes; but still finding the correct place in the Git pane when not using it frequently, is not that intuitive. For example I had already pushed the pull button, while searching how to "checkout the main branch", while I didn't check if I was on 'main' (but I was on 'main', so I guess no harm done).