Merge pull request #158 from james-baber/document-rig-freezing

added freeze operator to documentation
#154

Author: james-baber

docs/Gemfile

@@ -31,3 +31,6 @@ gem "wdm", "~> 0.1.0", :install_if => Gem.win_platform?
 # kramdown v1, comment out this line.
 gem "kramdown-parser-gfm"
 
+# This plugin is for site seo
+gem "jekyll-seo-tag"
+

docs/_config.yml

@@ -23,15 +23,27 @@ url: "https://epicgames.github.io/BlenderTools"
 
 github:  EpicGames/BlenderTools
 
+social:
+  name: Unreal Engine
+  links:
+    - https://twitter.com/UnrealEngine
+    - https://github.com/epicgames
+    - http://unrealengine.com
+
+webmaster_verifications:
+  google: G-NVX6X5L76V
+
 # Build settings
 markdown: kramdown
 theme: minima
 
-
 header_pages:
   - index.md
   - about.md
 
+plugins:
+ - jekyll-seo-tag
+
 
 # Exclude from processing.
 # The following items will not be processed, by default. Create a custom list

docs/_includes/head.html

@@ -21,4 +21,14 @@
 
   {%- include custom-head.html -%}
 
+  <!-- Global site tag (gtag.js) - Google Analytics -->
+  <script async src="https://www.googletagmanager.com/gtag/js?id=G-NVX6X5L76V"></script>
+  <script>
+    window.dataLayer = window.dataLayer || [];
+    function gtag(){dataLayer.push(arguments);}
+    gtag('js', new Date());
+
+    gtag('config', 'G-NVX6X5L76V');
+  </script>
+
 </head>

docs/ue2rigify/user-interface/3d-view-panel.md

@@ -59,4 +59,9 @@ This operator switches the current mode to ‘Source’ mode, and restores the v
 
 ### Bake
 
-This operator bakes the ‘Control’ rig actions to the ‘Source’ rig actions.
+This operator bakes the ‘Control’ rig actions to the ‘Source’ rig actions.
+
+### Freeze
+This operator freezes the rig so the user doesn't lose their data by changing modes. If the .blend file is saved in control mode, UE to Rigify will automatically freeze the rig so the rig stays unmodified from when it was last saved.
+Since mode changes are actually a complete deletion and creation of a new rigify rig, only the info provided by the "template" will be available after a mode change. So this is what freezing is for; it is a way to prevent doing a mode change. Mode changes can potentially be destructive. If you are adding information that is not through the rigify properties on the metarig, or through the node trees, then that data will be deleted on a mode change.
+UE to Rigify is designed to quickly create and delete all the constraint hierarchy, rigify rigs, and their associated data while the user is flipping through modes and editing the custom template. However, once a final custom template is made, it is highly recommended that the user freeze the rig when animating in control mode.