docs(va): move the embed page to /visualanalytics

- rename docs/embed-va.md -> docs/visualanalytics.md, so the page is served
  at /visualanalytics/
- redirect the old /embed-va/ path to the new one
- point the three inbound links (index, filter, deploy-viya) at the new path
- fill in og_title and og_image so link previews carry the page title and a
  card image instead of the site defaults
- the object's author often has elevated permissions, not usually an admin

docs/deploy-viya.md

@@ -175,4 +175,4 @@ It is possible to embed a Data Controller table within SAS Visual Analytics by s
 
 To make the portlet more visually appealing, the Data Controller title bar can be removed by adding `?embed=true` to the URL.  When opening in a new window, the title bar will be gone.
 
-For a deeper VA integration - where report row selections drive filters and column visibility in the Data Controller editor - append `?embed=va` instead.  See the [SAS Visual Analytics Embed](/embed-va/) page for details on filter modes, configuration, and debugging.
+For a deeper VA integration - where report row selections drive filters and column visibility in the Data Controller editor - append `?embed=va` instead.  See the [SAS Visual Analytics Embed](/visualanalytics/) page for details on filter modes, configuration, and debugging.

docs/filter.md

@@ -7,7 +7,7 @@ og_image:  https://docs.datacontroller.io/img/filter_dynamic_on.png
 
 # Filtering
 
-Data Controller for SAS® enables you to create complex table filters. The "dynamic" setting enables the dropdown values to be pre-filtered by previous filter clauses.  Filtered views are shareable!  They are also used when [embedded in VA.](/embed-va)
+Data Controller for SAS® enables you to create complex table filters. The "dynamic" setting enables the dropdown values to be pre-filtered by previous filter clauses.  Filtered views are shareable!  They are also used when [embedded in VA.](/visualanalytics/)
 
 The clause shown above the grid is the resolved WHERE clause that was applied, so it uses SAS syntax - a date, datetime or time filter reads as a SAS literal, eg `SOME_DATE = '20APR2042'd`, rather than the internal day or second count.
 

docs/index.md

@@ -42,7 +42,7 @@ Data Controller is regularly updated with new features.  If you see something th
 * [Row Level Security](/row-level-security)
 * Excel [formula support](excel)
 * Dynamic [cell dropdown](/dynamic-cell-dropdown)
-* [SAS Visual Analytics embed](/embed-va/) - drive the editor from VA report selections
+* [SAS Visual Analytics embed](/visualanalytics/) - drive the editor from VA report selections
 * Works on ALL flavours of SAS (Base, EBI, Viya)
 
 

docs/visualanalytics.md

@@ -1,7 +1,9 @@
 ---
 layout: article
 title: SAS Visual Analytics Embed
-description: Embed the Data Controller editor inside a SAS VA report as a data-driven content object.  Row selections in the VA report drive filters and column visibility in the editor.
+description: Embed the Data Controller editor inside a SAS Visual Analytics report as a data-driven content object, so report selections drive filters and column visibility in the editor.
+og_title: Embedding Data Controller in SAS Visual Analytics
+og_image: https://docs.datacontroller.io/img/va-embed-og.png
 ---
 
 # Embedding inside SAS Visual Analytics
@@ -183,7 +185,7 @@ The mapping lives entirely in the URL of the report object, so the job is to get
 
 The object runs as the person **viewing** the report, using their SAS identity - there is no service account behind it. That person must therefore be a registered Data Controller user: if they are not, DC shows its login card inside the object instead of the editor, which looks like a broken embed rather than a permissions matter.
 
-Register everyone who will open the report before you ship it (Users in DC), and test the report as one of them rather than as the person who built it - the author is usually an administrator, so a report that works for them can fail for everyone else.
+Register everyone who will open the report before you ship it (Users in DC), and test the report as one of them rather than as the person who built it - the author often has elevated permissions, so a report that works for them can fail for everyone else.
 
 ## Debugging
 

mkdocs.yml

@@ -73,7 +73,7 @@ nav:
     - Selectboxes: dcc-selectbox.md
     - Tables: dcc-tables.md
     - Validations: dcc-validations.md
-    - Visual Analytics: embed-va.md
+    - Visual Analytics: visualanalytics.md
 - Macros: macros.md
 - Installation:
     - System Requirements: dci-requirements.md
@@ -113,6 +113,7 @@ plugins:
       redirect_maps:
           'dci-evaluation.md': 'dci-deploysas9.md'
           'dcu-fileupload.md': 'files.md'
+          'embed-va.md': 'visualanalytics.md'
 
 # Repository
 repo_name: 'dc/docs.datacontroller.io'