# Contributing to Haxe manual
**URL:** https://community.haxe.org/t/contributing-to-haxe-manual/233
**Category:** Haxe
**Tags:** documentation
**Created:** [November 24, 2017, 5:03pm UTC](https://community.haxe.org/t/contributing-to-haxe-manual/233 "2017-11-24T17:03:43Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@elsassph](https://community.haxe.org/u/elsassph)
#### Post date: [November 24, 2017, 5:03pm UTC](https://community.haxe.org/t/contributing-to-haxe-manual/233/1 "2017-11-24T17:03:43Z")
As I was answering tips about `@:jsRequire` ([Haxe-react- howto create externs for grid-styled - #9 by axelhuizinga](http://community.haxe.org/t/haxe-react-howto-create-externs-for-grid-styled/198/9)) I had a look at the documentation ([Loading extern classes using "require" function - Haxe - The Cross-platform Toolkit](https://haxe.org/manual/target-javascript-require.html)) and though “oh maybe I could add something here”.
“Contribute to this page” deeplinks to the article on Github, but generally the repository root doesn’t have any documentation on How to contribute - I’d expect something explaining the decision/review process, and more importantly, how to build it locally to preview the changes?
---
### Author:  [@elsassph](https://community.haxe.org/u/elsassph)
#### Post date: [November 26, 2017, 11:25pm UTC](https://community.haxe.org/t/contributing-to-haxe-manual/233/2 "2017-11-26T23:25:44Z")
So I wrote a blog post about that:
> **[Using NPM modules from Haxe](http://philippe.elsass.me/2017/11/using-npm-modules-from-haxe/)**
>
> When targeting JavaScript, using NPM modules is a must, and although there is nothing you can’t do with Haxe, it requires to understand how these modules work in order to write (even minimal) externs.
Some of that info would be useful to have in the documentation - like “how to convert ES6 imports into Haxe require”.
---
### Author:  [@mark.knol](https://community.haxe.org/u/mark.knol)
#### Post date: [November 29, 2017, 7:29pm UTC](https://community.haxe.org/t/contributing-to-haxe-manual/233/3 "2017-11-29T19:29:31Z")
Doesn’t this info help?
>
In the haxemanual project there is a convert.hxml, you can run that to generate the markdown files. You can check those markdown files in online tool to check if it looks good.
In the convert hxml you can disable pdf/ebook related commands.
Hope this helps, otherwise let me know!
---
### Author:  [@elsassph](https://community.haxe.org/u/elsassph)
#### Post date: [November 29, 2017, 8:47pm UTC](https://community.haxe.org/t/contributing-to-haxe-manual/233/4 "2017-11-29T20:47:03Z")
Thanks, I had skimmed through this readme but missed the compilation.