Updated PyroCMS version to 2.2

This got reverted in the merge.

I also switched any references to use `{{ variables:get_var
name='pyrocms_version' }}` instead. This allows the one place of
changing it in the config.

Author: chadwithuhc

assets/embeds/header.html

@@ -48,7 +48,7 @@ <h3><a href=""><img src="assets/img/logo.png" /></a></h3>
 
          <div id="box">
 
-          <div class="breadcrumbs"><strong>PyroCMS 2.1</strong> | {{ breadcrumbs:crumbs }}</div>
+          <div class="breadcrumbs"><strong>PyroCMS {{ variables:get_var name="pyrocms_version" }}</strong> | {{ breadcrumbs:crumbs }}</div>
 
 <div id="menu">
 

config.php

@@ -18,4 +18,4 @@
  */
 
 // The current PyroCMS version
-$config['pyrocms_version']		= '2.1.0';
+$config['pyrocms_version']		= '2.2';

content/developers/contributing/coding-standards.md

@@ -250,7 +250,7 @@ String concatenation should not contain spaces around the joined parts.
 ## Documentation
 Having a good API documentation is a vital requirement for any successful project. When building your module, please take the time to document its code or even write help articles on it (but that is a different story). 
 
-Most of PyroCMS' core components [are documented](http://docs.pyrocms.com/2.1/api/) and add-ons are actually expected to keep up by at least having each of their files declare the respective package they belong to. Anything can be documented except for views. Classes and functions should be documented using the standard PHPDoc format. 
+Most of PyroCMS' core components <a href="/{{ variables:get_var name='pyrocms_version' }}/api/">are documented</a> and add-ons are actually expected to keep up by at least having each of their files declare the respective package they belong to. Anything can be documented except for views. Classes and functions should be documented using the standard PHPDoc format. 
 
 The actual API Documentation is being generated by [DocBlox](http://www.docblox-project.org/). This gives the ability to reflect the HMVC approach used in building PyroCMS into the actual API documentation. This is how the API Documentation packages are structured in PyroCMS:
 

content/developers/contributing/using-git.md

@@ -12,7 +12,7 @@ Go to out [GitHub Repository](http://github.com/pyrocms/pyrocms/) and click "For
 
 You will be set up with a new repository which is a copy of ours. That means you can work on your copy of our repository without us needing to give you access to anything. You can use the following command to get a copy on your computer in your current directory. Best to put this into htdocs (or somewhere you have a server/domains's document root set).
 
-	git clone [email protected]:yourusername/pyrocms.git -b 2.1/develop
+	git clone [email protected]:yourusername/pyrocms.git -b {{ variables:get_var name="pyrocms_version" }}/develop
 
 Now you can edit away on the source code and everything is tracked. When you commit your work *please* commit carefully and do not send us your config.php or database.php files in the changes.
 
@@ -25,8 +25,8 @@ To make a pull request, see the [GitHub pull request guide](https://help.github.
 Even if you have a copy of our repository then you are basically taking a snapshot of our repository as it is at the time. If we push new commits you will miss out entirely unless you add us as another remote (this works for either workflow).
 
 	git remote add pyrocms git://github.com/pyrocms/pyrocms.git
-	git pull pyrocms 2.1/develop
-	git push origin 2.1/develop
+	git pull pyrocms {{ variables:get_var name="pyrocms_version" }}/develop
+	git push origin {{ variables:get_var name="pyrocms_version" }}/develop
 
 That will take any new commits from the main PyroCMS repository and push them to your own repository.
 

content/developers/tools/keywords.md

@@ -54,4 +54,4 @@ You can return an array or a string of the keywords with the following methods:
 
 	"keyword_1, keyword_2, keyword_3"
 
-For more on usage see the [API Documentation: Keywords](/2.1/api/classes/Keywords.html).
+For more on usage see the <a href="/{{ variables:get_var name='pyrocms_version' }}/api/classes/Keywords.html">API Documentation: Keywords</a>.

content/setup/installation.md

@@ -4,7 +4,7 @@ The first step in getting up and running with PyroCMS is downloading a copy of t
 
 ## Downloading PyroCMS Manually
 
-You can download the latest 2.1.x version of PyroCMS <a href="https://github.com/pyrocms/pyrocms/zipball/2.1/master">here</a>. Extract the files from the zip and copy or upload them to your webserver or development environment.
+You can download the latest version of PyroCMS <a href="https://github.com/pyrocms/pyrocms/zipball/{{ variables:get_var name='pyrocms_version' }}/master">here</a>. Extract the files from the zip and copy or upload them to your webserver or development environment.
 
 ## Downloading PyroCMS using Git