Answers.Body: <p>Yes, the <a href="http://buildwithcraft.com/docs/templating/categorymodel" rel="nofollow">CategoryModel</a> for your category will be available to the template as the variable <code>category</code>.</p>
  
  <pre><code>&lt;h2 class="categoryTitle"&gt;{{ category.title }}&lt;/h2&gt;
  {{ dump(category) }}
  </code></pre>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-27T22:36:29.623Z
Answers.Text: Too fast.... :)
Answers.UserDisplayName: Douglas McDonald
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-27T22:39:57.420Z
Answers.Text: Its a tie. I think we'll need to see the server logs :)
Answers.UserDisplayName: Mats Mikkel Rummelhoff
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-27T22:35:08.300Z
Answers.LastActivityDate: 2015-04-27T22:35:08.300Z
Answers.UserDisplayName: Mats Mikkel Rummelhoff
Body: <p>I have setup a category group to use Url's. When navigating to that url does the template have direct access to that category's inputs like you would with and entry? Or do you have to use the segment and get the data that way?</p>
  
Tags: <categories><url>
Title: When accessing a Category url is there direct access to the Category's fields?
ThreadText: # When accessing a Category url is there direct access to the Category's fields?
  
  (Asked by: username_0 on 2015-04-27)
  
  I have setup a category group to use Url's. When navigating to that url does the template have direct access to that category's inputs like you would with and entry? Or do you have to use the segment and get the data that way?
  
  **Tags:** categories, url
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-04-27. Score: 3 | Accepted answer
  
  Yes, the [CategoryModel](http://buildwithcraft.com/docs/templating/categorymodel) for your category will be available to the template as the variable `category`.
  
  ```
  <h2 class="categoryTitle">{{ category.title }}</h2>
  {{ dump(category) }}
  
  ```
  
  > **Comments:**
  > **username_2**: Too fast.... :)  
  > **username_1**: Its a tie. I think we'll need to see the server logs :)  
  
  ---
  
  