-
Notifications
You must be signed in to change notification settings - Fork 236
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 to the MyST documentation system #565
Comments
Docstrings still need to be written in reStructuredText, see executablebooks/MyST-Parser#228. |
@cauliyang Are you still planning to work on this? |
@cjolowicz, Sorry for the late reply, and I am still working on that. Last two weeks, I am busy with my Ph.D. project. I will try my best to finish this switch as soon as possible next week 😃 . |
Cool, you are responsible for lots of work ^^ . do you think which part I should mainly focus on? I will try my best 🚀 |
If I misunderstand you, please correct me. |
Let's start with your existing PR, which converts only the README. The PR should be changed so there is no option for RST: The README will always be Markdown. Does that make sense? We can tackle the rest later. |
Updated the issue description with a breakdown of the files that need to converted. |
Yep, that make sense! I can continue to convert other files under the doc to markdown. If you have any comments please free feel to tell me. It is my pleasure to contribute this project 😎 |
MyST allows you to write Sphinx documentation entirely in markdown.
Here is a breakdown of the files that need to be converted:
The RST files under
{{cookiecutter.project_name}}
:The RST files under
{{cookiecutter.project_name}}/docs
:Converting the Cookiecutter's own documentation is tracked in a separate issue, see #1080.
The text was updated successfully, but these errors were encountered: