With Angular, we can give style to components in a way that will not affect the rest of the application. It's a good practice to encapsulate the component-related style this way.
We can also state general style rules to be used across the application. This is good for creating the same look-and-feel for all our components. For example, we can decide what color palette will be used as the theme of our app. Then, if we'd like to change the colors or offer different themes, we can change it in just one place, instead of in each component.
Angular gives us different style encapsulation methods, but we'll stick to the default.
You can change the style as you wish - the size of elements, the colors - however you'd like!
Note: You can use SCSS files in the project, which is a nicer way to write style. It has great features that help the developer. SCSS files are compiled to CSS when the project is built.
The Angular CLI has generated a general stylesheet for us at style.css in πsrc folder. Paste the following code into this file:
How does the project know to look at this file? In the Angular CLI configuration file angular.json under apps[0].styles, you can state the files for the build tool to take and add to the project. You can open the browser's dev tools and see the style inside the element:
Open the file list-manager.component.css and paste the following style inside:
How does this stylesheet get attached to the todo-list-manager component? Look at the file list-manager.component.ts. One of the properties in the object passed to the @Component decorator is styleUrls. It's a list of stylesheets to be used by Angular, which encapsulates the style within the component.