Defines the AppComponent along with an HTML template, CSS stylesheet, and a unit test.It is the root component of what will become a tree of nested componentsas the application evolves.

Defines AppModule, the root module that tells Angular how to assemble the application.Right now it declares only the AppComponent.Soon there will be more components to declare.

A folder where you can put images and anything else to be copied wholesalewhen you build your application.

This folder contains one file for each of your destination environments,each exporting simple configuration variables to use in your application.The files are replaced on-the-fly when you build your app.You might use a different API endpoint for development than you do for productionor maybe different analytics tokens.You might even use some mock services.Either way, the CLI has you covered.

Every site wants to look good on the bookmark bar.Get started with your very own Angular icon.

The main HTML page that is served when someone visits your site.Most of the time you'll never need to edit it.The CLI automatically adds all js and css files when building your app so younever need to add any <script> or <link> tags here manually.

The main entry point for your app.Compiles the application with the JIT compilerand bootstraps the application's root module (AppModule) to run in the browser.You can also use the AOT compilerwithout changing any code by passing in --aot to ng build or ng serve.

Different browsers have different levels of support of the web standards.Polyfills help normalize those differences.You should be pretty safe with core-js and zone.js, but be sure to check outthe Browser Support guide for more information.

Your global styles go here.Most of the time you'll want to have local styles in your components for easier maintenance,but styles that affect all of your app need to be in a central place.

This is the main entry point for your unit tests.It has some custom configuration that might be unfamiliar, but it's not something you'llneed to edit.

TypeScript compiler configuration for the Angular app (tsconfig.app.json)and for the unit tests (tsconfig.spec.json).

Inside e2e/ live the End-to-End tests.They shouldn't be inside src/ because e2e tests are really a separate app thatjust so happens to test your main app.That's also why they have their own tsconfig.e2e.json.

Node.js creates this folder and puts all third party modules listed inpackage.json inside of it.

Configuration for Angular CLI.In this file you can set several defaults and also configure what files are includedwhen your project is build.Check out the official documentation if you want to know more.

Simple configuration for your editor to make sure everyone that uses your projecthas the same basic configuration.Most editors support an .editorconfig file.See http://editorconfig.org for more information.

Git configuration to make sure autogenerated files are not commited to source control.

Unit test configuration for the Karma test runner,used when running ng test.

npm configuration listing the third party packages your project uses.You can also add your own custom scripts here.

End-to-end test configuration for Protractor,used when running ng e2e.

Basic documentation for your project, pre-filled with CLI command information.Make sure to enhance it with project documentation so that anyonechecking out the repo can build your app!

TypeScript compiler configuration for your IDE to pick up and give you helpful tooling.

Linting configuration for TSLint together withCodelyzer, used when running ng lint.Linting helps keep your code style consistent.