angular-cn/aio/tools/transforms
Pete Bacon Darwin 18b6d580c5 fix(docs-infra): update overload rendering (#24976)
Based on the review here:
https://github.com/angular/angular/pull/24976#issuecomment-415535125

PR Close #24976
2018-11-01 14:17:11 -07:00
..
angular-api-package feat(docs-infra): rename tagdef: `@experimental` to `@publicApi` (#26595) 2018-10-19 14:35:52 -07:00
angular-base-package build(docs-infra): mark code blocks to disable auto-linking (#26675) 2018-10-26 18:09:20 -04:00
angular-content-package feat(docs-infra): add "suggest edits" feature to all docs (#24378) 2018-08-31 09:42:10 -07:00
angular.io-package feat(docs-infra): generate Angular CLI command reference (#25363) 2018-09-26 11:24:02 -07:00
authors-package
cli-docs-package build(docs-infra): display github links in CLI API docs (#26515) 2018-10-19 11:12:54 -07:00
content-package build(docs-infra): display github links in CLI API docs (#26515) 2018-10-19 11:12:54 -07:00
examples-package build(docs-infra): allow `""` as empty region in `{@example}` tags (#26514) 2018-10-18 09:54:17 -07:00
helpers
links-package
post-process-package
remark-package build(aio): map H3 headings into H4 headings for certain templates (#24000) 2018-06-13 16:47:40 -07:00
target-package
templates fix(docs-infra): update overload rendering (#24976) 2018-11-01 14:17:11 -07:00
.eslintignore
.eslintrc.js
README.md
config.js
test.js

README.md

Overview

All the content that is rendered by the AIO application, and some of its configuration files, are generated from source files by Dgeni. Dgeni is a general purpose documentation generation tool.

Markdown files in /aio/content, code comments in the core Angular source files and example files are processed and transformed into files that are consumed by the AIO application.

Dgeni is configured by "packages", which contain services and processors. Some of these packages are installed as node_modules from the dgeni-packages and some are specific to the AIO project.

The project specific packages are stored in this folder (aio/tools/transforms).

If you are an author and want to know how to generate the documentation, the steps are outlined in the top level README.md.

Root packages

To run Dgeni, you must specify a root package, which acts as the entry point to the documentation generation. This root 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.

  • The primary root package is defined in tools/transforms/angular.io-package/index.js. This package is used to run a full generation of all the documentation.
  • There are also root packages defined in tools/transforms/authors-package/*-package.js. These packages are used by the documentation authors when writing docs, since it allows them to run partial doc generation, which is not complete but is faster for quickly seeing changes to the document that you are working on.

Other packages

  • angular-base-package
  • angular-api-package
  • angular-content-package
  • content-package
  • examples-package
  • links-package
  • post-process-package
  • remark-package
  • target-package

Templates

All the templates for the angular.io dgeni transformations are stoted in the tools/transforms/templates folder. See the README.