From dfc32351b201bc0f3867e9354bee9edeec1d4a14 Mon Sep 17 00:00:00 2001
From: Jarrad Hope <me@jarradhope.com>
Date: Mon, 27 Feb 2017 17:39:00 +0100
Subject: [PATCH] Deployed a5a9d62 with MkDocs version: 0.16.1

---
 .DS_Store                                     | Bin 6148 -> 6148 bytes
 .../development/building-status/index.html    |   2 +-
 .../mission-and-core-values/index.html        |   2 +-
 index.html                                    |   2 +-
 mkdocs/search_index.json                      |   8 +--
 sitemap.xml                                   |  56 +++++++++---------
 6 files changed, 35 insertions(+), 35 deletions(-)

diff --git a/.DS_Store b/.DS_Store
index b5787ce04a0198d9d515679c9349cb6491598862..d566a2fb088c4974ebe790e25cd57d2a47cee973 100644
GIT binary patch
delta 241
zcmZoMXfc@JFUrKgz`)4BAi%(o&rr;e$dJQOoK(KKk$E}eWCIZvGfsvAh9aO;0kU*)
zK~heB5>VsGq=KBx;t~Uc>x@jyEUawo9GpPF%Q@MfNq%w_lX-n~a7KQ4Kw?QoQeqKU
zE?z*Qy4u3nNJqiY(4tmHq1xQsKu5vE*sQjelS5q9(AF~{x3a3brnYV-(0m|Z1Ue23
n_@Ok6ngwKFaa~z(QC?1dUOG^gkzsQcb1%!phJ?-R9Dn%%w$wF6

delta 315
zcmZoMXfc@JFUrioz`)4BAi%&-#E{95#8Apm!jQRHk$E|z3rLEGA(<hcArB~sBn{-J
zCzTf$B<18M0oD9SD#*z!E-^5;$;iaa!pg?Z!O6u9f&zkElU<qQSppJEGA73`+1JMe
zXQrekB^HHerj%sF3y203rIux;mIox}rG{k|XC`IlWR_HNaDrgGfOvJap|PQkg1J$x
zjzYDW36N=OW>Q-#Fq?xzTGQ0gH?p9%YtiB*OP4KQap(xp9YDYc^a>aVLunXw6v*JQ
e#pRil;^ds9{QMk{Zk#^e%*#BBWiva+Uw#00?nyNO

diff --git a/contributing/development/building-status/index.html b/contributing/development/building-status/index.html
index e24314e..228ac0b 100644
--- a/contributing/development/building-status/index.html
+++ b/contributing/development/building-status/index.html
@@ -265,7 +265,7 @@
 # or
 $ git clone git@github.com:status-im/status-react.git -b develop &amp;&amp; cd status-react
 
-$ lein deps &amp;&amp; npm install &amp;&amp; ./re-natal deps
+$ lein deps &amp;&amp; npm install &amp;&amp; ./re-natal deps &amp;&amp; lein generate-externs
 $ mvn -f modules/react-native-status/ios/RCTStatus dependency:unpack
 $ cd ios &amp;&amp; pod install &amp;&amp; cd ..
 </code></pre>
diff --git a/getting-started/mission-and-core-values/index.html b/getting-started/mission-and-core-values/index.html
index 7954cd5..3b58759 100644
--- a/getting-started/mission-and-core-values/index.html
+++ b/getting-started/mission-and-core-values/index.html
@@ -252,7 +252,7 @@
 <h3 id="technology">Technology</h3>
 <ul>
 <li>
-<p>Status is built using Clojure.js, React and Golang. It includes a geth node on your device that uses the Light Ethereum Subprotocol (LES) to validate and sync with the blockchain. It uses Whisper (shh) as its messaging client and aims to integrate Swarm for storage.</p>
+<p>Status is built using ClojureScript, React and Golang. It includes a geth node on your device that uses the Light Ethereum Subprotocol (LES) to validate and sync with the blockchain. It uses Whisper (shh) as its messaging client and aims to integrate Swarm for storage.</p>
 </li>
 <li>
 <p>We build systems where the goal is not to dominate and control, but to provide tools and applications that facilitate the better angels of our nature, rather than feeding the purely consumerist habits we have become so used to believing have no alternative.  </p>
diff --git a/index.html b/index.html
index 63cbae6..3277009 100644
--- a/index.html
+++ b/index.html
@@ -359,5 +359,5 @@ Without the dedication of these fine gentleman, Status would not exist.</p>
 
 <!--
 MkDocs version : 0.16.1
-Build Date UTC : 2017-02-09 13:32:09
+Build Date UTC : 2017-02-27 16:38:59
 -->
diff --git a/mkdocs/search_index.json b/mkdocs/search_index.json
index 36a6c8c..b54a7eb 100644
--- a/mkdocs/search_index.json
+++ b/mkdocs/search_index.json
@@ -42,7 +42,7 @@
         }, 
         {
             "location": "/getting-started/mission-and-core-values/", 
-            "text": "Mission \n Core Values\n\n\nJoin us in putting Ethereum on every mobile device on the planet.\n\n\nBeliefs\n\n\nIt is our belief that messenger apps are on the path to becoming gateways to our economies and social lives, they have the highest retention rates on user acquisition and more time is spent in messenger apps than any others. Successful messaging apps lend themselves to mass adoption and, combined with a strong open source community, we believe Status can solve a real problem with the on-boarding of people onto the blockchain;\u200aour favourite being Ethereum.  \n\n\nBlockchains, more specifically \npublic Blockchains\n, have the potential to restructure the very fabric of our society. We believe Ethereum provides the clearest path forward towards an internet where users get to own their own data, and economies are built on open protocols. We imagine a future where decentralized applications make central intermediaries and centralised servers largely redundant. We can pave the way towards \nconversational crypto-commerce\n.  \n\n\nThe Mission\n\n\nOur mission is to facilitate the transition to a more open internet. Status strives to lower the barriers to interacting with Ethereum, and to provide an onramp to the Web 3.0 for the average smartphone user - whilst at the same time fostering an inclusive and diverse open source community.\n\n\nWe intend to employ a strategy that contains three core components: \nTechnology\n, \nCommunity\n \n \nUser Aquisition\n.\n\n\nTechnology\n\n\n\n\n\n\nStatus is built using Clojure.js, React and Golang. It includes a geth node on your device that uses the Light Ethereum Subprotocol (LES) to validate and sync with the blockchain. It uses Whisper (shh) as its messaging client and aims to integrate Swarm for storage.\n\n\n\n\n\n\nWe build systems where the goal is not to dominate and control, but to provide tools and applications that facilitate the better angels of our nature, rather than feeding the purely consumerist habits we have become so used to believing have no alternative.  \n\n\n\n\n\n\nWe actively experiment with and deploy the latest technologies in the ongoing drive to provide a slick user experience while not compromising on the security or sovereignity of any user's data.\n\n\n\n\n\n\nWe offer an intuitve entry point into decentralized, encrypted, peer-ro-peer networks that is maintained by a large and diverse group of open-source developers.\n\n\n\n\n\n\nWe approach all contributions with an open mind and respect the opinions of our fellow developers. We aim to foster an environment conducive to easy, intuitive and consistent learning and one that fosters innovation at all levels.\n\n\n\n\n\n\nWe aim to help as many people to learn and contribute to the community's effort and always aim to encourage those more new to the paradigm of massively concurrent peer-to-peer networks than we are.\n\n\n\n\n\n\nCommunity\n\n\nworking with dapp develoeprs\n\n\nUser Aquisition\n\n\nmarketing campaigns for dapp developers, user aquisition for mass adoption\n\n\nCore Values\n\n\n\n\n\n\nFree (libre) and open source software.\n\n\n\n\n\n\nReciprocity, open-mindedness, respect and encouragement.\n\n\n\n\n\n\nOur work is driven by a belief that Ethereum and public blockchains can yield great benefits to society, and access to DApps and Ethereum should be made available to anyone, anywhere.\n\n\n\n\n\n\nThe systems we're creating must be open, permissionless, award fair access and democratise power.\n\n\n\n\n\n\nCommunication should be clear and transparent to everyone in the community.", 
+            "text": "Mission \n Core Values\n\n\nJoin us in putting Ethereum on every mobile device on the planet.\n\n\nBeliefs\n\n\nIt is our belief that messenger apps are on the path to becoming gateways to our economies and social lives, they have the highest retention rates on user acquisition and more time is spent in messenger apps than any others. Successful messaging apps lend themselves to mass adoption and, combined with a strong open source community, we believe Status can solve a real problem with the on-boarding of people onto the blockchain;\u200aour favourite being Ethereum.  \n\n\nBlockchains, more specifically \npublic Blockchains\n, have the potential to restructure the very fabric of our society. We believe Ethereum provides the clearest path forward towards an internet where users get to own their own data, and economies are built on open protocols. We imagine a future where decentralized applications make central intermediaries and centralised servers largely redundant. We can pave the way towards \nconversational crypto-commerce\n.  \n\n\nThe Mission\n\n\nOur mission is to facilitate the transition to a more open internet. Status strives to lower the barriers to interacting with Ethereum, and to provide an onramp to the Web 3.0 for the average smartphone user - whilst at the same time fostering an inclusive and diverse open source community.\n\n\nWe intend to employ a strategy that contains three core components: \nTechnology\n, \nCommunity\n \n \nUser Aquisition\n.\n\n\nTechnology\n\n\n\n\n\n\nStatus is built using ClojureScript, React and Golang. It includes a geth node on your device that uses the Light Ethereum Subprotocol (LES) to validate and sync with the blockchain. It uses Whisper (shh) as its messaging client and aims to integrate Swarm for storage.\n\n\n\n\n\n\nWe build systems where the goal is not to dominate and control, but to provide tools and applications that facilitate the better angels of our nature, rather than feeding the purely consumerist habits we have become so used to believing have no alternative.  \n\n\n\n\n\n\nWe actively experiment with and deploy the latest technologies in the ongoing drive to provide a slick user experience while not compromising on the security or sovereignity of any user's data.\n\n\n\n\n\n\nWe offer an intuitve entry point into decentralized, encrypted, peer-ro-peer networks that is maintained by a large and diverse group of open-source developers.\n\n\n\n\n\n\nWe approach all contributions with an open mind and respect the opinions of our fellow developers. We aim to foster an environment conducive to easy, intuitive and consistent learning and one that fosters innovation at all levels.\n\n\n\n\n\n\nWe aim to help as many people to learn and contribute to the community's effort and always aim to encourage those more new to the paradigm of massively concurrent peer-to-peer networks than we are.\n\n\n\n\n\n\nCommunity\n\n\nworking with dapp develoeprs\n\n\nUser Aquisition\n\n\nmarketing campaigns for dapp developers, user aquisition for mass adoption\n\n\nCore Values\n\n\n\n\n\n\nFree (libre) and open source software.\n\n\n\n\n\n\nReciprocity, open-mindedness, respect and encouragement.\n\n\n\n\n\n\nOur work is driven by a belief that Ethereum and public blockchains can yield great benefits to society, and access to DApps and Ethereum should be made available to anyone, anywhere.\n\n\n\n\n\n\nThe systems we're creating must be open, permissionless, award fair access and democratise power.\n\n\n\n\n\n\nCommunication should be clear and transparent to everyone in the community.", 
             "title": "Mission & Core Values"
         }, 
         {
@@ -62,7 +62,7 @@
         }, 
         {
             "location": "/getting-started/mission-and-core-values/#technology", 
-            "text": "Status is built using Clojure.js, React and Golang. It includes a geth node on your device that uses the Light Ethereum Subprotocol (LES) to validate and sync with the blockchain. It uses Whisper (shh) as its messaging client and aims to integrate Swarm for storage.    We build systems where the goal is not to dominate and control, but to provide tools and applications that facilitate the better angels of our nature, rather than feeding the purely consumerist habits we have become so used to believing have no alternative.      We actively experiment with and deploy the latest technologies in the ongoing drive to provide a slick user experience while not compromising on the security or sovereignity of any user's data.    We offer an intuitve entry point into decentralized, encrypted, peer-ro-peer networks that is maintained by a large and diverse group of open-source developers.    We approach all contributions with an open mind and respect the opinions of our fellow developers. We aim to foster an environment conducive to easy, intuitive and consistent learning and one that fosters innovation at all levels.    We aim to help as many people to learn and contribute to the community's effort and always aim to encourage those more new to the paradigm of massively concurrent peer-to-peer networks than we are.", 
+            "text": "Status is built using ClojureScript, React and Golang. It includes a geth node on your device that uses the Light Ethereum Subprotocol (LES) to validate and sync with the blockchain. It uses Whisper (shh) as its messaging client and aims to integrate Swarm for storage.    We build systems where the goal is not to dominate and control, but to provide tools and applications that facilitate the better angels of our nature, rather than feeding the purely consumerist habits we have become so used to believing have no alternative.      We actively experiment with and deploy the latest technologies in the ongoing drive to provide a slick user experience while not compromising on the security or sovereignity of any user's data.    We offer an intuitve entry point into decentralized, encrypted, peer-ro-peer networks that is maintained by a large and diverse group of open-source developers.    We approach all contributions with an open mind and respect the opinions of our fellow developers. We aim to foster an environment conducive to easy, intuitive and consistent learning and one that fosters innovation at all levels.    We aim to help as many people to learn and contribute to the community's effort and always aim to encourage those more new to the paradigm of massively concurrent peer-to-peer networks than we are.", 
             "title": "Technology"
         }, 
         {
@@ -432,7 +432,7 @@
         }, 
         {
             "location": "/contributing/development/building-status/", 
-            "text": "Building Status\n\n\nThis document is the entry point for developers of Status. This guide is for anyone who is interested in building, developing, debugging or submitting a bug report, pull request or contributing to Status with code.\n\n\nThis guide is written with OS X in mind.\n\n\nBuild and Test\n\n\nRequirements\n\n\n\n\nHomebrew\n + \nbrew update\n (optional, for OS X)\n\n\nNode \n NPM\n \nbrew install node watchman\n\n\nLein\n \nbrew install leiningen\n\n\nreact-native\n \nnpm install -g react-native-cli\n\n\nLatest JDK\n \nbrew cask install java\n\n\nAndroid SDK with build tools version 23.0.1 [Mac] \nbrew install android-sdk\n or \nWindows/Linux\n\n\nGenymotion\n (optional, you may use an Android Virtual Device or real device)\n\n\nSetup Android Development Environment / Simulator\n\n\nGIT over SSH, please add public key to Github\n\n\nMaven\n \nbrew install maven\n\n\nCocoapods\n \nsudo gem install cocoapods\n\n\n\n\nDependencies \n Setup\n\n\n$ git clone git@github.com:status-im/status-react.git -b master \n cd status-react\n# or\n$ git clone git@github.com:status-im/status-react.git -b develop \n cd status-react\n\n$ lein deps \n npm install \n ./re-natal deps\n$ mvn -f modules/react-native-status/ios/RCTStatus dependency:unpack\n$ cd ios \n pod install \n cd ..\n\n\n\nBuilding Status for Release\n\n\n# fill in store file properties in android/gradle.properties\n$ lein prod-build\n$ react-native run-android --variant=release\n# for iOS, build in Xcode\n\n\n\nBuilding Status for Development\n\n\n$ ./re-natal use-android-device \ndevice\n # (genymotion, real or avd)\n# or\n$ ./re-natal use-ios-device \ndevice\n # (simulator or real)\n\n$ ./re-natal use-figwheel\n\n# new tab, run figwheel REPL\n$ BUILD_IDS=\"ios,android\" lein repl\n\n# new tab, run react native packager\n$ react-native start\n\n# new tab, enable communication to react-native and figwheel\n# for android\n$ adb reverse tcp:8081 tcp:8081\n$ adb reverse tcp:3449 tcp:3449\n$ react-native run-android\n\n# for ios\n$ react-native run-ios\n\n\n\nAccess Geth on Device\n\n\nadb forward tcp:8545 tcp:8545\nbuild/bin/geth attach http://localhost:8545\n\n\n\nContributing\n\n\nPlease make sure your contributions adhere to our coding guidelines:\n\n\n\n\nCode must be idiomatic Clojure, please refer to the \nstyle guidelines\n (i.e. use \nlein eastwood\n\n \n \nlein kibit\n).\n\n\nCode must be documented.\n\n\nPull requests need to be based on and opened against the \ndevelop\n branch.\n\n\nCommit messages should be prefixed with the root namespace(s) under \nstatus-im\n that they modify.\n\n\ne.g. \"contacts, ios: add contact stylistic changes\"\n\n\n\n\nIssues\n\n\nOnly Github is used to track issues. (Please include the commit and branch when reporting an issue.)\n\n\nOverv.io\n is used to overview issues in multiple repositories.\n\n\nCode formatting\n\n\nPlease run \nlein eastwood\n and \nlein kibit\n before contributing.\n\n\nBranch naming\n\n\nBranch format must be under \nCATEGORY/PLAIN-TEXT-#ISSUE_NUMBER\n acceptable branches are;\n\n\nfeature/discover\n or \nbug/broken-form-#113\n\n\nThe following categories are;\n- \nfeature/\n for implementation of features\n- \nbug/\n for fixing bugs\n- \ntests/\n for unit/UI tests\n- \nexperiment/\n for non-features\n- \nwip/\n for longer lived branches\n- \njunk/\n for irrelevant/soon-to-be-deleted branches\n\n\nPull Requests\n\n\nPull Requests should by default use the \ndevelop\n branch as a base. The \nmaster\n branch is kept stable and \ndevelop\n is periodically merged there. Tags are used for releases. Each Pull Request must be rebased against \ndevelop\n and squashed into a single commit, prefixed with the root namespace(s) under \nstatus-im\n that they modify. e.g.\n\n\n\n\n\"contacts, ios: add contact stylistic changes\"\n\n\n\n\nWalkthrough\n\n\nFork the repository on Github's web UI.\n\n\nClone your fork. Add the upstream as a remote.\n\n\n$ git clone git@github.com:\nyou\n/status-react.git\n$ git remote add upstream git@github.com:status-im/status-react.git\n\n\n\nNow you have two remotes: \norigin\n pointing to your fork and \nupstream\n pointing to the shared repo.\n\n\n$ git fetch --all\n\n\n\nThen isolate the bug/feature work you will do into a topic branch\n\n\n$ git checkout -b bug/missing-contact-#116 upstream/develop\n\n\n\nKeep your branch fresh against upstream\n\n\n$ git fetch upstream\n$ git rebase upstream/develop\n\n\n\nIf multiple people are working on the same feature branch don't forget to also\n\n\n$ git rebase upstream bug/missing-contact-#116\n\n\n\nWhen you are ready to make your pull request\n\n\n$ git push origin\n\n\n\nAfter PR has been reviewed do a final cleanup and squash your commit\n\n\n$ git rebase -i upstream/develop\n$ git push -f origin\n\n\n\nRepository Overview\n\n\nThe Status application is divided into 6 core repositories;\n\n\n\n\n\n\nstatus-react\n - our main react native application writtein in Clojurescript, Java \n Objective C\n\n\n\n\n\n\ngo-ethereum\n - our branch of \ngo-ethereum\n which contains our custom modifications in \ngo-ethereum/status-develop\n\n\n\n\n\n\nstatus-go\n - represents our binding to the \ngo-ethereum\n lib and exposes methods to \nstatus-react\n to Java / Objective C.\n\n\n\n\nstatus-lib\n - implements our application protocols for chatbots, has been absorbed into \nstatus-react\n until application protocol settles\n\n\nreact-native-status\n - the intent behind this repo was to seperate Java/Objective C code into a react native module, it may be absorbed into \nstatus-react\n in future\n\n\nstatus-server\n - is our intermediary server primarily used for contact discovery.", 
+            "text": "Building Status\n\n\nThis document is the entry point for developers of Status. This guide is for anyone who is interested in building, developing, debugging or submitting a bug report, pull request or contributing to Status with code.\n\n\nThis guide is written with OS X in mind.\n\n\nBuild and Test\n\n\nRequirements\n\n\n\n\nHomebrew\n + \nbrew update\n (optional, for OS X)\n\n\nNode \n NPM\n \nbrew install node watchman\n\n\nLein\n \nbrew install leiningen\n\n\nreact-native\n \nnpm install -g react-native-cli\n\n\nLatest JDK\n \nbrew cask install java\n\n\nAndroid SDK with build tools version 23.0.1 [Mac] \nbrew install android-sdk\n or \nWindows/Linux\n\n\nGenymotion\n (optional, you may use an Android Virtual Device or real device)\n\n\nSetup Android Development Environment / Simulator\n\n\nGIT over SSH, please add public key to Github\n\n\nMaven\n \nbrew install maven\n\n\nCocoapods\n \nsudo gem install cocoapods\n\n\n\n\nDependencies \n Setup\n\n\n$ git clone git@github.com:status-im/status-react.git -b master \n cd status-react\n# or\n$ git clone git@github.com:status-im/status-react.git -b develop \n cd status-react\n\n$ lein deps \n npm install \n ./re-natal deps \n lein generate-externs\n$ mvn -f modules/react-native-status/ios/RCTStatus dependency:unpack\n$ cd ios \n pod install \n cd ..\n\n\n\nBuilding Status for Release\n\n\n# fill in store file properties in android/gradle.properties\n$ lein prod-build\n$ react-native run-android --variant=release\n# for iOS, build in Xcode\n\n\n\nBuilding Status for Development\n\n\n$ ./re-natal use-android-device \ndevice\n # (genymotion, real or avd)\n# or\n$ ./re-natal use-ios-device \ndevice\n # (simulator or real)\n\n$ ./re-natal use-figwheel\n\n# new tab, run figwheel REPL\n$ BUILD_IDS=\"ios,android\" lein repl\n\n# new tab, run react native packager\n$ react-native start\n\n# new tab, enable communication to react-native and figwheel\n# for android\n$ adb reverse tcp:8081 tcp:8081\n$ adb reverse tcp:3449 tcp:3449\n$ react-native run-android\n\n# for ios\n$ react-native run-ios\n\n\n\nAccess Geth on Device\n\n\nadb forward tcp:8545 tcp:8545\nbuild/bin/geth attach http://localhost:8545\n\n\n\nContributing\n\n\nPlease make sure your contributions adhere to our coding guidelines:\n\n\n\n\nCode must be idiomatic Clojure, please refer to the \nstyle guidelines\n (i.e. use \nlein eastwood\n\n \n \nlein kibit\n).\n\n\nCode must be documented.\n\n\nPull requests need to be based on and opened against the \ndevelop\n branch.\n\n\nCommit messages should be prefixed with the root namespace(s) under \nstatus-im\n that they modify.\n\n\ne.g. \"contacts, ios: add contact stylistic changes\"\n\n\n\n\nIssues\n\n\nOnly Github is used to track issues. (Please include the commit and branch when reporting an issue.)\n\n\nOverv.io\n is used to overview issues in multiple repositories.\n\n\nCode formatting\n\n\nPlease run \nlein eastwood\n and \nlein kibit\n before contributing.\n\n\nBranch naming\n\n\nBranch format must be under \nCATEGORY/PLAIN-TEXT-#ISSUE_NUMBER\n acceptable branches are;\n\n\nfeature/discover\n or \nbug/broken-form-#113\n\n\nThe following categories are;\n- \nfeature/\n for implementation of features\n- \nbug/\n for fixing bugs\n- \ntests/\n for unit/UI tests\n- \nexperiment/\n for non-features\n- \nwip/\n for longer lived branches\n- \njunk/\n for irrelevant/soon-to-be-deleted branches\n\n\nPull Requests\n\n\nPull Requests should by default use the \ndevelop\n branch as a base. The \nmaster\n branch is kept stable and \ndevelop\n is periodically merged there. Tags are used for releases. Each Pull Request must be rebased against \ndevelop\n and squashed into a single commit, prefixed with the root namespace(s) under \nstatus-im\n that they modify. e.g.\n\n\n\n\n\"contacts, ios: add contact stylistic changes\"\n\n\n\n\nWalkthrough\n\n\nFork the repository on Github's web UI.\n\n\nClone your fork. Add the upstream as a remote.\n\n\n$ git clone git@github.com:\nyou\n/status-react.git\n$ git remote add upstream git@github.com:status-im/status-react.git\n\n\n\nNow you have two remotes: \norigin\n pointing to your fork and \nupstream\n pointing to the shared repo.\n\n\n$ git fetch --all\n\n\n\nThen isolate the bug/feature work you will do into a topic branch\n\n\n$ git checkout -b bug/missing-contact-#116 upstream/develop\n\n\n\nKeep your branch fresh against upstream\n\n\n$ git fetch upstream\n$ git rebase upstream/develop\n\n\n\nIf multiple people are working on the same feature branch don't forget to also\n\n\n$ git rebase upstream bug/missing-contact-#116\n\n\n\nWhen you are ready to make your pull request\n\n\n$ git push origin\n\n\n\nAfter PR has been reviewed do a final cleanup and squash your commit\n\n\n$ git rebase -i upstream/develop\n$ git push -f origin\n\n\n\nRepository Overview\n\n\nThe Status application is divided into 6 core repositories;\n\n\n\n\n\n\nstatus-react\n - our main react native application writtein in Clojurescript, Java \n Objective C\n\n\n\n\n\n\ngo-ethereum\n - our branch of \ngo-ethereum\n which contains our custom modifications in \ngo-ethereum/status-develop\n\n\n\n\n\n\nstatus-go\n - represents our binding to the \ngo-ethereum\n lib and exposes methods to \nstatus-react\n to Java / Objective C.\n\n\n\n\nstatus-lib\n - implements our application protocols for chatbots, has been absorbed into \nstatus-react\n until application protocol settles\n\n\nreact-native-status\n - the intent behind this repo was to seperate Java/Objective C code into a react native module, it may be absorbed into \nstatus-react\n in future\n\n\nstatus-server\n - is our intermediary server primarily used for contact discovery.", 
             "title": "Building Status"
         }, 
         {
@@ -452,7 +452,7 @@
         }, 
         {
             "location": "/contributing/development/building-status/#dependencies-setup", 
-            "text": "$ git clone git@github.com:status-im/status-react.git -b master   cd status-react\n# or\n$ git clone git@github.com:status-im/status-react.git -b develop   cd status-react\n\n$ lein deps   npm install   ./re-natal deps\n$ mvn -f modules/react-native-status/ios/RCTStatus dependency:unpack\n$ cd ios   pod install   cd ..", 
+            "text": "$ git clone git@github.com:status-im/status-react.git -b master   cd status-react\n# or\n$ git clone git@github.com:status-im/status-react.git -b develop   cd status-react\n\n$ lein deps   npm install   ./re-natal deps   lein generate-externs\n$ mvn -f modules/react-native-status/ios/RCTStatus dependency:unpack\n$ cd ios   pod install   cd ..", 
             "title": "Dependencies &amp; Setup"
         }, 
         {
diff --git a/sitemap.xml b/sitemap.xml
index e034d0d..80d8c88 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -4,7 +4,7 @@
     
     <url>
      <loc>https://wiki.status.im/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
     
@@ -13,37 +13,37 @@
         
     <url>
      <loc>https://wiki.status.im/getting-started/mission-and-core-values/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>https://wiki.status.im/getting-started/user-guide/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>https://wiki.status.im/getting-started/faq/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>https://wiki.status.im/getting-started/code-of-conduct/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>https://wiki.status.im/contributing/development/introduction/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>https://wiki.status.im/community/how-to-grow-our-community/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
@@ -59,31 +59,31 @@
         
     <url>
      <loc>https://wiki.status.im/contributing/design-guidelines/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>https://wiki.status.im/contributing/testing-and-feedback/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>https://wiki.status.im/contributing/documenting/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>https://wiki.status.im/contributing/outreach/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>https://wiki.status.im/contributing/translations/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
@@ -93,31 +93,31 @@
         
     <url>
      <loc>https://wiki.status.im/community/how-to-grow-our-community/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>https://wiki.status.im/community/slack/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>https://wiki.status.im/community/newsletter/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>https://wiki.status.im/community/blog/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>https://wiki.status.im/community/tell-a-friend/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
@@ -127,55 +127,55 @@
         
     <url>
      <loc>https://wiki.status.im/proposals/commiteth/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>https://wiki.status.im/proposals/contact-sharing/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>https://wiki.status.im/proposals/chat-api/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>https://wiki.status.im/proposals/discover/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>https://wiki.status.im/proposals/messaging/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>https://wiki.status.im/proposals/erc20-exchange/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>https://wiki.status.im/proposals/sticker-market/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>https://wiki.status.im/proposals/visual-programming/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>https://wiki.status.im/proposals/moments/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
@@ -185,13 +185,13 @@
         
     <url>
      <loc>https://wiki.status.im/licenses/mpl2/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>
         
     <url>
      <loc>https://wiki.status.im/licenses/lgpl-v3.0-static/</loc>
-     <lastmod>2017-02-09</lastmod>
+     <lastmod>2017-02-27</lastmod>
      <changefreq>daily</changefreq>
     </url>