Hello @jgrenat, that sounds like fun!
I just published a new extensible markdown parser library (check out the README for a description of some of the features that make it unique)
I created a ticket with a “good first issue” tag, in case anybody wants to play around with the
elm/parser library. It’s really fun, but the markdown spec is huge so I would welcome some contributions here!
Hopefully this library is a good place to contribute because it is set up with some nice unit tests and an end-to-end test suite that runs all of the examples from the Github-flavored markdown spec page (1400 tests in all!). So the Travis build will tell you if you introduce any new regressions when you create a pull request. Feel free to ping me on Slack if you end up hacking on it!
Also, you can see all of the current failures in the Github-flavored markdown test suite here. It includes the expected and actual output, and the markdown input that caused it, so it’s pretty useful for just finding something else to hack on in the project.