cordova-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dblot...@apache.org
Subject [07/15] docs commit: Snapshotting dev to 6.x.
Date Sat, 19 Mar 2016 09:36:23 GMT
http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/e3751865/www/docs/en/6.x/guide/platforms/win8/index.md
----------------------------------------------------------------------
diff --git a/www/docs/en/6.x/guide/platforms/win8/index.md b/www/docs/en/6.x/guide/platforms/win8/index.md
index 7a6ee17..408d533 100644
--- a/www/docs/en/6.x/guide/platforms/win8/index.md
+++ b/www/docs/en/6.x/guide/platforms/win8/index.md
@@ -22,12 +22,12 @@ title: Windows Platform Guide
 
 # Windows Platform Guide
 
-This guide shows how to set up your SDK development environment to build 
-and deploy Cordova apps for Windows 8.1, Windows Phone 8.1, and 
-Windows 10 Universal App Platform.  It shows how to use either shell tools 
-to generate and build apps, or the cross-platform Cordova CLI. (See the [Overview](../../overview/index.html#development-paths) for a comparison of these 
-development options.) This section also shows how to modify Cordova apps 
-within Visual Studio. Regardless of [which](../../overview/index.html#development-paths) approach you take, you need to 
+This guide shows how to set up your SDK development environment to build
+and deploy Cordova apps for Windows 8.1, Windows Phone 8.1, and
+Windows 10 Universal App Platform.  It shows how to use either shell tools
+to generate and build apps, or the cross-platform Cordova CLI. (See the [Overview](../../overview/index.html#development-paths) for a comparison of these
+development options.) This section also shows how to modify Cordova apps
+within Visual Studio. Regardless of [which](../../overview/index.html#development-paths) approach you take, you need to
 install the Visual Studio SDK, as described below.
 
 Developers wishing to target Windows Phone 8 should use the wp8 platform,
@@ -44,8 +44,8 @@ on how to support IE along with comparable WebKit browsers.
 
 To develop apps for Windows platform you need:
 
-- A Windows 8.1, 32 or 64-bit machine (_Home_, _Pro_, or _Enterprise_ editions) 
-  with minimum 4 GB of RAM along with [Visual Studio 2015](http://www.visualstudio.com/downloads) 
+- A Windows 8.1, 32 or 64-bit machine (_Home_, _Pro_, or _Enterprise_ editions)
+  with minimum 4 GB of RAM along with [Visual Studio 2015](http://www.visualstudio.com/downloads)
   or Visual Studio 2013.  An evaluation version of Windows 8.1 Enterprise is
   available from the
   [Microsoft Developer Network](https://technet.microsoft.com/evalcenter/hh699156.aspx).
@@ -59,7 +59,7 @@ To develop apps for Windows 10:
   [Visual Studio 2015](http://www.visualstudio.com/downloads) or higher.
 
 App compatibility is determined by the OS that the app targeted.  Apps are forwardly-compatible
-but not backwardly-compatible, so an app targeting Windows 10 cannot run on 8.1, but 
+but not backwardly-compatible, so an app targeting Windows 10 cannot run on 8.1, but
 an app built for 8.1 can run on 10.
 
 Cordova apps targeting Windows can be developed on a Mac, either by running a
@@ -70,18 +70,18 @@ Windows development environment on a Mac:
 - [VMWare Fusion](http://msdn.microsoft.com/en-US/library/windows/apps/jj945426)
 
 - [Parallels Desktop](http://msdn.microsoft.com/en-US/library/windows/apps/jj945424)
-  
+
 - [Boot Camp](http://msdn.microsoft.com/en-US/library/windows/apps/jj945423)
 
 ## Installing the Requirements
 
 Install any edition of
 [Visual Studio](http://www.visualstudio.com/downloads) matching the version
-requirements listed above.  
+requirements listed above.
 
 <br/><p align="center"><img src="{{ site.baseurl }}/static/img/guide/platforms/win8/win8_installSDK.png" /></p><br/>
 
-For Windows 10, the Visual Studio installer has an option to install tools to 
+For Windows 10, the Visual Studio installer has an option to install tools to
 build Universal Windows Apps.  You must ensure that this option is selected
 when installing to install the required SDK.
 
@@ -92,29 +92,33 @@ when installing to install the required SDK.
 After installation, you should be ready to develop apps targetting Windows platform. Refer to [Create your first app](../../cli/index.html) guide for details.
 
 By default the `cordova build` command produces two packages: Windows 8.1 and Windows Phone 8.1.
-To upgrade Windows package to version 10 the following configuration setting must be 
+To upgrade Windows package to version 10 the following configuration setting must be
 added to configuration file (`config.xml`).
 
-        <preference name="windows-target-version" value="10.0" />
+```xml
+<preference name="windows-target-version" value="10.0" />
+```
 
 Once you add this setting `build` command will start producing Windows 10 packages.
 
 ### Considerations for target Windows version
 
 Windows 10 supports a new "Remote" mode for Cordova apps (and HTML apps in general). This mode enables
-apps to have much more freedom with respect to use of DOM manipulation and common web patterns such as the use 
-of inline script, but does so by reducing the set of capabilities your app may use when 
+apps to have much more freedom with respect to use of DOM manipulation and common web patterns such as the use
+of inline script, but does so by reducing the set of capabilities your app may use when
 submitted to the public Windows Store. For more information about Windows 10 and Remote Mode, look at
 the [Understanding Remote Mode vs Local Mode](#understanding-remote-mode-vs-local-mode) section.
 
-When using Remote Mode, developers are encouraged to apply a Content Security Policy (CSP) to their application 
+When using Remote Mode, developers are encouraged to apply a Content Security Policy (CSP) to their application
 to prevent script injection attacks.
 
 ### The --appx parameter
 
 You may decide that you want to build a particular version of your application targeting a particular OS (for example, you might have set that you want to target Windows 10, but you want to build for Windows Phone 8.1).  To do this, you can use the `--appx` parameter:
 
-        > cordova build windows -- --appx=8.1-phone
+```
+cordova build windows -- --appx=8.1-phone
+```
 
 The build system will ignore the preference set in config.xml for the target Windows version and strictly build a package for Windows Phone 8.1.
 
@@ -124,21 +128,29 @@ Valid values for the `--appx` flag are `8.1-win`, `8.1-phone`, and `uap` (for Wi
 
 To deploy Windows package:
 
-        > cordova run windows -- --win  # explicitly specify Windows as deployment target
-        > cordova run windows # `run` uses Windows package by default
+```
+cordova run windows -- --win  # explicitly specify Windows as deployment target
+cordova run windows # `run` uses Windows package by default
+```
 
 To deploy Windows Phone package:
 
-        > cordova run windows -- --phone  # deploy app to Windows Phone 8.1 emulator
-        > cordova run windows --device -- --phone  # deploy app to connected device
+```
+cordova run windows -- --phone  # deploy app to Windows Phone 8.1 emulator
+cordova run windows --device -- --phone  # deploy app to connected device
+```
 
-This command will give you the list of all available targets: 
+This command will give you the list of all available targets:
 
-        > cordova run windows --list
+```
+cordova run windows --list
+```
 
 This allows you to run the application on a specific device or emulator, in this case "Emulator 8.1 720p 4.7 inch"
 
-        > cordova run windows --target="Emulator 8.1 720P 4.7 inch" -- --phone       
+```
+cordova run windows --target="Emulator 8.1 720P 4.7 inch" -- --phone
+```
 
 You can also use __cordova run --help__ to see additional build and run options.
 
@@ -234,24 +246,26 @@ cordova build -- --packageCertificateKeyFile="platforms\windows\CordovaApp_Tempo
 
 Alternatively, these values could be specified using a build configuration file (build.json) using CLI (--buildConfig). A sample build configuration file:
 
-    {
-        "windows": {
-            "debug": {
-                "packageCertificateKeyFile": "platforms\\windows\\CordovaApp_TemporaryKey.pfx"
-            },
-            "release": {
-                "packageCertificateKeyFile": "c:\\path-to-key\\keycert.pfx",
-                "packageThumbprint": "ABCABCABCABC123123123123",
-                "publisherId": "CN=FakeCorp.com, L=Redmond, S=Washington, C=US"
-            }
+```json
+{
+    "windows": {
+        "debug": {
+            "packageCertificateKeyFile": "platforms\\windows\\CordovaApp_TemporaryKey.pfx"
+        },
+        "release": {
+            "packageCertificateKeyFile": "c:\\path-to-key\\keycert.pfx",
+            "packageThumbprint": "ABCABCABCABC123123123123",
+            "publisherId": "CN=FakeCorp.com, L=Redmond, S=Washington, C=US"
         }
     }
+}
+```
 
 There is also support to mix and match command line arguments and parameters in build.json file. Values from the command line arguments will get precedence.
 
 ### Creating a certificate key
 Signing is required for distributing and installing Windows Store apps. This process is normally handled by Visual Studio when you deploy a package for release. To do this without Visual Studio we need to create our own certificates. [This](https://msdn.microsoft.com/en-us/library/windows/desktop/jj835832(v=vs.85).aspx) article has instructions on how to do that.
- 
+
 Once you have the pfx file created and provided to build.json file, you might get the following error: "The key file may be password protected. To correct this, try to import the certificate manually into the current user's personal certificate  store.". In order to import it you have to use [certutil][2] from an admin prompt:
 
 `certutil -user -p PASSWORD -importPFX FakeCorp.com.pfx`
@@ -264,7 +278,9 @@ Where:
 
 Once installed, next step is to add packageThumbprint and packageCertificateKeyFile to build.json. In order to find the packageThumbprint, search for the CommonName you've associated with the certificate:
 
-`powershell -Command " & {dir -path cert:\LocalMachine\My | where { $_.Subject -like \"*FakeCorp.com*\" }}"`
+```powershell
+powershell -Command " & {dir -path cert:\LocalMachine\My | where { $_.Subject -like \"*FakeCorp.com*\" }}"
+```
 
 Once these final values are provided. Cordova should successfully package and sign the app.
 
@@ -284,7 +300,7 @@ If you want to use Cordova's Windows-centered shell tools in conjunction with th
   are available in `package/bin` directory. (Consult the
   __README__ file if necessary for more detailed directions.)
 
-These shell tools allow you to create, build, and run Windows apps. Each cordova command corresponds to one of these shell tool scripts. 
+These shell tools allow you to create, build, and run Windows apps. Each cordova command corresponds to one of these shell tool scripts.
 
 For example, the lower-level shell-tool approach corresponding to `cordova create HelloWorld` is:
 
@@ -295,7 +311,7 @@ C:\path\to\cordova-windows\package\bin\create.bat C:\path\to\new\hello HelloWorl
 Similarly for `cordova build --debug`:
 
 ```
-C:\path\to\project\cordova\build.bat --debug   
+C:\path\to\project\cordova\build.bat --debug
 ```
 
 ## Upgrading
@@ -304,27 +320,29 @@ Refer to [this](upgrade.html) article for instructions to upgrade your `cordova-
 
 ## Supporting Toasts
 
-Windows requires an app manifest capability declaration in order to support 
-toast notifications.  When using the `cordova-plugin-local-notifications` 
+Windows requires an app manifest capability declaration in order to support
+toast notifications.  When using the `cordova-plugin-local-notifications`
 plugin, or any other plugin that is attempting to use toast notifications,
-add the following preference to your config.xml to enable it to publish 
+add the following preference to your config.xml to enable it to publish
 toast notifications, unless the plugin makes that change on it's own:
 
-    <preference name="WindowsToastCapable" value="true" />
+```xml
+<preference name="WindowsToastCapable" value="true" />
+```
 
 This preference sets the corresponding flag in your app manifest. Plugins
-should do the work necessary to configure the appearance of the 
+should do the work necessary to configure the appearance of the
 displayed notifications.
 
 ## Understanding Remote Mode vs Local Mode
 Windows 10 introduces a new feature called "Remote mode" for HTML applications. Prior to it, Windows 8.1 apps
-worked on what is now termed as "Local Mode" in Windows 10, in which HTML Applications have full access to the native 
-Windows API surface and capabilities. Local Mode disallows inline script in order to prevent script injection attacks, 
+worked on what is now termed as "Local Mode" in Windows 10, in which HTML Applications have full access to the native
+Windows API surface and capabilities. Local Mode disallows inline script in order to prevent script injection attacks,
 which could result in leaking personally-identifiable information due to malicious code. It also requires developers who
 perform DOM manipulation to do so within an explicit context
 (`MSApp.execUnsafeLocalFunction`).
 
-Remote Mode eliminates those requirements, which makes it possible to use unmodified libraries like jQuery 
+Remote Mode eliminates those requirements, which makes it possible to use unmodified libraries like jQuery
 or AngularJS directly in your code, without any changes.  To do so, it removes your ability to declare certain
 capabilities when certifying your app in the Windows Store.  The removal of these capabilities usually doesn't
 prevent accessing certain functionality, but it might require the use of a different combination of APIs or tactics.

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/e3751865/www/docs/en/6.x/guide/platforms/win8/plugin.md
----------------------------------------------------------------------
diff --git a/www/docs/en/6.x/guide/platforms/win8/plugin.md b/www/docs/en/6.x/guide/platforms/win8/plugin.md
index 300dc9a..9ca2431 100644
--- a/www/docs/en/6.x/guide/platforms/win8/plugin.md
+++ b/www/docs/en/6.x/guide/platforms/win8/plugin.md
@@ -22,35 +22,29 @@ title: Windows Plugins
 
 # Windows Plugins
 
-This section provides details for how to implement a plugin for use in 
-a Windows Store app. Before reading this, see Create your fist plugin 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.
+This section provides details for how to implement a plugin for use in
+a Windows Store app for Windows 8.1 phone and desktop, and Universal Windows Platform (Windows 10+). Before reading this, see [Create your fist plugin](../../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.
 
 ## Creating a Windows Plugin in JavaScript
 
-These instructions are to create a pure JavaScript plugin.
+Windows Cordova plugins are essentially a thin wrapper around existing WinJS provided functions, but assuming you will want to define your JS common interface for multiple devices, you will typically have one JS file that provides the API:
 
-Windows Cordova plugins are essentially a thin wrapper around existing WinJS provided functions, but assuming you will want to define your JS common interface for multiple devices, you will typically have one JS file that provides the API.
-
-    // inside file echoplugin.js
-    var EchoPlugin = {
-        // the echo function calls successCallback with the provided text in strInput
-        // if strInput is empty, it will call the errorCallback
-        echo:function(successCallback, errorCallback, strInput) {
-            cordova.exec(successCallback,errorCallback,"EchoPlugin","echo",[strInput]);
-        }
+```js
+// inside file echoplugin.js
+var EchoPlugin = {
+    // the echo function calls successCallback with the provided text in strInput
+    // if strInput is empty, it will call the errorCallback
+    echo:function(successCallback, errorCallback, strInput) {
+        cordova.exec(successCallback,errorCallback,"EchoPlugin","echo",[strInput]);
     }
-
-
-## The Cordova exec proxy
+}
+```
 
 The `cordova.exec` function is defined differently on every platform, this is because each platform has it's own way of communicating between the application js code, and the native wrapper code. But in the case of Windows, there is no native wrapper, so the exec call is there for consistency. So even though you could write the Windows specific code as a part of plugin's common JS code directly, this is not recommended and plugin authors should use the same exec API for Windows as for other platforms. This way the plugin API becomes consistent and you can also take advantage of any parameter checking, or other common code provided by developers who were working on other platforms.
 
 On Windows, cordova provides a proxy that you can use to register an object that will handle all cordova.exec calls to an API. So in our case, we will assume that the code in `echoplugin.js` is handling cross platform relevant JavaScript, and we can simply write a proxy for Windows.
 
-```
+```js
 // in file echoplugin.js
 window.echo = function(str, callback) {
     cordova.exec(callback, function(err) {
@@ -59,7 +53,7 @@ window.echo = function(str, callback) {
 };
 ```
 
-```
+```js
 // in file echopluginProxy.js
 cordova.commandProxy.add("Echo",{
     echo:function(successCallback,errorCallback,strInput) {
@@ -77,111 +71,120 @@ The `echoplugin.js` file will forward the `echo` function call to this proxy thr
 
 The plugin.xml file will have the settings required for our plugin. In this case, we want to add our `echoplugin.js` file in the `www` directory and the `echopluginProxy.js` file inside the `windows` source code of our application. Details of these elements can be found in the [Plugin.xml](../../plugin_ref/spec.html) reference.
 
-    <?xml version="1.0" encoding="UTF-8"?>
-    <plugin xmlns="http://apache.org/cordova/ns/plugins/1.0"
-        id="echoplugin"
-        version="0.1.0">
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<plugin xmlns="http://apache.org/cordova/ns/plugins/1.0"
+    id="echoplugin"
+    version="0.1.0">
 
-        <js-module src="www/echoplugin.js" name="echoplugin">
-            <clobbers target="window.echoplugin" />
-        </js-module>
+    <js-module src="www/echoplugin.js" name="echoplugin">
+        <clobbers target="window.echoplugin" />
+    </js-module>
 
-        <!-- windows -->
-        <platform name="windows">
-            <js-module src="src/windows/echopluginProxy.js" name="EchoProxy">
-                <merges target="" />
-            </js-module>
-        </platform>
+    <!-- windows -->
+    <platform name="windows">
+        <js-module src="src/windows/echopluginProxy.js" name="EchoProxy">
+            <merges target="" />
+        </js-module>
+    </platform>
 
-        <!-- other platforms -->
+    <!-- other platforms -->
 
-    </plugin>
+</plugin>
+```
 
 This gives us a working Windows JavaScript plugin that uses a common file ( echoplugin.js ) and uses a proxy to provide the Windows only portion of implementation ( echopluginProxy.js ). So how do we add native/managed code to this? Well we are going to start the same, the only difference will be what we do inside in echopluginProxy methods.
 
-## How WinJS accesses native/managed code
+## Creating a Windows Plugin in C++ or managed code.
 
-In Windows, WinJS authored apps are able to interact with native code, this inter-op is available for Windows Runtime Components. The details are numerous, and this guide will only cover the basics. Microsoft provides much more info [here](http://msdn.microsoft.com/en-us/library/windows/apps/hh441569.aspx).
+In Windows, Javascript authored apps are able to interop with native (C++) and managed code (C#, VB) by creating a Windows runtime component. You can learn the basics here and checkout more details in guides on MSDN:
+- [Creating Windows Runtime Components in C# and Visual Basic](https://msdn.microsoft.com/en-us/library/windows/apps/br230301.aspx)
+- [Creating Windows Runtime Components in C++](http://msdn.microsoft.com/en-us/library/windows/apps/hh441569.aspx)
 
 When you create your Windows Runtime Component, any class that is defined as `public ref class sealed` is considered an 'activatable class' and will be callable from JavaScript.
 
-    // in your header file .h
-    namespace EchoRuntimeComponent
+```cpp
+// in your header file .h
+namespace EchoRuntimeComponent
+{
+    public ref class EchoPluginRT sealed
     {
-        public ref class EchoPluginRT sealed 
-        {
-            public:
-            static Platform::String^ Echo(Platform::String^ input);
-        }
+        public:
+        static Platform::String^ Echo(Platform::String^ input);
     }
+}
 
-    // in the implementation file .cpp
-    using namespace EchoRuntimeComponent;
-    using namespace Platform;
+// in the implementation file .cpp
+using namespace EchoRuntimeComponent;
+using namespace Platform;
 
-    Platform::String^ EchoPluginRT::Echo(Platform::String^ input)
+Platform::String^ EchoPluginRT::Echo(Platform::String^ input)
+{
+    if(input->IsEmpty())
     {
-        if(input->IsEmpty()) 
-        {
-            return "Error: input string is empty.";
-        }
-        else
-        {
-            return input->ToString() + "echo";
-        }
+        return "Error: input string is empty.";
     }
+    else
+    {
+        return input->ToString() + "echo";
+    }
+}
+```
 
 Now in order for us to call the native code, we use the namespace, classname, and lowerCamelCase the method we are calling.
 
-```
+```js
 var res = EchoRuntimeComponent.EchoPluginRT.echo("boom");
 ```
 
 Moving this to our echopluginProxy.js file, we get:
 
-    // in file echopluginProxy.js
-    cordova.commandProxy.add("EchoPlugin",{
-        echo:function(successCallback,errorCallback,strInput) {
-            var res = EchoRuntimeComponent.EchoPluginRT.echo(strInput);
-            if(res.indexOf("Error") == 0) {
-                errorCallback(res);
-            }
-            else {
-                successCallback(res);
-            }
+```js
+// in file echopluginProxy.js
+cordova.commandProxy.add("EchoPlugin",{
+    echo:function(successCallback, errorCallback, strInput) {
+        var res = EchoRuntimeComponent.EchoPluginRT.echo(strInput);
+        if(res.indexOf("Error") == 0) {
+            errorCallback(res);
         }
-    });
+        else {
+            successCallback(res);
+        }
+    }
+});
+```
 
 And that's it, we have an end to end C++ backed js callable plugin for use in Apache Cordova Windows!
 
-## Considerations
+### Considerations
 
 - The callback is typically async, so calling the callback right away is probably not expected by the caller. In practice, if the call is not async, you should at least use a javascript timeout to force the callback to be called asynchronously.
-- Activatable classes can be used to do event dispatching, async callbacks, passing your own object types, arrays, collections, overloaded methods and much more. Refer [here](http://msdn.microsoft.com/en-us/library/windows/apps/hh441569.aspx) for details.
+- Activatable classes can be used to do event dispatching, async callbacks, passing your own object types, arrays, collections, overloaded methods and much more. Refer to [Creating Windows Runtime Components in C++](http://msdn.microsoft.com/en-us/library/windows/apps/hh441569.aspx) for details.
 
-## Defining your plugin
+### Defining your plugin in plugin.xml
 
 Now that we have a working plugin, we need to revisit the plugin definition from earlier so we can publish it. We can now add the runtime component as a framework, through the `<framework>` tag inside our platfrom settings. Note that the output type of a WindowsRuntimeComponent can be either .winmd or .dll
 
-    <?xml version="1.0" encoding="UTF-8"?>
-    <plugin xmlns="http://apache.org/cordova/ns/plugins/1.0"
-        id="echoplugin"
-        version="0.2.0">
-
-        <js-module src="www/echoplugin.js" name="echoplugin">
-            <clobbers target="window.echoplugin" />
-        </js-module>
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<plugin xmlns="http://apache.org/cordova/ns/plugins/1.0"
+    id="echoplugin"
+    version="0.2.0">
 
-        <!-- windows -->
-        <platform name="windows">
-            <js-module src="src/windows/echopluginProxy.js" name="EchoProxy">
-                <merges target="" />
-            </js-module>
-            <framework src="src/windows/EchoRuntimeComponent.winmd" custom="true"/>
-        </platform>
+    <js-module src="www/echoplugin.js" name="echoplugin">
+        <clobbers target="window.echoplugin" />
+    </js-module>
 
-        <!-- other platforms -->
+    <!-- windows -->
+    <platform name="windows">
+        <js-module src="src/windows/echopluginProxy.js" name="EchoProxy">
+            <merges target="" />
+        </js-module>
+        <framework src="src/windows/EchoRuntimeComponent.winmd" custom="true"/>
+    </platform>
 
-    </plugin>
+    <!-- other platforms -->
+</plugin>
+```
 
-That's it, you now have a distributable plugin that you can share with the world!
\ No newline at end of file
+That's it, you now have a distributable plugin that you can share with the world!

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/e3751865/www/docs/en/6.x/guide/platforms/win8/upgrade.md
----------------------------------------------------------------------
diff --git a/www/docs/en/6.x/guide/platforms/win8/upgrade.md b/www/docs/en/6.x/guide/platforms/win8/upgrade.md
index cc39ee3..6afb707 100644
--- a/www/docs/en/6.x/guide/platforms/win8/upgrade.md
+++ b/www/docs/en/6.x/guide/platforms/win8/upgrade.md
@@ -26,8 +26,9 @@ For upgrading from `windows` version 4.0.0 or higher, run `cordova platform upda
 
 For projects not created with the cordova CLI, run:
 
-        bin\update <project_path>
-
+```
+bin\update <project_path>
+```
 
 # Upgrading Windows 8
 
@@ -38,19 +39,21 @@ version of the CLI.
 
 ## Upgrade to 4.0.0 from 3.1.0 or later
 
-For projects that were created with the cordova CLI: 
+For projects that were created with the cordova CLI:
 
-1. Update the `cordova` CLI version. See [The Command-Line Interface](../../cli/index.html). 
+1. Update the `cordova` CLI version. See [The Command-Line Interface](../../cli/index.html).
 
 2. Run `cordova platform update windows8`.
-        
+
 For projects not created with the cordova CLI, run:
 
-        bin\update <project_path>
+```
+bin\update <project_path>
+````
 
 ## Upgrade to 3.1.0
 
-Cordova CLI support for Windows 8 was introduced in Cordova 3.1.0. To upgrade, we suggest creating a new Cordova CLI project and moving over all necessary assets.  
+Cordova CLI support for Windows 8 was introduced in Cordova 3.1.0. To upgrade, we suggest creating a new Cordova CLI project and moving over all necessary assets.
 
 ## Upgrade to 2.9.0 from 2.8.0
 
@@ -66,7 +69,7 @@ The following commands should be done from within Visual Studio to be sure that
 
 The following commands should be done from within Visual Studio to be sure that the any project references are updated/deleted.
 
-1. Remove `cordova-2.7.0.js` from the project's `www` directory. 
+1. Remove `cordova-2.7.0.js` from the project's `www` directory.
 
 2. Add `cordova.js` file from the source to the project's `www` directory. (Note that the file no longer contains a version number in the filename.)
 

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/e3751865/www/docs/en/6.x/guide/support/index.md
----------------------------------------------------------------------
diff --git a/www/docs/en/6.x/guide/support/index.md b/www/docs/en/6.x/guide/support/index.md
index 8d4af80..9ccfe0a 100644
--- a/www/docs/en/6.x/guide/support/index.md
+++ b/www/docs/en/6.x/guide/support/index.md
@@ -49,7 +49,7 @@ CLI's shorthand names.
     <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</td>
+        <td data-col="blackberry10" class="y">Mac, Windows, Linux</td>
         <td data-col="ios"        class="y">Mac</td>
         <td data-col="ubuntu"        class="y">Ubuntu</td>
         <td data-col="winphone8"  class="y">Windows</td>
@@ -82,7 +82,7 @@ CLI's shorthand names.
     </tr>
 
     <tr>
-        <th><a href="../../cordova-plugin-device-motion/">Accelerometer</a></th>
+        <th><a href="../../reference/cordova-plugin-device-motion/">Accelerometer</a></th>
         <td data-col="android"    class="y"></td>
         <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="y"></td>
@@ -92,7 +92,7 @@ CLI's shorthand names.
     </tr>
 
     <tr>
-        <th><a href="../../cordova-plugin-battery-status/">BatteryStatus</a></th>
+        <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>
@@ -102,7 +102,7 @@ CLI's shorthand names.
     </tr>
 
     <tr>
-        <th><a href="../../cordova-plugin-camera/">Camera</a></th>
+        <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>
@@ -112,7 +112,7 @@ CLI's shorthand names.
     </tr>
 
     <tr>
-        <th><a href="../../cordova-plugin-media-capture/">Capture</a></th>
+        <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>
@@ -122,7 +122,7 @@ CLI's shorthand names.
     </tr>
 
     <tr>
-        <th><a href="../../cordova-plugin-device-orientation/">Compass</a></th>
+        <th><a href="../../reference/cordova-plugin-device-orientation/">Compass</a></th>
         <td data-col="android"    class="y"></td>
         <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="y">(3GS+)</td>
@@ -132,7 +132,7 @@ CLI's shorthand names.
     </tr>
 
     <tr>
-        <th><a href="../../cordova-plugin-network-information/">Connection</a></th>
+        <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>
@@ -142,7 +142,7 @@ CLI's shorthand names.
     </tr>
 
     <tr>
-        <th><a href="../../cordova-plugin-contacts/">Contacts</a></th>
+        <th><a href="../../reference/cordova-plugin-contacts/">Contacts</a></th>
         <td data-col="android"    class="y"></td>
         <td data-col="blackberry10" class="y"></td>
         <td data-col="ios"        class="y"></td>
@@ -152,7 +152,7 @@ CLI's shorthand names.
     </tr>
 
     <tr>
-        <th><a href="../../cordova-plugin-device/">Device</a></th>
+        <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>
@@ -172,7 +172,7 @@ CLI's shorthand names.
     </tr>
 
     <tr>
-        <th><a href="../../cordova-plugin-file">File</a></th>
+        <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>
@@ -182,7 +182,7 @@ CLI's shorthand names.
     </tr>
 
     <tr>
-        <th><a href="../../cordova-plugin-file-transfer/">File Transfer</a></th>
+        <th><a href="../../reference/cordova-plugin-file-transfer/">File Transfer</a></th>
         <td data-col="android"    class="y"></td>
         <td data-col="blackberry10" class="y">* Do not support onprogress nor abort</td>
         <td data-col="ios"        class="y"></td>
@@ -192,7 +192,7 @@ CLI's shorthand names.
     </tr>
 
     <tr>
-        <th><a href="../../cordova-plugin-geolocation/">Geolocation</a></th>
+        <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>
@@ -202,7 +202,7 @@ CLI's shorthand names.
     </tr>
 
     <tr>
-        <th><a href="../../cordova-plugin-globalization/">Globalization</a></th>
+        <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>
@@ -212,7 +212,7 @@ CLI's shorthand names.
     </tr>
 
     <tr>
-        <th><a href="../../cordova-plugin-inappbrowser/">InAppBrowser</a></th>
+        <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>
@@ -222,7 +222,7 @@ CLI's shorthand names.
     </tr>
 
     <tr>
-        <th><a href="../../cordova-plugin-media/">Media</a></th>
+        <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>
@@ -232,7 +232,7 @@ CLI's shorthand names.
     </tr>
 
     <tr>
-        <th><a href="../../cordova-plugin-dialogs/">Notification</a></th>
+        <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>
@@ -242,7 +242,7 @@ CLI's shorthand names.
     </tr>
 
     <tr>
-        <th><a href="../../cordova-plugin-splashscreen/">Splashscreen</a></th>
+        <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>
@@ -252,7 +252,7 @@ CLI's shorthand names.
     </tr>
 
     <tr>
-        <th><a href="../../cordova-plugin-statusbar/">Status Bar</a></th>
+        <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>
@@ -272,7 +272,7 @@ CLI's shorthand names.
     </tr>
 
     <tr>
-        <th><a href="../../cordova-plugin-vibration/">Vibration</a></th>
+        <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>

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/e3751865/www/docs/en/6.x/platform_plugin_versioning_ref/index.md
----------------------------------------------------------------------
diff --git a/www/docs/en/6.x/platform_plugin_versioning_ref/index.md b/www/docs/en/6.x/platform_plugin_versioning_ref/index.md
index 3e2c6f6..e07d05c 100644
--- a/www/docs/en/6.x/platform_plugin_versioning_ref/index.md
+++ b/www/docs/en/6.x/platform_plugin_versioning_ref/index.md
@@ -21,7 +21,7 @@ title: Platforms and Plugins Version Management
 ---
 
 # Platforms and Plugins Version Management
-From version 4.3.0 onwards, Cordova provides the ability to save and restore platforms and plugins. 
+From version 4.3.0 onwards, Cordova provides the ability to save and restore platforms and plugins.
 
 This feature allows developers to save and restore their app to a known state without having to check in all of the platform and plugin source code.
 
@@ -36,16 +36,19 @@ One scenario where save/restore capabilities come in handy is in large teams tha
 ### Saving platforms
 To save a platform, you issue the following command :
 
-    $ cordova platform add <platform[@<version>] | directory | git_url> --save
+```bash
+$ cordova platform add <platform[@<version>] | directory | git_url> --save
+```
 
 After running the above command, the resulting config.xml looks like :
 
-    <?xml version='1.0' encoding='utf-8'?>
-        ...
-        <engine name="android" spec="~4.0.0" />
-        ...
-    </xml>
-
+```xml
+<?xml version='1.0' encoding='utf-8'?>
+    ...
+    <engine name="android" spec="~4.0.0" />
+    ...
+</xml>
+```
 
 Some examples :
 
@@ -58,14 +61,18 @@ Some examples :
 The '--save' flag described above is only useful when you remember to use it during the platform addition.
 If you have a pre-existing project and you want to save all the currently added platforms in your project, you can use :
 
-    $ cordova platform save
-
+```bash
+$ cordova platform save
+```
 
 ### Updating / Removing platforms
 It is also possible to update/delete from config.xml during the commands 'cordova platform update' and 'cordova platform remove' :
 
-    $ cordova platform update <platform[@<version>] | directory | git_url> --save
-    $ cordova platform remove <platform> --save
+```bash
+$ cordova platform update <platform[@<version>] | directory | git_url> --save
+$ cordova platform remove <platform> --save
+```
+
 Some examples :
 
   * **'cordova platform update android --save'** => In addition to updating the android platform to the pinned version, update config.xml entry
@@ -84,11 +91,13 @@ Example:
 
 Suppose your config.xml file contains the following entry:
 
-    <?xml version='1.0' encoding='utf-8'?>
-        ...
-        <engine name="android" spec="3.7.0" />
-        ...
-    </xml>
+```xml
+<?xml version='1.0' encoding='utf-8'?>
+    ...
+    <engine name="android" spec="3.7.0" />
+    ...
+</xml>
+```
 
 If you run the command **'cordova platform add android'** (no version/folder/git_url specified), the platform 'android@3.7.0' (as retrieved from config.xml) will be installed.
 
@@ -102,15 +111,19 @@ _(The plugin commands are a mirror of the platform commands)_
 ### Saving plugins
 To save a plugin, you issue the following command :
 
-    $ cordova plugin add <plugin[@<version>] | directory | git_url> --save
+```bash
+$ cordova plugin add <plugin[@<version>] | directory | git_url> --save
+```
 
 After running the above command, the resulting config.xml looks like :
 
-    <?xml version='1.0' encoding='utf-8'?>
-        ...
-        <plugin name="cordova-plugin-console" spec="~1.0.0" />
-        ...
-    </xml>
+```xml
+<?xml version='1.0' encoding='utf-8'?>
+    ...
+    <plugin name="cordova-plugin-console" spec="~1.0.0" />
+    ...
+</xml>
+```
 
 
 Some examples :
@@ -124,14 +137,18 @@ Some examples :
 The '--save' flag described above is only useful when you remember to use it during the plugin addition.
 If you have a pre-existing project and you want to save all currently added plugins in the project, you can use :
 
-    $ cordova plugin save
+```bash
+$ cordova plugin save
+```
 
 
 ### Updating / Removing plugins
 It is also possible to update/delete from config.xml during the commands 'cordova plugin update' and 'cordova plugin remove' :
 
-    $ cordova plugin update <plugin[@<version>] | directory | git_url> --save
-    $ cordova plugin remove <plugin> --save
+```bash
+$ cordova plugin update <plugin[@<version>] | directory | git_url> --save
+$ cordova plugin remove <plugin> --save
+```
 Some examples :
 
   * **'cordova plugin update cordova-plugin-console --save'** => In addition to updating the console plugin to the pinned version, update config.xml entry
@@ -150,11 +167,13 @@ Example:
 
 Suppose your config.xml file contains the following entry:
 
-    <?xml version='1.0' encoding='utf-8'?>
-        ...
-        <plugin name="cordova-plugin-console" spec="0.2.11" />
-        ...
-    </ xml>
+```xml
+<?xml version='1.0' encoding='utf-8'?>
+    ...
+    <plugin name="cordova-plugin-console" spec="0.2.11" />
+    ...
+</ xml>
+```
 
 If you run the command **'cordova plugin add cordova-plugin-console'** (no version/folder/git_url specified), the plugin 'cordova-plugin-console@0.2.11' (as retrieved from config.xml) will be installed.
 

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/e3751865/www/docs/en/6.x/plugin_ref/plugman.md
----------------------------------------------------------------------
diff --git a/www/docs/en/6.x/plugin_ref/plugman.md b/www/docs/en/6.x/plugin_ref/plugman.md
index b7449fb..1dfc352 100644
--- a/www/docs/en/6.x/plugin_ref/plugman.md
+++ b/www/docs/en/6.x/plugin_ref/plugman.md
@@ -74,7 +74,9 @@ listed on the Platform guides page.
 
 Once you have installed Plugman and have created a Cordova project, you can start adding plugins to the platform with:
 
-    $ plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin <name|url|path> [--plugins_dir <directory>] [--www <directory>] [--variable <name>=<value> [--variable <name>=<value> ...]]
+```bash
+$ plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin <name|url|path> [--plugins_dir <directory>] [--www <directory>] [--variable <name>=<value> [--variable <name>=<value> ...]]
+```
 
 Using minimum parameters, this command installs a plugin into a cordova project. You must specify a platform and cordova project location for that platform. You also must specify a plugin, with the different `--plugin` parameter forms being:
 
@@ -92,7 +94,9 @@ Other parameters:
 
 To uninstall a plugin, you simply pass the `--uninstall` flag and provide the plugin ID.
 
-    $ plugman --uninstall --platform <ios|android|blackberry10|wp8> --project <directory> --plugin <id> [--www <directory>] [--plugins_dir <directory>]
+```bash
+$ plugman --uninstall --platform <ios|android|blackberry10|wp8> --project <directory> --plugin <id> [--www <directory>] [--plugins_dir <directory>]
+```
 
 
 ## Help Commands
@@ -100,21 +104,27 @@ To uninstall a plugin, you simply pass the `--uninstall` flag and provide the pl
 Plugman features a global help command which may help you if you get stuck or are experiencing problems. It will display
 a list of all available Plugman commands and their syntax:
 
-    plugman -help
-    plugman  # same as above
+```bash
+plugman -help
+plugman  # same as above
+```
 
-   **NOTE**: `plugman -help` may show some additional registry-related commands. These commands are for plugin developers and may not be implemented on third-party plugin registries.
+**NOTE**: `plugman -help` may show some additional registry-related commands. These commands are for plugin developers and may not be implemented on third-party plugin registries.
 
 
 You can also append the `--debug|-d` flag to any Plugman command to run that command in verbose mode, which will display
 any internal debugging messages as they are emitted and may help you track down problems like missing files.
 
-    # Adding Android battery-status plugin to "myProject":
-    plugman -d --platform android --project myProject --plugin cordova-plugin-battery-status
+```bash
+# Adding Android battery-status plugin to "myProject":
+plugman -d --platform android --project myProject --plugin cordova-plugin-battery-status
+```
 
 Finally, you can use the `--version|-v` flag to see which version of Plugman you are using.
 
-    plugman -v
+```bash
+plugman -v
+```
 
 ## Registry Actions
 
@@ -126,20 +136,26 @@ third-party plugin registries.
 
 You can use Plugman to search the [Plugin registry](http://plugins.cordova.io) for plugin id's that match the given space separated list of keywords.
 
-    plugman search <plugin keywords>
+```bash
+plugman search <plugin keywords>
+```
 
 ### Changing the Plugin Registry
 
 You can get or set the URL of the current plugin registry that plugman is using. Generally you should leave this set at http://registry.cordova.io unless you want to use a third party plugin registry.
 
-    plugman config set registry <url-to-registry>
-    plugman config get registry
+```bash
+plugman config set registry <url-to-registry>
+plugman config get registry
+```
 
 ### Get Plugin Information
 
 You can get information about any specific plugin stored in the plugin repository with:
 
-    plugman info <id>
+```bash
+plugman info <id>
+```
 
 This will contact the plugin registry and fetch information such as the plugin's version number.
 
@@ -152,72 +168,108 @@ platform, and reference the platform's project directory.
 
 * cordova-plugin-battery-status
 
-    `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-battery-status`
+    ```bash
+    plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-battery-status
+    ```
 
 * cordova-plugin-camera
 
-    `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-camera`
+    ```bash
+    plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-camera
+    ```
 
 * cordova-plugin-console
 
-    `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-console`
+    ```bash
+    plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-console
+    ```
 
 * cordova-plugin-contacts
 
-    `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-contacts`
+    ```bash
+    plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-contacts
+    ```
 
 * cordova-plugin-device
 
-    `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-device`
+    ```bash
+    plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-device
+    ```
 
 * cordova-plugin-device-motion (accelerometer)
 
-    `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-device-motion`
+    ```bash
+    plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-device-motion
+    ```
 
 * cordova-plugin-device-orientation (compass)
 
-    `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-device-orientation`
+    ```bash
+    plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-device-orientation
+    ```
 
 * cordova-plugin-dialogs
 
-    `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-dialogs`
+    ```bash
+    plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-dialogs
+    ```
 
 * cordova-plugin-file
 
-    `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-file`
+    ```bash
+    plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-file
+    ```
 
 * cordova-plugin-file-transfer
 
-    `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-file-transfer`
+    ```bash
+    plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-file-transfer
+    ```
 
 * cordova-plugin-geolocation
 
-    `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-geolocation`
+    ```bash
+    plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-geolocation
+    ```
 
 * cordova-plugin-globalization
 
-    `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-globalization`
+    ```bash
+    plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-globalization
+    ```
 
 * cordova-plugin-inappbrowser
 
-    `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-inappbrowser`
+    ```bash
+    plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-inappbrowser
+    ```
 
 * cordova-plugin-media
 
-    `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-media`
+    ```bash
+    plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-media
+    ```
 
 * cordova-plugin-media-capture
 
-    `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-media-capture`
+    ```bash
+    plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-media-capture
+    ```
 
 * cordova-plugin-network-information
 
-    `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-network-information`
+    ```bash
+    plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-network-information
+    ```
 
 * cordova-plugin-splashscreen
 
-    `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-splashscreen`
+    ```bash
+    plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-splashscreen
+    ```
 
 * cordova-plugin-vibration
 
-    `plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-vibration`
+    ```bash
+    plugman --platform <ios|android|blackberry10|wp8> --project <directory> --plugin cordova-plugin-vibration
+    ```

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/e3751865/www/docs/en/6.x/plugin_ref/spec.md
----------------------------------------------------------------------
diff --git a/www/docs/en/6.x/plugin_ref/spec.md b/www/docs/en/6.x/plugin_ref/spec.md
index 3d06e6c..e4d99cd 100644
--- a/www/docs/en/6.x/plugin_ref/spec.md
+++ b/www/docs/en/6.x/plugin_ref/spec.md
@@ -35,7 +35,7 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   version(string) | *Required* <br/> A version number for the plugin. [Semver](http://semver.org/) syntax is supported.
 
   Example:
-  ```
+  ```xml
   <?xml version="1.0" encoding="UTF-8"?>
   <plugin xmlns="http://apache.org/cordova/ns/plugins/1.0"
       xmlns:android="http://schemas.android.com/apk/res/android"
@@ -55,21 +55,21 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   platform(string) | **For custom frameworks only** <br/> *Required* <br/> The platforms your framework supports. You may use the wildcard `*` to say supported for all platforms, specify multiple with a pipe character like `android|ios|blackberry10` or just a single platform like `android`.
 
   Examples:
-  ```
+  ```xml
   <engines>
     <engine name="cordova-android" version="=1.8.0" />
   </engines>
   ```
 
   Engine elements may also specify fuzzy matches using '>', '>=' etc. to avoid repetition, and to reduce maintenance when the underlying platform is updated.
-  ```
+  ```xml
   <engines>
     <engine name="cordova-android" version=">=1.8.0" />
-  </engines>  
+  </engines>
   ```
 
   The `<engine>` tags also has default support for all of the main platforms Cordova exists on. Specifying the cordova engine tag means that all versions of Cordova on any platform must satisfy the engine version attribute. You may also list specific platforms and their versions in order to override the catch-all cordova engine:
-  ```
+  ```xml
   <engines>
     <engine name="cordova" version=">=1.7.0" />
     <engine name="cordova-android" version=">=1.8.0" />
@@ -78,7 +78,7 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   ```
 
   Custom frameworks example:
-  ```
+  ```xml
   <engines>
     <engine name="my_custom_framework" version="1.0.0" platform="android" scriptSrc="path_to_my_custom_framework_version"/>
     <engine name="another_framework" version=">0.2.0" platform="ios|android" scriptSrc="path_to_another_framework_version"/>
@@ -91,7 +91,7 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   The `name` element is used to specify the name of the plugin. This element does not (yet) handle localization.
 
   Example:
-  ```
+  ```xml
   <name>Foo</name>
   ```
 
@@ -100,7 +100,7 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   The `description` element is used to specify the description of the plugin. This element does not (yet) handle localization.
 
   Example:
-  ```
+  ```xml
   <description>Foo plugin description</description>
   ```
 
@@ -109,7 +109,7 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   The content of the `author` element contains the name of the plugin author.
 
   Example:
-  ```
+  ```xml
   <author>Foo plugin author</author>
   ```
 
@@ -118,7 +118,7 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   The content of the `keywords` element contains comma separated keywords to describe the plugin.
 
   Example:
-  ```
+  ```xml
   <keywords>foo,bar</keywords>
   ```
 
@@ -127,7 +127,7 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   This element is used to specify the license of the plugin.
 
   Example:
-  ```
+  ```xml
   <license>Apache 2.0 License</license>
   ```
 
@@ -140,8 +140,8 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   src(string) | *Required* <br/>  Where the file or directory is located in the plugin package, relative to the `plugin.xml` document. If a file does not exist at the specified src location, the CLI stops and reverses the installation process, issues a notification about the conflict, and exits with a non-zero code.
   target(string) | *Required* <br/> Where the file or directory should be located in the Cordova app, relative to the `www` directory. If a file already exists at the target location, the CLI stops and reverses the installation process, issues a notification about the conflict, and exits with a non-zero code.
 
-  Examples: 
-  ```
+  Examples:
+  ```xml
   <!-- a single file, to be copied in the root directory -->
   <asset src="www/foo.js" target="foo.js" />
   <!-- a directory, also to be copied in the root directory -->
@@ -149,7 +149,7 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   ```
 
   Assets can be targeted to subdirectories as well. This will create the `js/experimental` directory within the `www` directory, unless already present, and copy the `new-foo.js` file and renames it to `foo.js`.
-  ```
+  ```xml
   <asset src="www/new-foo.js" target="js/experimental/foo.js" />
   ```
 
@@ -165,7 +165,7 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   Example:
 
   When installing a plugin with the example below, socket.js is copied to `www/plugins/my-plugin-id/socket.js`, and added as an entry to `www/cordova_plugins.js`. At load time, code in `cordova.js` uses XHR to read each file and inject a `<script>` tag into HTML.
-  ```
+  ```xml
   <js-module src="socket.js" name="Socket">
   </js-module>
   ```
@@ -181,7 +181,7 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   target(string) | The namespace where module.exports gets inserted to.
 
   Example:
-  ```
+  ```xml
   <js-module src="socket.js" name="Socket">
     <clobbers target="chrome.socket" />
   </js-module>
@@ -197,7 +197,7 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   target(string) | The namespace which module.exports gets merged to.
 
   Example:
-  ```
+  ```xml
   <js-module src="socket.js" name="Socket">
     <merges target="chrome.socket" />
   </js-module>
@@ -209,7 +209,7 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   Allowed within `<js-module>` element. It implies that your code should be specified with `cordova.require`, but not installed on the `window` object. This is useful when initializing the module, attaching event handlers or otherwise. You can only have up to one `<runs/>` tag. Note that including a `<runs/>` with `<clobbers/>` or `<merges/>` is redundant, since they also `cordova.require` your module.
 
   Example:
-  ```
+  ```xml
   <js-module src="socket.js" name="Socket">
     <runs/>
   </js-module>
@@ -228,7 +228,7 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   version(string) | The version of the plugin depended on. Semver syntax is supported.
 
   Examples:
-  ```
+  ```xml
   <dependency id="cordova-plugin-someplugin" url="https://github.com/myuser/someplugin" commit="428931ada3891801" subdir="some/path/here" />
   <dependency id="cordova-plugin-someplugin" version="1.0.1">
   ```
@@ -242,7 +242,7 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   name(string) | *Required* <br/> Allowed values: ios, android, blackberry10, amazon-fireos, wp8, windows <br/> Identifies a platform as supported, associating the element's children with that platform.
 
   Example:
-  ```
+  ```xml
   <platform name="android">
     <!-- android-specific elements -->
   </platform>
@@ -260,7 +260,7 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   compiler-flags(string) | ==iOS== <br/> If set, assigns the specified compiler flags for the particular source file.
 
   Examples:
-  ```
+  ```xml
   <!-- android -->
   <source-file src="src/android/Foo.java" target-dir="src/com/alunny/foo" />
   <!-- ios -->
@@ -281,12 +281,12 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   Example:
 
   For iOS:
-  ```
+  ```xml
   <header-file src="CDVFoo.h" />
   ```
 
 ### resource-file
-  
+
   This is like `<source-file>` element, but specifically for platforms such as iOS and Android that distinguish between source files, headers, and resources.
 
   Attributes(type) | Description
@@ -300,12 +300,12 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   Examples:
 
   For Android:
-  ```
+  ```xml
   <resource-file src="FooPluginStrings.xml" target="res/values/FooPluginStrings.xml" />
   ```
 
   For Windows:
-  ```
+  ```xml
   <resource-file src="src/windows/win81/MobServices.pri" target="win81/MobServices.pri" device-target="windows" versions="8.1" arch="x64"/>
   ```
 
@@ -325,8 +325,8 @@ Plugin.xml file defines the structure and settings required for your plugin. It
 
   Examples:
 
-  For XML: 
-  ```
+  For XML:
+  ```xml
   <config-file target="AndroidManifest.xml" parent="/manifest/application">
       <activity android:name="com.foo.Foo" android:label="@string/app_name">
           <intent-filter>
@@ -335,8 +335,8 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   </config-file>
   ```
 
-  For `plist`: 
-  ```
+  For `plist`:
+  ```xml
   <config-file target="*-Info.plist" parent="CFBundleURLTypes">
       <array>
           <dict>
@@ -348,7 +348,7 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   ```
 
   For windows-specific attributes:
-  ```
+  ```xml
   <config-file target="package.appxmanifest" parent="/Package/Capabilities" versions="<8.1.0">
       <Capability Name="picturesLibrary" />
       <DeviceCapability Name="webcam" />
@@ -357,14 +357,14 @@ Plugin.xml file defines the structure and settings required for your plugin. It
       <DeviceCapability Name="webcam" />
   </config-file>
   ```
-  The above example will set pre-8.1 platforms (Windows 8, specifically) to require the `webcam` device capability and the `picturesLibrary` general capability, and apply the `webcam` device capability only to Windows 8.1 projects that build for Windows Phone.  Windows desktop 8.1 systems are unmodified. 
+  The above example will set pre-8.1 platforms (Windows 8, specifically) to require the `webcam` device capability and the `picturesLibrary` general capability, and apply the `webcam` device capability only to Windows 8.1 projects that build for Windows Phone.  Windows desktop 8.1 systems are unmodified.
 
 ### plugins-plist
 
-  Specifies a key and value to append to the correct `AppInfo.plist` file in an iOS Cordova project. This is _outdated_ as it only applies to cordova-ios 2.2.0 and below. Use the `<config-file>` tag for newer versions of Cordova. 
+  Specifies a key and value to append to the correct `AppInfo.plist` file in an iOS Cordova project. This is _outdated_ as it only applies to cordova-ios 2.2.0 and below. Use the `<config-file>` tag for newer versions of Cordova.
 
   Example:
-  ```
+  ```xml
   <plugins-plist key="Foo" string="CDVFoo" />
   ```
 
@@ -380,13 +380,13 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   versions(string) | ==windows== <br/> Indicates that the `<SDKReference>` should only be included when building for versions that match the specified version string. Value can be any valid node semantic version range string.
 
   Examples:
-  ```
+  ```xml
   <lib-file src="src/BlackBerry10/native/device/libfoo.so" arch="device" />
   <lib-file src="src/BlackBerry10/native/simulator/libfoo.so" arch="simulator" />
   ```
 
   For Windows:
-  ```
+  ```xml
   <lib-file src="Microsoft.WinJS.2.0, Version=1.0" arch="x86" />
   <lib-file src="Microsoft.WinJS.2.0, Version=1.0" versions=">=8.1" />
   <lib-file src="Microsoft.WinJS.2.0, Version=1.0" target="phone" />
@@ -404,22 +404,22 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   weak(boolean) | *Default: false* <br/> Indicates whether the framework should be weakly linked.
   type(string) | Indicates the type of framework to add.
   parent(string) | *Default: .* <br/> Sets the relative path to the directory containing the sub-project to which to add the reference. The default, `.`, implies the application project.
-  arch(string) | ==windows== <br/> Allowed values: `x86`, `x64` or `ARM`. <br/> Indicates that the framework should only be included when building for the specified architecture. 
+  arch(string) | ==windows== <br/> Allowed values: `x86`, `x64` or `ARM`. <br/> Indicates that the framework should only be included when building for the specified architecture.
   device-target(string) | ==windows== <br/> Allowed values: `win` (or `windows`), `phone` or `all`. <br/>  Indicates that the framework should only be included when building for the specified target device type.
   versions(string) | ==windows== <br/> Indicates that the framework should only be included when building for versions that match the specified version string. Value can be any valid node semantic version range string.
   target-dir(string) | ==windows== <br/>  Indicates a subdirectory into which the framework should be copied. In practice, this is most important when plugin contains different framework versions for different chip architectures or device targets, but which have the same name. This allows you to specify different subfolders for each framework version so that they don't overlap each other.
 
   Examples:
 
-  For iOS: 
-  ```
+  For iOS:
+  ```xml
   <framework src="libsqlite3.dylib" />
   <framework src="social.framework" weak="true" />
   <framework src="relative/path/to/my.framework" custom="true" />
   ```
 
   On Android (as of cordova-android@4.0.0), framework tags are used to include Maven dependencies, or to include bundled library projects.
-  ```
+  ```xml
   <!-- Depend on latest version of GCM from play services -->
   <framework src="com.google.android.gms:play-services-gcm:+" />
   <!-- Depend on v21 of appcompat-v7 support library -->
@@ -429,17 +429,17 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   ```
 
   Framework can also be used to have custom .gradle files sub-included into the main project's .gradle file:
-  ```
+  ```xml
   <framework src="relative/path/rules.gradle" custom="true" type="gradleReference" />
   ```
 
   On Windows, using `custom='true'` and `type='projectReference'` will add a reference to the project which will be added to the compile+link steps of the cordova project.  This essentially is the only way currently that a 'custom' framework can target multiple architectures as they are explicitly built as a dependency by the referencing cordova application.
-  ```
+  ```xml
   <framework src="path/to/project/LibProj.csproj" custom="true" type="projectReference"/>
   ```
 
   Examples of using these Windows specific attributes:
-  ```  
+  ```xml
   <framework src="src/windows/example.dll" arch="x64" />
   <framework src="src/windows/example.dll" versions=">=8.0" />
   <framework src="src/windows/example.vcxproj" type="projectReference" target="win" />
@@ -452,7 +452,7 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   Additional information provided to users. This is useful when you require extra steps that can't be easily automated or are beyond the CLI's scope. The contents of this tag gets printed out when the CLI installs the plugin.
 
   Example:
-  ```
+  ```xml
   <info>
   You need to install __Google Play Services__ from the `Android Extras` section using the Android SDK manager (run `android`).
 
@@ -466,8 +466,8 @@ Plugin.xml file defines the structure and settings required for your plugin. It
 
   Represents your custom script which will be called by Cordova when certain action occurs (for example, after plugin is added or platform prepare logic is invoked). This is useful when you need to extend default Cordova functionality. See [Hooks Guide](../guide/appdev/hooks/index.html) for more information.
 
-  Example: 
-  ```
+  Example:
+  ```xml
   <hook type="after_plugin_install" src="scripts/afterPluginInstall.js" />
   ```
 
@@ -475,13 +475,13 @@ Plugin.xml file defines the structure and settings required for your plugin. It
 
   In certain cases, a plugin may need to make configuration changes dependent on the target application. For example, to register for C2DM on Android, an app whose package id is `my-app-id` would require a permission such as:
 
-  ```
+  ```xml
   <uses-permission android:name="my-app-id.permission.C2D_MESSAGE"/>
   ```
 
   In such cases where the content inserted from the `plugin.xml` file is not known ahead of time, variables can be indicated by a dollar-sign followed by a series of capital letters, digits, or underscores. For the above example, the `plugin.xml` file would include this tag:
 
-  ```  
+  ```xml
   <uses-permission android:name="$PACKAGE_NAME.permission.C2D_MESSAGE"/>
   ```
 
@@ -489,7 +489,7 @@ Plugin.xml file defines the structure and settings required for your plugin. It
 
   Plugman can request users to specify a plugin's required variables. For example, API keys for C2M and Google Maps can be specified as a command-line argument:
 
-  ```
+  ```bash
   plugman --platform android --project /path/to/project --plugin name|git-url|path --variable API_KEY=!@CFATGWE%^WGSFDGSDFW$%^#$%YTHGsdfhsfhyer56734
   ```
 
@@ -498,7 +498,7 @@ Plugin.xml file defines the structure and settings required for your plugin. It
 ## preference
 
   As seen in the previous section, sometimes plugin might require user to specify values for their variables. To make those variable mandatory, the `<platform>` tag needs to contain
-  a `<preference>` tag. 
+  a `<preference>` tag.
   The CLI checks that these required preferences are passed in.  If not, it should warn the user how to pass the variable in and exit with a non-zero code.
 
   Attributes(type) | Description
@@ -507,6 +507,6 @@ Plugin.xml file defines the structure and settings required for your plugin. It
   default(string) | Default value of the variable. If present, its value will be used and no error will be emitted in case user does not enter any value.
 
   Example:
-  ```
+  ```xml
   <preference name="API_KEY" default="default-value" />
   ```


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


Mime
View raw message