convert README and Doc files to markdown?
See original GitHub issuePyPI recently added support for package long_description
set in Markdown format, and Sphinx also supports Markdown (see http://www.sphinx-doc.org/en/master/usage/markdown.html).
ReStructuredText may be more powerful, but life is too short to learn another markup language, and most people are already familiar with Markdown.
I also believe that having the docs set in Markdown instead of RST may lower the entry barrier and we could get more contributions.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Docs to Markdown - Google Workspace Marketplace
Docs to Markdown (GD2md-html) converts Google Docs to simple, readable Markdown or HTML. Now open-source! This add-on allows you to create documents using ......
Read more >ms office - How can doc/docx files be converted to markdown ...
Pandoc supports conversion from docx to markdown directly: pandoc -f docx -t markdown foo.docx -o foo.markdown. Several markdown formats are supported:
Read more >Convert WORD to Markdown Online - Aspose Products
1. Upload Word files to convert them to MD format online. 2. Specify Word to MD conversion options. 3. Click the button to...
Read more >How to Easily Convert Word to Markdown with Pandoc - Medium
The easiest way to convert a Word document to a Markdown file is with the -f (FORMAT) flag. This is the file format...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
not sure I qualify as a “Sphinx expert”… but here’s my 2¢:
all Sphinx projects I’ve worked on were written in reST. I have yet to see a project using Sphinx with Markdown.
it’s very easy to learn reST (and Sphinx) by looking at the source code of vanilla, defcon, fontParts, drawBot etc.
the biggest barrier to writing documentation is writing documentation 😃
This is automated with RTD and is simple to implement. The sphinx-quickstart configuration tool does most of the work for you and RTD updates with every commit pushed to the repository so there is no documentation maintenance involved. Any undocumented areas would just need to have the docstrings updated.
Agree. Would add that it would be helpful to have separate Markdown documentation (or a dedicated documentation website) for the executables in the project along with some common usage examples. Searching through RTD to find the module that implements the executables is an unnecessary barrier to understand how they work. I would recommend working under the assumption that many users with an interest in this project will approach it with no knowledge of the organization of the source and where to find this information in the automated documentation or source docstrings.
pandoc makes MD --> rST simple. It may support the rST --> MD direction as well. I am not a fan of rST and use MD --> rST whenever it is necessary.