cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CB-13930) Remove deprecated platforms and plugins from docs
Date Thu, 01 Mar 2018 18:11:01 GMT

    [ https://issues.apache.org/jira/browse/CB-13930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16382407#comment-16382407 ] 

ASF GitHub Bot commented on CB-13930:
-------------------------------------

stevengill closed pull request #796: CB-13930: removed deprecated platforms and plugins. Removed old apach…
URL: https://github.com/apache/cordova-docs/pull/796
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/www/_data/contribute-repo-links.yml b/www/_data/contribute-repo-links.yml
index 7c40be050..9183ee266 100644
--- a/www/_data/contribute-repo-links.yml
+++ b/www/_data/contribute-repo-links.yml
@@ -1,177 +1,102 @@
 -   title: Platforms
     projects:
-    -   project: Amazon Fire OS
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-amazon-fireos.git;a=summary
-        mirror: https://github.com/apache/cordova-amazon-fireos
 
     -   project: Android
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;a=summary
         mirror: https://github.com/apache/cordova-android
 
-    -   project: Bada
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-bada.git;a=summary
-        mirror: https://github.com/apache/cordova-bada
-
-    -   project: Blackberry
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-blackberry.git;a=summary
-        mirror: https://github.com/apache/cordova-blackberry
-
-    -   project: FirefoxOS
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-firefoxos.git;a=summary
-        mirror: https://github.com/apache/cordova-firefoxos
-
     -   project: iOS
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=summary
         mirror: https://github.com/apache/cordova-ios
 
     -   project: Mac OS X
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-osx.git;a=summary
         mirror: https://github.com/apache/cordova-osx
 
-    -   project: Qt
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-qt.git;a=summary
-        mirror: https://github.com/apache/cordova-qt
-
-    -   project: Tizen
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-tizen.git;a=summary
-        mirror: https://github.com/apache/cordova-tizen
-
-    -   project: Ubuntu
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-ubuntu.git;a=summary
-        mirror: https://github.com/apache/cordova-ubuntu
-
-    -   project: WebOS
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-webos.git;a=summary
-        mirror: https://github.com/apache/cordova-webos
-
     -   project: Windows (desktop)
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git;a=summary
         mirror: https://github.com/apache/cordova-windows
 
-    -   project: Windows Phone 7
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-wp7.git;a=summary
-        mirror: https://github.com/apache/cordova-wp7
-
-    -   project: Windows Phone 8
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-wp8.git;a=summary
-        mirror: https://github.com/apache/cordova-wp8
-
     -   project: Browser
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-browser.git;a=summary
         mirror: https://github.com/apache/cordova-browser
 
 -   title: Plugins
     projects:
     -   project: Battery Status
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-battery-status.git;a=summary
         mirror: https://github.com/apache/cordova-plugin-battery-status
 
     -   project: Camera
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-camera.git;a=summary
         mirror: https://github.com/apache/cordova-plugin-camera
 
     -   project: Device
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-device.git;a=summary
         mirror: https://github.com/apache/cordova-plugin-device
 
     -   project: Dialogs
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-dialogs.git;a=summary
         mirror: https://github.com/apache/cordova-plugin-dialogs
 
     -   project: File
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-file.git;a=summary
         mirror: https://github.com/apache/cordova-plugin-file
 
     -   project: Geolocation
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-geolocation.git;a=summary
         mirror: https://github.com/apache/cordova-plugin-geolocation
 
     -   project: In-App Browser
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-inappbrowser.git;a=summary
         mirror: https://github.com/apache/cordova-plugin-inappbrowser
 
     -   project: Media
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-media.git;a=summary
         mirror: https://github.com/apache/cordova-plugin-media
 
     -   project: Media Capture
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-media-capture.git;a=summary
         mirror: https://github.com/apache/cordova-plugin-media-capture
 
     -   project: Network Information
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-network-information.git;a=summary
         mirror: https://github.com/apache/cordova-plugin-network-information
 
+    -   project: Screen Orientation
+        mirror: https://github.com/apache/cordova-plugin-screen-orientation
+
     -   project: Splashscreen
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-splashscreen.git;a=summary
         mirror: https://github.com/apache/cordova-plugin-splashscreen
 
     -   project: Statusbar
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-statusbar.git;a=summary
         mirror: https://github.com/apache/cordova-plugin-statusbar
 
     -   project: Vibration
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-vibration.git;a=summary
         mirror: https://github.com/apache/cordova-plugin-vibration
 
 -   title: Other
     projects:
     -   project: Cordova Docs
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=summary
         mirror: https://github.com/apache/cordova-docs
 
     -   project: Cordova JS (JavaScript API)
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-js.git;a=summary
         mirror: https://github.com/apache/cordova-js
 
     -   project: Cordova CLI
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;a=summary
         mirror: https://github.com/apache/cordova-cli
 
     -   project: Cordova Plugman (Plugin Manager)
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;a=summary
         mirror: https://github.com/apache/cordova-plugman
 
     -   project: Cordova Lib (Common Code)
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;a=summary
         mirror: https://github.com/apache/cordova-lib
 
+    -   project: Cordova Common
+        mirror: https://github.com/apache/cordova-common
+
+    -   project: Cordova Serve
+        mirror: https://github.com/apache/cordova-serve
+
+    -   project: Cordova Create
+        mirror: https://github.com/apache/cordova-create
+
+    -   project: Cordova Fetch
+        mirror: https://github.com/apache/cordova-fetch
+
     -   project: Cordova Mobile Spec (Test Suite)
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-mobile-spec.git;a=summary
         mirror: https://github.com/apache/cordova-mobile-spec
 
-    -   project: Cordova Medic (Test Automation)
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-medic.git;a=summary
-        mirror: https://github.com/apache/cordova-medic
-
     -   project: Cordova Paramedic (Test Automation)
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-paramedic.git;a=summary
         mirror: https://github.com/apache/cordova-paramedic
 
-    -   project: Weinre (Web Inspector Remote)
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-weinre.git;a=summary
-        mirror: https://github.com/apache/cordova-weinre
-
-    -   project: Cordova App Harness
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-app-harness.git;a=summary
-        mirror: https://github.com/apache/cordova-app-harness
-
     -   project: Cordova Hello World (Sample App)
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-app-hello-world.git;a=summary
         mirror: https://github.com/apache/cordova-app-hello-world
 
     -   project: Cordova Coho (Release Tool)
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;a=summary
         mirror: https://github.com/apache/cordova-coho
-
-    -   project: Cordova Registry Web (Plugin Registry UI)
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-registry-web.git;a=summary
-        mirror: https://github.com/apache/cordova-registry-web
-
-    -   project: Cordova Registry (Plugin Registry App)
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-registry.git;a=summary
-        mirror: https://github.com/apache/cordova-registry
-
-    -   project: Cordova Labs (Experimental Content)
-        apache: https://git-wip-us.apache.org/repos/asf?p=cordova-labs.git;a=summary
-        mirror: https://github.com/apache/cordova-labs
diff --git a/www/_data/fetched-files.yml b/www/_data/fetched-files.yml
index afd935700..e0df449f0 100644
--- a/www/_data/fetched-files.yml
+++ b/www/_data/fetched-files.yml
@@ -29,20 +29,6 @@
         commit: "master"
     dest:
         path: "reference/cordova-plugin-camera/index.md"
--
-    src:
-        repoName: "apache/cordova-plugin-console"
-        packageName: "cordova-plugin-console"
-        commit: "master"
-    dest:
-        path: "reference/cordova-plugin-console/index.md"
--
-    src:
-        repoName: "apache/cordova-plugin-contacts"
-        packageName: "cordova-plugin-contacts"
-        commit: "master"
-    dest:
-        path: "reference/cordova-plugin-contacts/index.md"
 -
     src:
         repoName: "apache/cordova-plugin-device"
@@ -50,20 +36,6 @@
         commit: "master"
     dest:
         path: "reference/cordova-plugin-device/index.md"
--
-    src:
-        repoName: "apache/cordova-plugin-device-motion"
-        packageName: "cordova-plugin-device-motion"
-        commit: "master"
-    dest:
-        path: "reference/cordova-plugin-device-motion/index.md"
--
-    src:
-        repoName: "apache/cordova-plugin-device-orientation"
-        packageName: "cordova-plugin-device-orientation"
-        commit: "master"
-    dest:
-        path: "reference/cordova-plugin-device-orientation/index.md"
 -
     src:
         repoName: "apache/cordova-plugin-dialogs"
@@ -78,13 +50,6 @@
         commit: "master"
     dest:
         path: "reference/cordova-plugin-file/index.md"
--
-    src:
-        repoName: "apache/cordova-plugin-file-transfer"
-        packageName: "cordova-plugin-file-transfer"
-        commit: "master"
-    dest:
-        path: "reference/cordova-plugin-file-transfer/index.md"
 -
     src:
         repoName: "apache/cordova-plugin-geolocation"
@@ -92,13 +57,6 @@
         commit: "master"
     dest:
         path: "reference/cordova-plugin-geolocation/index.md"
--
-    src:
-        repoName: "apache/cordova-plugin-globalization"
-        packageName: "cordova-plugin-globalization"
-        commit: "master"
-    dest:
-        path: "reference/cordova-plugin-globalization/index.md"
 -
     src:
         repoName: "apache/cordova-plugin-inappbrowser"
@@ -157,8 +115,8 @@
         path: "reference/cordova-plugin-whitelist/index.md"
 -
     src:
-        repoName: "apache/cordova-plugin-legacy-whitelist"
-        packageName: "cordova-plugin-legacy-whitelist"
+        repoName: "apache/cordova-plugin-screen-orientation"
+        packageName: "cordova-plugin-screen-orientation"
         commit: "master"
     dest:
-        path: "reference/cordova-plugin-legacy-whitelist/index.md"
+        path: "reference/cordova-plugin-screen-orientation/index.md"
diff --git a/www/_data/redirects.yml b/www/_data/redirects.yml
index 83cd42416..c85c4741e 100644
--- a/www/_data/redirects.yml
+++ b/www/_data/redirects.yml
@@ -40,6 +40,46 @@ docs:
     "dev/cordova/plugins/pluginapis.html": "deprecated.html"
     "latest/cordova/plugins/pluginapis.html": "deprecated.html"
 
+    # Removing deprecated platforms and plugins
+    "dev/guide/platforms/blackberry10/home.html": "deprecated.html"
+    "latest/guide/platforms/blackberry10/home.html": "deprecated.html"
+    "dev/guide/platforms/blackberry10/index.html": "deprecated.html"
+    "latest/guide/platforms/blackberry10/index.html": "deprecated.html"
+    "dev/guide/platforms/blackberry10/tools.html": "deprecated.html"
+    "latest/guide/platforms/blackberry10/tools.html": "deprecated.html"
+    "dev/guide/platforms/blackberry10/config.html": "deprecated.html"
+    "latest/guide/platforms/blackberry10/config.html": "deprecated.html"
+    "dev/guide/platforms/blackberry10/plugin.html": "deprecated.html"
+    "latest/guide/platforms/blackberry10/plugin.html": "deprecated.html"
+    "dev/guide/platforms/blackberry10/upgrade.html": "deprecated.html"
+    "latest/guide/platforms/blackberry10/upgrade.html": "deprecated.html"
+    "dev/guide/platforms/blackberry/upgrade.html": "deprecated.html"
+    "latest/guide/platforms/blackberry/upgrade.html": "deprecated.html"
+    "dev/guide/platforms/ubuntu/index.html": "deprecated.html"
+    "latest/guide/platforms/ubuntu/index.html": "deprecated.html"
+    "dev/guide/platforms/wp8/home.html": "deprecated.html"
+    "latest/guide/platforms/wp8/home.html": "deprecated.html"
+    "dev/guide/platforms/wp8/index.html": "deprecated.html"
+    "latest/guide/platforms/wp8/index.html": "deprecated.html"
+    "dev/guide/platforms/wp8/plugin.html": "deprecated.html"
+    "latest/guide/platforms/wp8/plugin.html": "deprecated.html"
+    "dev/guide/platforms/wp8/upgrade.html": "deprecated.html"
+    "latest/guide/platforms/wp8/upgrade.html": "deprecated.html"
+    "dev/guide/platforms/wp8/parallels.html": "deprecated.html"
+    "latest/guide/platforms/wp8/parallels.html": "deprecated.html"
+    "dev/guide/platforms/wp8/vmware.html": "deprecated.html"
+    "latest/guide/platforms/wp8/vmware.html": "deprecated.html"
+    "dev/guide/platforms/wp8/webview.html": "deprecated.html"
+    "latest/guide/platforms/wp8/webview.html": "deprecated.html"
+
+    "latest/reference/cordova-plugin-contacts/index.html": "deprecated.html"
+    "latest/reference/cordova-plugin-console/index.html": "deprecated.html"
+    "latest/reference/cordova-plugin-device-motion/index.html": "deprecated.html"
+    "latest/reference/cordova-plugin-device-orientation/index.html": "deprecated.html"
+    "latest/reference/cordova-plugin-file-transfer/index.html": "deprecated.html"
+    "latest/reference/cordova-plugin-globalization/index.html": "deprecated.html"
+    "latest/reference/cordova-plugin-legacy-whitelist/index.html": "deprecated.html"
+
     # Old plugin API docs need to be redirected to latest where we pull in the READMEs
     "latest/cordova/accelerometer/acceleration/acceleration.html": "latest/reference/cordova-plugin-device-motion/index.html"
     "latest/cordova/accelerometer/accelerometer.clearWatch.html": "latest/reference/cordova-plugin-device-motion/index.html"
diff --git a/www/_data/toc/en_dev-src.yml b/www/_data/toc/en_dev-src.yml
index 15d555e02..2d9a4d8a6 100644
--- a/www/_data/toc/en_dev-src.yml
+++ b/www/_data/toc/en_dev-src.yml
@@ -12,12 +12,9 @@
             name: Develop for platforms
             children:
                 - url: guide/platforms/android/index.html
-                - url: guide/platforms/blackberry10/home.html
                 - url: guide/platforms/ios/index.html
                 - url: guide/platforms/osx/index.html
-                - url: guide/platforms/ubuntu/index.html
                 - url: guide/platforms/win8/index.html
-                - url: guide/platforms/wp8/home.html
         - url: platform_plugin_versioning_ref/index.html
         - url: config_ref/images.html
         - url: cordova/storage/storage.html
@@ -32,10 +29,8 @@
             name: Develop for platforms
             children:
                 - url: guide/platforms/android/plugin.html
-                - url: guide/platforms/blackberry10/plugin.html
                 - url: guide/platforms/ios/plugin.html
                 - url: guide/platforms/win8/plugin.html
-                - url: guide/platforms/wp8/plugin.html
         - url: plugin_ref/plugman.html
 -
     name: Advanced Topics
@@ -55,22 +50,16 @@
             children:
                 - url: reference/cordova-plugin-battery-status/index.html
                 - url: reference/cordova-plugin-camera/index.html
-                - url: reference/cordova-plugin-console/index.html
-                - url: reference/cordova-plugin-contacts/index.html
                 - url: reference/cordova-plugin-device/index.html
-                - url: reference/cordova-plugin-device-motion/index.html
-                - url: reference/cordova-plugin-device-orientation/index.html
                 - url: reference/cordova-plugin-dialogs/index.html
                 - url: reference/cordova-plugin-file/index.html
-                - url: reference/cordova-plugin-file-transfer/index.html
                 - url: reference/cordova-plugin-geolocation/index.html
-                - url: reference/cordova-plugin-globalization/index.html
                 - url: reference/cordova-plugin-inappbrowser/index.html
                 - url: reference/cordova-plugin-media/index.html
                 - url: reference/cordova-plugin-media-capture/index.html
                 - url: reference/cordova-plugin-network-information/index.html
+                - url: reference/cordova-plugin-screen-orientation/index.html
                 - url: reference/cordova-plugin-splashscreen/index.html
-                - url: reference/cordova-plugin-vibration/index.html
                 - url: reference/cordova-plugin-statusbar/index.html
+                - url: reference/cordova-plugin-vibration/index.html
                 - url: reference/cordova-plugin-whitelist/index.html
-                - url: reference/cordova-plugin-legacy-whitelist/index.html
diff --git a/www/contribute/index.html b/www/contribute/index.html
index 6aa4484c5..fb0383fd5 100644
--- a/www/contribute/index.html
+++ b/www/contribute/index.html
@@ -69,9 +69,6 @@ <h2>{{ projectType.title }}</h2>
                         <div class="link-box">
                             <a class="link-github" target="_blank" href="{{ project.mirror }}"></a>
                         </div>
-                        <div class="link-box">
-                            <a class="link-apache" target="_blank" href="{{ project.apache }}"></a>
-                        </div>
                     </div>
                 </div>
             </li>
diff --git a/www/docs/en/dev/config_ref/images.md b/www/docs/en/dev/config_ref/images.md
index 68dbf50e2..5520f9d7a 100644
--- a/www/docs/en/dev/config_ref/images.md
+++ b/www/docs/en/dev/config_ref/images.md
@@ -76,16 +76,6 @@ different screen resolutions.
 - [Android icon guide](https://www.google.com/design/spec/style/icons.html)
 - [Android - Supporting multiple screens](http://developer.android.com/guide/practices/screens_support.html)
 
-##BlackBerry10
-```xml
-    <platform name="blackberry10">
-        <icon src="res/bb10/icon-86.png" />
-        <icon src="res/bb10/icon-150.png" />
-    </platform>
-```
-###See Also
-- [BlackBerry's documentation][blackberry_icon] for targeting multiple sizes and locales.
-
 ##Browser
 Icons are not applicable to the Browser platform.
 
@@ -190,14 +180,4 @@ Although it is not recommended, it is also possible to define icons using the `w
 - [Windows 10 platform guidelines for icons](https://msdn.microsoft.com/en-us/library/windows/apps/mt412102.aspx).
 - [Windows 8.1 tiles and icons sizes](https://msdn.microsoft.com/en-us/library/windows/apps/xaml/hh781198.aspx)
 
-##Windows Phone 8 (WP8 Platform)
-```xml
-    <platform name="wp8">
-        <icon src="res/wp/ApplicationIcon.png" width="99" height="99" />
-        <!-- tile image -->
-        <icon src="res/wp/Background.png" width="159" height="159" />
-    </platform>
-```
-
-[blackberry_icon]: http://developer.blackberry.com/html5/documentation/icon_element.html
 [splashscreen_plugin]: ../reference/cordova-plugin-splashscreen/
diff --git a/www/docs/en/dev/config_ref/index.md b/www/docs/en/dev/config_ref/index.md
index 52f2b5f04..9a15c91c9 100644
--- a/www/docs/en/dev/config_ref/index.md
+++ b/www/docs/en/dev/config_ref/index.md
@@ -47,7 +47,6 @@ For example:
 
 ```
 app/platforms/ios/AppName/config.xml
-app/platforms/blackberry10/www/config.xml
 app/platforms/android/res/xml/config.xml
 ```
 
@@ -296,9 +295,8 @@ android-maxSdkVersion(integer) <br/> ==Android== | *Default: Not Specified* <br/
 android-minSdkVersion(integer) <br/> ==Android== | *Default: Dependent on cordova-android Version* <br/>  Sets the `minSdkVersion` attribute of the `<uses-sdk>` tag in the project's `AndroidManifest.xml` (see [here][uses-sdk]).
 android-targetSdkVersion(integer) <br/> ==Android== | *Default: Dependent on cordova-android Version* <br/>  Sets the `targetSdkVersion` attribute of the `<uses-sdk>` tag in the project's `AndroidManifest.xml` (see [here][uses-sdk]).
 AppendUserAgent(string) <br/> ==Android== ==iOS== | If set, the value will append to the end of old UserAgent of webview. When using with OverrideUserAgent, this value will be ignored.
-BackgroundColor(string) <br/> ==Android== ==iOS== ==BlackBerry== ==Windows== | Sets the app's background color. Supports a four-byte hex value, with the first byte representing the alpha channel, and standard RGB values for the following three bytes. <br/> For Windows, the alpha channel is ignored. <br/> __Note__: `transparent` value will set the application tile background to the accent color on Windows.
+BackgroundColor(string) <br/> ==Android== ==iOS== ==Windows== | Sets the app's background color. Supports a four-byte hex value, with the first byte representing the alpha channel, and standard RGB values for the following three bytes. <br/> For Windows, the alpha channel is ignored. <br/> __Note__: `transparent` value will set the application tile background to the accent color on Windows.
 BackupWebStorage(string) <br/> ==iOS== | *Default: cloud* <br/> Allowed values: none, local, cloud. <br/>   Set to cloud to allow web storage data to backup via iCloud. Set to local to allow only local backups via iTunes sync. Set to none prevent web storage backups.
-ChildBrowser(string) <br/> ==BlackBerry== | *Default: enable* <br/>  Disables child browser windows. By default, apps launch a secondary browser window to display resources accessed via window.open() or by specifying a _blank anchor target. Specify disable to override this default behavior.
 CordovaWebViewEngine(string) <br/> ==iOS== | *Default: CDVUIWebViewEngine* <br/>  This sets the WebView engine plugin to be used to render the host app. The plugin must conform to the CDVWebViewEngineProtocol protocol. The 'value' here should match the 'feature' name of the WebView engine plugin that is installed. This preference usually would be set by the WebView engine plugin that is installed, automatically.
 CordovaDefaultWebViewEngine(string) <br/> ==iOS== | *Default: CDVUIWebViewEngine* <br/> As the previous setting, CordovaWebViewEngine, this enables you to override the default fallback WebView with a different plugin. The default WebView uses a private plugin, CDVUIWebViewEngine. You can override this if you need to use a public plugin instead. A use case for this setting is where you need to use something other than the default CDVUIWebViewEngine to render the host app. If CordovaDefaultWebViewEngine and CordovaWebViewEngine is set, CordovaWebViewEngine will be chosen to render the host app for devices running iOS9 and above, while CordovaDefaultWebViewEngine will be the fallback for iOS8. The plugin must conform to the CDVWebViewEngineProtocol protocol. The 'value' here should match the 'feature' name of the WebView engine plugin that is installed.
 DefaultVolumeStream(string) <br/> ==Android== | *Default: default* <br/>  Added in cordova-android 3.7.0, This preference sets which volume the hardware volume buttons link to. By default this is "call" for phones and "media" for tablets. Set this to "media" to have your app's volume buttons always change the media volume. Note that when using Cordova's media plugin, the volume buttons will dynamically change to controlling the media volume when any Media objects are active.
@@ -310,7 +308,6 @@ ErrorUrl(string) <br/> ==iOS== | If set, will display the referenced local page
 ForegroundText(string) <br/> ==Windows== | *Default: "light"* <br/>   Works for Windows 8.1 projects only. Allowed values: "light", "dark". Set to "dark" if you use the `BackgroundColor="white"` or another light color to avoid Windows Store submissions errors.
 FullScreen(boolean) <br/> ==Android== | *Default: false* <br/>  Allows you to hide the status bar at the top of the screen. <br/> __Note__: Recommended platform-agnostic way to achieve this is to use the [StatusBar plugin][statusbar_plugin].
 GapBetweenPages(float) <br/> ==iOS== | *Default: 0* <br/>  The size of the gap, in points, between pages.
-HideKeyboardFormAccessoryBar(boolean) <br/> ==BlackBerry== | *Default: false* <br/>  Set to true to hide the additional toolbar that appears above the keyboard, helping users navigate from one form input to another.
 HideMousePointer(integer) <br/> ==OS X== | *Default: -1* <br/> **(OS X 4.0.0+)** Sets the timeout for hiding the mouse pointer. Set to 0 for immediate, set to -1 for never.
 InAppBrowserStorageEnabled (boolean) <br/> ==Android== | *Default: true* <br/>  Controls whether pages opened within an InAppBrowser can access the same localStorage and WebSQL storage as pages opened with the default browser.
 KeepRunning(boolean) <br/> ==Android== | *Default: true* <br/>  Determines whether the application stays running in the background even after a [pause](../../../cordova/events/events.pause.html) event fires. Setting this to false does not kill the app after a [pause](../../../cordova/events/events.pause.html) event, but simply halts execution of code within the cordova webview while the app is in the background.
@@ -327,7 +324,6 @@ OverrideUserAgent(string) <br/> ==Android== | If set, the value will replace the
 PageLength(float) <br/> ==iOS== | *Default: 0* <br/>  The size of each page, in points, in the direction that the pages flow. When PaginationMode is right to left or left to right, this property represents the width of each page. When PaginationMode is topToBottom or bottomToTop, this property represents the height of each page. The default value is 0, which means the layout uses the size of the viewport to determine the dimensions of the page.
 PaginationBreakingMode(string) <br/> ==iOS== | *Default: page* <br/> Allowed values: page, column <br/>  Valid values are page and column.The manner in which column- or page-breaking occurs. This property determines whether certain CSS properties regarding column- and page-breaking are honored or ignored. When this property is set to column, the content respects the CSS properties related to column-breaking in place of page-breaking.
 PaginationMode(string) <br/> ==iOS== | *Default: unpaginated* <br/> Allowed values: unpaginated, leftToRight, topToBottom, bottomToTop, rightToLeft <br/>  This property determines whether content in the web view is broken up into pages that fill the view one screen at a time,or shown as one long scrolling view. If set to a paginated form, this property toggles a paginated layout on the content, causing the web view to use the values of PageLength and GapBetweenPages to relayout its content.
-PopupBlocker(string) <br/> ==BlackBerry== | *Default: enable* <br/>  Enables the popup blocker, which prevents calls to window.open(). By default, popups display in a child browser window. Setting the preference to enable prevents it from displaying at all.
 SetFullscreen(boolean) <br/> ==Android== | *Default: false* <br/>  Same as the Fullscreen parameter in the global configuration of this xml file. This Android-specific element is deprecated in favor of the global Fullscreen element, and will be removed in a future version.
 ShowTitle(boolean) <br/> ==Android== | *Default: false* <br/>  Show the title at the top of the screen.
 SplashScreenBackgroundColor <br/> ==Windows== | *Default: #464646* <br/>  Sets the splashscreen background color. Supports a CSS color name or a four-byte hex value, with the first byte representing the alpha channel, and standard RGB values for the following three bytes. <br/> The alpha channel is ignored although `transparent` value will cause black/white background color in case of Dark/Light theme accordingly.
@@ -337,7 +333,6 @@ SuppressesLongPressGesture(boolean) <br/> ==iOS== | *Default: false* <br/>  Set
 TopActivityIndicator(string) <br/> ==iOS== | *Default: gray* <br/> Allowed values: whiteLarge, white, gray. <br/>   <br/> Controls the appearance of the small spinning icon in the status bar that indicates significant processor activity.
 uap-target-min-version(string) <br/> ==Windows== | This property sets the MinTargetVersion for the Windows UAP. If not specified, this is set to the initial release version 10.0.10240.0 <br/> **Note:** This preference is set in the jsproj file and not in the appxmanifest file. So users with OS version lower than this value would not be able to run the app.
 UIWebViewDecelerationSpeed(string) <br/> ==iOS== | *Default: normal* <br/> Allowed values: normal, fast <br/>  This property controls the deceleration speed of momentum scrolling. normal is the default speed for most native apps, and fast is the default for Mobile Safari.
-WebSecurity(string) <br/> ==BlackBerry== | *Default: enable* <br/>  Set to disable to override web security settings, allowing access to remote content from unknown sources. This preference is intended as a development convenience only, so remove it before packaging the app for distribution. For the released app, all URIs should be known and whitelisted using the <access> element, described in the Domain Whitelist Guide.
 WindowSize(string) <br/> ==OS X== | *Default: auto* <br/> **(OS X 4.0.0+)** Sets the size of the application window. <br/> Accepts the format `WxH` for a specific width and height or the special values `auto` and `fullscreen`. The latter will open a borderless window spanning the entire desktop area. Please note, that this is different from the _normal_ OS X fullscreen mode, which would never span multiple displays. <br/> **Note**: The global cordova `fullscreen` preference has no effect in OS X.
 WindowsDefaultUriPrefix(string) <br/> ==Windows== | Allowed values: `ms-appx://`, `ms-appx-web://` <br/>  Identifies whether you want your app to target the local context or remote context as its startup URI. When building for Windows 10, the default is the remote context (`ms-appx-web://`). <br/> In order to have a local-mode application that is not impacted by Remote Mode capability restrictions, you must set this preference to `ms-appx://` and not declare any `<access>` elements with remote URIs. The local mode is the default for Windows 8.1
 WindowsStoreDisplayName(string) <br/> ==Windows== | A friendly name for the publisher that can be displayed to users.
@@ -406,11 +401,6 @@ Examples:
 <preference name="WindowsToastCapable" value="true" />
 <preference name="uap-target-min-version" value="10.0.10586.0" />
 
-<!-- BlackBerry only preferences -->
-<preference name="ChildBrowser" value="disable"/>
-<preference name="PopupBlocker" value="enable"/>
-<preference name="WebSecurity" value="disable"/>
-
 <!-- OS X only preferences -->
 <preference name="HideMousePointer" value="5"/>
 <preference name="OSXLocalStoragePath" value="~/.myapp/database"/>
diff --git a/www/docs/en/dev/cordova/events/events.md b/www/docs/en/dev/cordova/events/events.md
index 6af0e176c..07b2f197c 100644
--- a/www/docs/en/dev/cordova/events/events.md
+++ b/www/docs/en/dev/cordova/events/events.md
@@ -88,9 +88,7 @@ The following table lists the cordova events and the supported platforms:
     <tr>
         <th>Supported Platforms/<br/>Events</td>
         <th>android</th>
-        <th>blackberry10</th>
         <th>ios</th>
-        <th>Windows Phone 8</th>
         <th>Windows</th>
     </tr>
 </thead>
@@ -99,99 +97,77 @@ The following table lists the cordova events and the supported platforms:
     <tr>
         <th><a href="#deviceready">deviceready</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="y"></td>
-        <td data-col="winphone8"  class="y"></td>
         <td data-col="win"       class="y"></td>
     </tr>
 
     <tr>
         <th><a href="#pause">pause</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="y"></td>
-        <td data-col="winphone8"  class="y"></td>
         <td data-col="win"       class="y"></td>
     </tr>
 
     <tr>
         <th><a href="#resume">resume</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="y"></td>
-        <td data-col="winphone8"  class="y"></td>
         <td data-col="win"       class="y"></td>
     </tr>
 
     <tr>
         <th><a href="#backbutton">backbutton</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="n"></td>
-        <td data-col="winphone8"  class="n"></td>
         <td data-col="win"       class="y"></td>
     </tr>
 
     <tr>
         <th><a href="#menubutton">menubutton</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="n"></td>
-        <td data-col="winphone8"  class="n"></td>
         <td data-col="win"       class="n"></td>
     </tr>
 
     <tr>
         <th><a href="#searchbutton">searchbutton</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="n"></td>
         <td data-col="ios"        class="n"></td>
-        <td data-col="winphone8"  class="n"></td>
         <td data-col="win"       class="n"></td>
     </tr>
 
     <tr>
         <th><a href="#startcallbutton">startcallbutton</a></th>
         <td data-col="android"    class="n"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="n"></td>
-        <td data-col="winphone8"  class="n"></td>
         <td data-col="win"       class="n"></td>
     </tr>
 
     <tr>
         <th><a href="#endcallbutton">endcallbutton</a></th>
         <td data-col="android"    class="n"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="n"></td>
-        <td data-col="winphone8"  class="n"></td>
         <td data-col="win"       class="n"></td>
     </tr>
 
     <tr>
         <th><a href="#volumedownbutton">volumedownbutton</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="n"></td>
-        <td data-col="winphone8"  class="n"></td>
         <td data-col="win"       class="n"></td>
     </tr>
 
     <tr>
         <th><a href="#volumeupbutton">volumeupbutton</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="n"></td>
-        <td data-col="winphone8"  class="n"></td>
         <td data-col="win"       class="n"></td>
     </tr>
 
     <tr>
         <th><a href="#activated">activated</a></th>
         <td data-col="android"    class="n"></td>
-        <td data-col="blackberry10" class="n"></td>
         <td data-col="ios"        class="n"></td>
-        <td data-col="winphone8"  class="n"></td>
         <td data-col="win"       class="y"></td>
     </tr>
 </tbody>
@@ -475,4 +451,4 @@ The subscription to the `activated` event should be done before `deviceready` ha
 
 [UIApplicationExitsOnSuspend]: http://developer.apple.com/library/ios/#documentation/general/Reference/InfoPlistKeyReference/Articles/iPhoneOSKeys.html
 [AndroidLifeCycleGuide]: ../../guide/platforms/android/lifecycle.html
-[MSDNActivatedEvent]: https://msdn.microsoft.com/en-us/library/windows/apps/br212679.aspx
\ No newline at end of file
+[MSDNActivatedEvent]: https://msdn.microsoft.com/en-us/library/windows/apps/br212679.aspx
diff --git a/www/docs/en/dev/guide/hybrid/plugins/index.md b/www/docs/en/dev/guide/hybrid/plugins/index.md
index 39283a249..55b3309d3 100644
--- a/www/docs/en/dev/guide/hybrid/plugins/index.md
+++ b/www/docs/en/dev/guide/hybrid/plugins/index.md
@@ -197,8 +197,6 @@ listed below, and each builds on the simple Echo Plugin example above:
 
 - [Android Plugins](../../platforms/android/plugin.html)
 - [iOS Plugins](../../platforms/ios/plugin.html)
-- [BlackBerry 10 Plugins](../../platforms/blackberry10/plugin.html)
-- [Windows Phone 8 Plugins](../../platforms/wp8/plugin.html)
 - [Windows Plugins](../../platforms/win8/plugin.html)
 
 ## Publishing Plugins
diff --git a/www/docs/en/dev/guide/platforms/blackberry/upgrade.md b/www/docs/en/dev/guide/platforms/blackberry/upgrade.md
deleted file mode 100644
index 9d0bab234..000000000
--- a/www/docs/en/dev/guide/platforms/blackberry/upgrade.md
+++ /dev/null
@@ -1,441 +0,0 @@
----
-license: >
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-        http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
-
-title: Upgrading BlackBerry
----
-
-# Upgrading BlackBerry
-
-This guide shows how to modify BlackBerry projects to upgrade from
-older versions of Cordova.  These instructions apply to projects
-created with an older set of command-line tools that precede the
-`cordova` CLI utility. See [The Command-Line Interface](../../cli/index.html) for information
-how to update the version of the CLI.
-
-## Upgrading 2.8.0 projects to 2.9.0 ##
-
-BlackBerry 10:
-
-1. Download and extract the Cordova 2.9.0 source to a permanent location on your hard drive, for example to `~/Cordova-2.9.0`.
-
-2. Quit any running SDK tools: Eclipse, Momentics and the like.
-
-3. Navigate to the directory where you put the downloaded source above, using a unix like terminal: Terminal.app, Bash, Cygwin, etc.
-
-4. Create a new project, as described in BlackBerry Shell Tool Guide. This becomes the home of your updated project.
-
-5. Copy your project's source from the old project's `/www` directory to the new project's `/www` directory.
-
-6. Update the Cordova script reference in the `www/index.html` file (and any other files that contain the script reference) to point to the new `cordova.js` file.
-
-### BlackBerryOS/Playbook ###
-
-1. Download and extract the Cordova 2.9.0 source to a permanent location on your hard drive, for example to `~/Cordova-2.9.0`.
-
-2. Quit any running SDK tools: Eclipse, Momentics and the like.
-
-3. Navigate to the directory where you put the downloaded source above, using a unix like terminal: Terminal.app, Bash, Cygwin, etc.
-
-4. Create a new project, as described in BlackBerry Shell Tool Guide. You need the assets from this new project.
-
-5. Copy the `www/cordova.js` file from the new project into the `www` directory, and delete the `www/cordova.js` file.
-
-6. Update the Cordova script reference in the `www/index.html` file (and any other files that contain the script reference) to point to the new `cordova.js` file.
-
-7. Copy the `native` directory from the new project into the existing project, overwriting the old `native` directory.
-
-8. Copy the `lib` directory from the new project into the existing project, overwriting the old `lib` directory.
-
-9. Copy the `cordova` directory from the new project into the existing project, overwriting the old `cordova` directory.
-
-## Upgrading 2.7.0 projects to 2.8.0 ##
-
-BlackBerry 10:
-
-BlackBerry 10 uses the new CLI tooling and manages core APIs as plugins. The instructions migrate your project to a new project, rather than updating an existing project, due to the complexity of updating an old project.
-Also note that the cordova js script file is now called 'cordova.js' and no longer contains a version string.
-
-1. Download and extract the Cordova 2.8.0 source to a permanent location on your hard drive, for example to `~/Cordova-2.8.0`.
-
-2. Quit any running SDK tools: Eclipse, Momentics and the like.
-
-3. Navigate to the directory where you put the downloaded source above, using a unix like terminal: Terminal.app, Bash, Cygwin, etc.
-
-4. Create a new project, as described in BlackBerry Shell Tool Guide. This becomes the home of your updated project.
-
-5. Copy your project's source from the old project's `/www` directory to the new project's `/www` directory.
-
-6. Update the Cordova script reference in the `www/index.html` file (and any other files that contain the script reference) to point to the new `cordova.js` file.
-
-BlackBerryOS/Playbook:
-
-1. Download and extract the Cordova 2.8.0 source to a permanent location on your hard drive, for example to `~/Cordova-2.8.0`.
-
-2. Quit any running SDK tools: Eclipse, Momentics and the like.
-
-3. Navigate to the directory where you put the downloaded source above, using a unix like terminal: Terminal.app, Bash, Cygwin, etc.
-
-4. Create a new project, as described in BlackBerry Shell Tool Guide. You need the assets from this new project.
-
-5. Copy the `www/cordova.js` file from the new project into the `www` directory, and delete the `www/cordova.js` file.
-
-6. Update the Cordova script reference in the `www/index.html` file (and any other files that contain the script reference) to point to the new `cordova.js` file.
-
-7. Copy the `native` directory from the new project into the existing project, overwriting the old `native` directory.
-
-8. Copy the `lib` directory from the new project into the existing project, overwriting the old `lib` directory.
-
-9. Copy the `cordova` directory from the new project into the existing project, overwriting the old `cordova` directory.
-
-## Upgrading 2.6.0 projects to 2.7.0 ##
-
-1. Download and extract the Cordova 2.7.0 source to a permanent location on your hard drive, for example to `~/Cordova-2.7.0`.
-
-2. Quit any running SDK tools: Eclipse, Momentics and the like.
-
-3. Navigate to the directory where you put the downloaded source above, using a unix like terminal: Terminal.app, Bash, Cygwin, etc.
-
-4. Create a new project, as described in BlackBerry Shell Tool Guide. You need the assets from this new project.
-
-5. Copy the `www/cordova-2.7.0.js` file from the new project into the `www` directory, and delete the `www/cordova-2.6.0.js` file.
-
-6. Update the Cordova script reference in the `www/index.html` file (and any other files that contain the script reference) to point to the new `cordova-2.7.0.js` file.
-
-7. Copy the `native` directory from the new project into the existing project, overwriting the old `native` directory.
-
-8. Copy the `lib` directory from the new project into the existing project, overwriting the old `lib` directory.
-
-9. Copy the `cordova` directory from the new project into the existing project, overwriting the old `cordova` directory.
-
-## Upgrade to 2.6.0 from 2.5.0 ##
-
-Updating the PhoneGap download directory:
-
-It is recommended that you download a fresh copy of the entire directory.
-
-However, here are the new parts needed for the piecemeal update:
-
-1. Update the cordova.blackberry.js file in the `Phonegap-2.6.0/lib/blackberry/javascript` directory.
-
-2. Update the `ext`, `ext-air`, and `ext-qnx` in the `Phonegap-2.6.0/lib/blackberry/framework` directory.
-
-3. Update the `build.xml` file in the `Phonegap-2.6.0/lib/blackberry` directory.
-
-4. Update the `Phonegap-2.6.0/lib/blackberry/bin` directory.
-
-5. Update the `VERSION` file in the `Phonegap-2.6.0/lib/blackberry` directory.
-
-Updating the `example/` directory or migrating an existing project:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Update the contents of the `ext-qnx/` directory.
-
-4. Copy the new `cordova-2.6.0.js` into your project.
-
-5. Update your HTML to use the new `cordova-2.6.0.js` file.
-
-## Upgrade to 2.5.0 from 2.4.0 ##
-
-Updating the PhoneGap download directory:
-
-It is recommended that you download a fresh copy of the entire directory.
-
-However, here are the new parts needed for the piecemeal update:
-
-1. Update the cordova.blackberry.js file in the `Phonegap-2.5.0/lib/blackberry/javascript` directory.
-
-2. Update the `ext`, `ext-air`, and `ext-qnx` in the `Phonegap-2.5.0/lib/blackberry/framework` directory.
-
-3. Update the `build.xml` file in the `Phonegap-2.5.0/lib/blackberry` directory.
-
-4. Update the `Phonegap-2.5.0/lib/blackberry/bin` directory.
-
-5. Update the `VERSION` file in the `Phonegap-2.5.0/lib/blackberry` directory.
-
-Updating the example/ directory or migrating an existing project:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Update the contents of the `ext-qnx/` directory.
-
-4. Copy the new `cordova-2.5.0.js` into your project.
-
-5. Update your HTML to use the new `cordova-2.5.0.js` file.
-
-## Upgrade to 2.4.0 from 2.3.0 ##
-
-Updating just the `www` directory:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Copy the new `cordova-2.4.0.js` into your project.
-    - If playbook, then update the .js file in the `playbook/` directory.
-    - If BlackBerry 10, then update the .js file in the `qnx/` directory.
-
-5. Update your HTML to use the new `cordova-2.4.0.js` file.
-
-Updating the sample directory (ie, updating using the ant tools):
-
-1. Open the `sample/lib/` directory.
-
-2. Update the .jar file in the `cordova.2.3.0/ext/` directory.
-
-3. Update the contents of the `cordova.2.3.0/ext-air/` directory.
-
-4. Update the contents of the `cordova.2.3.0/ext-qnx/` directory.
-
-5. Update the .js file in the `cordova.2.3.0/javascript/` directory.
-
-6. Open the `sample/lib/` directory and rename the `cordova.2.3.0/` directory to `cordova.2.4.0/`.
-
-7. Type `ant blackberry build` or `ant playbook build` to update the `www` directory with updated Cordova.
-
-8. Open the `www` directory and update your HTML to use the new `cordova-2.4.0.js` file.
-
-## Upgrade to 2.3.0 from 2.2.0 ##
-
-Updating just the `www` directory:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Copy the new `cordova-2.3.0.js` into your project.
-    - If playbook, then update the .js file in the `playbook/` directory.
-    - If BlackBerry 10, then update the .js file in the `qnx/` directory.
-
-5. Update your HTML to use the new `cordova-2.3.0.js` file.
-
-Updating the sample directory (ie, updating using the ant tools):
-
-1. Open the `sample/lib/` directory.
-
-2. Update the .jar file in the `cordova.2.2.0/ext/` directory.
-
-3. Update the contents of the `cordova.2.2.0/ext-air/` directory.
-
-4. Update the contents of the `cordova.2.2.0/ext-qnx/` directory.
-
-5. Update the .js file in the `cordova.2.2.0/javascript/` directory.
-
-6. Open the `sample/lib/` directory and rename the `cordova.2.2.0/` directory to `cordova.2.3.0/`.
-
-7. Type `ant blackberry build` or `ant playbook build` to update the `www` directory with updated Cordova.
-
-8. Open the `www` directory and update your HTML to use the new `cordova-2.3.0.js` file.
-
-## Upgrade to 2.2.0 from 2.1.0 ##
-
-Updating just the www directory:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Copy the new `cordova-2.2.0.js` into your project.
-    - If playbook, then update the .js file in the `playbook/` directory.
-    - If BlackBerry 10, then update the .js file in the `qnx/` directory.
-
-5. Update your HTML to use the new `cordova-2.2.0.js` file.
-
-Updating the sample directory (ie, updating using the ant tools):
-
-1. Open the `sample/lib/` directory.
-
-2. Update the .jar file in the `cordova.2.1.0/ext/` directory.
-
-3. Update the contents of the `cordova.2.1.0/ext-air/` directory.
-
-4. Update the contents of the `cordova.2.1.0/ext-qnx/` directory.
-
-5. Update the .js file in the `cordova.2.1.0/javascript/` directory.
-
-6. Open the `sample/lib/` directory and rename the `cordova.2.1.0/` directory to `cordova.2.2.0/`.
-
-7. Type `ant blackberry build` or `ant playbook build` to update the `www` directory with updated Cordova.
-
-8. Open the `www` directory and update your HTML to use the new `cordova-2.2.0.js` file.
-
-## Upgrade to 2.1.0 from 2.0.0 ##
-
-Updating just the `www` directory:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Copy the new `cordova-2.1.0.js` into your project.
-    - If playbook, then update the .js file in the `playbook/` directory.
-
-5. Update your HTML to use the new `cordova-2.1.0.js` file.
-
-Updating the sample directory (ie, updating using the ant tools):
-
-1. Open the `sample/lib/` directory.
-
-2. Update the .jar file in the `cordova.2.0.0/ext/` directory.
-
-3. Update the contents of the `cordova.2.0.0/ext-air/` directory.
-
-4. Update the .js file in the `cordova.2.0.0/javascript/` directory.
-
-5. Open the `sample/lib/` directory and rename the `cordova.2.0.0/` directory to `cordova.2.1.0/`.
-
-6. Type `ant blackberry build` or `ant playbook build` to update the `www` directory with updated Cordova.
-
-7. Open the `www` directory and update your HTML to use the new `cordova-2.1.0.js` file.
-
-## Upgrade to 2.0.0 from 1.9.0 ##
-
-Updating just the `www` directory:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Copy the new `cordova-2.0.0.js` into your project.
-    - If playbook, then update the .js file in the `playbook/` directory.
-
-5. Update your HTML to use the new `cordova-2.0.0.js` file.
-
-6. Update the `www/plugins.xml` file. Two plugins changed their
-   namespace/service label. Change the old entries for the Capture and
-   Contact plugins from:
-   ```xml
-   <plugin name="Capture" value="org.apache.cordova.media.MediaCapture"/>
-   <plugin name="Contact" value="org.apache.cordova.pim.Contact"/>
-   ```
-
-   To:
-   ```xml
-   <plugin name="Capture" value="org.apache.cordova.capture.MediaCapture"/>
-   <plugin name="Contacts" value="org.apache.cordova.pim.Contact"/>
-   ```
-
-Updating the sample directory (ie, updating using the ant tools):
-
-1. Open the `sample/lib/` directory.
-
-2. Update the .jar file in the `cordova.1.9.0/ext/` directory.
-
-3. Update the contents of the `cordova.1.9.0/ext-air/` directory.
-
-4. Update the .js file in the `cordova.1.9.0/javascript/` directory.
-
-5. Open the `sample/lib/` directory and rename the `cordova.1.9.0/` directory to `cordova.2.0.0/`.
-
-6. Type `ant blackberry build` or `ant playbook build` to update the `www` directory with updated Cordova.
-
-7. Open the `www` directory and update your HTML to use the new `cordova-2.0.0.js` file.
-
-8. Open the `www` directory and update the `plugins.xml` file. Two plugins
-   changed their namespace/service label. Change the old entries for the
-   Capture and Contact plugins from:
-   ```xml
-   <plugin name="Capture" value="org.apache.cordova.media.MediaCapture"/>
-   <plugin name="Contact" value="org.apache.cordova.pim.Contact"/>
-   ```
-
-   To:
-   ```xml
-   <plugin name="Capture" value="org.apache.cordova.capture.MediaCapture"/>
-   <plugin name="Contacts" value="org.apache.cordova.pim.Contact"/>
-   ```
-
-- To upgrade to 1.8.0, please go from 1.7.0
-
-## Upgrade to 1.8.0 from 1.7.0 ##
-
-Updating just the `www` directory:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Copy the new `cordova-1.8.0.js` into your project.
-    - If playbook, then update the .js file in the `playbook/` directory.
-
-5. Update your HTML to use the new `cordova-1.8.0.js` file.
-
-6. Update the `www/plugins.xml` file. Two plugins changed their
-   namespace/service label. Change the old entries for the Capture and
-   Contact plugins from:
-   ```xml
-   <plugin name="Capture" value="org.apache.cordova.media.MediaCapture"/>
-   <plugin name="Contact" value="org.apache.cordova.pim.Contact"/>
-   ```
-
-   To:
-   ```xml
-   <plugin name="Capture" value="org.apache.cordova.capture.MediaCapture"/>
-   <plugin name="Contacts" value="org.apache.cordova.pim.Contact"/>
-   ```
-
-Updating the sample directory (ie, updating using the ant tools):
-
-1. Open the `sample/lib/` directory.
-
-2. Update the .jar file in the `cordova.1.7.0/ext/` directory.
-
-3. Update the contents of the `cordova.1.7.0/ext-air/` directory.
-
-4. Update the .js file in the `cordova.1.7.0/javascript/` directory.
-
-5. Open the `sample/lib/` directory and rename the `cordova.1.7.0/` directory to `cordova.1.8.0/`.
-
-6. Type `ant blackberry build` or `ant playbook build` to update the `www` directory with updated Cordova.
-
-7. Open the `www` directory and update your HTML to use the new `cordova-1.8.0.js` file.
-
-8. Open the `www` directory and update the `plugins.xml` file. Two plugins
-   changed their namespace/service label. Change the old entries for the
-   Capture and Contact plugins from:
-   ```xml
-   <plugin name="Capture" value="org.apache.cordova.media.MediaCapture"/>
-   <plugin name="Contact" value="org.apache.cordova.pim.Contact"/>
-   ```
-
-   To:
-   ```xml
-   <plugin name="Capture" value="org.apache.cordova.capture.MediaCapture"/>
-   <plugin name="Contacts" value="org.apache.cordova.pim.Contact"/>
-   ```
diff --git a/www/docs/en/dev/guide/platforms/blackberry10/config.md b/www/docs/en/dev/guide/platforms/blackberry10/config.md
deleted file mode 100644
index ce2d5c397..000000000
--- a/www/docs/en/dev/guide/platforms/blackberry10/config.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-license: >
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-        http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
-
-title: BlackBerry 10 Configuration
----
-
-# BlackBerry 10 Configuration
-
-The `config.xml` file controls an app's basic settings that apply
-across each application and CordovaWebView instance. This section
-details preferences that only apply to BlackBerry 10 builds. See [The config.xml
-File](config_ref_index.md.html#The%20config.xml%20File) for information on global configuration options.
-
-- `ChildBrowser` (`disable` or the default `enable`): Disables child
-  browser windows. By default, apps launch a secondary browser window
-  to display resources accessed via `window.open()` or by specifying a
-  `_blank` anchor target. Specify `disable` to override this default
-  behavior.
-  ```xml
-  <preference name="ChildBrowser" value="disable"/>
-  ```
-
-- `PopupBlocker` (`enable` or the default `disable`): Enables the
-  popup blocker, which prevents calls to `window.open()`. By default,
-  popups display in a child browser window. Setting the preference to
-  `enable` prevents it from displaying at all.
-  ```xml
-  <preference name="PopupBlocker" value="enable"/>
-  ```
-
-- `WebSecurity` (`disable` or the default `enable`): Set to `disable`
-  to override web security settings, allowing access to remote content
-  from unknown sources. This preference is intended as a development
-  convenience only, so remove it before packaging the app for
-  distribution.  For the released app, all URIs should be known and
-  whitelisted using the `<access>` element, described in the Domain
-  [Whitelist Guide](../../appdev/whitelist/index.html).
-  ```xml
-  <preference name="WebSecurity" value="disable"/>
-  ```
diff --git a/www/docs/en/dev/guide/platforms/blackberry10/home.md b/www/docs/en/dev/guide/platforms/blackberry10/home.md
deleted file mode 100644
index 1461e0505..000000000
--- a/www/docs/en/dev/guide/platforms/blackberry10/home.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-license: >
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-        http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
-
-title: Blackberry 10 Guides
-toc_title: Blackberry 10
----
-
-# Blackberry 10 Guides
-
-* [BlackBerry 10 Platform Guide](index.html)
-* [BlackBerry 10 Shell Tool Guide](tools.html)
-* [BlackBerry 10 Configuration](config.html)
-* [BlackBerry 10 Plugins](plugin.html)
-* [Upgrading BlackBerry 10](upgrade.html)
\ No newline at end of file
diff --git a/www/docs/en/dev/guide/platforms/blackberry10/index.md b/www/docs/en/dev/guide/platforms/blackberry10/index.md
deleted file mode 100644
index 0ce8760a6..000000000
--- a/www/docs/en/dev/guide/platforms/blackberry10/index.md
+++ /dev/null
@@ -1,297 +0,0 @@
----
-license: >
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-        http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
-
-title: BlackBerry 10 Platform Guide
----
-
-# BlackBerry 10 Platform Guide
-
-This guide shows how to set up your SDK environment to deploy
-Cordova apps for BlackBerry 10 devices.  For previous versions of
-BlackBerry, you need to use a different SDK environment and set of
-command-line tools, described in the BlackBerry Platform Guide.
-For BlackBerry 10, you need to install the SDK regardless of whether
-you want to use the cross-platform Cordova CLI for development, or a
-narrower set of platform-centered command-line tools.  For a
-comparison of the two development paths, see the [Overview](../../overview/index.html).  For
-details on each, see [Cordova CLI Reference][cli] and the BlackBerry 10
-Shell Tool Guide.
-
-## Requirements
-
-The development environment is available on Windows, Mac and Linux.
-
-Developers should use the `cordova` utility in conjunction with the
-BlackBerry WebWorks SDK or BlackBerry Native SDK. See The Command-Line
-Interface for information how to install `cordova`, add projects, then
-build and deploy for each platform.
-
-BlackBerry 10 Device Simulator:
-
-* Processor: Intel dual core 2.0 GHz/AMD Athlon 4200+ or higher
-* Disk space: 10 GB
-* RAM Memory: 4 GB
-* Virtualization: one of the following:
-  * __Intel Virtualization Technology__ (VT, VT-x, vmx) &rarr; [Intel VT-x supported processor list](http://ark.intel.com/products/virtualizationtechnology)
-  * __AMD Virtualization__ (AMD-V, SVM) (Since May 2006 all AMD CPUs include AMD-V except Sempron).
-
-More information about requirements: [BB10 Simulator requeriments](http://developer.blackberry.com/devzone/develop/simulator/simulator_systemrequirements.html).
-
-## Install the BlackBerry WebWorks SDK
-
-Download and install the BlackBerry WebWorks SDK from [developer.blackberry.com](https://developer.blackberry.com/html5/download/)
-
-The installer will add command-line tools to your path. Depending on your OS,
-you may need to open a new terminal window or re-log in.
-
-## Install the BlackBerry Native SDK
-
-If you need to compile native code, for example when developing a native plugin, you
-will need to install the BlackBerry Native SDK.
-
-In order to get the BlackBerry Native SDK, download and install the IDE for BlackBerry available from
-[developer.blackberry.com](http://developer.blackberry.com/native/download/), then using the IDE, install the BlackBerry Native SDK.
-Following installation, you need to add its command-line tools to your
-system path.
-
-On Windows:
-
-* Go to __My Computer &rarr; Properties &rarr; Advanced &rarr; Environment Variables__.
-
-* Append the Native SDK's install directory to the PATH, for example:
-  ```
-  ;C:\bbndk\host_10_1_0_132\win32\x86\usr\bin\
-  ```
-
-On Mac and Linux:
-
-* Edit the `~/.bash_profile` file, adding a line such as the
-  following, depending on where the Native SDK was installed:
-    ```bash
-    export PATH=${PATH}:/Applications/bbndk/host_10_1_0_132/darwin/x86/usr/bin/
-
-    # or for the 10.2 Native SDK:
-    export PATH=${PATH}:/Applications/Momentics.app/host_10_2_0_15/darwin/x86/usr/bin/
-    ```
-
-* Run the following to apply the change in the current session:
-    ```bash
-    $ source ~/.bash_profile
-    ```
-
-If you got any environmental problem, using the Native SDK from the command line, execute the appropriate file for your platform, located within the installation path:
-
-* On Windows &rarr; MS-DOS shell:
-  ```
-  C:\> \bbndk\bbndk-env_xx_xx_xx_xxxx.bat
-  ```
-
-* On Windows &rarr; git bash shell:
-  ```
-  $ `\bbndk\bbndk-env_xx_xx_xx_xxxx.bat`
-  ```
-
-* On Linux &rarr; Installed as root user:
-  ```bash
-  $ `./opt/bbndk/bbndk-env_xx_xx_xx_xxxx.sh`
-  ```
-
-* On Linux &rarr; Installed as non-root user:
-  ```bash
-  $ `./home/username/bbndk/bbndk-env_xx_xx_xx_xxxx.sh`
-  ```
-
-* On Mac:
-  ```bash
-  $ `/Developer/SDKs/bbndk/bbndk-env_xx_xx_xx_xxxx.sh`
-  ```
-
-## Set up for Signing
-
-If you wish to test on a device or distribute apps through BlackBerry
-World, your system must be setup for code signing.
-
-To obtain a signing key, go to the [BlackBerry Keys Order Form] (https://www.blackberry.com/SignedKeys/codesigning.html).
-
-Select the first checkbox: "for BlackBerry10 apps developed using BlackBerry
-NDK" and then sign in or create a BBID.
-
-Enter a password and click "Get Token" to download bbidtoken.csk. Save this
-file to the default location for your OS which will be displayed on the
-download page.
-
-The final step is to generate a signing certificate:
-
-```bash
-$ blackberry-keytool -genkeypair -storepass <password> -author 'Your Name’
-```
-
-## Create a Project
-
-Use the `cordova` utility to set up a new project, as described in
-[Cordova CLI Reference][cli]. For example, in a source-code directory:
-
-```bash
-$ cordova create hello com.example.hello
-$ cd hello
-$ cordova platform add blackberry10
-$ cordova build
-```
-
-## Deploy to Emulator
-
-If you wish to run a device emulator, download and install the
-BlackBerry 10 Simulator.
-
-* [Download](http://developer.blackberry.com/native/download/)
-* [Getting Started](http://developer.blackberry.com/devzone/develop/simulator/blackberry_10_simulator_start.html)
-
-Before testing an app on either an emulator or a device, you need to
-enable development mode.
-
-Launch the emulator image, then choose __Settings__ from the home screen:
-
-![]({{ site.baseurl }}/static/img/guide/platforms/blackberry10/bb_home.png)
-
-Navigate to the __Security and Privacy &rarr; Development Mode__
-section and enable the option:
-
-![]({{ site.baseurl }}/static/img/guide/platforms/blackberry10/bb_devel.png)
-
-An additional set of command-line utilities are included when you set
-up the BlackBerry 10 platform for your project.  The following
-command, in this case invoked from the project top-level directory,
-associates a target named _emu_ with the IP address displayed above.
-
-* On Windows:
-  ```
-  $ platforms\blackberry10\cordova\target.bat add emu 169.254.0.1 -t simulator
-  ```
-
-* On Mac/Linux:
-  ```bash
-  platforms/blackberry10/cordova/target add emu 169.254.0.1 -t simulator
-  ```
-
-Then, run the `emulate` command to view the app:
-```bash
-$ cordova emulate blackberry10
-```
-
-## Deploy to Device
-
-To deploy to a device, make sure it is plugged into your computer.
-Enable development mode and obtain the IP address as desribed in the
-emulator section above. You will also need to obtain the PIN from the
-the __Settings__ application under __About &rarr; Hardware__:
-
-![]({{ site.baseurl }}/static/img/guide/platforms/blackberry10/bb_pin.png)
-
-Run the target command-line utility to associate a name with an IP
-address, device password and PIN.
-
-* On Windows:
-  ```
-  $ platforms\blackberry10\cordova\target.bat add mydevice 169.254.0.1 -t device --password 123456 --pin FFFF972E
-  ```
-
-* On Mac/Linux:
-  ```bash
-  $ platforms/blackberry10/cordova/target add mydevice 169.254.0.1 -t device --password 123456 --pin FFFF972E
-  ```
-
-where:
-
-* `--password` refers to the password to unlock the device.
-
-* `--pin` refers to the device PIN obtained from the __Settings__ application.
-
-Then, run the `run` command to view the app:
-
-```bash
-$ cordova run blackberry10
-```
-
-If a debug token is not yet set up for the device, an error message
-prompts you to use the platform run script with the password you
-provided when registering for signing keys.
-
-* On Windows:
-  ```
-  $ platforms\blackberry10\cordova\run.bat --device --keystorepass mysecret
-  ```
-
-* On Mac/Linux:
-  ```bash
-  $ platforms/blackberry10/cordova/run --device --keystorepass mysecret
-  ```
-
-## Debugging with WebInspector
-
-When debugging on the device or an emulator, you may run WebInspector
-remotely to view the application's internal state.  A prompt displays
-the URL that allows you to connect to the app with a standard web
-browser.  For more information, see
-[Debugging using WebInspector](http://developer.blackberry.com/html5/documentation/web_inspector_overview_1553586_11.html).
-
-## Building a Release Version
-
-By default, running the `cordova build` command creates an unsigned
-_.bar_ package file suitable for testing on a device or simulator.
-
-Use `--release` to create a release version suitable for distribution
-through BlackBerry World.
-
-```bash
-$ cordova build --release --keystorepass <signing password>
-```
-
-The `--keystorepass` option specifies the password you defined when
-configuring your computer to sign applications.
-
-
-## Deploy to Other Locations
-
-The instructions above assume a device is plugged in via USB or a
-simulator is running on the local machine. It is also possible to
-deploy to other locations.
-
-An additional set of command-line utilities are included when you set
-up the BlackBerry 10 platform for your project.  The following
-command, in this case invoked from the project top-level directory,
-associates a target named _emu_ with an IP address.
-
-* On Windows:
-  ```
-  $ platforms\blackberry10\cordova\build.bat --release --keystorepass mysecret
-  ```
-
-* On Mac/Linux:
-  ```bash
-  $ platforms/blackberry10/cordova/build --release --keystorepass mysecret
-  ```
-
-Once the target is defined, you can provide it to the run command using
-`--target`:
-
-```bash
-$ cordova run blackberry10 --target=emu
-```
-
-[cli]: ../../../reference/cordova-cli/index.html
diff --git a/www/docs/en/dev/guide/platforms/blackberry10/plugin.md b/www/docs/en/dev/guide/platforms/blackberry10/plugin.md
deleted file mode 100644
index 6ec41336b..000000000
--- a/www/docs/en/dev/guide/platforms/blackberry10/plugin.md
+++ /dev/null
@@ -1,283 +0,0 @@
----
-license: >
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-        http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
-
-title: BlackBerry 10 Plugins
-toc_title: Blackberry 10
----
-
-# BlackBerry 10 Plugins
-
-This section provides details for how to implement native plugin code
-on the BlackBerry 10 platform. Before reading this, see Application
-Plugins for an overview of the plugin's structure and its common
-JavaScript interface. This section continues to demonstrate the sample
-_echo_ plugin that communicates from the Cordova webview to the native
-platform and back.
-
-The Echo plugin basically returns whatever string the `window.echo`
-function sends from JavaScript:
-
-```javascript
-window.echo = function(str, callback) {
-    cordova.exec(callback, function(err) {
-        callback('Nothing to echo.');
-    }, "Echo", "echo", [str]);
-};
-```
-
-A Cordova plugin for BlackBerry 10 contains both JavaScript and native
-code, which communicate with each other through a framework provided
-by JNEXT. Every plugin must also include a `plugin.xml` file.
-
-## Creating the Native Class
-
-To create the native portion of your plugin, open the BlackBerry 10
-NDK IDE and select __File &rarr; New &rarr; BlackBerry Project &rarr;
-Native Extension &rarr; BlackBerry 10__. Enter the desired
-project name and location, then press __Finish__.
-
-The project created by the IDE contains sample code for a memory
-plugin. You may replace or modify these files to implement your own
-functionality:
-
-- `*name*_js.hpp`: C++ header for the JNEXT code.
-
-- `*name*_js.cpp`: C++ code for JNEXT.
-
-The native interface for the JNEXT extension can be viewed in the
-plugin header file located in the project's public directory. It also
-features constants and utility functions available from within native
-code. The plugin must be derived from `JSExt`, which is defined in
-`plugin.h`. That is, you must implement the following class:
-
-```cpp
-class JSExt
-{
-public:
-    virtual ~JSExt() {};
-    virtual string InvokeMethod( const string& strCommand ) = 0;
-    virtual bool CanDelete( void ) = 0;
-private:
-    std::string m_id;
-};
-```
-
-The extension should include the `plugin.h` header file. In the `Echo`
-example, you use `JSExt` as follows in the `echo_js.hpp` file:
-
-```cpp
-#include "../public/plugin.h"
-#include <string>
-
-#ifndef ECHO_JS_H_
-#define ECHO_JS_H_
-
-class Echo : public JSExt
-{
-public:
-    explicit Echo(const std::string& id);
-    virtual ~Echo();
-    virtual std::string InvokeMethod(const std::string& command);
-    virtual bool CanDelete();
-private:
-    std::string m_id;
-};
-
-#endif // ECHO_JS_H_
-```
-
-The `m_id` attribute contains the `JNEXT` id for the object, which is
-passed to the class as an argument to the constructor. It is needed
-for the native side to trigger events on the JavaScript side.  The
-`CanDelete` method determines whether the native object can be
-deleted.  The `InvokeMethod` function is called as a result from a
-request from JavaScript to invoke a method of this particular
-object. The only argument to this function is a string passed from
-JavaScript that this method parses to determine which of the native
-object's methods should execute.  These methods are implemented in
-`echo_js.cpp`. Here is the `InvokeMethod` function for the `Echo`
-example:
-
-```cpp
-string Echo::InvokeMethod(const string& command) {
-
-    //parse command and args from string
-    int index = command.find_first_of(" ");
-    string strCommand = command.substr(0, index);
-    string strValue = command.substr(index + 1, command.length());
-
-    // Determine which function should be executed
-    if (strCommand == "echo") {
-        return strValue;
-    } else {
-        return "Unsupported Method";
-    }
-}
-```
-
-The native plugin must also implement the following callback
-functions:
-
-- `extern char* onGetObjList( void );`
-
-- `extern JSExt* onCreateObject( const string& strClassName, const string& strObjId );`
-
-The `onGetObjList` function returns a comma-separated list of classes
-supported by JNEXT. JNEXT uses this function to determine the set of
-classes that JNEXT can instantiate. The `Echo` plugin implements the
-following in `echo_js.cpp`:
-
-```cpp
-char* onGetObjList() {
-    static char name[] = "Echo";
-    return name;
-}
-```
-
-The `onCreateObject ` function takes two parameters. The first is the
-name of the requested class to be created from the JavaScript side,
-with valid names as those returned in `onGetObjList`. The second
-parameter is the class's unique object id. This method returns a
-pointer to the created plugin object. The `Echo` plugin implements the
-following in `echo_js.cpp`:
-
-```cpp
-JSExt* onCreateObject(const string& className, const string& id) {
-    if (className == "Echo") {
-        return new Echo(id);
-    }
-    return NULL;
-}
-```
-
-## Creating the Plugin's JavaScript
-
-The plugin must contain the following JavaScript files:
-
-- `client.js`: This is considered the client side and contains the API
-  available to a Cordova application. The API in `client.js` calls
-  makes calls to `index.js`. The API in `client.js` also connects
-  callback functions to the events that fire the callbacks.
-
-- `index.js`: Cordova loads `index.js` and makes it accessible through
-  the cordova.exec bridge. The `client.js` file makes calls to the API
-  in the `index.js` file, which in turn makes call to JNEXT to
-  communicate with the native side.
-
-The client and server side (`client.js` and `index.js`) interacts
-through the `Cordova.exec` function. The `client.js` needs to invoke
-the `exec` function and provide the necessary arguments. The `Echo`
-plugin implements the following in the `client.js` file:
-
-```javascript
-var service = "org.apache.cordova.blackberry.echo",
-    exec = cordova.require("cordova/exec");
-
-module.exports = {
-    echo: function (data, success, fail) {
-        exec(success, fail, service, "echo", { data: data });
-    }
-};
-```
-
-The `index.js` component uses JNEXT to interact with the native
-side. Attaching a constructor function named `Echo` to JNEXT allows
-you to perform the following key operations using the `init` function:
-
-- Specify the required module exported by the native side. The name of
-  the required module must match the name of a shared library file
-  (`.so` file):
-
-    ```javascript
-    JNEXT.require("libecho")
-    ```
-
-- Create an object by using an acquired module and save the ID that's
-  returned by the call:
-
-    ```javascript
-    self.m_id = JNEXT.createObject("libecho.Echo");
-    ```
-
-  When the application calls the `echo` function in `client.js`, that
-  call in turn calls the `echo` function in `index.js`, where the
-  `PluginResult` object sends data as a response back to `client.js`.
-  Since the `args` argument passed into the functions was converted by
-  `JSON.stringfy()` and encoded as a `URIcomponent`, you must call the
-  following:
-
-```javascript
-data = JSON.parse(decodeURIComponent(args.data));
-```
-
-You can now send the data back, as in the following:
-
-```javascript
-module.exports = {
-    echo: function (success, fail, args, env) {
-        var result = new PluginResult(args, env),
-        data = JSON.parse(decodeURIComponent(args.data)),
-        response = echo.getInstance().echo(data);
-        result.ok(response, false);
-    }
-};
-```
-
-## Plugin Architecture
-
-You can place the plugin's artifacts, including the `plugin.xml` file,
-the JavaScript and C++ source files, and the `.so` binary files within
-any directory structure, as long as you correctly specify the file
-locations in the `plugin.xml` file. Here is a typical structure:
-
-***project_directory*** (>plugin.xml)
-
-- **www** (>client.js)
-- **src**
-  - **blackberry10** (>index.js, **native** >*.cpp, *.hpp)
-  - **device** (>*binary file* *.so)
-  - **simulator** (>*binary file* *.so)
-
-The list shows the hierarchical relationship among the top-level
-folders. The parenthesis shows the contents of a given directory. All
-directory names appear in bold text. File names are preceded by the `>`
-sign.
-
-## The _plugin.xml_ file
-
-The `plugin.xml` file contains the extension's namespace and other
-metadata. Set up the `Echo` plugin as follows:
-
-```xml
-<plugin xmlns="http://www.phonegap.com/ns/plugins/1.0"
-    id="org.apache.cordova.blackberry.echo"
-    version="1.0.0">
-    <js-module src="www/client.js">
-        <merges target="navigator" />
-    </js-module>
-    <platform name="blackberry10">
-        <source-file src="src/blackberry10/index.js" />
-        <lib-file src="src/blackberry10/native/device/libecho.so" arch="device" />
-        <lib-file src="src/blackberry10/native/simulator/libecho.so" arch="simulator" />
-        <config-file target="www/config.xml" parent="/widget">
-            <feature name="org.apache.cordova.blackberry.echo" value="org.apache.cordova.blackberry.echo" />
-        </config-file>
-    </platform>
-</plugin>
-```
diff --git a/www/docs/en/dev/guide/platforms/blackberry10/tools.md b/www/docs/en/dev/guide/platforms/blackberry10/tools.md
deleted file mode 100644
index b209e100a..000000000
--- a/www/docs/en/dev/guide/platforms/blackberry10/tools.md
+++ /dev/null
@@ -1,205 +0,0 @@
----
-license: >
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-        http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
-
-title: BlackBerry 10 Shell Tool Guide
----
-
-# BlackBerry 10 Shell Tool Guide
-
-The `cordova` command-line utility is a high-level tool that allows
-you to build applications across several platforms at once. An older
-version of the Cordova framework provides sets of command-line tools
-specific to each platform. To use them as an alternative to the CLI,
-you need to download this version of Cordova from
-[cordova.apache.org](http://cordova.apache.org). The download contains
-separate archives for each platform. Expand the platform you wish to
-target. The tools described here are typically available in the
-top-level `bin` directory, otherwise consult the __README__ file for
-more detailed directions.
-
-For information on the low-level command-line interface that enables
-plugins, see [Using Plugman to Manage Plugins](../../../plugin_ref/plugman.html). See Application Plugins
-for details on how to develop plugins.
-
-If you need help with any command listed below, type the command along
-with the `-h` or `-help` arguments, which are supported by all
-commands and which provide descriptions for each of the available
-arguments.
-
-## Create an App
-
-The `create` command creates a new project:
-
-```
-bin/create <path-to-project> <project-package> <project-name>
-```
-
-where
-
-- `<path-to-project>` specifies the directory you want the project created in
-
-- `<project-package>` specifies a reverse domain style identifier
-
-- `<project-name>` specifies the apps display name
-
-__NOTE__: the `create` command bootstraps dependency installation
-through the `npm install` command. Depending on the installation
-directory and system permissions, this may require administrator
-privileges.  If there's problem on OSX/Linux, run `sudo npm install`
-before using the `create` command. On Windows, run `npm install` in a
-command-line utility opened with administrator privileges.
-
-## Create a Target
-
-The `target` command allows you to manage the emulator or BlackBerry
-devices that you use to test the app. You can add or remove a target,
-or set a target as the default target.
-
-### Add a Target
-
-```
-<path-to-project>/cordova/target add <name> <ip-address> [-t | --type <device | simulator>] [-p | --password <password>] [--pin <device-pin>]
-```
-
-where
-
-- `<name>` specifies a unique name for the target.
-
-- `<ip-address>` specifies the ip address of the BlackBerry device or
-  simulator.
-
-- `-p | --password <password>` specifies the password for the device or
-  emulator. This is required only if the device or emulator is
-  password protected.
-
-- `--pin <device-pin>` specifies the PIN of the BlackBerry device,
-  which identifies that device as a valid host for the debug
-  token. This argument is required only when creating a debug
-  token.
-
-### Remove a Target
-
-```
-<path-to-project>/cordova/target remove <name>
-```
-
-### Set a Target as the Default
-
-```
-<path-to-project>/cordova/target default <name>
-```
-
-## Build the App
-
-The `build` command builds the project as a .bar file. You can build
-the app in either release mode (which produces a signed .bar file) or
-in debug mode (which produces an unsigned .bar file).
-
-### Build the App in Release Mode
-
-```
-<path-to-project>/cordova/build release [-k | --keystorepass <password>] [-b | --buildId <number>] [-p | --params <params-JSON-file>]
-```
-
-where
-
--   `-k | --keystorepass <password>`  specifies the password you defined when you configured your computer to sign applications.
-
--   `-b | --buildId <number>`  specifies the build version number of your application. Typically, this number should be incremented from the previous signed version. This argument is optional.
-
--   `-p | --params <params-JSON-file>`  specifies a JSON file containing additional parameters to pass to downstream tools. This argument is optional.
-
-### Build the Project in Debug Mode
-
-```
-<path-to-project>/cordova/build debug [<target>] [-k | --keystorepass <password>] [-p | --params <params-JSON-file>]  [-ll | --loglevel <error|warn|verbose>]
-```
-
-where
-
-- `<target>` specifies the name of a previously added target. If
-  `<target>` is not specified, the default target is used, if one has
-  been created. This argument is only required if you want the script
-  to deploy the app to a BlackBerry device or emulator and you have
-  not created a default target. Additionally, if `<target>` is a
-  device, then that device must be connected to your computer by USB
-  connection or be connected to the same Wi-Fi network as your
-  computer.
-
-- `-k | --keystorepass <password>` specifies the password you defined
-  when you configured your computer to sign applications. This
-  password is also used to create your debug token. This argument is
-  only required if you want the script to create and install the debug
-  token for you.
-
-- `-p | --params <params-JSON-file>` specifies a JSON file containing
-  additional parameters to pass to downstream tools.
-
-- `-ll | --loglevel <level>` specifies the log level. The log level may
-  be one of `error`, `warn`, or `verbose`.
-
-If you have previously defined a default target (and previously
-installed a debug token, if that target is a BlackBerry device), you
-can run the script with no arguments, and the script packages your
-app and deploys it to the default target. For example:
-
-```
-<path-to-project>/cordova/build debug
-```
-
-## Run the App
-
-The `run` command deploys the app's most recent build on the specified
-BlackBerry device or an emulator. To deploy your app, you need to
-specify a target for the device or emulator:
-
-```
-<path-to-project>/cordova/run <target>
-```
-
-...where `<target> `specifies the name of a previously added target.
-If `<target>` is a device, then it must be connected to your computer
-via USB cable, or else over the same Wi-Fi network as your computer.
-
-## Handle Plugins
-
-The `target` command allows you to add and remove plugins.  To fetch a
-locally hosted plugin:
-
-```
-<path-to-project>/cordova/plugin fetch <path-to-plugin>
-```
-
-View a list of installed plugins:
-
-```
-<path-to-project>/cordova/plugin ls
-```
-
-Add a plugin:
-
-```
-<path-to-project>/cordova/plugin add <name>
-```
-
-Remove a plugin:
-
-```
-<path-to-project>/cordova/plugin rm <name>
-```
diff --git a/www/docs/en/dev/guide/platforms/blackberry10/upgrade.md b/www/docs/en/dev/guide/platforms/blackberry10/upgrade.md
deleted file mode 100644
index fe9f28208..000000000
--- a/www/docs/en/dev/guide/platforms/blackberry10/upgrade.md
+++ /dev/null
@@ -1,516 +0,0 @@
----
-license: >
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-        http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
-
-title: Upgrading BlackBerry 10
----
-
-# Upgrading BlackBerry 10
-
-This guide shows how to modify BlackBerry projects to upgrade from older versions of Cordova.
-Most of these instructions apply to projects created with an older set
-of command-line tools that precede the `cordova` CLI utility. See [The Command-Line Interface](../../cli/index.html) for information how to update the
-version of the CLI.
-
-## Upgrading 3.6.0 Projects to 4.0.0
-
-For non-CLI projects, run:
-
-        bin/update path/to/project
-
-For CLI projects:
-
-1. Update the `cordova` CLI version. See [The Command-Line Interface](../../cli/index.html).
-
-2. Run `cordova platform update blackberry` in your existing projects.
-
-## Upgrading to 3.2.0 from 3.1.0
-
-For projects that were created with the cordova CLI:
-
-1. Update the `cordova` CLI version. See [The Command-Line Interface](../../cli/index.html).
-
-2. Run `cordova platform update blackberry`
-
-For projects not created with the cordova CLI, run:
-
-        bin/update <project_path>
-
-## Upgrade to 3.1.0 from 3.0.0
-
-1. Create a new Apache Cordova 3.1.0 project using the cordova CLI, as
-   described in [The Command-Line Interface](../../cli/index.html).
-
-2. Add your platforms to the cordova project, for example: `cordova
-   platform add blackberry10`.
-
-3. Copy the contents of the original project's `www` directory to the `www` directory
-   at the root of the cordova project you just created.
-
-4. Copy or overwrite any native assets from your original project
-   (`Resources`, etc.)
-
-5. Copy the `config.xml` file into the `www` directory, and remove any
-   plugin definitions. You need to modify settings here rather than
-   within the platform directory.
-
-6. Use the cordova CLI tool to install any plugins you need. Note that
-   the CLI handles all core APIs as plugins, so they may need to be
-   added. Only plugins marked 3.0.0 and above are compatible with the CLI.
-
-7. Build and test.
-
-Please note that the CLI supports the BlackBerry10 platform exclusively. For PlayBook and BBOS, please see Cordova version 2.9.0 and below.
-
-## Upgrade to the CLI (3.0.0) from 2.9.0
-
-1. Create a new Apache Cordova 3.0.0 project using the cordova CLI, as
-   described in [The Command-Line Interface](../../cli/index.html).
-
-2. Add your platforms to the cordova project, for example: `cordova
-   platform add blackberry10`.
-
-3. Copy the contents of the original project's `www` directory to the `www` directory
-   at the root of the cordova project you just created.
-
-4. Copy or overwrite any native assets from your original project
-   (`Resources`, etc.)
-
-5. Copy the `config.xml` file into the `www` directory, and remove any
-   plugin definitions. You need to modify settings here rather than
-   within the platform directory.
-
-6. Use the cordova CLI tool to install any plugins you need. Note that
-   the CLI handles all core APIs as plugins, so they may need to be
-   added. Only 3.0.0 plugins are compatible with the CLI.
-
-7. Build and test.
-
-## Upgrading 2.8.0 Projects to 2.9.0
-
-For BlackBerry 10:
-
-1. Download and extract the Cordova 2.9.0 source to a permanent directory location on your hard drive, for example to `~/Cordova-2.9.0`.
-
-2. Quit any running SDK tools: Eclipse, Momentics and the like.
-
-3. Navigate to the directory where you put the downloaded source above, using a unix like terminal: Terminal.app, Bash, Cygwin, etc.
-
-4. Create a new project, as described in BlackBerry Shell Tool Guide. This becomes the home of your updated project.
-
-5. Copy your projects source from the old project's `/www` directory to the new project's `/www` directory.
-
-6. Update the Cordova script reference in the `www/index.html` file (and any other files that contain the script reference) to point to the new `cordova.js` file.
-
-For BlackBerryOS/Playbook:
-
-1. Download and extract the Cordova 2.9.0 source to a permanent directory location on your hard drive, for example to `~/Cordova-2.9.0`.
-
-2. Quit any running SDK tools: Eclipse, Momentics and the like.
-
-3. Navigate to the directory where you put the downloaded source above, using a unix like terminal: Terminal.app, Bash, Cygwin, etc.
-
-4. Create a new project, as described in BlackBerry Shell Tool Guide. You need the assets from this new project.
-
-5. Copy the `www/cordova.js` file from the new project into the `www` directory, and delete the `www/cordova.js` file.
-
-6. Update the Cordova script reference in the `www/index.html` file (and any other files that contain the script reference) to point to the new `cordova.js` file.
-
-7. Copy the `native` directory from the new project into the existing project, overwriting the old `native` directory.
-
-8. Copy the `lib` directory from the new project into the existing project, overwriting the old `lib` directory.
-
-9. Copy the `cordova` directory from the new project into the existing project, overwriting the old `cordova` directory.
-
-## Upgrading 2.7.0 Projects to 2.8.0
-
-BlackBerry 10 uses the new CLI tooling and manages core APIs as plugins. The instructions migrate your project to a new project, rather than updating an existing project, due to the complexity of updating an old project.
-Also note that the cordova js script file is now called 'cordova.js' and no longer contains a version string.
-
-1. Download and extract the Cordova 2.8.0 source to a permanent directory location on your hard drive, for example to `~/Cordova-2.8.0`.
-
-2. Quit any running SDK tools: Eclipse, Momentics and the like.
-
-3. Navigate to the directory where you put the downloaded source above, using a unix like terminal: Terminal.app, Bash, Cygwin, etc.
-
-4. Create a new project, as described in BlackBerry Shell Tool Guide. This becomes the home of your updated project.
-
-5. Copy your projects source from the old project's `/www` directory to the new project's `/www` directory.
-
-6. Update the Cordova script reference in the `www/index.html` file (and any other files that contain the script reference) to point to the new `cordova.js` file.
-
-For BlackBerryOS/Playbook:
-
-1. Download and extract the Cordova 2.8.0 source to a permanent directory location on your hard drive, for example to `~/Cordova-2.8.0`.
-
-2. Quit any running SDK tools: Eclipse, Momentics and the like.
-
-3. Navigate to the directory where you put the downloaded source above, using a unix like terminal: Terminal.app, Bash, Cygwin, etc.
-
-4. Create a new project, as described in BlackBerry Shell Tool Guide. You need the assets from this new project.
-
-5. Copy the `www/cordova.js` file from the new project into the `www` directory, and delete the `www/cordova.js` file.
-
-6. Update the Cordova script reference in the `www/index.html` file (and any other files that contain the script reference) to point to the new `cordova.js` file.
-
-7. Copy the `native` directory from the new project into the existing project, overwriting the old `native` directory.
-
-8. Copy the `lib` directory from the new project into the existing project, overwriting the old `lib` directory.
-
-9. Copy the `cordova` directory from the new project into the existing project, overwriting the old `cordova` directory.
-
-## Upgrading 2.6.0 Projects to 2.7.0
-
-1. Download and extract the Cordova 2.7.0 source to a permanent directory location on your hard drive, for example to `~/Cordova-2.7.0`.
-
-2. Quit any running SDK tools: Eclipse, Momentics and the like.
-
-3. Navigate to the directory where you put the downloaded source above, using a unix like terminal: Terminal.app, Bash, Cygwin, etc.
-
-4. Create a new project, as described in BlackBerry Shell Tool Guide. You need the assets from this new project.
-
-5. Copy the `www/cordova-2.7.0.js` file from the new project into the `www` directory, and delete the `www/cordova-2.6.0.js` file.
-
-6. Update the Cordova script reference in the `www/index.html` file (and any other files that contain the script reference) to point to the new `cordova-2.7.0.js` file.
-
-7. Copy the `native` directory from the new project into the existing project, overwriting the old `native` directory.
-
-8. Copy the `lib` directory from the new project into the existing project, overwriting the old `lib` directory.
-
-9. Copy the `cordova` directory from the new project into the existing project, overwriting the old `cordova` directory.
-
-## Upgrade to 2.6.0 from 2.5.0
-
-Updating the PhoneGap download directory:
-
-It is recommended that you download a fresh copy of the entire directory.
-
-However, here are the new parts needed for the piecemeal update:
-
-1. Update the cordova.blackberry.js file in the `Phonegap-2.6.0/lib/blackberry/javascript` directory.
-
-2. Update the `ext`, `ext-air`, and `ext-qnx` in the `Phonegap-2.6.0/lib/blackberry/framework` directory.
-
-3. Update the `build.xml` file in the `Phonegap-2.6.0/lib/blackberry` directory.
-
-4. Update the `Phonegap-2.6.0/lib/blackberry/bin` directory.
-
-5. Update the `VERSION` file in the `Phonegap-2.6.0/lib/blackberry` directory.
-
-Updating the example/ directory or migrating an existing project:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Update the contents of the `ext-qnx/` directory.
-
-4. Copy the new `cordova-2.6.0.js` into your project.
-
-5. Update your HTML to use the new `cordova-2.6.0.js` file.
-
-## Upgrade to 2.5.0 from 2.4.0
-
-Updating the PhoneGap download directory:
-
-It is recommended that you download a fresh copy of the entire directory.
-
-However, here are the new parts needed for the piecemeal update:
-
-1. Update the cordova.blackberry.js file in the `Phonegap-2.5.0/lib/blackberry/javascript` directory.
-
-2. Update the `ext`, `ext-air`, and `ext-qnx` in the `Phonegap-2.5.0/lib/blackberry/framework` directory.
-
-3. Update the `build.xml` file in the `Phonegap-2.5.0/lib/blackberry` directory.
-
-4. Update the `Phonegap-2.5.0/lib/blackberry/bin` directory.
-
-5. Update the `VERSION` file in the `Phonegap-2.5.0/lib/blackberry` directory.
-
-Updating the example/ directory or migrating an existing project:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Update the contents of the `ext-qnx/` directory.
-
-4. Copy the new `cordova-2.5.0.js` into your project.
-
-5. Update your HTML to use the new `cordova-2.5.0.js` file.
-
-## Upgrade to 2.4.0 from 2.3.0
-
-Updating just the `www` directory:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Copy the new `cordova-2.4.0.js` into your project.
-    - If playbook, then update the .js file in the `playbook/` directory.
-    - If BlackBerry 10, then update the .js file in the `qnx/` directory.
-
-5. Update your HTML to use the new `cordova-2.4.0.js` file.
-
-Updating the sample directory (i.e., updating using the ant tools):
-
-1. Open the `sample/lib/` directory.
-
-2. Update the .jar file in the `cordova.2.3.0/ext/` directory.
-
-3. Update the contents of the `cordova.2.3.0/ext-air/` directory.
-
-4. Update the contents of the `cordova.2.3.0/ext-qnx/` directory.
-
-5. Update the .js file in the `cordova.2.3.0/javascript/` directory.
-
-6. Open the `sample/lib/` directory and rename the `cordova.2.3.0/` directory to `cordova.2.4.0/`.
-
-7. Type `ant blackberry build` or `ant playbook build` to update the `www` directory with updated Cordova.
-
-8. Open the `www` directory and update your HTML to use the new `cordova-2.4.0.js` file.
-
-## Upgrade to 2.3.0 from 2.2.0
-
-Updating just the `www` directory:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Copy the new `cordova-2.3.0.js` into your project.
-    - If playbook, then update the .js file in the `playbook/` directory.
-    - If BlackBerry 10, then update the .js file in the `qnx/` directory.
-
-5. Update your HTML to use the new `cordova-2.3.0.js` file.
-
-Updating the sample directory (i.e., updating using the ant tools):
-
-1. Open the `sample/lib/` directory.
-
-2. Update the .jar file in the `cordova.2.2.0/ext/` directory.
-
-3. Update the contents of the `cordova.2.2.0/ext-air/` directory.
-
-4. Update the contents of the `cordova.2.2.0/ext-qnx/` directory.
-
-5. Update the .js file in the `cordova.2.2.0/javascript/` directory.
-
-6. Open the `sample/lib/` directory and rename the `cordova.2.2.0/` directory to `cordova.2.3.0/`.
-
-7. Type `ant blackberry build` or `ant playbook build` to update the `www` directory with updated Cordova.
-
-8. Open the `www` directory and update your HTML to use the new `cordova-2.3.0.js` file.
-
-## Upgrade to 2.2.0 from 2.1.0
-
-Updating just the www directory:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Copy the new `cordova-2.2.0.js` into your project.
-    - If playbook, then update the .js file in the `playbook/` directory.
-    - If BlackBerry 10, then update the .js file in the `qnx/` directory.
-
-5. Update your HTML to use the new `cordova-2.2.0.js` file.
-
-Updating the sample directory (i.e., updating using the ant tools):
-
-1. Open the `sample/lib/` directory.
-
-2. Update the .jar file in the `cordova.2.1.0/ext/` directory.
-
-3. Update the contents of the `cordova.2.1.0/ext-air/` directory.
-
-4. Update the contents of the `cordova.2.1.0/ext-qnx/` directory.
-
-5. Update the .js file in the `cordova.2.1.0/javascript/` directory.
-
-6. Open the `sample/lib/` directory and rename the `cordova.2.1.0/` directory to `cordova.2.2.0/`.
-
-7. Type `ant blackberry build` or `ant playbook build` to update the `www` directory with updated Cordova.
-
-8. Open the `www` directory and update your HTML to use the new `cordova-2.2.0.js` file.
-
-## Upgrade to 2.1.0 from 2.0.0
-
-Updating just the `www` directory:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Copy the new `cordova-2.1.0.js` into your project.
-    - If playbook, then update the .js file in the `playbook/` directory.
-
-5. Update your HTML to use the new `cordova-2.1.0.js` file.
-
-Updating the sample directory (i.e., updating using the ant tools):
-
-1. Open the `sample/lib/` directory.
-
-2. Update the .jar file in the `cordova.2.0.0/ext/` directory.
-
-3. Update the contents of the `cordova.2.0.0/ext-air/` directory.
-
-4. Update the .js file in the `cordova.2.0.0/javascript/` directory.
-
-5. Open the `sample/lib/` directory and rename the `cordova.2.0.0/` directory to `cordova.2.1.0/`.
-
-6. Type `ant blackberry build` or `ant playbook build` to update the `www` directory with updated Cordova.
-
-7. Open the `www` directory and update your HTML to use the new `cordova-2.1.0.js` file.
-
-## Upgrade to 2.0.0 from 1.9.0
-
-Updating just the `www` directory:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Copy the new `cordova-2.0.0.js` into your project.
-    - If playbook, then update the .js file in the `playbook/` directory.
-
-5. Update your HTML to use the new `cordova-2.0.0.js` file.
-
-6. Update the `www/plugins.xml` file. Two plugins changed their
-   namespace/service label. Change the old entries for the Capture and
-   Contact plugins from:
-
-        <plugin name="Capture" value="org.apache.cordova.media.MediaCapture"/>
-        <plugin name="Contact" value="org.apache.cordova.pim.Contact"/>
-
-   To:
-
-        <plugin name="Capture" value="org.apache.cordova.capture.MediaCapture"/>
-        <plugin name="Contacts" value="org.apache.cordova.pim.Contact"/>
-
-Updating the sample directory (i.e., updating using the ant tools):
-
-1. Open the `sample/lib/` directory.
-
-2. Update the .jar file in the `cordova.1.9.0/ext/` directory.
-
-3. Update the contents of the `cordova.1.9.0/ext-air/` directory.
-
-4. Update the .js file in the `cordova.1.9.0/javascript/` directory.
-
-5. Open the `sample/lib/` directory and rename the `cordova.1.9.0/` directory to `cordova.2.0.0/`.
-
-6. Type `ant blackberry build` or `ant playbook build` to update the `www` directory with updated Cordova.
-
-7. Open the `www` directory and update your HTML to use the new `cordova-2.0.0.js` file.
-
-8. Open the `www` directory and update the `plugins.xml` file. Two plugins
-   changed their namespace/service label. Change the old entries for the
-   Capture and Contact plugins from:
-
-    ```xml
-    <plugin name="Capture" value="org.apache.cordova.media.MediaCapture"/>
-    <plugin name="Contact" value="org.apache.cordova.pim.Contact"/>
-    ```
-
-    To:
-
-    ```xml
-    <plugin name="Capture" value="org.apache.cordova.capture.MediaCapture"/>
-    <plugin name="Contacts" value="org.apache.cordova.pim.Contact"/>
-    ```
-
-- To upgrade to 1.8.0, please go from 1.7.0
-
-## Upgrade to 1.8.0 from 1.7.0
-
-Updating just the `www` directory:
-
-1. Open the `www` directory, which contains the app.
-
-2. Remove and update the .jar file in the `ext/` directory.
-
-3. Update the contents of the `ext-air/` directory.
-
-4. Copy the new `cordova-1.8.0.js` into your project.
-    - If playbook, then update the .js file in the `playbook/` directory.
-
-5. Update your HTML to use the new `cordova-1.8.0.js` file.
-
-6. Update the `www/plugins.xml` file. Two plugins changed their
-   namespace/service label. Change the old entries for the Capture and
-   Contact plugins from:
-
-    ```xml
-    <plugin name="Capture" value="org.apache.cordova.media.MediaCapture"/>
-    <plugin name="Contact" value="org.apache.cordova.pim.Contact"/>
-    ```
-
-    To:
-
-    ```xml
-    <plugin name="Capture" value="org.apache.cordova.capture.MediaCapture"/>
-    <plugin name="Contacts" value="org.apache.cordova.pim.Contact"/>
-    ```
-
-Updating the sample directory (i.e., updating using the ant tools):
-
-1. Open the `sample/lib/` directory.
-
-2. Update the .jar file in the `cordova.1.7.0/ext/` directory.
-
-3. Update the contents of the `cordova.1.7.0/ext-air/` directory.
-
-4. Update the .js file in the `cordova.1.7.0/javascript/` directory.
-
-5. Open the `sample/lib/` directory and rename the `cordova.1.7.0/` directory to `cordova.1.8.0/`.
-
-6. Type `ant blackberry build` or `ant playbook build` to update the `www` directory with updated Cordova.
-
-7. Open the `www` directory and update your HTML to use the new `cordova-1.8.0.js` file.
-
-8. Open the `www` directory and update the `plugins.xml` file. Two plugins
-   changed their namespace/service label. Change the old entries for the
-   Capture and Contact plugins from:
-
-    ```xml
-    <plugin name="Capture" value="org.apache.cordova.media.MediaCapture"/>
-    <plugin name="Contact" value="org.apache.cordova.pim.Contact"/>
-    ```
-
-    To:
-
-    ```xml
-    <plugin name="Capture" value="org.apache.cordova.capture.MediaCapture"/>
-    <plugin name="Contacts" value="org.apache.cordova.pim.Contact"/>
-    ```
diff --git a/www/docs/en/dev/guide/platforms/ubuntu/index.md b/www/docs/en/dev/guide/platforms/ubuntu/index.md
deleted file mode 100644
index 9fbe1ff44..000000000
--- a/www/docs/en/dev/guide/platforms/ubuntu/index.md
+++ /dev/null
@@ -1,232 +0,0 @@
----
-license: >
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-        http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
-
-title: Ubuntu Platform Guide
-toc_title: Ubuntu
----
-
-# Ubuntu Platform Guide
-
-This guide shows how to set up a development environment for creating Cordova applications for Ubuntu.
-
-You will need an Ubuntu system for building applications, either running natively or in a virtual machine. You will also need an Ubuntu phone for testing your application, though an emulator can be used for basic verifications.
-
-## Development Platform Requirements
-
-### Minimum and Recommended Versions
-
-Developing Cordova apps requires a system running Ubuntu.
-
-The recommended environment is Ubuntu 16.04 LTS, running NodeJS 4.2.x and NPM 2.15.x. 
-
-Packages are still available for systems running the previous LTS release (14.04) but some components like NodeJS or phablet-shell may not support all of the latest options.
-
-The target environment is an Ubuntu phone, supporting at least the ubuntu-sdk-api-15.04 framework. All phones on the market, or development images, support that framework by default.
-
-The cordova-ubuntu platform support code requires at least cordova-cli 4.3.1. This is the minimum and recommended version at the time of this writing. cordova-ubuntu 4.3.x releases are all compatible with that tool release.
-
-For the latest information on Cordova app support for Ubuntu runtime platforms,
-see [wiki.ubuntu.com/Cordova](http://wiki.ubuntu.com/Cordova).
-
-## Installing the Development Environment
-
-### Install Ubuntu
-
-Installation images of Ubuntu 16.04 LTS are available at http://www.ubuntu.com/download
-
-The simplest option is to download an Ubuntu Desktop image.
-
-In any case, the Debian packaging system will ensure that all underlying dependencies for the development environment will be installed. This lets you also install a build environment from an Ubuntu server installation as well.
-
-### Ubuntu Virtual Machine (optional)
-
-Ubuntu can also be used in a virtual machine.
-
-You can get an Ubuntu instance on all of the leading public clouds. In fact, Ubuntu is the most popular cloud operating system (http://www.ubuntu.com/cloud/public-cloud). Running in the cloud will let you build your Cordova application. However you will still need to connect a local instance to a phone via USB for testing your app.
-
-You can also install Ubuntu in local VM, with Virtualbox, VMWare or Parallels on either Windows or Mac OS. That configuration lets you re-direct a USB port inside the virtual machine, to let the Ubuntu build system access the Ubuntu phone hardware and install the app for testing.
-
-Refer to the documentation for either your public cloud of choice, or the local virtual machine for the details of the installation procedure.
-
-Once you have a basic Ubuntu VM set up, you can install the rest of the required elements below.
-
-### Node and NPM
-
-Ubuntu 16.04 LTS comes with the required versions of both NodeJS and NPM. To install simlpy do:
-
-```bash
-$ sudo apt-get install nodejs npm
-$ node -v
-v.4.2.6
-$ npm -v
-2.15.6
-```
-
-### Cordova CLI
-
-The Cordova command line interface can be installed either via npm, or you can use a pre-packaged version available specifically for Ubuntu.
-
-The recommended installation path is to use the pre-packaged version for Ubuntu, as it generally contains Ubuntu specific fixes which may not all have been merged upstream.
-
-Installing the cordova-cli deb package requires to:
-1. Add the Ubuntu Cordova
-[Personal Package Archive](https://launchpad.net/~cordova-ubuntu/+archive/ppa)
-to your Ubuntu system
-1. Install the cordova-cli package (and its dependencies)
-
-```bash
-$ sudo apt-add-repository ppa:cordova-ubuntu/ppa
-$ sudo apt-get update
-$ sudo apt-get install cordova-cli
-```
-
-### Add an Ubuntu "click chroot"
-
-The build environment needs to be separated from the developer's environment, to prevent unwanted side effects and provide a clean, repeatable process.
-
-Ubuntu devices currently use the click packaging system.
-
-To produce click packages, a "click chroot" is required. It is a separate build environment designed to produce binaries, by having a build tools and dependencies contained inside a chroot.
-
-Generally, a click chroot hosts cross-compilation tools which can produce binaries for a different architecture (like armhf) than the one of the developer's system (generally x86).
-
-Last, the click chroot will need to be provisionned with libraries, or more generally "frameworks", corresponding to the target environment.
-
-Ubuntu devices will support the ubuntu-sdk-15.04 framework or later versions.
-
-### Create a click chroot environment
-
-```bash
-$ sudo apt-add-repository ppa:ubuntu-sdk-team/ppa
-$ sudo apt-get update
-# this will create a clean click chroot build environment
-sudo apt-get install click-dev phablet-tools ubuntu-sdk-api-15.04
-```
-
-### Add build dependencies for Cordova
-
-```bash
-# add build dependencies inside the click chroot
-sudo click chroot -a armhf -f ubuntu-sdk-15.04 install cmake libicu-dev:armhf pkg-config qtbase5-dev:armhf qtchooser qtdeclarative5-dev:armhf qtfeedback5-dev:armhf qtlocation5-dev:armhf qtmultimedia5-dev:armhf qtpim5-dev:armhf libqt5sensors5-dev:armhf qtsystems5-dev:armhf
-```
-
-### Ubuntu IDE (optional)
-
-You may also want to install the Ubuntu QtCreator development environment. See
-[developer.ubuntu.com](http://developer.ubuntu.com) for more info. (The
-QtCreator SDK is not required to add Ubuntu platform support to your Cordova
-app.)
-
-
-## Project Workflow
-
-To test your installation, or simply to start developing an application, you can follow the steps below.
-
-### Create a project
-
-Creates an app in a `hello` directory whose display name is
-`HelloWorld`:
-
-```bash
-$ cordova create helloworld helloworld.ubuntudeveloper HelloWorld
-$ cd hello
-$ cordova platform add ubuntu
-```
-
-Note that Ubuntu applications use a pair <appname>.<username> as a naming convention.
-
-### Add a Plugin
-
-```bash
-$ cordova plugin add cordova-plugin-camera
-```
-
-### Build for Ubuntu devices
-
-```bash
-$ cordova build --device
-```
-
-You can see detailed build logs with the following options:
-```bash
-$ cordova -d build --device -- --verbose
-```
-
-You can build your app for a different target framework by specifying the option below:
-```bash
-$ cordova -d build --device -- --framework=ubuntu-sdk-16.04
-```
-
-Note that for the latter to work, you will need to have a corresponding click chroot installed on your build system.
-
-### Run the App on an Ubuntu device
-
-```bash
-$ cordova run --device
-```
-
-This will:
-1. build the app for the device target
-1. package it using the click packaging system
-1. transfer the app on the device
-1. stop the app if it was already running
-1. install the app
-1. start the app
-
-
-## Debugging
-
-You can enable chrome devtools support to debug your app, by adding the --debug flag:
-
-```bash
-$ cordova run --device --debug
-```
-
-Then simply connect to the URL mentioned in the logs.
-
-## Publishing your app
-
-Once you have finished developing and testing your app, you can publish it on the Ubuntu App Store.
-
-### Generate and verify the package
-
-Your app is already packaged in a format compatible with the app store. Just find the .click package generate by the cordova-ubuntu build system:
-
-```bash
-$ cordova build --device
-$ find -name "*.click"
-```
-
-You can manually verify that the package passes all verification steps enforced by the Ubuntu App Store system, by using the click-reviewer-tools:
-
-```bash
-$ click review -v <click file>
-```
-
-Note: this step is done automatically by the build system as well.
-
-### Sign up and upload to the app store
-
-You need to first create a free developer account on the Ubuntu App Store.
-
-Then you will be able to upload your package to the store and make it available to all users of Ubuntu devices.
-
-The full process is documented online at https://developer.ubuntu.com/en/publish/
-
-
diff --git a/www/docs/en/dev/guide/platforms/wp8/home.md b/www/docs/en/dev/guide/platforms/wp8/home.md
deleted file mode 100644
index e7ed71e37..000000000
--- a/www/docs/en/dev/guide/platforms/wp8/home.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-license: >
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-        http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
-
-title: WP8 Guides
-toc_title: WP8
----
-
-# WP8 Guides
-
-* [Windows Phone 8 Platform Guide](index.html)
-* [Windows Phone 8 Plugins](plugin.html)
-* [Upgrading Windows Phone 8](upgrade.html)
\ No newline at end of file
diff --git a/www/docs/en/dev/guide/platforms/wp8/index.md b/www/docs/en/dev/guide/platforms/wp8/index.md
deleted file mode 100644
index 04732c7d1..000000000
--- a/www/docs/en/dev/guide/platforms/wp8/index.md
+++ /dev/null
@@ -1,256 +0,0 @@
----
-license: >
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-        http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
-
-title: Windows Phone 8 Platform Guide
----
-
-# Windows Phone 8 Platform Guide
-
-This guide shows how to set up your SDK development environment to
-deploy Cordova apps for Windows Phone devices.  It focuses on Windows
-Phone 8, but provides additional details on how to support Windows
-Phone 7.
-
-It shows how to use either Windows Phone-specific shell tools to
-generate and build apps, or the cross-platform Cordova CLI discussed
-in [The Command-Line Interface](../../cli/index.html).  (See the [Overview](../../overview/index.html) for a comparison of
-these development workflows.) This section also shows how to open
-Cordova apps so that you can modify them within Visual Studio.
-Regardless of which approach you take, you need to install the Windows
-Phone SDK, as described below.
-
-See the following for details specific to the Windows Phone platform:
-
-- [Windows Phone 8 Plugins](plugin.html)
-- [Upgrading Windows Phone 8](upgrade.html)
-
-For the Windows Phone 8 platform, the Cordova WebView relies on
-Internet Explorer 10 as its rendering engine, so as a practical matter
-you can use IE10's powerful debugger to test any web content that
-doesn't invoke Cordova APIs.  The Windows Phone Developer Blog
-provides
-[helpful guidance](http://blogs.windows.com/windows_phone/b/wpdev/archive/2012/11/15/adapting-your-webkit-optimized-site-for-internet-explorer-10.aspx)
-on how to support IE10 along with comparable WebKit browsers.
-
-## Requirements and Support
-
-You need the following:
-
-- A 64-bit version of Windows 8 Pro, either an installation disk or an
-  _ISO_ disk image file. An evaluation version is available on the
-  [Microsoft Developer Network](http://msdn.microsoft.com/en-US/evalcenter/jj554510).
-  The Pro version is necessary to run the device emulator.
-
-- The [Windows Phone SDK](http://www.microsoft.com/en-us/download/details.aspx?id=35471).
-
-- In order to deploy via the command-line with the Windows Phone 8.0 SDK,
-[Visual Studio 2012 Update 2](https://support.microsoft.com/en-us/kb/2797912)
-must be installed.
-
-To develop Cordova apps for Windows Phone devices, you may use a PC
-running Windows, but you may also develop on a Mac, either by running
-a virtual machine environment or by using Boot Camp to dual-boot a
-Windows partition. Consult these resources to set up the required
-Windows development environment on a Mac:
-
-- __VMWare Fusion__: To set up the Windows 8 virtual machine, follow
-  the instructions provided by the
-  [Microsoft Developer Network](http://msdn.microsoft.com/en-US/library/windows/apps/jj945426),
-  then see [Configuring VMWare Fusion](vmware.html) for information on preparing the
-  virtual environment to run the emulator bundled with the SDK.
-
-- __Parallels Desktop__: To set up the Windows 8 virtual machine,
-  follow the instructions provided by the
-  [Microsoft Developer Network](http://msdn.microsoft.com/en-US/library/windows/apps/jj945424),
-  then see [Configuring Parallels Desktop](parallels.html) for information on preparing
-  the virtual environment to run the emulator bundled with the SDK.
-  
-<!--
-- __VirtualBox__: To set up the Windows 8 virtual machine, follow the
-  installation instructions provided by the [Microsoft Developer
-  Network](http://msdn.microsoft.com/en-US/library/windows/apps/jj945425).
-
-  2DO: virtualBox doesn't work yet; any extra config info?
--->
-
-- __Boot Camp__: To set up the Windows 8 partition, follow the
-  installation instructions provided by the [Microsoft Developer
-  Network](http://msdn.microsoft.com/en-US/library/windows/apps/jj945423).
-  
-If you are developing on a PC, its processor must support
-virtualization (_VT-x_ on Intel) and [Second Level Address Translation
-(SLAT)](http://en.wikipedia.org/wiki/Second_Level_Address_Translation).
-Consult [Intel's list of supporting
-processors](http://ark.intel.com/Products/VirtualizationTechnology).
-Virtualization is typically disabled by default, so you need to enable
-it in your BIOS settings. The PC should have at least 6.5GB of free
-hard disk space, and 4GB of RAM.
-
-## Using Cordova Shell Tools
-
-If you want to use Cordova's Windows Phone-centered shell tools in
-conjunction with the SDK, you have two basic options:
-
-- Access them locally from project code generated by the CLI. They are
-  available in the `platforms/wp8/cordova` directory after you add the
-  `wp8` platform as described below.
-
-- Download them from a separate distribution at
-  [cordova.apache.org](http://cordova.apache.org).  The Cordova
-  distribution contains separate archives for each platform.  Be sure
-  to expand the appropriate archive, `cordova-wp8\wp8` in this case,
-  within an empty directory.  The relevant batch utilities are
-  available in the top-level `bin` directory. (Consult the __README__
-  file if necessary for more detailed directions.)
-
-These shell tools allow you to create, build, and run Windows Phone
-apps.  For information on the additional command-line interface that
-enables plugin features across all platforms, see Using Plugman to
-Manage Plugins. See Application Plugins for guidance on how to develop
-plugins, and [Windows Phone 8 Plugins](plugin.html) for details specific to the Windows
-Phone platform.
-
-## Install the SDK
-
-Install the latest version of the Windows Phone SDK from the
-__Downloads__ area of
-[dev.windowsphone.com](https://dev.windowsphone.com/en-us/downloadsdk).
-You may also install more recent emulator update packages.
-
-![]({{ site.baseurl }}/static/img/guide/platforms/wp8/wp8_downloadSDK.png)
-
-## Create a New Project
-
-At this point, to create a new project you can choose between the
-cross-platform CLI tool described in [The Command-Line Interface](../../cli/index.html), or
-the set of Windows Phone-specific shell tools. From within a
-source-code directory, here's the CLI approach:
-
-        > cordova create hello com.example.hello HelloWorld
-        > cd hello
-        > cordova platform add wp8
-
-Here's the corresponding lower-level shell-tool approach:
-
-        C:\path\to\cordova-wp8\bin\create.bat C:\path\to\new\hello com.example.hello HelloWorld
-
-## Build the Project
-
-If you are using the CLI in development, the project directory's
-top-level `www` directory contains the source files. Run either of
-these within the project directory to rebuild the app:
-
-        > cordova build
-        > cordova build wp8   # do not rebuild other platforms
-
-If you are using the Windows Phone-specific shell tools in
-development, there is a different approach.  Once you generate the
-project, the default app's source is available in the
-`projects\wp8\www` subdirectory. Subsequent commands are available in
-the `cordova` subdirectory at the same level.
-
-The `build` command cleans project files and rebuilds the app.  The first
-example generates debugging information, and the second signs the apps
-for release:
-
-        C:\path\to\project\cordova\build.bat --debug        
-        C:\path\to\project\cordova\build.bat --release
-
-The `clean` command helps flush out directories in preparation for the
-next `build`:
-
-        C:\path\to\project\cordova\clean.bat
-
-## Deploy to Emulator
-
-At this point you can use the `cordova` CLI utility to deploy the
-application to the emulator from the command line:
-
-        > cordova emulate wp8
-
-Otherwise use the alternate shell interface:
-
-        C:\path\to\project\cordova\run
-
-By default, the `run` script invokes the emulator flag, and accepts
-additional build flags, for which `--debug` provides the default:
-
-        C:\path\to\project\cordova\run --emulator --debug
-        C:\path\to\project\cordova\run --emulator --release
-        C:\path\to\project\cordova\run --emulator --nobuild
-
-The emulator launches a device image with the app installed. From the
-home screen, navigate to the apps panel to launch the __HelloWorld__
-app. This shows the app launching with its splash screen followed by
-its main interface:
-
-![]({{ site.baseurl }}/static/img/guide/platforms/wp8/wp8_emulator.png)
-
-The emulator's basic controls on the top-right of the device screen
-allow you to toggle between portrait and landscape orientation. The
-__>>__ button opens more controls that allow you to test more complex
-orientations and gestures:
-
-![]({{ site.baseurl }}/static/img/guide/platforms/wp8/wp8_emulator_orient.png)
-
-These advanced controls also allow you to modify the device's
-location or to simulate sequences of movements:
-
-![]({{ site.baseurl }}/static/img/guide/platforms/wp8/wp8_emulator_loc.png)
-
-## Deploy to Device
-
-Before testing your application on a device, the device must be
-registered. Consult [Microsoft's
-documentation][1]
-for details on how to deploy and test on Windows Phone 8. Also, make
-sure the phone is connected to the computer, and the screen is
-unlocked.
-
-Then run the following CLI command to run the app on the device:
-
-    > cordova run wp8
-
-It corresponds to this lower-level shell command:
-
-    C:\path\to\project\cordova\run --device
-
-Alternately, if you are working in Visual Studio, select __Windows
-Phone Device__ from the drop-down menu at the top, then press the
-green __Play__ button nearby or else type __F5__.
-
-## Modify the Project in the SDK
-
-Once you build a Cordova app as described above, you can open it with
-the SDK. The various `build` commands generates a Visual Studio
-Solution (_.sln_) file. Open the file to modify the project within
-Visual Studio. The web-based source code is available within the
-project's `www` directory. Along with other tools the SDK provides,
-the control below the menu allows you to launch the app in a Windows
-Phone emulator:
-
-![]({{ site.baseurl }}/static/img/guide/platforms/wp8/wp8_vs.png)
-
-Consult the [Overview](../../overview/index.html) for advice on how to use Cordova's command-line
-tools or the SDK in your workflow. The Cordova CLI relies on
-cross-platform source code that routinely overwrites the
-platform-specific files used by the SDK. If you want to work within
-the SDK, use the lower-level shell tools as an alternative to the CLI.
-
-[1]: http://msdn.microsoft.com/en-us/library/windowsphone/develop/ff402565.aspx
diff --git a/www/docs/en/dev/guide/platforms/wp8/parallels.md b/www/docs/en/dev/guide/platforms/wp8/parallels.md
deleted file mode 100644
index 9a9501808..000000000
--- a/www/docs/en/dev/guide/platforms/wp8/parallels.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-license: >
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-        http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
-
-title: Configuring Parallels Desktop
----
-
-# Configuring Parallels Desktop
-
-This section shows how to configure Parallels Desktop on a Mac so that
-you can use Cordova to generate Windows Phone applications.
-
-The
-[Microsoft Developer Network](http://msdn.microsoft.com/en-US/library/windows/apps/jj945424)
-provides general instructions for how to run Windows under Parallels
-Desktop. After installing Windows, follow these steps:
-
-1. Within Parallels Desktop, select the Windows 8 disk image you have
-   prepared, and choose __Settings__.
-
-1. Choose the __General &rarr; CPUs__ options. Specify _two_ CPUs.
-   Specify at least 2GB of memory, even if it falls outside the
-   recommended range:
-
-   ![]({{ site.baseurl }}/static/img/guide/platforms/wp8/parallel_cpu_opts.png)
-
-1. To be able to run the device emulator image within the Windows 8
-   virtual machine, choose the __Optimizations__ options and enable
-   __Nested Virtualization__.
-
-   ![]({{ site.baseurl }}/static/img/guide/platforms/wp8/parallel_optimize_opts.png)
-
-Once you complete these steps, you are ready to install the Windows
-Phone SDK.  See the [Windows Phone 8 Platform Guide](index.html) for details.
diff --git a/www/docs/en/dev/guide/platforms/wp8/plugin.md b/www/docs/en/dev/guide/platforms/wp8/plugin.md
deleted file mode 100644
index a7108ba1c..000000000
--- a/www/docs/en/dev/guide/platforms/wp8/plugin.md
+++ /dev/null
@@ -1,242 +0,0 @@
----
-license: >
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-        http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
-
-title: Windows Phone 8 Plugins
-toc_title: WP8
----
-
-# Windows Phone 8 Plugins
-
-This section provides details for how to implement native plugin code
-on the Windows Phone platform. Before reading this, see [Plugin Development Guide](../../hybrid/plugins/index.html)
-for an overview of the plugin's structure and its common
-JavaScript interface. This section continues to demonstrate the sample
-_echo_ plugin that communicates from the Cordova webview to the native
-platform and back.
-
-Writing a plugin for Cordova on Windows Phone requires a basic
-understanding of Cordova's architecture. Cordova-WP8 consists of a
-`WebBrowser` that hosts the application's JavaScript code and manages
-native API calls. You can extend a C# `BaseCommand` class
-(`WPCordovaClassLib.Cordova.Commands.BaseCommand`), which comes with
-most of the functionality you need:
-
-1. Select your project, and right-click to choose __Add &rarr; New
-   Item...__ If you wish, you can add it to the `Plugins` folder.
-
-2. Select __Class__ and name it `Echo.cs`.  This class name must
-   _exactly_ match what you call specify as the service in the
-   `cordova.exec()` call on the JavaScript side.
-
-3. Include the base classes implementation:
-
-        using WPCordovaClassLib.Cordova;
-        using WPCordovaClassLib.Cordova.Commands;
-        using WPCordovaClassLib.Cordova.JSON;
-
-4. Extend your class from `BaseCommand`:
-
-        public class Echo : BaseCommand
-        {
-            // ...
-        }
-
-5. Add an `echo` method that is callable from JavaScript:
-
-        public class Echo : BaseCommand
-        {
-            public void echo(string options)
-            {
-                // all JS callable plugin methods MUST have this signature!
-                // public, returning void, 1 argument that is a string
-            }
-        }
-
-See the
-[BaseCommand.cs](https://github.com/apache/cordova-wp8/blob/master/wp8/template/cordovalib/Commands/BaseCommand.cs)
-class for methods available for the plugin to override.  For example,
-the plugin can capture [pause][PauseEvent] and [resume][ResumeEvent] events.
-
-## Namespaces
-
-The default namespace for unqualified commands is:
-
-        namespace Cordova.Extension.Commands
-        {
-            // ...
-        }
-
-If you want to specify your own namespace, you need to make a fully
-qualified call to `cordova.exec`. For example, if you want to define
-your C# class like this:
-
-        namespace com.mydomain.cordovaExtensions
-        {
-            public class Echo : BaseCommand
-            {
-                // ...
-            }
-        }
-
-The JavaScript would need to call `exec` like this:
-
-        cordova.exec(win, fail, "com.mydomain.cordovaExtensions.Echo", ...);
-
-## Interpreting Arguments in C#
-
-In the example discussed in Application Plugins, the data your plugin
-receives is a string, but what if you want to pass an array of
-strings?  Suppose the JavaScript `cordova.exec` call is specified like
-this:
-
-        cordova.exec(win, fail, "Echo", "echo", ["input string"]);
-
-The value of `options` string passed to the `Echo.echo` method is
-JSON:
-
-        "[\"input string\"]"
-
-All JavaScript `exec` arguments are JSON-encoded before being passed
-into C#, and so need to be decoded:
-
-        string optVal = JsonHelper.Deserialize<string[]>(options)[0];
-        // optVal now has the value of "input string"
-
-## Passing Results from C# to JavaScript
-
-The `BaseCommand` class provides methods to pass data to JavaScript
-callback handlers.  If you simply want to signal success with no
-accompanying result, you can simply call:
-
-        DispatchCommandResult();
-        // calls back with an empty plugin result, considered a success callback
-
-To pass data back, you need to call `DispatchCommandResult`
-differently:
-
-        DispatchCommandResult(new PluginResult(PluginResult.Status.OK, "Everything went as planned, this is a result that is passed to the success handler."));
-
-Use an encoded JSON string to pass structured object data back to
-JavaScript:
-
-        DispatchCommandResult(new PluginResult(PluginResult.Status.OK, "{result:\"super awesome!\"}"));
-
-To signal an error, call `DispatchCommandResult` with a `PluginResult`
-object whose status is `ERROR`:
-
-        DispatchCommandResult(new PluginResult(PluginResult.Status.ERROR, "Echo signaled an error"));
-
-## Handling Serialization Errors
-
-When interpreting your arguments, `try`/`catch` blocks help screen out
-bad input. This pattern appears throughout the Cordova C# code:
-
-        string optVal = null;
-
-        try
-        {
-            optVal = JsonHelper.Deserialize<string[]>(options)[0];
-        }
-        catch(Exception)
-        {
-            // simply catch the exception, we handle null values and exceptions together
-        }
-
-        if (optVal == null)
-        {
-            DispatchCommandResult(new PluginResult(PluginResult.Status.JSON_EXCEPTION));
-        }
-        else
-        {
-            // ... continue on to do our work
-        }
-
-## Plugin Lifetime
-
-Plugins with long-running requests, background activity such as media
-playback, listeners, or that maintain internal state should implement
-the `onReset` method to clean up those activities. The method runs
-when the CordovaView WebBrowser navigates to a new page or refreshes, which
-reloads the JavaScript.
-
-        // defined in WPCordovaClassLib.Cordova.Commands.BaseCommand
-        public virtual void OnReset() { }
-
-## Plugin XML
-
-The following shows how to use the `plugin.xml` file to specify a
-plugin's source files on the Windows Phone platform.  See Application
-Plugins for an overview, and [Plugin Specification](../../../plugin_ref/spec.html) for details on
-available options.
-
-- The `<source-file>` element defines all plugin resources, such
-  as _.cs_, _.xaml_, _.xaml.cs_, and _.dll_ files, and image assets.
-
-- The `<config-file>` element defines elements to inject into a
-  configuration file. This example adds a plugin to the platform's
-  `config.xml` file:
-
-        <config-file target="config.xml" parent="/*">
-            <feature name="PluginName">
-                <param name="wp-package" value="PluginName"/>
-            </feature>
-        </config-file>
-
-  This example adds the contacts capability to the `WMAppManifest.xml`
-  file:
-
-        <config-file target="Properties/WMAppManifest.xml" parent="/Deployment/App/Capabilities">
-            <Capability Name="ID_CAP_CONTACTS" />
-        </config-file>
-
-## Debugging Plugins
-
-Use Visual Studio's debugger to debug a plugin's C# component. You can
-set a break point at any of the methods exposed by your class.
-
-JavaScript is more difficult to debug on Windows Phone. You need to
-use `console.log` to output the plugin's state, or to inform
-yourself of errors.
-
-## Common Pitfalls
-
-- Be careful not to pass arguments from JavaScript to the native side
-  that are difficult to deserialize as JSON. Most device platforms
-  expect the argument passed to `cordova.exec()` to be an array, such
-  as the following:
-
-        cordova.exec(win, fail, "ServiceName", "MethodName", ["this is a string", 54, {literal:'trouble'}]);
-
-  This may result in an overly complex string value for C# to decode:
-
-        "[\"this is a string\", 54, { literal:'trouble' }]"
-
-  Instead, consider converting _all_ parameters to strings before
-  calling `exec()`, and decoding each separately:
-
-        cordova.exec(win, fail, "ServiceName", "MethodName", ["this is a string", "54", "{literal:'trouble'}"]);
-        string[] optValues = JsonHelper.Deserialize<string[]>(options);
-
-- It is usually better to check parameters in JavaScript before
-  calling `exec()`. Doing so allows you to re-use more code and pull
-  unnecessary functionality from the plugin's various native
-  implementations.
-
-[PauseEvent]: ../../../cordova/events/events.html#pause
-[ResumeEvent]: ../../../cordova/events/events.html#resume
diff --git a/www/docs/en/dev/guide/platforms/wp8/upgrade.md b/www/docs/en/dev/guide/platforms/wp8/upgrade.md
deleted file mode 100644
index 4f9912651..000000000
--- a/www/docs/en/dev/guide/platforms/wp8/upgrade.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-license: >
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-        http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
-
-title: Upgrading Windows Phone 8
----
-
-# Upgrading Windows Phone 8
-
-This guide shows how to modify Windows Phone 8 projects, to upgrade from older versions of Cordova. Some of these
-instructions apply to projects created with an older set of
-command-line tools that precede the `cordova` CLI utility. See The
-Command-Line Interface for information how to update the version of
-the CLI.  The following section shows how to upgrade from non-CLI and
-CLI projects.
-
-## Upgrading 3.6.0 Projects to 4.0.0
-
-For non-CLI projects, run:
-
-        bin/update path/to/project
-        
-For CLI projects:
-
-1. Update the `cordova` CLI version. See [The Command-Line Interface](../../cli/index.html).
-
-2. Run `cordova platform update wp8` in your existing projects.
-
-
-## Upgrade to 3.2.0 from 3.1.0
-
-For projects that were created with the cordova CLI: 
-
-1. Update the `cordova` CLI version. See [The Command-Line Interface](../../cli/index.html). 
-
-2. Run `cordova platform update wp8`
-        
-For projects not created with the cordova CLI, run:
-
-        bin\update <project_path>
-
-## Upgrade to 3.1.0 from 3.0.0
-
-For projects that were created with the cordova CLI: 
-
-1. Update the `cordova` CLI version. See [The Command-Line Interface](../../cli/index.html). 
-
-2. Run `cordova platform update wp8`
-        
-For projects not created with the cordova CLI, run:
-
-        bin\update <project_path>
-
-## Upgrade to the CLI (3.0.0) from 2.9.0
-
-1. Create a new Apache Cordova 3.0.0 project using the cordova CLI, as
-   described in [The Command-Line Interface](../../cli/index.html).
-
-2. Add your platforms to the cordova project, for example: `cordova
-   platform add wp8`.
-
-3. Copy the contents of the project's `www` directory to the `www` directory
-   at the root of the cordova project you just created.
-
-4. Copy or overwrite any native assets from your original project
-   (`SplashScreen`, `ApplicationIcon`, etc.), making sure to add any
-   new files to the `.csproj` file. The windows phone project builds
-   inside the `platforms\wp8` directory.
-
-5. Use the cordova CLI tool to install any plugins you need. Note that
-   the CLI handles all core APIs as plugins, so they may need to be
-   added. Only 3.0.0 plugins are compatible with the CLI.
-
-6. Build and test.
-
-## Upgrade to 3.0.0 (non-CLI) from 2.x
-
-In Visual Studio's Solution Explorer window:
-
-1. Create a new Apache Cordova WP8 3.0.0 Project.
-
-2. Copy the contents of the `www` directory to the new project, and be sure these items are added to the VS project.
-
-3. Copy and overwrite any splash screen, or icon images.
-
-4. Copy over any plugins from the `plugins` directory to the new project and ensure that they are also added to the VS project. 
-
-5. Build and test.
-
-__NOTE__: all core APIs are removed from Cordova version 3.0, and must
-be installed separately as plugins.  For more information on how to
-re-enable these features in a non-CLI workflow, see Using Plugman to
-Manage Plugins.
diff --git a/www/docs/en/dev/guide/platforms/wp8/vmware.md b/www/docs/en/dev/guide/platforms/wp8/vmware.md
deleted file mode 100644
index 5c08fb886..000000000
--- a/www/docs/en/dev/guide/platforms/wp8/vmware.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-license: >
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-        http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
-
-title: Configuring VMWare Fusion
----
-
-# Configuring VMWare Fusion
-
-This section shows how to configure VMWare Fusion on a Mac so that
-you can use Cordova to generate Windows Phone applications.
-
-The [Microsoft Developer
-Network](http://msdn.microsoft.com/en-US/library/windows/apps/jj945426)
-provides general instructions for how to run Windows under VMWare
-Fusion.  After installing Windows, follow these steps:
-
-1. Within VMWare Fusion, select the Windows 8 disk image you have
-   prepared and choose __Settings__.
-
-1. Choose the __Processors & Memory__ configuration options. Make sure
-   to specify _two_ processor cores, and to __Enable hypervisor
-   applications in this Virtual machine__:
-
-   ![]({{ site.baseurl }}/static/img/guide/platforms/wp8/vmware_memory_opts.png)
-
-   The Windows Phone Emulator alone uses half a gigabyte of memory, so
-   overall you should reserve at least 2GB for VMWare.
-
-1. Choose the __Advanced__ settings. Enable the __Preferred
-   virtualization engine: Intel VT-x with EPT__ option:
-
-   ![]({{ site.baseurl }}/static/img/guide/platforms/wp8/vmware_advanced_opts.png)
-
-1. Modify the _.vmx_ file to add or modify the following settings:
-
-        hypervisor.cpuid.v0 = "FALSE"
-        mce.enable = "TRUE"
-        vhv.enable = "TRUE"
-
-Once you complete these steps, you are then ready to install the
-Windows Phone SDK.  See the [Windows Phone 8 Platform Guide](index.html) for details.
diff --git a/www/docs/en/dev/guide/platforms/wp8/webview.md b/www/docs/en/dev/guide/platforms/wp8/webview.md
deleted file mode 100644
index 03855da39..000000000
--- a/www/docs/en/dev/guide/platforms/wp8/webview.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-license: >
-    Licensed to the Apache Software Foundation (ASF) under one
-    or more contributor license agreements.  See the NOTICE file
-    distributed with this work for additional information
-    regarding copyright ownership.  The ASF licenses this file
-    to you under the Apache License, Version 2.0 (the
-    "License"); you may not use this file except in compliance
-    with the License.  You may obtain a copy of the License at
-
-        http://www.apache.org/licenses/LICENSE-2.0
-
-    Unless required by applicable law or agreed to in writing,
-    software distributed under the License is distributed on an
-    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-    KIND, either express or implied.  See the License for the
-    specific language governing permissions and limitations
-    under the License.
-
-title: Windows Phone 8.0 WebViews
----
-
-# Windows Phone 8.0 WebViews
-
-This guide shows how to embed a Cordova-enabled WebView component
-within a larger Windows Phone 8.0 application. 
-
-To follow these instructions, make sure you have the latest Cordova 
-distribution. Download it from 
-[cordova.apache.org](http://cordova.apache.org) and unzip its 
-Windows Phone 8.0 package (cordova-wp8-*.zip).
-
-1. Navigate to the package's `wp8/framework` directory and build
-   `WPCordovaClassLib.sln`. 
-   It creates the `Bin\Debug[Release]\WPCordovaClassLib.dll`.
-
-1. Copy the `WPCordovaClassLib.dll` file into the Windows Phone 8 project's
-    `/libs` directory and include `WPCordovaClassLib.dll` to your
-    project via `Project->References->Add Reference`.
-    Alternatively, you can directly reference the
-    `wp8/framework/WPCordovaClassLib.csproj` file.
-
-1. Add `CordovaView` component to your page (for example, `MainPage.xaml`).
-
-        xmlns:my="clr-namespace:WPCordovaClassLib;assembly=WPCordovaClassLib">
-        ...
-        <my:CordovaView HorizontalAlignment="Stretch" Margin="0,0,0,0" 
-        StartPageUri="html/index.html" x:Name="CordovaView" VerticalAlignment="Stretch" />
-
-1. Copy `common/www/cordova.js` along with the application's HTML 
-    and JavaScript files to the Windows Phone 8 project's `html` directory
-    and include new files to the project.
-
-1. Copy the `wp8/template/config.xml`to the project's root directory and 
-
-Instructions above will link core Cordova components only, 
-see [Using Plugman to Manage Plugins](../../../plugin_ref/plugman.html) in order to link Cordova plugins.
\ No newline at end of file
diff --git a/www/docs/en/dev/guide/support/index.md b/www/docs/en/dev/guide/support/index.md
index f59bfdfbd..a4fec2366 100644
--- a/www/docs/en/dev/guide/support/index.md
+++ b/www/docs/en/dev/guide/support/index.md
@@ -37,22 +37,16 @@ the core plugins, additional APIs are available via
     <tr>
         <th>Platform:</th>
         <th><a href="../android/index.html">Android</a></th>
-        <th><a href="../blackberry10/home.html">Blackberry 10</a></th>
         <th><a href="../ios/index.html">iOS</a></th>
         <th><a href="../osx/index.html">OS X</a></th>
-        <th><a href="../ubuntu/index.html">Ubuntu</a></th>
         <th><a href="../win8/index.html">Windows 8.1, 10, Phone 8.1</a></th>
-        <th><a href="../wp8/home.html">Windows Phone 8</a></th>
     </tr>
     <tr>
         <th>CLI shorthand:</th>
         <th>android</th>
-        <th>blackberry10</th>
         <th>ios</th>
         <th>osx</th>
-        <th>ubuntu</th>
         <th>windows</th>
-        <th>wp8</th>
     </tr>
 
 </thead>
@@ -65,12 +59,9 @@ the core plugins, additional APIs are available via
     <tr>
         <th><a href="../cli/index.html">Cordova<br/>CLI</a></th>
         <td data-col="android"    class="y">Mac, Windows, Linux</td>
-        <td data-col="blackberry10" class="y">Mac, Windows, Linux</td>
         <td data-col="ios"        class="y">Mac</td>
         <td data-col="osx"       class="y">Mac</td>
-        <td data-col="ubuntu"        class="y">Ubuntu</td>
         <td data-col="win8"       class="y">Windows</td>
-        <td data-col="wp8"  class="y">Windows</td>
     </tr>
 
     <tr>
@@ -81,177 +72,129 @@ the core plugins, additional APIs are available via
     <tr>
         <th><a href="../../reference/cordova-plugin-battery-status/">BatteryStatus</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="y"></td>
         <td data-col="osx"       class="n"></td>
-        <td data-col="ubuntu"        class="y"></td>
         <td data-col="win8"       class="y">Windows Phone 8.1 only</td>
-        <td data-col="wp8"  class="y"></td>
     </tr>
 
     <tr>
         <th><a href="../../reference/cordova-plugin-camera/">Camera</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="y"></td>
         <td data-col="osx"       class="n"></td>
-        <td data-col="ubuntu"        class="y"></td>
         <td data-col="win8"       class="y"></td>
-        <td data-col="wp8"  class="y"></td>
     </tr>
 
     <tr>
         <th><a href="../../reference/cordova-plugin-media-capture/">Capture</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="y"></td>
         <td data-col="osx"       class="n"></td>
-        <td data-col="ubuntu"        class="y"></td>
         <td data-col="win8"       class="y"></td>
-        <td data-col="wp8"  class="y"></td>
     </tr>
 
     <tr>
         <th><a href="../../reference/cordova-plugin-network-information/">Connection</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="y"></td>
         <td data-col="osx"       class="n"></td>
-        <td data-col="ubuntu"        class="y"></td>
         <td data-col="win8"       class="y"></td>
-        <td data-col="wp8"  class="y"></td>
     </tr>
 
     <tr>
         <th><a href="../../reference/cordova-plugin-device/">Device</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="y"></td>
         <td data-col="osx"       class="y"></td>
-        <td data-col="ubuntu"        class="y"></td>
         <td data-col="win8"       class="y"></td>
-        <td data-col="wp8"  class="y"></td>
     </tr>
 
     <tr>
         <th><a href="../../cordova/events/events.html">Events</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="y"></td>
         <td data-col="osx"       class="n"></td>
-        <td data-col="ubuntu"        class="y"></td>
         <td data-col="win8"       class="y"></td>
-        <td data-col="wp8"  class="y"></td>
     </tr>
 
     <tr>
         <th><a href="../../reference/cordova-plugin-file">File</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="y"></td>
         <td data-col="osx"       class="y"></td>
-        <td data-col="ubuntu"        class="y"></td>
         <td data-col="win8"       class="y"></td>
-        <td data-col="wp8"  class="y"></td>
     </tr>
 
     <tr>
         <th><a href="../../reference/cordova-plugin-geolocation/">Geolocation</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="y"></td>
         <td data-col="osx"       class="n"></td>
-        <td data-col="ubuntu"        class="y"></td>
         <td data-col="win8"       class="y"></td>
-        <td data-col="wp8"  class="y"></td>
     </tr>
 
     <tr>
         <th><a href="../../reference/cordova-plugin-globalization/">Globalization</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="y"></td>
         <td data-col="osx"       class="n"></td>
-        <td data-col="ubuntu"        class="y"></td>
         <td data-col="win8"       class="y"></td>
-        <td data-col="wp8"  class="y"></td>
     </tr>
 
     <tr>
         <th><a href="../../reference/cordova-plugin-inappbrowser/">InAppBrowser</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="y"></td>
         <td data-col="osx"       class="n"></td>
-        <td data-col="ubuntu"        class="y"></td>
         <td data-col="win8"       class="p">uses iframe</td>
-        <td data-col="wp8"  class="y"></td>
     </tr>
 
     <tr>
         <th><a href="../../reference/cordova-plugin-media/">Media</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="y"></td>
         <td data-col="osx"></td>
-        <td data-col="ubuntu"        class="y"></td>
         <td data-col="win8"       class="y"></td>
-        <td data-col="wp8"  class="y"></td>
     </tr>
 
     <tr>
         <th><a href="../../reference/cordova-plugin-dialogs/">Notification</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="y"></td>
         <td data-col="osx"       class="n"></td>
-        <td data-col="ubuntu"        class="y"></td>
         <td data-col="win8"       class="y"></td>
-        <td data-col="wp8"  class="y"></td>
     </tr>
 
     <tr>
         <th><a href="../../reference/cordova-plugin-splashscreen/">Splashscreen</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="y"></td>
         <td data-col="osx"       class="n"></td>
-        <td data-col="ubuntu"        class="y"></td>
         <td data-col="win8"       class="y"></td>
-        <td data-col="wp8"  class="y"></td>
     </tr>
 
     <tr>
         <th><a href="../../reference/cordova-plugin-statusbar/">Status Bar</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="n"></td>
         <td data-col="ios"        class="y"></td>
         <td data-col="osx"       class="n"></td>
-        <td data-col="ubuntu"        class="n"></td>
         <td data-col="win8"       class="y">Windows Phone 8.1 only</td>
-        <td data-col="wp8"  class="y"></td>
     </tr>
 
     <tr>
         <th><a href="../../cordova/storage/storage.html">Storage</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="y"></td>
         <td data-col="osx"       class="n"></td>
-        <td data-col="ubuntu"        class="y"></td>
         <td data-col="win8"       class="y">localStorage &amp; indexedDB</td>
-        <td data-col="wp8"  class="y">localStorage &amp; indexedDB</td>
     </tr>
 
     <tr>
         <th><a href="../../reference/cordova-plugin-vibration/">Vibration</a></th>
         <td data-col="android"    class="y"></td>
-        <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="y"></td>
         <td data-col="osx"       class="n"></td>
-        <td data-col="ubuntu"        class="y"></td>
         <td data-col="win8"       class="y">Windows Phone 8.1 only</td>
-        <td data-col="wp8"  class="y"></td>
     </tr>
 
     <tr>
@@ -261,22 +204,16 @@ the core plugins, additional APIs are available via
     <tr>
         <th><a href="../hybrid/plugins/index.html">Plugin<br/>Interface</a></th>
         <td data-col="android"    class="y"><a href="../platforms/android/plugin.html">(see details)</a></td>
-        <td data-col="blackberry10" class="y"><a href="../platforms/blackberry10/plugin.html">(see details)</a></td>
         <td data-col="ios"        class="y"><a href="../platforms/ios/plugin.html">(see details)</a></td>
         <td data-col="osx"       class="y"></td>
-        <td data-col="ubuntu"        class="y"></td>
         <td data-col="win8"       class="y"></td>
-        <td data-col="wp8"  class="y"><a href="../platforms/wp8/plugin.html">(see details)</a></td>
     </tr>
     <tr>
         <th><a href="../hybrid/webviews/index.html">Embedded<br/>WebView</a></th>
         <td data-col="android"    class="y"><a href="../platforms/android/webview.html">(see details)</a></td>
-        <td data-col="blackberry10" class="n"></td>
         <td data-col="ios"        class="y"><a href="../platforms/ios/webview.html">(see details)</a></td>
         <td data-col="osx"       class="y"></td>
-        <td data-col="ubuntu"        class="y"></td>
         <td data-col="win8"       class="n"></td>
-        <td data-col="wp8"  class="n"></td>
     </tr>
 </tbody>
 </table>
diff --git a/www/static/plugins/official-plugins.json b/www/static/plugins/official-plugins.json
index b26a0526f..debe3f152 100755
--- a/www/static/plugins/official-plugins.json
+++ b/www/static/plugins/official-plugins.json
@@ -2,17 +2,15 @@
     "plugins" : [
         "cordova-plugin-battery-status",
         "cordova-plugin-camera",
-        "cordova-plugin-console",
         "cordova-plugin-device",
         "cordova-plugin-dialogs",
         "cordova-plugin-file",
         "cordova-plugin-geolocation",
-        "cordova-plugin-globalization",
         "cordova-plugin-inappbrowser",
         "cordova-plugin-media",
         "cordova-plugin-media-capture",
-        "cordova-plugin-ms-appinsights",
         "cordova-plugin-network-information",
+        "cordova-plugin-screen-orientation",
         "cordova-plugin-splashscreen",
         "cordova-plugin-statusbar",
         "cordova-plugin-vibration",


 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Remove deprecated platforms and plugins from docs
> -------------------------------------------------
>
>                 Key: CB-13930
>                 URL: https://issues.apache.org/jira/browse/CB-13930
>             Project: Apache Cordova
>          Issue Type: Task
>          Components: cordova-docs
>            Reporter: Steve Gill
>            Assignee: Steve Gill
>            Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org


Mime
View raw message