-
Notifications
You must be signed in to change notification settings - Fork 3
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
READMEs using .Rmd/.ipynb? #41
Comments
For the disadvantage point: do you really need to keep the md file? |
I'd want the docs to be visible in the repository, and Github renders So yes, I think the |
Interesting, I didn't know. However, it won't be able to show the result of R commands. If the |
Ok, I am probably slow to understand what you want: you want to be able to showcase the functionality, right? So why can't you just add the expected results in another chunk instead with
but you can still see it. Then, the Rmd can be used as a checking tool as well (which was the first reason you wanted to shift to .Rmd, no?) |
I’ve never used Jupyter, if the R integration isn’t too convoluted (such as having to wrap every R call into a Python wrapper …), I have no objections. |
After installing the kernel and a couple of packages, it's just selecting R from a dropdown menu. |
Just have seen this. This seems pretty nice. Can you confirm how it behaves with an extensive use? |
I haven't used them extensively, but so far they are working well. |
The couple of
README
s we have got now highlight some functionality of the modules they are in.Does it make sense to have
.Rmd
files instead that generate thoseREADME
s to showcase functionality?Advantages
.md
sDisadvantages
The text was updated successfully, but these errors were encountered: