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 to the MyST documentation system #565

Closed
cjolowicz opened this issue Sep 25, 2020 · 9 comments · Fixed by #1089
Closed

Switch to the MyST documentation system #565

cjolowicz opened this issue Sep 25, 2020 · 9 comments · Fixed by #1089
Labels
documentation Improvements or additions to documentation
Milestone

Comments

@cjolowicz
Copy link
Owner

cjolowicz commented Sep 25, 2020

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:

  • The wrapper files: codeofconduct.rst, contributing.rst, license.rst
  • The API reference: reference.rst
  • The command-line reference: usage.rst
  • The index: index.rst

Converting the Cookiecutter's own documentation is tracked in a separate issue, see #1080.

@cjolowicz cjolowicz added the documentation Improvements or additions to documentation label Sep 25, 2020
@cjolowicz cjolowicz added this to the Backlog milestone Sep 25, 2020
@cjolowicz cjolowicz changed the title Evaluate the MyST documentation system Switch to the MyST documentation system Jul 15, 2021
@cjolowicz cjolowicz modified the milestones: Backlog, Near-term Jul 15, 2021
@cjolowicz
Copy link
Owner Author

Docstrings still need to be written in reStructuredText, see executablebooks/MyST-Parser#228.

@cjolowicz
Copy link
Owner Author

@cauliyang Are you still planning to work on this?

@cjolowicz cjolowicz linked a pull request Jan 4, 2022 that will close this issue
@cauliyang
Copy link
Contributor

cauliyang commented Jan 4, 2022

@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 😃 .

@cjolowicz
Copy link
Owner Author

cjolowicz commented Jan 4, 2022

Awesome, no rush :)

I'll be working on converting the files outside the generated project (like the top-level README and the files under docs), see #1080.

@cauliyang
Copy link
Contributor

Cool, you are responsible for lots of work ^^ . do you think which part I should mainly focus on? I will try my best 🚀

@cauliyang
Copy link
Contributor

If I misunderstand you, please correct me.

@cjolowicz
Copy link
Owner Author

do you think which part I should mainly focus on?

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.

@cjolowicz
Copy link
Owner Author

Updated the issue description with a breakdown of the files that need to converted.

@cauliyang
Copy link
Contributor

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 😎

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants