{"_id":"55fd9c6e56d6990d00a6caa1","project":"54d64e6b276f8e0d00feab95","version":{"_id":"55fd9c6d56d6990d00a6ca9d","project":"54d64e6b276f8e0d00feab95","__v":1,"createdAt":"2015-09-19T17:33:33.368Z","releaseDate":"2015-09-19T17:33:33.368Z","categories":["55fd9c6e56d6990d00a6ca9e","55fd9c6e56d6990d00a6ca9f","55fd9c6e56d6990d00a6caa0"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.4.0","version":"1.4.0"},"__v":1,"category":{"_id":"55fd9c6e56d6990d00a6caa0","version":"55fd9c6d56d6990d00a6ca9d","__v":1,"project":"54d64e6b276f8e0d00feab95","pages":["55fd9c6e56d6990d00a6caa1","55fd9c6e56d6990d00a6caa2","55fd9c6e56d6990d00a6caa3","55fd9c6e56d6990d00a6caa4","55fd9c6e56d6990d00a6caa5","55fd9c6e56d6990d00a6caa6","55fd9c6e56d6990d00a6caa7","55fd9c6e56d6990d00a6caa8"],"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-02-07T18:14:40.771Z","from_sync":false,"order":2,"slug":"your-application","title":"Your Application"},"user":"54d64e31276f8e0d00feab94","updates":[],"next":{"pages":[],"description":""},"createdAt":"2015-02-07T17:49:55.222Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"settings":"","results":{"codes":[]},"auth":"required","params":[],"url":""},"isReference":false,"order":0,"body":"When you create an application with angular-kick, the basic folder structure looks like this:\n\n```\n/app\n  /assets\n  /config\n    /routes\n  /components\n  /directives\n  /filters\n  /partials\n  /models\n  /services\n  /states\n/test\n  /mock\n  /unit\n    /controllers\n    /components\n    /directives\n    /filters\n    /services\n```\n\n# /assets\nAll your images, fonts, stylesheets and custom js-plugins that didn't come from bower should be placed in corresponding directory under `/assets`. This way you will be sure, that webpack will catch all your assets, minify, optimize and serve them for you it their best state.\n\n# /config\nThis is the place for all your application configuration, such as interceptors, decorators, constants, values and other things that run on AngularJS .config application state.\n\nAlso there is a `/routes` subdirectory, where you will find all the routing of your application.\n\n# /components\nComponents are angular directives that have a template and a controller. This separation makes it easier to determine where files are located. By default, components are restricted to be only elements.\n\n# /directives\nIn this directory you should put directives that are pure functions without templates. By default, components are restricted to be only attributes.\n\n#/ /filters, /services, /models\nThis is the place for all your angular files.\n\n# /states\nStates in this folder are represented one-to-one as in your route files. This convention lets you easily determine where to look for some view based on url of the state.\n\n# /partials\nHere you store the partials for your application. Partials are common html pieces with no logic.\n\n# /test\nTesting application is easy with angular-kick. Every time you generate a directive, filter, service, model, or state, a corresponding test is created in this folder.\n\n# Utility folders\n\n## .test\nThis is the temporary directory created each time you run your tests once with `$ kick test`. This is made because the tests can run with different environment variables, and you don't want it to interfere with your files served from .tmp. Notice, that when you run `$ kick server:tdd` command, the test suit runs from .tmp directory along with browserSync.\n\n## node_modules\nDirectories for third party scripts and modules needed by karma and webpack\n\n## dist\nThis is the place to find you compiled and production-ready application after you run `$ kick bundle`","excerpt":"","slug":"folder-structure","type":"basic","title":"Folder Structure"}
When you create an application with angular-kick, the basic folder structure looks like this: ``` /app /assets /config /routes /components /directives /filters /partials /models /services /states /test /mock /unit /controllers /components /directives /filters /services ``` # /assets All your images, fonts, stylesheets and custom js-plugins that didn't come from bower should be placed in corresponding directory under `/assets`. This way you will be sure, that webpack will catch all your assets, minify, optimize and serve them for you it their best state. # /config This is the place for all your application configuration, such as interceptors, decorators, constants, values and other things that run on AngularJS .config application state. Also there is a `/routes` subdirectory, where you will find all the routing of your application. # /components Components are angular directives that have a template and a controller. This separation makes it easier to determine where files are located. By default, components are restricted to be only elements. # /directives In this directory you should put directives that are pure functions without templates. By default, components are restricted to be only attributes. #/ /filters, /services, /models This is the place for all your angular files. # /states States in this folder are represented one-to-one as in your route files. This convention lets you easily determine where to look for some view based on url of the state. # /partials Here you store the partials for your application. Partials are common html pieces with no logic. # /test Testing application is easy with angular-kick. Every time you generate a directive, filter, service, model, or state, a corresponding test is created in this folder. # Utility folders ## .test This is the temporary directory created each time you run your tests once with `$ kick test`. This is made because the tests can run with different environment variables, and you don't want it to interfere with your files served from .tmp. Notice, that when you run `$ kick server:tdd` command, the test suit runs from .tmp directory along with browserSync. ## node_modules Directories for third party scripts and modules needed by karma and webpack ## dist This is the place to find you compiled and production-ready application after you run `$ kick bundle`