The problem is that we don't tell them (simply) the "how?", It may seem obvious for people used to working with GitHub, markdown, and GitHub pages. But it is not the case for everyone, and it's understandable we work with heterogeneous people (managers, researchers, interns, externs, newcomers, ...) whose main focus is not to spend their days writing markdowns and submitting pull requests.
My propositions
So my proposition would be to make things the most explicit possible, by doing these documentation pages
The issue
We have a centralized and open-sourced documentation https://ontoportal.github.io/administration/ , and ask people to contribute to it.
The problem is that we don't tell them (simply) the "how?", It may seem obvious for people used to working with GitHub, markdown, and GitHub pages. But it is not the case for everyone, and it's understandable we work with heterogeneous people (managers, researchers, interns, externs, newcomers, ...) whose main focus is not to spend their days writing markdowns and submitting pull requests.
My propositions
So my proposition would be to make things the most explicit possible, by doing these documentation pages
And for people that want (and need) to know the details: