The vis.js library is developed by <ahref="http://almende.com"target="_blank">Almende B.V</a>,
as part of <ahref="http://chap.almende.com/"target="_blank">CHAP</a>.
Vis.js runs fine on Chrome, Firefox, Opera, Safari, IE9+, and most mobile browsers (with full touch support).
This site contains documentation, downloads and live examples of vis.js. The <ahref="https://github.com/almende/vis/issues">sourcecode of vis.js</a> is available at Github. For questions, issues, and suggestions please use the <ahref="https://github.com/almende/vis/issues">issues section</a> of the Github project.
<h3>installing with npm</h3>
<preclass="prettyprint">npm install vis</pre>
<h3>installing with bower</h3>
<preclass="prettyprint">bower install vis</pre>
<ahref="download/vis.zip"><h3>download zip (version <spanclass="version">3.6.2</span>)</h3></a>
The vis.js library is developed by <ahref="http://almende.com"target="_blank">Almende B.V</a>,
as part of <ahref="http://chap.almende.com/"target="_blank">CHAP</a>.
Vis.js runs fine on Chrome, Firefox, Opera, Safari, IE9+, and most mobile browsers (with full touch support).
This site contains documentation, downloads and live examples of vis.js. The <ahref="https://github.com/almende/vis/issues">sourcecode of vis.js</a> is available at Github. For questions, issues, and suggestions please use the <ahref="https://github.com/almende/vis/issues">issues section</a> of the Github project.
<h3>installing with npm</h3>
<preclass="prettyprint">npm install vis</pre>
<h3>installing with bower</h3>
<preclass="prettyprint">bower install vis</pre>
<ahref="download/vis.zip"><h3>download zip (version <spanclass="version">3.6.2</span>)</h3></a>
</p>
</div>
</div>
</div>
</div>
<hrclass="featurette-divider">
<br/><hrclass="featurette-divider"><br/>
<divclass="row featurette"id="showcase">
<divclass="col-md-7">
<h2class="featurette-heading">Showcase; <spanclass="text-muted">see vis in action!</span></h2>
<pclass="lead"><ahref="showcase.html">In this section you can see cool projects that vis was used in.</a> If you have made something and would like it featured,
please make an <ahref="https://github.com/almende/vis/issues"target="_blank">issue on github</a> with your project and how you'd like to be credited.</p>
<divclass="valign_parent">
<divclass="valign_child">
<h2class="featurette-heading">Showcase; <spanclass="text-muted">see vis in action!</span></h2>
<pclass="lead"><ahref="showcase.html">
In this section you can see cool projects that vis was used in.</a> If you have made something and would like it featured,
please make an <ahref="https://github.com/almende/vis/issues"target="_blank">issue on github</a> with your project and how you'd like to be credited.</p>
<h2class="featurette-heading">Contributing; <spanclass="text-muted">join the project</span></h2>
<pclass="lead">Since vis.js is an open source project, everybody can contribute to it. If you want to contribute, great! Here's how:</p>
<pclass="text-justify">First, fork vis on Github, then add your feature, fix a bug,
rephrase our writing etc. and do a <ahref="https://help.github.com/articles/using-pull-requests/">pull request</a> to the develop branch on Github!
Pull requests to the master branch will not be merged.
<br/><br/>
If you fork the codebase, you'll find all modules in seperate files. This makes it a lot easier to work on than the distributed and combined vis.js file.
<br/><br/>
If you want to contribute but don't know how, feel free to pick up <ahref="./featureRequests.html">a feature request described below</a>!
These come from ourselves as well as from Github issues. If you do, <ahref="https://github.com/almende/vis/issues"target="_blank">please post an issue on Github letting us know</a>, so we can mark the feature
under development as well as help out when needed. If we are about to implement something from <ahref="./featureRequests.html">the list</a>, we'll remove it before starting.
</p>
<divclass="valign_parent">
<divclass="valign_child">
<h2class="featurette-heading">Contributing; <spanclass="text-muted">join the project</span></h2>
<pclass="lead">Since vis.js is an open source project, everybody can contribute to it. If you want to contribute, great! Here's how:</p>
<pclass="text-justify">
First, fork vis on Github, then add your feature, fix a bug,
rephrase our writing etc. and do a <ahref="https://help.github.com/articles/using-pull-requests/">pull request</a> to the develop branch on Github!
Pull requests to the master branch will not be merged.
<br/><br/>
If you fork the codebase, you'll find all modules in seperate files. This makes it a lot easier to work on than the distributed and combined vis.js file.
<br/><br/>
If you want to contribute but don't know how, feel free to pick up <ahref="./featureRequests.html">a feature request described below</a>!
These come from ourselves as well as from Github issues. If you do, <ahref="https://github.com/almende/vis/issues"target="_blank">please post an issue on Github letting us know</a>, so we can mark the feature
under development as well as help out when needed. If we are about to implement something from <ahref="./featureRequests.html">the list</a>, we'll remove it before starting.
<pclass="lead">We get a lot of feature requests on Github. <ahref="./featureRequests.html">Here's a list of them!</a></p>
<pclass="text-justify">The requests that come in on Github usually have a good argumentation and a lot of these ideas have made it into vis! To keep a nice overview of them, to clean up
our Github issues and to supply a pool of ideas for people to contribute, we have made <ahref="./featureRequests.html">this list.</a>
<br/><br/>
This is by no means an end-of-the-line for your feature, but just something that we cannot pick up right away or cannot use in our projects at this time.
We'd like to invite people who want to contribute to pick up one (or more!) of these features. <ahref="./featureRequests.html">View the list here.</a>
<pclass="lead">We get a lot of feature requests on Github. <ahref="./featureRequests.html">Here's a list of them!</a></p>
<pclass="text-justify">
The requests that come in on Github usually have a good argumentation and a lot of these ideas have made it into vis! To keep a nice overview of them, to clean up
our Github issues and to supply a pool of ideas for people to contribute, we have made <ahref="./featureRequests.html">this list.</a>
<br/><br/>
This is by no means an end-of-the-line for your feature, but just something that we cannot pick up right away or cannot use in our projects at this time.
We'd like to invite people who want to contribute to pick up one (or more!) of these features. <ahref="./featureRequests.html">View the list here.</a>