# Meta: Documentation Guidelines
If you want your code to be copy-pastable, remove prompts such as
+ at the beginning of each new line. Some Docs authors prefer to not make copy-pasting easy, and that is okay.
# Console output
Console output should be clearly distinguished from code. Common approaches include:
- Include prompts on input (as seen when using the console).
- Comment out all output, with
##starting each line.
- Print as-is, trusting the leading
to make the output stand out from the input.
- Add a blank line between code and console output.
<- are fine for assigning R objects. Use white space appropriately to avoid writing code that is difficult to parse, such as
x<-1 (ambiguous between
x <- 1 and
x < -1)
# Code comments
Be sure to explain the purpose and function of the code itself. There isn't any hard-and-fast rule on whether this explanation should be in prose or in code comments. Prose may be more readable and allows for longer explanations, but code comments make for easier copy-pasting. Keep both options in mind.
Many examples are short enough to not need sections, but if you use them, start with H1.
# Making good examples
Most of the guidance for creating good examples for Q&A carries over into the documentation.
library(help = "datasets")
There are some additional considerations in the context of Docs:
To discuss editing the R tag Docs, visit the R chat.