volgh/
						├── node_modules
						├── src
						|   ├── app/
						|   |   ├── auth
						|   |   ├── components
						|   |   ├── pages
						|   |   ├── shared
						|   |   ├── app-routing.module.ts
						|   |   ├── app.component.html
						|   |   ├── app.component.scss
						|   |   ├── app.component.spec.ts
						|   |   ├── app.component.ts
						|   |   └── app.module.ts
						|   ├── assets/
						|   |   ├── css
						|   |   ├── iconfonts
						|   |   ├── images
						|   |   ├── plugins
						|   |   ├── scss
						|   |   ├── switcher
						|   ├── environments/
						|   |   ├── environment.prod.ts
						|   |   └── environment.ts
						|   ├── favicon.ico
						|   ├── index.html
						|   ├── main.ts
						|   ├── polyfills.ts
						|   ├── styles.css
						├── .editorconfig
						├── .eslintrc.json
						├── .gitignore
						├── angular.json
						├── gulpfile.js
						├── package-lock.json
						├── package.json
						├── README.md
						├── tsconfig.app.json
						├── tsconfig.json
						├── tsconfig.spec.json
						└── 

• volgh - Angular Admin Panel Template / : Root template folder contain all html, ts, css, scss, images and other files.
• node_modules : Node.js creates this folder and puts all third party modules listed in package.json inside of it.
• angular.json : Configuration for Angular CLI. In this file you can set several defaults and also configure what files are included when your project is built. Check out the official documentation if you want to know more.
• .editorconfig : Simple configuration for your editor to make sure everyone that uses your project has the same basic configuration. Most editors support an .editorconfig file. See http://editorconfig.org for more information..
• package.json : npm configuration listing the third party packages your project uses. You can also add your own custom scripts here.
• README.md : Basic documentation for your project, pre-filled with CLI command information. Make sure to enhance it with project documentation so that anyone checking out the repo can build your app!
• tsconfig.json : TypeScript compiler configuration for your IDE to pick up and give you helpful tooling.
• assets/ : Folder contain all the Admin Template assets which has css, iconfonts scss, and images,switcher.
  • css/: Folder contain assets which has complete styles.
    • icons : icons.css has all template icons link are imported.
    • style : Main style sheet for template.
    • plugins : Folder contain all template plugins.
  • images/ : Template images.
  • iconfonts/ : Folder contain all the template iconfonts.
  • plugins/ : Folder contain all template plugins.
  • scss/ : Folder contain all pages scss files.
• app/ : Folder contain all the Admin Template components.
  • app/app..{html, scss, spec.ts, ts} : Defines the AppComponent along with an HTML template, CSS/SCSS stylesheet, and a unit test. It is the root component of what will become a tree of nested components as the application evolves.
  • app/app-routing.module.ts : Routing basically means navigating between pages. You have seen many sites with links that direct you to a new page. This can be achieved using routing.
  • app/app.module.ts : 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.
  • index.html : 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 you never need to add any script or link tags here manually.
  • main.ts : The main entry point for your app. Compiles the application with the JIT compiler and bootstraps the application's root module (AppModule) to run in the browser. You can also use the AOT compiler without changing any code by passing in --aot to ng build or ng serve.
  • polyfills.ts : 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 out the Browser Support guide for more information.
  • styles.scss : 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.
  • favicon.ico : Every site wants to look good on the bookmark bar. Get started with your very own Angular icon.
  • environments : 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 production or maybe different analytics tokens. You might even use some mock services. Either way, the CLI has you covered.