Interactive JavaScript API Reference
JavaScript CSS
Permalink
Failed to load latest commit information.
content Add some missing CSSStyleDeclarations parameters Apr 29, 2016
static
templates
.gitignore
LICENSE
README.md
gulpfile.js
jsdocparser.js
makeapisets.js
makecustompage.js
makemetadata.js
makepage.js
package.json
styles.scss
template.js
test-jsdocparser.js

README.md

JavaScripture

JavaScripture.com is designed to be the fastest and easiest to use JavaScript API reference site by providing simple descriptions and interactive examples.

Contributing to the Documentation

JavaScripture's HTML is generated from a series of text files that contain the API, descriptions, and examples. Each text file describes one JavaScript type. The text files are grouped in folders under the content/ directory. These folders generate the sets available in the drop down under the search box on the website.

Copyright and License

Before contributing, be aware that the examples on the site are in the public domain. The remaining documentation and code are available under the Creative Commons Attribution-ShareAlike license. By contributing, you agree that the works produced are your own and to release the works under the corresponding license(s) listed above.

Getting the code and making changes

To contribute, you first need to fork the JavaScripture repository into your GitHub account where you will make your local changes. Then you will issue a pull request to get the get your changes into the main repository that the website is built out of.

Here are some helpful links to the GitHub documentation on using GitHub.

Building the documentation

After forking the repository (or making changes to your repository), you can build the site's html files.

Prerequisites for building

To build the documentation, run:

  • gulp

From the root folder. The generated files are in the site/ folder.

Documentation File Format

The information for each type is stored in a .jsdoc file. This is a custom file format that describes a JavaScript type.

Here's a simplified example (see content/JavaScript/Array.jsdoc for the complete file):

Array : Object

Arrays are containers ...

Spec:
http://...

----
new Array(length : Number) : Array

Creates a new Array...

<example>
console.log(new Array(5).length);
</example>

Spec: 
http://...

----
instance.length : Number

The number of items in ...

<example>
console.log(new Array(10).length);
</example>

Spec:
http://...

The file is broken into separate sections for each member of the type. The sections are separated by a line containing four dashes: "----"

Member Description

The first line in the first section is the type described in the file. The type is followed by a ":" and the base type.

After first line in the other sections are the member that section describes. The format for this line can be in any of the following:

The parameterList is a comma separated list of "name : Type" pairs (or empty if there are parameters). Optional parameters should be wrapped in []. After the name, you can specify " = value" to specify what value is used if the parameter is not specified. Here are some examples:

If the method takes a function as a parameter, such as a callback, you can specify parameters and return value such as:

If the method takes an object with several properties, you can define the expected properties like:

new Blob( \ 
    blobParts : Array, \
    [blobPropertyBag : { \
        type : String /* A valid mime type such as **'text/plain'** */, \ 
        endings = 'transparent' : String /* Must be either **'transparent'** or **'native'** */ \ 
    }]) : Blob

Description

After the first line of the section comes the description text for that member. In the description area, there is some special syntax to add links, code tags and examples.

  • Use %%link|Link Description%% to generate <a href="link">Link Description</a>
  • Use ** Code ** to generate <code>Code</code>

Also inside the description section you can add an example using the format:

<example>
console.log(10);
</example>

Or

<htmlexample>
<div>Hi</div>
<script>
  console.log(10);
</script>
</htmlexample>

The <example> generates an interactive example that only contains a text output area. <htmlexample> generates an interactive example that has an iframe to display the HTML and a text area below that to display the console output.

Metadata

After the description comes additional metadata for the member. The metadata is described by:

MetadataName:
MetadataValue

The possible MetadataNames are:

  • Spec - the value should be the link to the specification
  • ReadOnly - value should be true if the property is read only. Defaults to false.
  • Value - the value of the property such as seen here

Places For Contribution

Any contributions would be greatly appreciated.

Here are some ideas for improvements:

  • Spelling, grammar, and other editorial issues
  • Add missing descriptions and examples
  • Add any missing types
  • Switch documentation format to Markdown
  • Translate in other languages than English