diff --git a/aio/content/guide/component-styles.md b/aio/content/guide/component-styles.md index 854ec1bc9c..271085a7e2 100644 --- a/aio/content/guide/component-styles.md +++ b/aio/content/guide/component-styles.md @@ -220,8 +220,7 @@ You can also write `` tags into the component's HTML template.
-When building with the CLI, be sure to include the linked style file among the assets to be copied to the server as described in the [CLI wiki](https://github.com/angular/angular-cli/wiki/stories-asset-configuration). - +When building with the CLI, be sure to include the linked style file among the assets to be copied to the server as described in the [Assets configuration guide](guide/workspace-config#assets-configuration). Once included, the CLI will include the stylesheet, whether the link tag's href URL is relative to the application root or the component file. @@ -245,7 +244,6 @@ When building with the CLI, you must configure the `angular.json` to include _al Register **global** style files in the `styles` section which, by default, is pre-configured with the global `styles.css` file. See the [Styles configuration guide](guide/workspace-config#styles-and-scripts-configuration) to learn more. - ### Non-CSS style files @@ -265,10 +263,7 @@ you can write style files in [sass](https://sass-lang.com/), [less](http://lessc The CLI build process runs the pertinent CSS preprocessor. When generating a component file with `ng generate component`, the CLI emits an empty CSS styles file (`.css`) by default. -You can configure the CLI to default to your preferred CSS preprocessor -as explained in the [CLI wiki](https://github.com/angular/angular-cli/wiki/stories-css-preprocessors -"CSS Preprocessor integration"). - +You can configure the CLI to default to your preferred CSS preprocessor as explained in the [Workspace configuration guide](guide/workspace-config#generation-schematics).