Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversion of written material to RMarkdown #8

Open
6 tasks
katherinehebert opened this issue Jul 16, 2021 · 0 comments
Open
6 tasks

Conversion of written material to RMarkdown #8

katherinehebert opened this issue Jul 16, 2021 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@katherinehebert
Copy link
Contributor

Please read through the presenter and developer protocol for help with the GitHub workflow. For RMarkdown help, refer to our book template. R Markdown: The Definitive Guide is also a very helpful resource, and covers the tasks outlined below.

  • Remove symbols inherited from conversion from wiki to RMarkdown. We converted the content from our wiki to RMarkdown files, which has left a few symbols (such as '' before punctuation symbols) scattered throughout the text. Please remove these symbols within the text.
  • Convert mathematical symbols and equations to LaTeX format to ensure they are rendered correctly. There is an example of a LaTex equation in our book template, and a helpful guide to mathematical notation in RMarkdown here.
  • Match code chunks to the presentation. Verify that all code shown in the presentation is present in the RMarkdown version. The wiki and presentations were developed along different timelines, so certain code chunks may need to be inserted for the first time, completely changed, or edited. It is particularly important for the exercises (or challenges) to match the challenges in the presentations.
  • Add supporting images from the presentation and the wiki to the RMarkdown. These images include any image that is not coded in the presentations, including diagrams to explain contents or methods in greater detail.
  • Verify the code. Verify that the code chunks work, and that relevant outputs (tables, figures, etc.) are being shown correctly in the book.
  • Verify the writing. Reading through the text to improve the grammar and syntax is greatly appreciated, if time permits.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants