documentation is a mix of markdown and restructuredtext

[deronnax]

Issue description

documentation is a mix of markdown and restructuredtext, but the documentation says the documentation is restructuredtext. I found out commit 761a03d seemingly did a conversion to markdown which did not go all the way to the end.
I would like to know what is the pursued direction (markdown + restructuredtext or full markdown), and if the direction is full markdown, try to help.

Expected result

• either the documentation says the documentation is both markdown and restructuredtext
• either we clean out one of them (restructuredtext, I guess)

Actual result

mix of both

Steps to replicate

N/A

[matteius]

@deronnax Full markdown would be preferred I think; I ran out of time when I was working on that before. Any help is appreciated.

[thiagogquinto]

Hey @deronnax, @matteius , I am new in open source community, if possible, could I be assigned to this task? Just to be clear, if I be assigned, once I start making the contribution, I convert to fully md or fully rst?

[matteius]

@thiagogquinto I believe @deronnax is offering to help with this, but either way -- the plan is to go fully markdown. (so .md)

[thiagogquinto]

Ok @matteius, thanks for the reply! I will let him work on it then. Will just ask @deronnax that in case he changes of mind, let me know, please.

[deronnax]

@thiagogquinto I have not started the work, so you can take it :)

[thiagogquinto]

Thanks, I will work on it then.

[thiagogquinto]

Hey @matteius, could you help me with the following question: do you know what this reference points to?

No, it does not, intentionally. Pipfile and setup.py serve different purposes,
and should not consider each other by default. See :ref:`pipfile-vs-setuppy`
for more information.

The file is here, the line in question is on the line 102 of the file.