Answers.Body: <p>The default template path can be changed by setting the <a href="http://buildwithcraft.com/docs/php-constants#craft-templates-path"><code>CRAFT_TEMPLATES_PATH</code></a> PHP constant in your index.php file:</p>
  
  <pre><code>define('CRAFT_TEMPLATES_PATH', "path/to/templates");
  </code></pre>
  
  <p>I would recommend, however, that you start with the default path locations, until you are more comfortable with the app. There is a logical system in place which works really well once you get used to it. And you'll notice that the craft app folder (and all the plug-ins) are organized the same way, so once you start building your own sites and plugins it will all feel very integrated. Keep in mind the folder names also match the names of the controller classes, service classes, method names, etc. throughout the system which makes it easier to find your way around.</p>
  
  <p>Another thing to keep in mind is that placing your Craft templates in your web root would make the raw template files publicly accessible from a web browser. So if you decide to go this route, be sure to place a .htaccess file in your templates folder with this:</p>
  
  <pre><code>Deny from all
  </code></pre>
  
  <p>That will tell Apache to protect the files from direct HTTP traffic, even though they live within the web root.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-10-23T01:28:42.707Z
Answers.Text: @Brad I was looking for that link. Thanks.
Answers.UserDisplayName: Douglas McDonald
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-10-23T01:29:34.737Z
Answers.Text: No worries... :)
Answers.UserDisplayName: Brad Bell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-10-23T10:46:10.757Z
Answers.Text: Thanks, Brandon. We would be moving them out of the webroot where we keep our theme SASS files and uncompressed JS, so all the theme is in one place, but I will take your advice and have a play around first.
Answers.UserDisplayName: Russ Back
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-10-23T00:15:15.960Z
Answers.LastActivityDate: 2014-10-23T02:35:55.917Z
Answers.LastEditDate: 2014-10-23T02:35:55.917Z
Answers.UserDisplayName: Douglas McDonald
Body: <p>First Craft install so please excuse me if this is a newbie Q.</p>
  
  <p>Templates are in /craft/templates. Is it possible to move those to a different location? Our other sites (EE) have templates stored with the UI theme source files so everything to do with the the site look and feel is in one place.</p>
  
  <p>Thanks.</p>
  
Tags: <templating><config>
Title: Custom template location
ThreadText: # Custom template location
  
  (Asked by: username_0 on 2014-10-22)
  
  First Craft install so please excuse me if this is a newbie Q.
  
  Templates are in /craft/templates. Is it possible to move those to a different location? Our other sites (EE) have templates stored with the UI theme source files so everything to do with the the site look and feel is in one place.
  
  Thanks.
  
  **Tags:** templating, config
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2014-10-23. Score: 10 | Accepted answer
  
  The default template path can be changed by setting the [`CRAFT_TEMPLATES_PATH`](http://buildwithcraft.com/docs/php-constants#craft-templates-path) PHP constant in your index.php file:
  
  ```
  define('CRAFT_TEMPLATES_PATH', "path/to/templates");
  
  ```
  
  I would recommend, however, that you start with the default path locations, until you are more comfortable with the app. There is a logical system in place which works really well once you get used to it. And you'll notice that the craft app folder (and all the plug-ins) are organized the same way, so once you start building your own sites and plugins it will all feel very integrated. Keep in mind the folder names also match the names of the controller classes, service classes, method names, etc. throughout the system which makes it easier to find your way around.
  
  Another thing to keep in mind is that placing your Craft templates in your web root would make the raw template files publicly accessible from a web browser. So if you decide to go this route, be sure to place a .htaccess file in your templates folder with this:
  
  ```
  Deny from all
  
  ```
  
  That will tell Apache to protect the files from direct HTTP traffic, even though they live within the web root.
  
  > **Comments:**
  > **username_1**: @username_2 I was looking for that link. Thanks.  
  > **username_2**: No worries... :)  
  > **username_0**: Thanks, Brandon. We would be moving them out of the webroot where we keep our theme SASS files and uncompressed JS, so all the theme is in one place, but I will take your advice and have a play around first.  
  
  ---
  
  