Hi @pharmaR/ws-communications 👋
Coming out of our exec meeting this week and discussion about the recent Risk Tools developer day, one of the immediate actions we want to take is to establish a much clearer path for new contributors - both for the R Validation Hub as a whole and for the individual software products.
We're blessed to have @terrychr joining us as executive director of the R Consortium because we can tap into her background in marketing to give us some tips.
Doing my best to capture her feedback as we discussed changes to our contribute page
- We should ask ourselves:
- "what is the action [we] want people to take?"
- "how do we lower barriers [to getting involved]?"
- Calls to action should be crisp and clear:
- "If you go here and act like this, this is what will happen"
- It has to be obvious
- Convert blocks of text to visually clear organizations of actions
- Bulleted lists, tables, something that can be easily scanned
- At most 5 calls to action, with indication of expectations after that action
Given that our audience on this page might be more non-technical/leadership focused, or that developers might be earlier in their careers with little open-source experience, we felt that the first stop should be the R Consortium Slack (#wg-r-validation-hub channel) with pinned posts linking to additional resources.
@terrychr offered to take a first pass at the contribute Rmd page to make markdown edits and give feedback as we polish the page.
Hi @pharmaR/ws-communications 👋
Coming out of our exec meeting this week and discussion about the recent Risk Tools developer day, one of the immediate actions we want to take is to establish a much clearer path for new contributors - both for the R Validation Hub as a whole and for the individual software products.
We're blessed to have @terrychr joining us as executive director of the R Consortium because we can tap into her background in marketing to give us some tips.
Doing my best to capture her feedback as we discussed changes to our contribute page
Given that our audience on this page might be more non-technical/leadership focused, or that developers might be earlier in their careers with little open-source experience, we felt that the first stop should be the R Consortium Slack (
#wg-r-validation-hubchannel) with pinned posts linking to additional resources.@terrychr offered to take a first pass at the contribute Rmd page to make markdown edits and give feedback as we polish the page.