iOS: Update plugin documentation

docs/site/pages/plugins/beacon.mdx

@@ -32,6 +32,8 @@ interface DefaultBeacon {
 }
 ```
 
+## Usage
+
 <PlatformTabs>
   <core>
 
@@ -94,6 +96,15 @@ This will add additional React Context to the running player for the producers f
   </react>
   <ios>
 
+### CocoaPods
+Add the subspec to your `Podfile`
+
+```ruby
+pod 'PlayerUI/BeaconPlugin'
+```
+
+### Swift Usage
+
 To receive Beacon events from Player in iOS, add the `BeaconPlugin` to your plugin array:
 
 ```swift
@@ -102,7 +113,7 @@ var body: some View {
     flow: flow,
     plugins: [
       BeaconPlugin<DefaultBeacon> { (beacon: DefaultBeacon) in
-				// Process beacon into the format you need for Segment/Trinity and send it on
+				// Process beacon into the format you need for your analytics platform
 			}
     ]
   )
@@ -264,6 +275,8 @@ export const Component = (props) => {
   </react>
   <ios>
 
+The SwiftUIBeaconPlugin attaches a BeaconContext to the root of the SwiftUI view tree as an environment value, so when included any asset can use that context to send a beacon, if the context is in the environment:
+
 ```swift
 struct ActionAssetView: View {
   @ObservedObject var viewModel: AssetViewModel<ActionData>
@@ -275,4 +288,4 @@ struct ActionAssetView: View {
 ```
 
   </ios>
-</PlatformTabs>
+</PlatformTabs>

docs/site/pages/plugins/check-path.mdx

@@ -63,6 +63,34 @@ const rp = new ReactPlayer({
 This will automatically create the underlying _core_ version of the `CheckPathPlugin` to be made available via `React` Context for the hooks.
 
   </react>
+
+<ios>
+
+### CocoaPods
+
+Add the subspec to your `Podfile`
+
+```ruby
+pod 'PlayerUI/SwiftUICheckPathPlugin'
+```
+
+### Swift Usage
+
+This plugin takes no parameters, and the configuration comes from content, it can just be added to the plugin array:
+
+```swift
+var body: some View {
+    SwiftUIPlayer(
+        flow: flow,
+        plugins: [
+          SwiftUICheckPathPlugin()
+        ],
+        result: $resultBinding
+    )
+}
+```
+</ios>
+
 </PlatformTabs>
 
 
@@ -149,6 +177,30 @@ export const MyAsset = ({ id }) => {
 ```
 
   </react>
+  <ios>
+
+### Swift Usage
+
+The SwiftUICheckPathPlugin attaches the `BaseCheckPathPlugin`  named `checkPath` to the root of the SwiftUI view tree as an environment value, so when included any asset can use that environment value to access the base functionality
+
+```swift
+
+struct MyAsset: View {
+    @ObservedObject var viewModel: AssetViewModel<AssetData>
+    @Environment(\.checkPath) var checkPath
+
+    var body: some View {
+       let isInForm = checkPath?.hasParentContext(id: viewModal.data.id, query: "form")
+       if isInForm {
+         SelectChoice()
+       } else {
+         RadioGroup()
+    }
+}
+
+```
+</ios>
+
 </PlatformTabs>
 
 

docs/site/pages/plugins/common-expressions.mdx

@@ -9,6 +9,64 @@ This plugin exposes some basic expressions into Player content.
 
 It also serves as a good reference to adding your own custom expressions into Player.
 
+## Usage
+
+<PlatformTabs>
+  <core>
+
+Install the plugin:
+
+```bash
+yarn add @player-ui/common-types-plugin
+```
+
+Add it to Player:
+```js
+import CommonExpressionsPlugin from '@player-ui/common-expressions-plugin';
+
+const commonExpressionsPlugin = new CommonExpressionsPlugin();
+const player = new Player({ plugins: [commonExpressionsPlugin] });
+
+// Start your flow
+player.start(myFlow);
+```
+
+This will allow any included expressions or custom expressions to be used in the content
+
+  </core>
+
+<ios>
+
+### CocoaPods
+
+Add the subspec to your `Podfile`
+
+```ruby
+
+pod 'PlayerUI/CommonExpressionsPlugin'
+
+```
+
+### Swift Usage
+
+This plugin takes no parameters, and the configuration comes from content, it can just be added to the plugin array:
+
+```swift
+
+var body: some View {
+    SwiftUIPlayer(
+        flow: flow,
+        plugins: [
+          CommonExpressionsPlugin()
+        ],
+        result: $resultBinding
+    )
+}
+```
+</ios>
+
+</PlatformTabs>
+
 ---
 
 ## General

docs/site/pages/plugins/common-types.mdx

@@ -9,7 +9,65 @@ This plugin exposes some basic `DataTypes`, `validations`, and `formats` into Pl
 
 It also serves as a good reference to adding your own custom types into Player.
 
----
+## Usage
+
+<PlatformTabs>
+  <core>
+
+Install the plugin:
+
+```bash
+yarn add @player-ui/common-types-plugin
+```
+
+Add it to Player:
+```js
+import CommonTypesPlugin from '@player-ui/common-types-plugin';
+
+const commonTypesPlugin = new CommonTypesPlugin();
+const player = new Player({ plugins: [commonTypesPlugin] });
+
+// Start your flow
+player.start(myFlow);
+```
+
+This will allow any `DataTypes`, `formats`, `validations` and custom data types to be used in the content
+
+  </core>
+
+<ios>
+
+### CocoaPods
+
+Add the subspec to your `Podfile`
+
+```ruby
+
+pod 'PlayerUI/CommonTypesPlugin'
+
+```
+
+### Swift Usage
+
+This plugin takes no parameters, and the configuration comes from content, it can just be added to the plugin array:
+
+```swift
+
+var body: some View {
+    SwiftUIPlayer(
+        flow: flow,
+        plugins: [
+          CommonTypesPlugin()
+        ],
+        result: $resultBinding
+    )
+}
+```
+
+</ios>
+
+</PlatformTabs>
+
 
 ## Formats
 
@@ -313,4 +371,4 @@ Options:
 > A value representing a phone number
 
 * **validations**: `phone`
-* **format**: `phone` (`(###) ###-####`)
+* **format**: `phone` (`(###) ###-####`)

docs/site/pages/plugins/computed-properties.mdx

@@ -25,6 +25,33 @@ const player = new Player({
 ```
 
   </core>
+
+  <ios>
+
+### CocoaPods
+
+Add the subspec to your `Podfile`
+
+```ruby
+pod 'PlayerUI/ComputedPropertiesPlugin'
+```
+
+### Swift Usage
+
+This plugin takes no parameters, and the configuration comes from content, it can just be added to the plugin array:
+
+```swift
+var body: some View {
+    SwiftUIPlayer(
+        flow: flow,
+        plugins: [
+          ComputedPropertiesPlugin()
+        ],
+        result: $resultBinding
+    )
+}
+```
+  </ios>
 </PlatformTabs>
 
 ## Expression Data Type
@@ -62,4 +89,4 @@ Any data-lookup for that binding path will evaluate the given expression and ret
 
 Using the above schema, any reference to `{{foo.computedValue}}` will compute the `1 + 2 + 3` expression and use that as the underlying value for that path.
 
-Any write or set operation to `{{foo.computedValue}}` will result in a thrown exception for writing to a read-only path.
+Any write or set operation to `{{foo.computedValue}}` will result in a thrown exception for writing to a read-only path.

docs/site/pages/plugins/console-logger.mdx

@@ -34,23 +34,28 @@ consoleLogger.setSeverity('warn');
   </core>
   <ios>
 
-Add the subspec:
+### CocoaPods
+Add the subspec to your `Podfile`
 
 ```ruby
 pod 'PlayerUI/PrintLoggerPlugin'
 ```
 
-Construct the plugin:
+### Swift Usage
 
 ```swift
-SwiftUIPlayer(
-  flow: flow,
-  plugins: [PrintLoggerPlugin()],
-  result: $result
-)
+var body: some View {
+    SwiftUIPlayer(
+        flow: flow,
+        plugins: [
+          PrintLoggerPlugin()
+        ],
+        result: $resultBinding
+    )
+}
 ```
 
-To change the severity:
+To change the severity, supply it as an argument to the constructor:
 ```swift
 PrintLoggerPlugin(level: .warn)
 ```

docs/site/pages/plugins/expression.mdx

@@ -52,7 +52,14 @@ Any calls to `myCustomFunction()` within the flow will utilize the newly registe
   </core>
   <ios>
 
-### Use 
+### CocoaPods
+Add the subspec to your `Podfile`
+
+```ruby
+pod 'PlayerUI/ExpressionPlugin'
+```
+
+### Swift Usage
 
 The ExpressionPlugin lets you register custom expressions to run native code:
 
@@ -71,7 +78,7 @@ let expressionPlugin = ExpressionPlugin(expressions: [
 	}
 ])
 ```
-### Arguments
+#### Arguments
 
 Arguments can be passed to custom expressions, and your handler receives the arguments as an array of Any: