Name: Documentation
Owner: Babylon.js
Description: BabylonJS documentation page
Created: 2016-01-25 21:16:40.0
Updated: 2018-05-24 18:37:09.0
Pushed: 2018-05-24 00:48:16.0
Homepage: http://doc.babylonjs.com
Size: 111326
Language: CSS
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
Welcome on the repository of the official documentation of Babylon.js.
Before beginning, please be sure to have these packages installed:
See configure a remote for a fork and syncing a fork for additional github documentation.
You don't need to edit html yourself: edit markdown files and use:
ou want to edit some styles or see your changes without repeating ```grunt build```, then use ```grunt serve```.
`localhost:3000`If you want to add/update a tutorial, an extension or a class, you have to follow these steps:
`grunt build`NB: Sections like:
---
ID_PAGE: 24441 // Id of the page in the old doc, use to forward links
PG_TITLE: Cheetah3D // Name of the page in the old doc
TAGS:
- Cheetah3D // Deprecated, will be remove soon, except for classes
---
Are YAML meta description for files, this is used to make some link between the old and the new documentation.
Wherever you find these, please don't touch them :)
Categories classify the content.
Babylon101 - This is an introductory course for Babylon.js that takes users on a step by step journey through many basic features of the Babylon engine. Links on each page takes the reader to extra or related details. This means that although the course can be followed in a linear fashion it is not restricted to being read in this way. The idea is that this heading will stand by itself with no further sub sections.
How To - Usually this will consist of sub sections that descibe with words, pictures, examples and playgrounds how to contribute, apply or use a feature of the Babylon engine. For consistency use titles that complete a sentence starting How to ….
Features - These list and describe the features available with the Babylon.js system, that is the engine, extensions and any other resources that provide support for it and its use. Generally descriptions will be brief with lins to more detail. However there will be occasions when descriptions need to wander into how to territory to ensure clarity of understanding.
Extensions - This section provides details on user written code which extend Babylon.js and have to be loaded in addition to Babylon.js. Such code is found in the extensions repository.
Resources - These provide additional areas of support for Babylon.js and include
Within descriptions in the resources section there will be details of how to apply and use features of a resource. This is different to the 'How to..' section which is limited to Babylon.js itself.
Samples - Small project examples or useful functions.
They are implemented and can be seen in:
* [Babylon 101](http://doc.babylonjs.com/babylon101)
* [How To](http://doc.babylonjs.com/How_To)
* [Features](http://doc.babylonjs.com/features)
* [resources](http://doc.babylonjs.com/resources)
* [extensions](http://doc.babylonjs.com/extensions)
* [samples](http://doc.babylonjs.com/samples)
If you want to add your own content:
`grunt build`The three root arrays are mandatory, when displayed, object's order is kept.
Here is how the object is structured:
{
"How_To": [ // Mandatory
{ // This object represents a folder inside the How_To folder
"title": "title displayed", // The title displayed in the list of folders
"name": "foldername", // The folder name with no spaces, no special chars except underscores
"img": "img/How_To/name.jpg", // Place your image inside the public/img/how_to/
"desc": "my great tutos serie", // This is the description of the folder, don't make it too long :)
"files": [ // This is the list of files inside your folder
{
"title":'tuto title', // The title displayed in the list of How_To
"filename":'tuto title', // The file name with no spaces, no special chars except underscores, and no extension
"hidden" : true // Should this file be hidden in the global list ? false by default
},
...
]
},
...
],
"features": [], // Mandatory
"resources": [], // Mandatory
"extensions": [] // Mandatory
}
This can be done very easily by following these steps:
`versionand the ``previousVersion``` properties`npm run build``grunt build`A TOC is automatically generated on the compilation of the general, How_To, features, resources and extensions md files into HTML. In order to get a functional TOC, you need to follow two very simple rules:
* every markdown lines beginning by a series "#" will be included in the TOC
* DO NOT put a link inside of your heading
If you do put a link, like this:
## [](https://awesomewebsite.com/somethingInteresting.html)Animations
… or like this:
## [Animations](https://awesomewebsite.com/somethingEvenMoreInteresting.html)
… it will be included in the TOC, but won't be clickable (meaning, user's browser won't jump to the selected content)
Also, the TOC is automatically nested. It means that if you write something like this:
# Main title
<insert content here>
## Secondary title 1
<insert content here>
### Third title
<insert content here>
## Secondary title 2
<insert content here>
## Secondary title 3
<insert content here>
You will get the following TOC:
1. Main title
1. Secondary title 1
1. Third title
2. Secondary title 2
3. Secondary title 3
NB: For safety, you need to delete yourself the version of classes in content\classes in order to rebuild the same version.
Please leave us an issue with a link to your .d.ts and your config file.