mirror of
https://github.com/documentationjs/documentation.git
synced 2026-01-25 14:26:29 +00:00
* feat(config): add file property for notes Fixes #609 * feat(config): resolve files against the config file location
51 lines
1.5 KiB
Markdown
51 lines
1.5 KiB
Markdown
# Configuring documentation.js
|
|
|
|
Configuration is a completely optional step for generating documentation
|
|
with documentation.js. The tool is designed to accept any JSDoc-annotated
|
|
source code and automatically generate output.
|
|
|
|
Configuration - a `documentation.yml` file - will accomplish two goals:
|
|
|
|
* Organization: you can put top level documentation in order of importance
|
|
* Narration: you can add narrative sections - plain English writing - in
|
|
between autogenerated API documentation.
|
|
|
|
Here's how `documentation.yml` works:
|
|
|
|
```yml
|
|
toc:
|
|
- Map
|
|
- name: Geography
|
|
description: |
|
|
These are Mapbox GL JS's ways of representing locations
|
|
and areas on the sphere.
|
|
- LngLat
|
|
- LngLatBounds
|
|
```
|
|
|
|
This puts the top level API documentation for the `Map`, `LngLat`, and `LngLatBounds`
|
|
items in the given order, and inserts a narrative item titled `Geography`
|
|
after the section on maps. The `description` property of that narrative item
|
|
is interpreted as Markdown.
|
|
If you would like reuse your existing markdown files or just keep the content separate from the configuration you can use the `file` property. It is a filename it will be resolved against the directory that the `documentation.yml` file resides in.
|
|
|
|
So with a `documentation.yml` file like this
|
|
|
|
```yml
|
|
toc:
|
|
- Map
|
|
- name: Geography
|
|
file: geo.md
|
|
- LngLat
|
|
- LngLatBounds
|
|
```
|
|
|
|
and a file `geo.md`
|
|
|
|
```markdown
|
|
These are Mapbox GL JS's ways of representing locations
|
|
and areas on the sphere.
|
|
```
|
|
|
|
it would produce the same output as the previous example.
|