Answers.Body: <p>Generally when you are looking at the folder structure of a craft install your template files will be in <code>craft/templates/</code> (from doc root)</p>
  
  <blockquote>
    <p>craft/templates/ #</p>
    
    <p>This is where all of your site’s templates go.</p>
  </blockquote>
  
  <p>You can get more info about Craft's folder structure from the docs here: <a href="http://buildwithcraft.com/docs/folder-structure" rel="nofollow">http://buildwithcraft.com/docs/folder-structure</a></p>
  
  <blockquote>
    <p>Craft has a standard template path format that applies to each of
    these cases: a Unix-style file system path to the template file,
    relative from your craft/templates folder.</p>
    
    <p>If you have a template located at craft/templates/foo/bar.html, the
    following template paths would point to it:</p>
    
    <ul>
    <li>foo/bar</li>
    <li>foo/bar.html</li>
    </ul>
    
    <p><strong>Index Templates</strong></p>
    
    <p>If you name your template “index.html”, you don’t need to specify it
    in the template path.</p>
    
    <p>For example, if you have a template located at
    craft/templates/foo/bar/index.html, the following template paths would
    point to it:</p>
    
    <ul>
    <li>foo/bar</li>
    <li>foo/bar/index</li>
    <li>foo/bar/index.html</li>
    </ul>
  </blockquote>
  
  <p>If you need more information about templating you can also find that in the docs here: <a href="http://buildwithcraft.com/docs/templating-overview" rel="nofollow">http://buildwithcraft.com/docs/templating-overview</a></p>
  
  <p>As for the CSS files etc, it would really depend on the developer who set the site up, but the first place I would look is inside the <code>public</code> folder or whichever folder is considered the document root of the server.</p>
  
  <p>Hope that helps get you started!</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-19T14:59:55.680Z
Answers.Text: Thanks, this is helpfull! Is there a way to sync these with the other developer's files, or would we have to each work locally and then push through something like git?
Answers.UserDisplayName: user3675
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-19T15:05:06.527Z
Answers.Text: Yeah theres a bunch of different ways really, going down the git route might be a good option as then you have version control and all the obvious benefits that come with that. You could even use something like Transmit Disk mounting (osx) or Webdrive (windows) so you can both run off a staging server or something, even a shared dropbox folder with a local server would work. I guess it's down to preference but I would assume GIT is probably the method preferred by most...
Answers.UserDisplayName: Alec Ritson
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-19T14:16:31.680Z
Answers.LastActivityDate: 2015-05-19T14:16:31.680Z
Answers.UserDisplayName: Alec Ritson
Body: <p>I am trying to get started with Craft, and was added to an existing project as an admin. I have little experience working with CMS, and am having trouble figuring out how to access the actual html/css files, rather than just the dashboard?</p>
  
  <p>I've downloaded the Craft files locally, and have been looking through documentation, but any additional pointers to resources would be appreciated. Thanks!</p>
  
Tags: <templating><assets>
Title: Accessing Files
ThreadText: # Accessing Files
  
  (Asked by: username_0 on 2015-05-19)
  
  I am trying to get started with Craft, and was added to an existing project as an admin. I have little experience working with CMS, and am having trouble figuring out how to access the actual html/css files, rather than just the dashboard?
  
  I've downloaded the Craft files locally, and have been looking through documentation, but any additional pointers to resources would be appreciated. Thanks!
  
  **Tags:** templating, assets
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-05-19. Score: 2 | Accepted answer
  
  Generally when you are looking at the folder structure of a craft install your template files will be in `craft/templates/` (from doc root)
  
  > craft/templates/ #
  >
  > This is where all of your site’s templates go.
  
  You can get more info about Craft's folder structure from the docs here: <http://buildwithcraft.com/docs/folder-structure>
  
  > Craft has a standard template path format that applies to each of
  > these cases: a Unix-style file system path to the template file,
  > relative from your craft/templates folder.
  >
  > If you have a template located at craft/templates/foo/bar.html, the
  > following template paths would point to it:
  >
  > * foo/bar
  > * foo/bar.html
  >
  > **Index Templates**
  >
  > If you name your template “index.html”, you don’t need to specify it
  > in the template path.
  >
  > For example, if you have a template located at
  > craft/templates/foo/bar/index.html, the following template paths would
  > point to it:
  >
  > * foo/bar
  > * foo/bar/index
  > * foo/bar/index.html
  
  If you need more information about templating you can also find that in the docs here: <http://buildwithcraft.com/docs/templating-overview>
  
  As for the CSS files etc, it would really depend on the developer who set the site up, but the first place I would look is inside the `public` folder or whichever folder is considered the document root of the server.
  
  Hope that helps get you started!
  
  > **Comments:**
  > **username_0**: Thanks, this is helpfull! Is there a way to sync these with the other developer's files, or would we have to each work locally and then push through something like git?  
  > **username_1**: Yeah theres a bunch of different ways really, going down the git route might be a good option as then you have version control and all the obvious benefits that come with that. You could even use something like Transmit Disk mounting (osx) or Webdrive (windows) so you can both run off a staging server or something, even a shared dropbox folder with a local server would work. I guess it's down to preference but I would assume GIT is probably the method preferred by most...  
  
  ---
  
  