message: docs: move asset management section
  PR Close
diff: @@ -119,6 +119,17 @@ npm publish
  If you've never published a package in npm before, you must create a user account. Read more in [Publishing npm Packages](https://docs.npmjs.com/getting-started/publishing-npm-packages).
  +{@a lib-assets}
  +
  +## Managing assets in a library
  +
  +Starting with version 9.x of the [ng-packagr](https://github.com/ng-packagr/ng-packagr/blob/master/README.md) tool, you can configure the tool to automatically copy assets into your library package as part of the build process.
  +You can use this feature when your library needs to publish optional theming files, Sass mixins, or documentation (like a changelog).
  +
  +* Learn how to [copy assets into your library as part of the build](https://github.com/ng-packagr/ng-packagr/blob/master/docs/copy-assets.md).
  +
  +* Learn more about how to use the tool to [embed assets in CSS](https://github.com/ng-packagr/ng-packagr/blob/master/docs/embed-assets-css.md).
  +
  ## Linked libraries
  @@ -215,14 +226,3 @@ For this reason, an app that depends on a library should only use TypeScript pat
  TypeScript path mappings should *not* point to the library source `.ts` files.
  </div>
  -
  -{@a lib-assets}
  -
  -### Managing library assets with ng-packagr
  -
  -Starting with version 9.x of the [ng-packagr](https://github.com/ng-packagr/ng-packagr/blob/master/README.md) tool, you can configure the tool to automatically copy assets into your library package as part of the build process.
  -You can use this feature when your library needs to publish optional theming files, Sass mixins, or documentation (like a changelog).
  -
  -* Learn how to [copy assets into your library as part of the build](https://github.com/ng-packagr/ng-packagr/blob/master/docs/copy-assets.md).
  -
  -* Learn more about how to use the tool to [embed assets in CSS](https://github.com/ng-packagr/ng-packagr/blob/master/docs/embed-assets-css.md).
  