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

Markdown versus ReStructuredText #49

Closed
jdkent opened this issue Jan 15, 2019 · 3 comments
Closed

Markdown versus ReStructuredText #49

jdkent opened this issue Jan 15, 2019 · 3 comments

Comments

@jdkent
Copy link
Member

jdkent commented Jan 15, 2019

I'm curious if @tsalo or anyone has thoughts about markdown versus restructured text for the documentation, in my project I bit the bullet and pretty much have everything using restructured text so it can be easily rendered by sphinx-text, but markdown is more common in the wild.

@tsalo
Copy link
Member

tsalo commented Jan 15, 2019

I think using rst in the docs is best, and then we can use markdown in the repo proper (e.g., for the README, contributing guide, changelog). We can convert the markdown files from the top level of the repository to rst in the documentation with m2r.

@jdkent
Copy link
Member Author

jdkent commented Jan 15, 2019

That sounds alright to me, for some reason I feel like there were no great tools for converting markdown to restructured text that I could find during Neurohackademy, but I cannot back up my claim with evidence.

@tsalo
Copy link
Member

tsalo commented Jan 15, 2019

m2r has worked for me in the past, but I do remember it taking a while to figure out.

@tsalo tsalo closed this as completed Jun 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants