Dynamic plug-in doc updates

Author: opayne1

modules/about-dynamic-plug-ins.adoc

@@ -30,5 +30,14 @@ When creating your plug-in, follow these general guidelines:
 
 * Prefix your CSS class names with your plug-in name to avoid collisions. For example, `my-plugin_\_heading` and `my-plugin_\_icon`.
 * Maintain a consistent look, feel, and behavior with other console pages.
-* Use link:https://github.com/openshift/enhancements/blob/master/enhancements/console/dynamic-plugins.md#localization[react-i18next] for localization.
+* Follow link:https://www.i18next.com/[react-i18next] localization guidelines when creating your plug-in. You can use the `useTranslation` hook like the one in the following example:
++
+[source,ymal]
+----
+conster Header: React.FC = () => {
+  const { t } = useTranslation('plugin__console-demo-plugin');
+  return <h1>{t('Hello, World!')}</h1>;
+};
+----
+
 * _Do not_ use console CSS classes in your markup or override console CSS classes. These are not APIs and are subject to change. Using them might break your plug-in. Avoid selectors like element selectors that could affect markup outside of your plug-in’s components.

modules/adding-new-extension-dynamic-plug-in.adoc

@@ -2,7 +2,34 @@
 //
 // * web_console/dynamic-plug-ins.adoc
 
-:_content-type: CONCEPT
+:_content-type: PROCEDURE
 [id="adding-new-extension-dynamic-plugin_{context}"]
 = Adding a new extension to your plug-in
-You can add extensions to your plug-in that are loaded at runtime. 
+You can add extensions that allow you to customize your plug-in. Those extensions are then loaded to the console at run-time.
+
+. Edit the `console-extensions.json` file:
++
+[source,json]
+----
+[
+ {
+    "type": "console.flag", <1>
+    "properties": {
+      "handler": { "$codeRef": "barUtils.testHandler" } <2>
+    }
+  },
+  {
+    "type": "console.flag/model",
+    "properties": {
+      "flag": "EXAMPLE",
+      "model": {
+        "group": "kubevirt.io",
+        "version": "v1alpha3",
+        "kind": "ExampleModel"
+      }
+    }
+  }
+]
+----
+<1> Add the extension type(s) you want to include with this plug-in. You can include multiple extensions separated with a comma.
+<2> The `$codeRef` value should be formatted as either `moduleName.exportName` for a named export or `moduleName` for the default export. Only the plug-in’s exported modules can be used in code references.

modules/deployment-plug-in-cluster.adoc

@@ -10,7 +10,7 @@ After pushing an image with your changes to a registry, you can deploy the plug-
 
 .Procedure
 
-. To deploy your plug-in to a cluster, instantiate the link:https://github.com/spadgett/console-plugin-template/blob/main/template.yaml[template] by running the following command:
+. To deploy your plug-in to a cluster, instantiate your plug-in by running the following command:
 +
 [source,terminal]
 ----
@@ -26,7 +26,10 @@ $ oc process -f template.yaml \
 +
 This command runs a light-weight NGINX HTTP server to serve the assets for your plug-in.
 
-IMPORTANT: `PLUGIN_NAME` must match the plug-in name you used in the `consolePlugin` declaration of `package.json`.
+[IMPORTANT]
+====
+`PLUGIN_NAME` must match the plug-in name you used in the `consolePlugin` declaration of `package.json`.
+====
 
 [start=2]
 . Patch the *Console Operator* configuration to enable the plug-in by running the following command:

modules/disabling-plug-in-browser.adoc

@@ -0,0 +1,20 @@
+// Module included in the following assemblies:
+//
+// * web_console/dynamic-plug-ins.adoc
+
+:_content-type: PROCEDURE
+[id="disabling-your-plug-in-browser_{context}"]
+= Disabling your plug-in in the browser
+
+Console users can use the `disable-plugins` query parameter to disable specific or all dynamic plug-ins that would normally get loaded at run-time.
+
+.Procedure
+
+* To disable a specific plug-in(s), remove the plug-in you want to disable from the comma-separated list of plug-in names.
+
+* To disable all plug-ins, leave an an empty string in the `disable-plugins` query parameter.
+
+[NOTE]
+====
+Cluster administrators can disable plug-ins in the *Cluster Settings* page of the web console
+====