` tags in your config.xml are copied to the platform-specific configuration files, which means that any preferences [supported by the PhoneGap framework](http://docs.phonegap.com/en/edge/config_ref_index.md.html#The%20config.xml%20File), or by any plugins you are using, will work on PhoneGap Build.
+
+**Note**: make sure you select your PhoneGap version when looking at the PhoneGap docs page.
+
+In addition, PhoneGap Build supports some of its own custom preferences, used for things like selecting the PhoneGap version, platform sdk version targeting, and others. These custom preferences are listed below.
+
+If you want to see more detail about what exactly these custom preferences are doing, most of them are translated using the [open-source confetti library](http://github.com/phonegap-build/confetti). Check out the templates directory if you want to dig in.
+
+### Multi-Platform
+- [phonegap-version](#phonegap-version)
+- [orientation](#orientation)
+- [fullscreen](#fullscreen)
+
+### iOS Only
+- [target-device](#target-device)
+- [prerendered-icon](#prerendered-icon)
+- [detect-data-types](#detect-data-types)
+- [exit-on-suspend](#exit-on-suspend)
+- [deployment-target](#deployment-target)
+
+### Android Only
+- [android-build-tool](#android-build-tool)
+- [android-minSdkVersion](#android-minSdkVersion)
+- [android-maxSdkVersion](#android-maxSdkVersion)
+- [android-targetSdkVersion](#android-targetSdkVersion)
+- [android-installLocation](#android-installLocation)
+- [android-windowSoftInputMode](#android-windowSoftInputMode)
+
+### Windows Only (cli-6.1.1 and above)
+- [windows-arch](#windows-arch)
+- [windows-identity-name](#windows-identity-name)
+
+### Examples
+- [Full sample config.xml](#example)
+- [Platform selection](#platform-selection)
+
+
+### Multi-Platform
+**phonegap-version**: The version of PhoneGap / Cordova used. For a list of currently supported PhoneGap versions, and a breakdown of the individual platform versions, [go here](https://build.phonegap.com/current-support).
+
+
+**orientation**: Device orientation; possible values are default, landscape, or portrait
. Please note that default
means both landscape and portrait are enabled. If you want to use each platform's default settings (usually portrait only), remove this tag from your config.xml file.
+
+**fullscreen**: Makes your app full screen, with values true or false
. This hides the status bar at the top, and is false by default. Note: may not be supported by newer versions of iOS, but users can use
+the [config-file element on phonegap build](http://phonegap.com/blog/2014/01/30/customizing-your-android-manifest-and-ios-property-list-on-phonegap-build/), and set UIViewControllerBasedStatusBarAppearance to false and UIStatusBarHidden to true.
+
+### iOS Only
+**target-device**: For targeting a specific device; possible values are handset, tablet, or universal
. Note that this currently only applies to iOS builds; by default all builds are universal.
+
+**prerendered-icon**: This will cause iOS to not apply its gloss to the app's icon on the user's home screen; possible values are true or false
, default is false.
+
+**detect-data-types**: Controls whether certain data types (such as phone numbers and dates) are automatically turned into links by the system. Defaults to "true" (as does the system web view). In preference to this, try using meta-tags:
+ ```
+
+
+ ```
+And use detect-data-types if meta tags don't work for you.
+
+**exit-on-suspend**: If set to true, app will terminate when suspended, for example when home button is pressed; default is false.
+
+**deployment-target**: This sets the IPHONEOS_DEPLOYMENT_TARGET
in the build, which tranlsates to the MinimumOSVersion
in the ipa Propertly List.
+
+### Android Only
+**android-build-tool**: Minimum Android SDK version. Corresponds to the usesSdk
attributes in the AndroidManifest.xml
file - more details are in [the Android documentation](http://developer.android.com/guide/topics/manifest/uses-sdk-element.html). Defaults to 14 (Android 4.0, 4.0.1, 4.0.2).
+
+**android-minSdkVersion**: Minimum Android SDK version. Corresponds to the usesSdk
attributes in the AndroidManifest.xml
file - more details are in [the Android documentation](http://developer.android.com/guide/topics/manifest/uses-sdk-element.html). Defaults to 14 (Android 4.0, 4.0.1, 4.0.2).
+
+**android-maxSdkVersion**: Maximum Android SDK version. Corresponds to the usesSdk
attributes in the AndroidManifest.xml
file - more details are in [the Android documentation](http://developer.android.com/guide/topics/manifest/uses-sdk-element.html). Unset by default.
+
+**android-targetSdkVersion**:
+Corresponds to the usesSdk
attributes in the AndroidManifest.xml
file -- an integer designating the API Level that the application targets. If not set, the default value equals that given to minSdkVersion. More details are in [the Android documentation](http://developer.android.com/guide/topics/manifest/uses-sdk-element.html#target). Unset by default.
+
+**android-installLocation**: Where an app can be installed - defaults to internalOnly
(as the Android SDK). auto
or preferExternal
allow the app to be installed on an SD card - this can lead to unexpected behavior. More details available in [the Android documentation](http://developer.android.com/guide/appendix/install-location.html).
+
+**android-windowSoftInputMode**: How the main window of the activity interacts with the window containing the on-screen soft keyboard. More details, and possible values, available in [the Android documentation](http://developer.android.com/guide/topics/manifest/activity-element.html#wsoft).
+
+### Windows Only
+**windows-arch**: Select the architecture that your build targets. Valid values are `anycpu`, `arm`, `x86`, and `x64`.
+
+**windows-identity-name**: Set the App Idenity Name in your App Manifest, necessary for publishing to the App Store. This preference must match the App Identity Name from your *Windows Dev Center Account -> App Management -> App Identity*.
+
+
+
+### Example Config.xml
+
+
+
+
+ PhoneGap Example
+
+ An example for phonegap build docs.
+
+
+ wildabeast
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+### Platform Selection
+
+By default, preferences are for all platforms. To specify a preference to be for a single platform you can place any preference inside a platform tag.
+
+
+
+
+
+
+
+
+
+This fragment will make the iOS app be available in landscape orientation while the android app will be in portrait mode.
diff --git a/docs/4-phonegap-build/3-signing/1-ios.html.md b/docs/4-phonegap-build/3-signing/1-ios.html.md
new file mode 100755
index 000000000..a60b6e99c
--- /dev/null
+++ b/docs/4-phonegap-build/3-signing/1-ios.html.md
@@ -0,0 +1,94 @@
+---
+title: Signing
+url: phonegap-build/signing/ios
+github_url: https://github.com/phonegap/phonegap-docs/blob/master/docs/4-phonegap-build/3-signing/1-ios.html.md
+layout: subpage
+tabs:
+ - label: iOS
+ url: phonegap-build/signing/ios
+ - label: Android
+ url: phonegap-build/signing/android
+ - label: Windows
+ url: phonegap-build/signing/windows
+---
+
+- [Creating your key on Mac](#mac-users)
+- [Creating your key on Windows](#windows-users)
+- [Register Devices](#register-devices)
+- [Create Provisioning Profile](#create-provisioning-profile)
+- [Submit to Build](#submit-to-build)
+
+**Note: it is Phonegap Build's policy not to retrieve signing keys for users, for legal reasons. Back them up.**
+
+***
+
+### Mac Users
+
+#### Convert the iPhone Developer Certificate to a P12 file on Mac OS
+
+You'll first need to obtain an Apple Developer Certificate. See apple documenation for this.
+
+Next you'll export it to the P12 keystore format. To do this on Mac® OS:
+
+1. Open the Keychain Access application (in the Applications/Utilities folder).
+2. If you have not already added the certificate to Keychain, select File > Import. Then navigate to the certificate file (the .cer file) you obtained from Apple.
+3. Select the Keys category in Keychain Access.
+4. Select the private key associated with your iPhone Development Certificate. The private key is identified by the iPhone Developer: public certificate that is paired with it.
+5. Command-click the iPhone Developer certificate and select, Export "iPhone Developer: Name...".
+![Keychain export](/images/phonegap-build/keychain-export.png)
+6. Save your keystore in the Personal Information Exchange (.p12) file format.
+7. You will be prompted to create a password that is used when you use the keystore to sign applications or transfer the key and certificate in this keystore to another keystore.
+![keychain password](/images/phonegap-build/keychain-password.png)
+
+***
+
+### Windows Users
+
+#### Convert an Apple developer certificate to a P12 file on Windows
+
+To develop apps via Build, you must use a P12 certificate file. You generate this certificate based on the Apple iPhone developer certificate file you receive from Apple.
+
+1. Download and install [OpenSSL](http://slproweb.com/products/Win32OpenSSL.html)
+
+2. Convert the developer certificate file you receive from Apple into a PEM certificate file. To do this, run the following command-line statement from the [OpenSSL](http://slproweb.com/products/Win32OpenSSL.html) bin directory:
+
+`openssl x509 -in developer_identity.cer -inform DER -out developer_identity.pem -outform PEM`
+
+3. If you are using the private key from the keychain on a Mac computer, convert it into a PEM key:
+
+`openssl pkcs12 -nocerts -in mykey.p12 -out mykey.pem`
+
+4. You can now generate a valid P12 file, based on the key and the PEM version of the iPhone developer certificate:
+
+`openssl pkcs12 -export -inkey mykey.key -in developer_identity.pem -out iphone_dev.p12`
+
+### Register devices
+
+1. Visit [Apple Developer Portal](https://developer.apple.com/ios/manage/provisioningprofiles/index.action).
+2. Go to Device section. Under Manage tab, provide Device Name and [Device ID](https://developer.apple.com/ios/manage/devices/howto.action) (40 hex characters)
+
+### Create Provisioning Profile
+
+1. Visit [Apple Developer Portal](https://developer.apple.com/ios/manage/provisioningprofiles/index.action).
+2. Go to Provisioning section. Create new profile under Development tab.
+3. Fill the form with Profile Name, Certificates (as per .cer above), App ID and your development device.
+
+### Submit to Build
+
+Go to your Account > Edit Setting > Signing Keys' tab:
+
+![Edit Account](/images/phonegap-build/edit_account_settings.png)
+
+Click 'add a key...' and supply your previously generated p12:
+
+![Add Key](/images/phonegap-build/ios_add_key.png)
+
+### Unlocking the key.
+
+Go to your Account > Edit Setting > Signing Keys' tab:
+
+![Edit Account](/images/phonegap-build/edit_account_settings.png)
+
+Click 'lock' button and supply the certificate password you used to export your cert.
+
+![Unlock key](/images/phonegap-build/ios_unlock.png)
\ No newline at end of file
diff --git a/docs/4-phonegap-build/3-signing/2-android.html.md b/docs/4-phonegap-build/3-signing/2-android.html.md
new file mode 100755
index 000000000..e4f9a0d14
--- /dev/null
+++ b/docs/4-phonegap-build/3-signing/2-android.html.md
@@ -0,0 +1,64 @@
+---
+title: Signing
+url: phonegap-build/signing/android
+github_url: https://github.com/phonegap/phonegap-docs/blob/master/docs/4-phonegap-build/3-signing/2-android.html.md
+layout: subpage
+tabs:
+ - label: iOS
+ url: phonegap-build/signing/ios
+ - label: Android
+ url: phonegap-build/signing/android
+ - label: Windows
+ url: phonegap-build/signing/windows
+---
+
+- [Generating a private key](#generating-a-private-key)
+- [Submitting your key to build](#submitting-your-key-to-build)
+- [Unlocking your key](#unlocking-your-key)
+
+**Note: it is Phonegap Build's policy not to retrieve signing keys for users, for legal reasons. Back them up.**
+
+***
+
+### Generating a private key
+
+1. [Download and install Java](http://www.java.com/en/download/index.jsp).
+
+2. Set Java_Home directory (http://docs.oracle.com/cd/E19182-01/820-7851/inst_cli_jdk_javahome_t/index.html).
+
+3. Open the command prompt (cmd.exe) as an Administrator, then Run the following command: `$ keytool -genkey -v -keystore [keystore_name].keystore -alias [alias_name] -keyalg RSA -keysize 2048 -validity 10000`
+
+4. Keytool will ask for keystore password. Enter password and confirm:
+![Keystore Password](/images/phonegap-build/android_keystore_pass.png)
+
+5. Next, keytool will ask for additional information. Supply appropriately:
+![Keystore Password 2](/images/phonegap-build/additional_info.png)
+
+6. Next, keytool will ask password for Alias. Return if it's the same as keystore password. Othewise enter password and confirm:
+![Alias password](/images/phonegap-build/alias_password.png)
+
+7. Your signing key is now ready to submit:
+![Submit signing key](/images/phonegap-build/keystore_ready.png)
+
+### Submitting your key to Build
+
+Go to your Account > Edit Setting > Signing Key's tab.
+![Edit signing keys](/images/phonegap-build/edit_account_settings.png)
+
+Click 'add a key...', ensuring you use the same alias used when you generated your key.
+![Add info](/images/phonegap-build/add_key.png)
+
+### Unlocking your key
+
+Go to your Account > Edit Setting > Signing Key's tab:
+![Signing Keys](/images/phonegap-build/edit_account_settings.png)
+
+Click unlock button and supply the the certificate password (from step #6 above) and the keystore password (from step #4 above)
+
+![Unlocking](/images/phonegap-build/unlock_key.png)
+
+Lastly, either set your key to be default using the checkbox in the keys list, or in your individual application's details, select the key you've uploaded and unlocked.
+
+***
+
+[More info](http://developer.android.com/tools/publishing/app-signing.html#cert)
diff --git a/docs/4-phonegap-build/3-signing/3-windows.html.md b/docs/4-phonegap-build/3-signing/3-windows.html.md
new file mode 100755
index 000000000..9408ef6e5
--- /dev/null
+++ b/docs/4-phonegap-build/3-signing/3-windows.html.md
@@ -0,0 +1,44 @@
+---
+title: Signing
+url: phonegap-build/signing/windows
+github_url: https://github.com/phonegap/phonegap-docs/blob/master/docs/4-phonegap-build/3-signing/3-windows.html.md
+layout: subpage
+tabs:
+ - label: iOS
+ url: phonegap-build/signing/ios
+ - label: Android
+ url: phonegap-build/signing/android
+ - label: Windows
+ url: phonegap-build/signing/windows
+---
+
+
+- [Windows 10 (Universal) Signing](#windows): `phonegap-version cli-6.1.1` and greater
+- [Windows Phone 8.0/8.1 Signing](#winphone8): `phonegap-version cli-6.0.0` and below
+
+
+### Windows 10 (Universal) Signing
+
+Windows builds have a slightly more involved signing process than the previous Windows Phone Publisher ID method, which was a simple GUID setting. A .pfx certificate file is now required to sign your app and distribute it to the App Store. [This article on MSDN](https://msdn.microsoft.com/en-us/library/windows/desktop/jj835832%28v=vs.85%29.aspx) explains how to create a PFX store file. Ensure the Subject Name of your signing certificate matches the Windows Publisher ID from your [Microsoft Developer Account](https://developer.microsoft.com/en-us/dashboard/account/management).
+
+Go to your [PhoneGap Build Account Settings](https://buildstage.phonegap.com/people/edit), select the **Signing Keys** tab, upload your **Windows 10** pfx key and unlock it, and select it when building your application.
+
+**In addition:**
+
+1. The `author` field in your config.xml must match the Publisher Display Name from *Windows Dev Center -> Account Settings*, i.e:
+
+ ```<author>Adobe Systems Canada Inc</author>```
+
+2. A new config.xml preference `windows-identity-name` has been introduced to set the App Idenity Name in your App Manifest. This preference must match the App Identity Name from your *Windows Dev Center Account -> App Management -> App Identity*:
+
+ ```<preference name="windows-identity-name" value="PhonegapBuild.PGBDeveloper" />```
+
+
+### Windows Phone 8.0/8.1 Signing
+
+1. Log into the [Windows Dev Center](http://dev.windows.com), and click **Dashboard** in the top right.
+2. Click **Account Settings**.
+3. Copy the **Windows Publisher ID** field.
+4. Add the Publisher ID to your Signing Keys in your [PhoneGap Build Account Settings](https://build.phonegap.com/people/edit).
+5. Build your app using the newly added Windows Publisher ID, selected in a dropdown in your App details.
+6. Upload the resulting xap/appx file to the Windows Dev Center.
diff --git a/docs/4-phonegap-build/4-debugging/0-index.html.md b/docs/4-phonegap-build/4-debugging/0-index.html.md
new file mode 100755
index 000000000..f19b9ef67
--- /dev/null
+++ b/docs/4-phonegap-build/4-debugging/0-index.html.md
@@ -0,0 +1,56 @@
+---
+title: Debugging
+url: phonegap-build/debugging
+github_url: https://github.com/phonegap/phonegap-docs/blob/master/docs/4-phonegap-build/4-debugging/0-index.html.md
+layout: subpage
+---
+
+PhoneGap is an embedded webview, and both Android and iOS provide tools for debugging web applications running on mobile devices. These tools allow you to inspect HTML and CSS, as well as run and debug Javascript code.
+
+- [**iOS**: Safari Web Inspector](#safari-web-inspector)
+- [**Android**: Chrome Developer Tools](#chrome-developer-tools)
+- [**Windows Phone**: Visual Studio Web Debugging Tools](#visual-studio-debug-tools)
+- [Weinre Remote Debugger](weinre)
+- [Debugging Crashes and Native Exceptions](#crashes-and-native-exceptions)
+
+### Safari Web Inspector
+
+Steps:
+
+1. Connect your iOS device to your computer
+2. Launch Safari
+3. Launch your PhoneGap application on your iOS Device
+4. Open Safari's **Develop** menu, and you should see your iOS Device listed.
+5. Select your PhoneGap Webview listed under your device.
+
+More info can be found on the [Apple Developer Website](https://developer.apple.com/safari/tools/).
+
+### Chrome Developer Tools
+
+1. [Ensure Developer Options are enabled on your Android test device](http://developer.android.com/tools/device.html#developer-device-options).
+2. Launch Google Chrome Web Browser.
+3. Navigate to chrome://inspect in Chrome.
+4. Select your PhoneGap Application running on your device, and the Developer tools will launch.
+
+### Visual Studio Debug Tools
+
+[See the Microsoft Blog Post](https://blogs.msdn.microsoft.com/visualstudioalm/2014/04/04/diagnosing-mobile-website-issues-on-windows-phone-8-1-with-visual-studio/).
+
+### Crashes and Native Exceptions
+
+If your PhoneGap application is crashing or freezing, or if the Javascript Console shows no errors, you may need to use the Native SDKs in order to debug your application:
+
+#### iOS
+
+- [Debugging Deployed iOS Apps](https://developer.apple.com/library/ios/qa/qa1747/_index.html)
+- There may also be third party applications which allow you to view your **iOS Device Console**.
+
+#### Android
+
+- Download and install the Android SDK. Attach your device to your computer, and run `adb logcat` to view your device logs and watch for Exceptions.
+
+
+#### Windows Phone
+
+- See [Microsft Visual Studio](https://www.visualstudio.com/en-us/visual-studio-homepage-vs.aspx).
+
diff --git a/docs/4-phonegap-build/4-debugging/weinre.html.md b/docs/4-phonegap-build/4-debugging/weinre.html.md
new file mode 100755
index 000000000..ade98faea
--- /dev/null
+++ b/docs/4-phonegap-build/4-debugging/weinre.html.md
@@ -0,0 +1,141 @@
+---
+title: Weinre
+url: phonegap-build/debugging/weinre
+github_url: https://github.com/phonegap/phonegap-docs/blob/master/docs/4-phonegap-build/4-debugging/weinre.html.md
+layout: subpage
+---
+
+The open-source Weinre project is available for remotely debugging Javascript applications. A Weinre instance is hosted on PhoneGap Build, or you can run your own instance locally:
+
+- [Using PhoneGap Build's Debug Server](#phonegap-build-debug-server)
+- [Running your own local Debug Server](#running-a-local-debug-server)
+
+### PhoneGap Build Debug Server
+
+This section shows how to use standard Web Inspector tools available from the
+ PhoneGap Build site
+to debug PhoneGap apps while they are running on your device. See the PhoneGap Build section for details on how to provide the site with project code, and how to get the resulting compiled apps onto your device.
+
+To enable debugging from within the list of existing __Apps__, click on the name of the application to view its details. Click on the __Settings__ tab, then select the __Enable debugging__ check box:
+
+![](/images/phonegap-build/pgbuild_dbg_select.png)
+
+Once the debugging option is selected and you build the project, the __Debug__ button appears along with other options to update code and rebuild the project. When you preview the app on the device, perhaps by scanning the QR code as described in the PhoneGap Build section, pressing __Debug__ opens a web page that allows you to communicate with the app as it runs on the device:
+
+![](/images/phonegap-build/pgbuild_dbg_remote.png)
+
+Pressing the listed target gives you access to the app's internal state. The debugger may occasionally lose its connection if you pause the app or if the device goes into a standby mode. In that case, the __Remote__ tab may present a new target with which to re-establish the connection.
+
+Once connected, the __Elements__ tab allows you to view the app's full DOM tree as it executes:
+
+![](/images/phonegap-build/pgbuild_dbg_elements.png)
+
+You can use this interface to modify the application as it runs. For example, the default PhoneGap app generated by the CLI (see The Command-line Interface) presents a slowly blinking status message beneath the icon:
+
+![](/images/phonegap-build/pgbuild_dbg_blink.png)
+
+Selecting various elements from the DOM tree in the debug view highlights them on the device if visible, which may help you locate the relevant code:
+
+
+
+The sidebar on the right allows you to view information about CSS properties applied to each element and the selectors that specify them. If you double-click on the `class` attribute and delete the `blink` text, the message stops blinking on the device, and the `.blink` selector disappears from the sidebar's __Matched CSS Rules__:
+
+ .blink {
+ -webkit-animation: fade;
+ -webkit-animation-delay: initial;
+ -webkit-animation-direction: initial;
+ -webkit-animation-duration: 3000ms;
+ -webkit-animation-fill-mode: initial;
+ -webkit-animation-iteration-count: infinite;
+ -webkit-animation-name: fade;
+ -webkit-animation-timing-function: initial;
+ }
+
+To see the same change without editing the DOM, select the __Console__ tab and type a JavaScript call directly onto the command line. This example selects the element whose `id` is `deviceready` and turns on or off its `blink` class:
+
+ document.querySelector('#deviceready').classList.toggle('blink')
+
+The method's return value displays within the console. Typing the name of _any_ object allows you to view its evaluated contents:
+
+![](/images/phonegap-build/pgbuild_dbg_toggle.png)
+
+The browser engine's error messages and results of `console.log()` calls also appear on the console.
+
+Navigating back to the __Elements__ view displays the results of the change, but note there may be a delay, and you may need to re-select the DOM node to view its current state.
+
+The Web Inspector offers several other useful features:
+
+* The __Network__ tab lists details on network requests the app makes
+ while executing, along with a timeline interface to visualize a
+ progression of network interactions.
+
+* The __Timeline__ tab similarly visualizes load times for the app's
+ component resources.
+
+* The __Resources__ tab allows you to inspect cookies and the contents
+ of various client-side databases (`localStorage`, `sessionStorage`,
+ Web SQL) set by the Storage API. Note that this view also allows
+ you to inspect the HTML5 Application Cache, which allows you install
+ an app persistently from a set of network resources. However, this
+ feature is less appropriate for PhoneGap apps, which are already
+ delivered to the device as part of an installed native package.
+
+Despite slight differences in how Web Inspector features appear in different WebKit-based browser environments, the documentation for
+
Google Chrome
+and
+
Apple Safari
+provides a good overview.
+
+
+### Running a Local Debug Server
+
+PhoneGap Build allows users to use their own debug server with the Build service.
+
+Build uses a tool called Weinre to enable remote debugging of mobile apps.
+
+This guide provides information on setting up your own local server.
+
+The pre-requisites for running Weinre are that you need to have `npm` installed. Once you've installed Weinre you will only be able to use the local server within your own network unless you plan to host it on a publicly accessible location. This will require additional setup that is outside the scope of this guide.
+
+#### Set Up Weinre
+
+Once you have `npm` installed, obtaining and installing Weinre is as simple as running the following command in a terminal.
+
+ sudo npm -g install weinre
+
+That's it! Now you're ready to run your very own Weinre instance.
+
+#### Start Weinre
+
+To start your new local Weinre instance run the following command:
+
+ weinre
+
+You will now see output like the following:
+
+ Hardeeps-MacBook-Air:~ hardeep$ weinre
+ 2013-07-01T20:03:34.890Z weinre: starting server at `http://localhost:8080`
+
+Weinre is now up and running! If you are running this behind a router that uses NAT you will need to find your IP address. You will use this IP when specifying your configuration with Build.
+
+#### Using a Local Weinre Instance with Build
+
+Obtain the ip address of your machine running Weinre. This can be done on Windows by running `ipconfig` or on OSX/Linux by running `ifconfig`.
+
+Now include a reference to the Weinre debug script on your debug server, like so:
+
+
+
+**Make sure your remove this before publishing your app!**
+
+#### Common Issues
+
+__I can't connect to my Local Server__
+
+First of all make sure that your server is running. Chances are if you're using the default configuration you can visit `http://localhost:8080` and it should be responding.
+
+If this works it's most likely the IP address you're providing to Build; please verify that it is correct. A google search such as `windows [version] find ip address` or `OSX [version] find ip address` will help you find articles on getting the right ip.
+
+Assuming that you're using a router running NAT verify that you can visit it within your network by visiting `http://[ip address]:8080`.
+
+
diff --git a/docs/4-phonegap-build/5-developer-api/0-index.html.md b/docs/4-phonegap-build/5-developer-api/0-index.html.md
new file mode 100755
index 000000000..d4ec66842
--- /dev/null
+++ b/docs/4-phonegap-build/5-developer-api/0-index.html.md
@@ -0,0 +1,58 @@
+---
+title: Developer API
+url: phonegap-build/developer-api
+github_url: https://github.com/phonegap/phonegap-docs/blob/master/docs/4-phonegap-build/5-developer-api/0-index.html.md
+layout: subpage
+---
+
+
+The PhoneGap Build API allows applications to use the PhoneGap Build web service to create, build, update, and download PhoneGap apps. It integrates easily into IDEs, shell scripts, app builders, and elsewhere.
+
+The core sections discussed in this documentation article are:
+
+* [Authentication Methods](oauth)
+* [The Read API](read)
+* [The Write API](write)
+
+Here are some additional notes on using the API.
+
+- [JSON](#JSON)
+- [JSONP](#JSONP)
+- [HATEOAS](#HATEOAS)
+
+### JSON
+
+All successful requests return either a JSON-encoded string or a binary file. All requests that fail return a JSON-encoded string in the following form, with an appropriate status code:
+
+ {
+ "error":"some error message"
+ }
+
+When using the API, check each returned status code; if it's not 200, check the error field on the parsed response, for example:
+
+ if (res.status != 200)
+ console.log(JSON.parse(res.body).error)
+
+As is standard in HTTP, a _4xx_ status indicates an error with the request, while a _5xx_ status indicates an server error. Contact
+
PhoneGap's support forums
+if you get a 500 error, or an unexpected 400 error.
+
+### JSONP
+
+JSONP access is available for PhoneGap Build developers: just add a `callback` parameter to your requests, and the JSONP response body is wrapped in that function:
+
+ $ curl https://build.phonegap.com/api/v1/me?auth_token=ASTRINGTOKEN&callback=exec
+ exec({
+ "username":"alunny",
+ "email":"andrew.lunny@nitobi.com"
+ })
+
+This allows you to access the PhoneGap Build API using `