angular-docs-cn/aio/tools/transforms
Stefanie Fluin cf034f759a feat(aio): api page styles
Changed description from h3 to h2 to match the other header
Created api page classes for consistent styling
Add styles for info-bar section
Wrapped pre tags for code not to go off of screen
2017-04-21 16:24:37 +01:00
..
angular.io-package build(aio): add the `id` to the DocumentContents at doc-gen time (#16139) 2017-04-20 22:14:51 -05:00
authors-package build(aio): compute which examples to include when watching guide docs (#16213) 2017-04-20 22:16:21 -05:00
content-package build(aio): move the `transforms` folder into the `tools` folder 2017-04-16 22:05:23 +01:00
examples-package build(aio): move the `transforms` folder into the `tools` folder 2017-04-16 22:05:23 +01:00
helpers build(aio): move the `transforms` folder into the `tools` folder 2017-04-16 22:05:23 +01:00
links-package build(aio): move the `transforms` folder into the `tools` folder 2017-04-16 22:05:23 +01:00
remark-package feat(aio): add GH-style anchor links to headings (#16161) 2017-04-19 22:34:46 -05:00
target-package build(aio): move the `transforms` folder into the `tools` folder 2017-04-16 22:05:23 +01:00
templates feat(aio): api page styles 2017-04-21 16:24:37 +01:00
.eslintignore build(aio): move the `transforms` folder into the `tools` folder 2017-04-16 22:05:23 +01:00
.eslintrc.js build(aio): move the `transforms` folder into the `tools` folder 2017-04-16 22:05:23 +01:00
README.md build(aio): move the `transforms` folder into the `tools` folder 2017-04-16 22:05:23 +01:00

README.md

Documentation Generation

The dgeni tool is used to generate the documentation from the source files held in this repository. The documentation generation is configured by a dgeni package defined in tools/transforms/angular.io-package/index.js. This package, in turn requires a number of other packages, some are defined locally in the tools/transforms folder, such as tools/transforms/cheatsheet-package and tools/transforms/content-package, etc. And some are brought in from the dgeni-packages node modules, such as jsdoc and nunjucks.

Generating the docs

To generate the documentation simply run yarn docs from the command line.

Testing the dgeni packages

The local packages have unit tests that you can execute by running yarn docs-test from the command line.

What does it generate?

The output from dgeni is written to files in the src/content folder.

Notably this includes a JSON file containing the partial HTML for each "page" of the documentation, such as API pages and guides. It also includes JSON files that contain metadata about the documentation such as navigation data and keywords for building a search index.

Viewing the docs

You can view the pages by running yarn start and navigating to https://localhost:4200.