Larger Documentation Use Case Headings?

I was reading through the documentation and got to the JQuery case, and at that point it was a little confusing. I did not see the JQuery heading because it’s written in small light gray color, and if I had seen that right away, it would have been a lot less confusing …

It’s still seems a little “Indirect” to go directly from Papa.parse to $ … I’m assuming some JQuery plugin or something is needed to complete the setup?

[pokoli]

Hi @oleersoy,

Our docs are in the docs folder in this repository and are written using html. Any patch to improve it’s format is welcome!

[oleersoy]

I have a doubt about the TypeScript integration. Does the process of using paparse with typescript differ for any other javascript library?

Only the setup part (Installing the @Types for Node and Papaparse). Once Typescript compiles to Javascript the rest of the process should be the same.

I will prefer to add a link to the oficial typescript documentation where it explains how to use with a existing framework than copying a custom descrption. Of course, any PR including this is also very welcome

Sure - I was also thinking also perhaps just add links to articles in the README.md that way specific integration setups. That way they can just be added with little effort as people write them up.