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

switch pkg to use markdown docs #658

Closed
sckott opened this issue Feb 1, 2018 · 8 comments
Closed

switch pkg to use markdown docs #658

sckott opened this issue Feb 1, 2018 · 8 comments

Comments

@sckott
Copy link
Contributor

sckott commented Feb 1, 2018

No description provided.

@sckott sckott added this to the v0.9.3 milestone Feb 12, 2018
@sckott sckott modified the milestones: v0.9.3, v1.0 Mar 20, 2018
@sckott sckott added the docs label Mar 20, 2018
@alanocallaghan
Copy link

Can you elaborate on this a bit @sckott ?

@jarioksa
Copy link
Contributor

Yeah, I'm baffled, too. rmarkdown is a tool: why should you change the final product (docs) just to use another tool for a similar result?

@Rekyt
Copy link

Rekyt commented Oct 12, 2018

I think that @sckott means to change the documentation that is generated by roxygen2 to use markdown format (see more about it in this vignette of roxygen2)

@sckott
Copy link
Contributor Author

sckott commented Oct 12, 2018

yes, to use markdown formatting instead of latex. i think it's easier for everyone to contribute when it's markdown. in addition, it usually takes up less characters so it's easier less text. I'm not sure i see a downside other than the work that goes into it.

the only caveat is markdown doesn't work in templates AFAIK https://github.com/ropensci/taxize/tree/master/man-roxygen

@alanocallaghan if you're interested in contributing you can look at that link for how to use markdown

@alanocallaghan
Copy link

You mean to change the roxygen docs to use Markdown formatting ("`id`") instead of latex ("\code{id}")?

@sckott
Copy link
Contributor Author

sckott commented Oct 15, 2018

@alanocallaghan Yes, that's one example.

@alanocallaghan
Copy link

Alrighty, I'll try to get that done asap. Thanks for clarifying.

@sckott
Copy link
Contributor Author

sckott commented Oct 16, 2018

@alanocallaghan thanks. i'd suggest doing a one or a few files in a small pull request instead of trying for all of them in 1 PR - and go from there if the first one goes well

@sckott sckott modified the milestones: v1.0, v0.9.7 Mar 11, 2019
@sckott sckott closed this as completed Mar 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants