_The Turing Way_ project is an open-source endeavour that empowers contributors from around the world to leverage their skills, knowledge and expertise to build and expand its content.
_The Turing Way_ guides are evolving with multiple chapters co-developed by individuals from varied backgrounds, who are all passionate about sharing knowledge around data science and research.
To sustain and support this vibrant community, _The Turing Way_ book must remain consistent and accessible as it evolves.
Although the style guide chapter already outlines guidelines for keeping a consistent style across the book, not all chapters follow these suggestions as they have been written asynchronously by different authors.
We have curated a consistency checklist that chapters in _The Turing Way_ need to pass to help us maintain a consistent style across the book. However, we need your help to push this forward!
For reference, the checklist is discussed in the chapter on maintaining consistency in _The Turing Way_. There you can also find useful instructions on how to address these issues
At the time that this issue was created, the maintaining consistency chapter is yet to be merged. However, you can check out the PR here
This issue focuses on maintaining consistency in Typical workflows subchapter of the Code Reviewing Process chapter in the Guide to Reproducible Research. To help with this, we invite contributors to do the following:
## becomes #).Typical workflows to Typical Workflows)Anyone who would like to make the _The Turing Way_ as consistent and polished as possible. We especially welcome new contributors to try their hand on this!
For any questions, comments, suggestions, or feedback, please comment below :muscle:
Actions:
Most helpful comment
Actions: