This project was generated with Angular CLI version 17.3.0.
Take a careful look at style variables and global utility classes in styles.css. Our goal is to build a good application while keeping our code clear, so:
If you have to, make a new utility class for team reusability. Feel free to refactor anything as long as you're making the code more legible.
A good front-end application might look as if it were built by one single person. That means everyone keeps the same pattern while developing components.
Sometimes it can't be helped, but for most cases, it's totally reasonable. To maintain standardization while setting CSS sizes, give preference to the use of multiple values or divisors of 4 (0.1, 0.2, 0.4, 0.8,..., 4, 8, 12,...).
Design is definitely a concern, but not as high and costly as functionality. We must focus on delivering functional components, adjusting the visual part of the application is a quicker and easier job. Make sure it's simple.
Run ng serve for a dev server. Navigate to http://localhost:4200/. The application will automatically reload if you change any of the source files.
Run ng generate component components\component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.
Run ng build to build the project. The build artifacts will be stored in the dist/ directory.
Run ng test to execute the unit tests via Karma.
Run ng e2e to execute the end-to-end tests via a platform of your choice. To use this command, you need to first add a package that implements end-to-end testing capabilities.
To get more help on the Angular CLI use ng help or go check out the Angular CLI Overview and Command Reference page.