Answers.Body: <p>Before I create any fields I try to plan them on paper. This helps me to create my first logical groups. It doesn't prevent changes later on, but at least reduces them a little.</p>
  
  <p>Also all my global sets have prefix: <code>global__settings</code>, <code>global__misc</code>...</p>
  
  <p>Now if I have to create a new set and move some fields, I can do a "Search &amp; Replace" on all templates, and thanks to the prefix I don't have to worry about replacing the wrong variables.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-03T13:02:39.253Z
Answers.Text: If only you could have tabs with a single set.
Answers.UserDisplayName: Steve Adams
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-03T13:54:06.263Z
Answers.Text: It's on the list: https://plus.google.com/113470279619182545258/posts/GKy8nvysiDR
Answers.UserDisplayName: Victor
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-01T16:25:14.167Z
Answers.LastActivityDate: 2014-07-01T16:25:14.167Z
Answers.UserDisplayName: Victor
Body: <p>I've found it a little challenging to use global sets effectively, so I'm wondering how others are doing it.</p>
  
  <p>The fact that a global <em>has</em> to be in a set has been a little tricky to deal with at the beginning a of a build, as knowing what those sets might be is hard when there aren't any globals yet.</p>
  
  <p>This leaves me using sets like "Misc", "Content", and "Settings", which doesn't end up being all that helpful.</p>
  
  <p>The arbitrary nature of these assignments also present a problem when using those globals, because you have to call them with their set name <code>{{ settings.analyticsId }}</code>.</p>
  
  <p>Just thinking out loud, and wondering how others are dealing!</p>
  
Tags: <control-panel>
Title: How are people organizing their global sets?
ThreadText: # How are people organizing their global sets?
  
  (Asked by: username_0 on 2014-07-01)
  
  I've found it a little challenging to use global sets effectively, so I'm wondering how others are doing it.
  
  The fact that a global *has* to be in a set has been a little tricky to deal with at the beginning a of a build, as knowing what those sets might be is hard when there aren't any globals yet.
  
  This leaves me using sets like "Misc", "Content", and "Settings", which doesn't end up being all that helpful.
  
  The arbitrary nature of these assignments also present a problem when using those globals, because you have to call them with their set name `{{ settings.analyticsId }}`.
  
  Just thinking out loud, and wondering how others are dealing!
  
  **Tags:** control-panel
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2014-07-01. Score: 1
  
  Before I create any fields I try to plan them on paper. This helps me to create my first logical groups. It doesn't prevent changes later on, but at least reduces them a little.
  
  Also all my global sets have prefix: `global__settings`, `global__misc`...
  
  Now if I have to create a new set and move some fields, I can do a "Search & Replace" on all templates, and thanks to the prefix I don't have to worry about replacing the wrong variables.
  
  > **Comments:**
  > **username_2**: If only you could have tabs with a single set.  
  > **username_1**: It's on the list: https://plus.google.com/113470279619182545258/posts/GKy8nvysiDR  
  
  ---
  
  