Merge pull request #1199 from validmind/staging

Merge staging into prod for 26.03

Author: nrichers

.github/actions/setup-r/action.yml

@@ -59,9 +59,6 @@ jobs:
         with:
           version: ${{ vars.QUARTO_VERSION }}
 
-      - name: Setup R environment
-        uses: ./.github/actions/setup-r
-
       - name: Install Poetry
         run: |
           curl -sSL https://install.python-poetry.org | python3 -

.github/workflows/deploy-docs-prod.yaml

@@ -59,9 +59,6 @@ jobs:
         with:
           version: ${{ vars.QUARTO_VERSION }}
 
-      - name: Setup R environment
-        uses: ./.github/actions/setup-r
-
       - name: Install Poetry
         run: |
           curl -sSL https://install.python-poetry.org | python3 -

.github/workflows/deploy-docs-staging.yaml

@@ -59,9 +59,6 @@ jobs:
       with:
         version: ${{ vars.QUARTO_VERSION }}
 
-    - name: Setup R environment
-      uses: ./.github/actions/setup-r
-
     - name: Install Poetry
       run: |
         curl -sSL https://install.python-poetry.org | python3 -

.github/workflows/validate-docs-site.yaml

@@ -9,7 +9,7 @@ attestation instance
 : The invocation of the attestation process on the {{< var validmind.platform >}}. Created when the attestation is triggered by the schedule you set up, it includes a snapshot with model activity and artifacts, questionnaire responses and review status, forming a full record of the review and approval process. 
 
 attestation participant
-: A user assigned to one of three roles in the attestation workflow — submitter, reviewer, or approver. Submitters must be model stakeholders; reviewers and approvers can be assigned by stakeholder or role.
+: A user who participates in the attestation workflow as a submitter, reviewer, or approver. Submitters are assigned from model stakeholders; reviewers and approvers are assigned from organizational roles.
 
 attestation period  
 : The time window during which attestation is active, with fixed start and end dates. Each period creates an unchanging model snapshot. Periods are usually scheduled quarterly or annually and can align with regulatory or internal cycles.

internal/testing/mobile-demo/new-docs-site.mov

@@ -7,7 +7,7 @@ a {
 }
 
 /* Section-specific underline treatments */
-div[id^="fn"] a:hover,
+div[id^="fn"] a:hover:not(.button),
 #connect-with-us a:hover,
 #prerequisites a:hover,
 #supported-model-types a:hover,

internal/testing/mobile-demo/old-docs-site.mov

@@ -6,7 +6,7 @@ SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
 
 a. In the left sidebar that appears for your model, click **{{< fa file >}} Documents** and select **Documentation**.
 
-b. Under **[template]{.smallcaps}**, select `Binary classification`.
+b. Under [create document]{.smallcaps}, select `Binary classification` from the **[template]{.smallcaps}** drop-down menu.
 
 c. Click **Use Template** to apply the template.
 
@@ -20,7 +20,7 @@ c. Click **Use Template** to apply the template.
 :::: {.content-visible unless-format="revealjs" unless-meta="includes.developer"}
 a. In the left sidebar that appears for your model, click **{{< fa file >}} Documents** and select **Validation Report**.
 
-a. Under **[template]{.smallcaps}**, select `Generic Validation Report`.
+b. Under [create document]{.smallcaps}, select `Generic Validation Report` from the **[template]{.smallcaps}** drop-down menu.
 
 c. Click **Use Template** to apply the template.