prod: June 2nd, 2025 by validbeck · Pull Request #742 · validmind/documentation

validbeck · 2025-06-02T17:41:14Z

Internal Notes for Reviewers

* Editing new quickstart links * Pulled in notebooks from beck/sc-7911/edit-code-samples-notebooks-quickstart-for * Typo * Removing old move command * Pulled in latest changes for quickstart for model documentation --------- Co-authored-by: Lois Ansah <loiscodes@gmail.com>

Merge main into staging

* Add initial Lighthouse, and Vale checks * Add Vale config file, update readme * More Vale config shenanigans * Yet more Vale fun * Switch vale sync to install * Increase Ligthouse level to 1 * Add mkdir step * Update readme again, bump lighthose to depth 2 * Fix .vale.ini and sync packages * Simplify Vale workflow after package install * Bump down Lighthouse depth to 1 * Fix JSON output for Vale * Switch to environment variable for depth * Work around comment lenght limit for Vale * Add debug info for sitemap URL * Bump up Vale linter to post the first 30 files and ignore *.yml * Simplify Vale linter message * Experiment with new Lighthouse depth var * Simplify Vale message yet again * Add debug info to sitemap generation step * Move sitemap generation into Makefile and add as post-render step * Improve check for preview URL & sitemap * Add wait loop for preview site * Fix timestamp issue for GitHub * Undo make get-source * Fix Lighthouse URL list logic, again * Better debug for URL list, update readme * Yet mode debugging for URL list * Update get_url_depth logic to omit the slashes in the base URL * We have another bug * Try to fix get_urls_from_sitemap * Reduce debug clutter * Uncomment print statement * Fix HEAD issue in path in URL list * More logic fixed * Switch to simpler logic for depth and root pages * Try depth level 1 * Switch back to depth 0 * Switch back to depth 1 and attempt to fix path issue * Attempt to fix HEAD in URL issue, again * Try fixing branch for post-render step again, revert to depth 0 for now * Try fixing PR branch error * Try Makefile to get the PR branch again * Attempt to fetch branch in workflow, again * feat: repair helm chart conflicts * Also update Makefile * Remove some debug info * Undo unrelated changes * Undo newline for validate docs site workflow * Attempt to fetch the branch name on GitHub again * Progress but still not quite the branch name * Change depth level to 1 * Add check for Lighthouse audit result * Try to fix URL construction issue & better authentication * Try to fix URL segment duplication issue, again * Add commit SHA to Lighthouse comment * Add earlier step to check if we can access password-protected page * Improve URL-based authentication * Add debug info * Sometimes it's as simple as the wrong preview base URL ... * Simplify auth check * Verbose curl to understand why this is failing still ... * Simplify function def * Simplify, improve ... something * Cursor yeeting the correct URLs again for no reason at all ... * Yeet auth headers step and simplify other stuff * Fix generate URLs to check step * Use same URL-based auth for Lighthouse audit step * DEFAULT_DEPTH to 0 and add links to reports * Add better URLs to PR comment * Try to fix report URLs, again * Better report URLs for individual topics * Update readme * Minor readme tweak * Minor readme tweak * Minor readme tweak * Changed default depth to 1 * Changed default depth back to 0 * Change DEFAULT_DEPTH to 1 * Initial HTML sitemap * Update permissions for workflow * Remove duplicate permissions section * Change DEFAULT_DEPTH back to 0 before merging --------- Co-authored-by: Spencer Krum <nibz@validmind.ai> Co-authored-by: Lois Ansah <loiscodes@gmail.com>

Merge main into staging

…734) * Adding slideover extension * Adding slideover examples to training template * slideover BG adjust * slideover border styling * slideover bold & links * slideover embed * slideover code adjust * Tweaking embed & code * Editing * Fixing top & left rotational arrows * Applying width fixes here too * Updating template reference * Editing * .three-quarters * Tweak

Merge main into staging

) * Latest notebooks from beck/sc-10339/create-code-samples-notebook-quickstart-for * Linking new validation quickstart * New notebook edits * More updates * Pulled in the changes from VAlidmind-library --------- Co-authored-by: Lois Ansah <loiscodes@gmail.com>

Merge main into staging

* if condition for workflow success * Add retries to gh pr merge step * Add space before ellipsis, the shame ... --------- Co-authored-by: Nik Richers <nik@validmind.ai>

Merge main into staging

…r fundamentals (#740) * Developer Fundamentals 1 - slideovers * Fixed auto-collapse arrow directions * Developer Fundamentals 2 - slideovers * Developer Fundamentals 3 - slideovers * Developer Fundamentals 4 - slideovers * Developer Fundamentals slideovers - proofreading * Setup for Validator Fundamentals slideovers * Validation Fundamentals 1 - slideovers * Custom slideover CSS * Pulling in latest slideover css * Validation Fundamentals - slideovers * Proofreading + removing old validator fundamentals * Proofreading pt2 * Proofreading pt3 * Final proofread

Merge main into staging

github-actions · 2025-06-02T17:43:30Z

Vale source linter

⚠️ WARN: Found 13252 issues across 604 files — Check the workflow run or download the full report

Show first 30 files with issues

site/404.qmd

Line 2: Use parentheses judiciously. (suggestion)
Line 3: Did you really mean 'html'? (error)
Line 53: Did you really mean 'const'? (error)
Line 53: Use parentheses judiciously. (suggestion)
Line 54: Did you really mean 'const'? (error)
Line 54: Did you really mean 'ctx'? (error)
Line 54: Use parentheses judiciously. (suggestion)
Line 54: Put a nonbreaking space between the number and the unit in '2d'. (error)
Line 58: Did you really mean 'const'? (error)
Line 58: Did you really mean 'fontSize'? (error)
... and 23 more issues

site/about/contributing/style-guide/conventions.qmd

Line 6: Use 'it's' instead of 'it is'. (suggestion)
Line 6: In general, use active voice instead of passive voice ('is received'). (suggestion)
Line 6: Use parentheses judiciously. (suggestion)
Line 9: Use 'capability' or 'feature' instead of 'functionality'. (warning)
Line 9: Use 'shouldn't' instead of 'should not'. (suggestion)
Line 9: In general, use active voice instead of passive voice ('be lost'). (suggestion)
Line 15: Did you really mean 'Palo'? (error)
Line 19: Avoid using 'will'. (warning)
Line 19: In general, use American spelling instead of 'centre'. (warning)
Line 19: Avoid using 'will'. (warning)
... and 182 more issues

site/about/contributing/style-guide/style-guide.qmd

Line 2: Spell out 'USING', if it's unfamiliar to the audience. (suggestion)
Line 2: Spell out 'THE', if it's unfamiliar to the audience. (suggestion)
Line 2: Spell out 'THE', if it's unfamiliar to the audience. (suggestion)
Line 2: Spell out 'TITLE', if it's unfamiliar to the audience. (suggestion)
Line 2: Spell out 'THE', if it's unfamiliar to the audience. (suggestion)
Line 22: Try to avoid using first-person plural like 'we'. (warning)
Line 22: Try to avoid using first-person plural like 'we'. (warning)
Line 22: Try to avoid using first-person plural like 'We'. (warning)
Line 24: Try to avoid using first-person plural like 'Our'. (warning)
Line 24: Try to avoid using first-person plural like 'our'. (warning)
... and 13 more issues

site/about/contributing/style-guide/voice-and-tone.qmd

Line 6: Try to avoid using first-person plural like 'we'. (warning)
Line 8: Try to avoid using first-person plural like 'we'. (warning)
Line 8: Try to avoid using first-person plural like 'our'. (warning)
Line 8: Try to avoid using first-person plural like 'we'. (warning)
Line 8: Try to avoid using first-person plural like 'we'. (warning)
Line 18: Avoid using 'will'. (warning)
Line 18: In general, use active voice instead of passive voice ('be reviewed'). (suggestion)
Line 22: Use parentheses judiciously. (suggestion)
Line 22: Try to avoid using first-person plural like 'we'. (warning)
Line 22: Don't put a space before or after a dash. (error)
... and 39 more issues

site/about/contributing/validmind-community.qmd

Line 8: Use parentheses judiciously. (suggestion)
Line 8: Spell out 'MRM', if it's unfamiliar to the audience. (suggestion)
Line 8: Try to avoid using first-person plural like 'our'. (warning)
Line 8: Don't use exclamation points in text. (error)
Line 8: Try to avoid using first-person plural like 'us'. (warning)
Line 11: Try to avoid using first-person plural like 'our'. (warning)
Line 11: Use parentheses judiciously. (suggestion)
Line 11: Don't use exclamation points in text. (error)
Line 12: Try to avoid using first-person plural like 'our'. (warning)
Line 12: Use parentheses judiciously. (suggestion)
... and 36 more issues

site/about/deployment/_deployment-available-options.qmd

Line 1: Try to avoid using first-person plural like 'Our'. (warning)
Line 1: Use parentheses judiciously. (suggestion)
Line 1: Use 'Google Cloud Platform' or 'GCP' instead of 'Cloud'. (warning)
Line 3: Try to avoid using first-person plural like 'We'. (warning)
Line 5: Don't put a space before or after a dash. (error)
Line 5: Use parentheses judiciously. (suggestion)
Line 5: In general, use active voice instead of passive voice ('be established'). (suggestion)
Line 7: Use parentheses judiciously. (suggestion)
Line 7: Spell out 'VPV', if it's unfamiliar to the audience. (suggestion)
Line 7: Don't put a space before or after a dash. (error)
... and 1 more issues

site/about/deployment/deployment-options.qmd

Line 24: Use parentheses judiciously. (suggestion)
Line 26: Use 'Google Cloud Platform' or 'GCP' instead of 'Cloud'. (warning)
Line 28: Try to avoid using first-person plural like 'our'. (warning)
Line 32: Don't put a space before or after a dash. (error)
Line 32: Did you really mean 'validators'? (error)
Line 34: Don't put a space before or after a dash. (error)
Line 36: Don't put a space before or after a dash. (error)
Line 38: Don't put a space before or after a dash. (error)
Line 42: Try to avoid using first-person plural like 'We'. (warning)
Line 42: Use 'data is' instead of 'data are'. (warning)
... and 12 more issues

site/about/deployment/multi-tenant-cloud.qmd

Line 13: Use 'tap' instead of 'touch'. (warning)
Line 17: Did you really mean 'deployment_'? (error)
Line 19: Use 'it's' instead of 'it is'. (suggestion)
Line 21: Use parentheses judiciously. (suggestion)
Line 29: Don't put a space before or after a dash. (error)
Line 30: Don't put a space before or after a dash. (error)
Line 31: Don't put a space before or after a dash. (error)
Line 32: Don't put a space before or after a dash. (error)
Line 39: In general, use active voice instead of passive voice ('is encrypted'). (suggestion)
Line 40: Use parentheses judiciously. (suggestion)
... and 2 more issues

site/about/deployment/virtual-private-validmind.qmd

Line 2: Spell out 'USING', if it's unfamiliar to the audience. (suggestion)
Line 2: Spell out 'THE', if it's unfamiliar to the audience. (suggestion)
Line 2: Spell out 'THE', if it's unfamiliar to the audience. (suggestion)
Line 2: Spell out 'TITLE', if it's unfamiliar to the audience. (suggestion)
Line 2: Spell out 'THE', if it's unfamiliar to the audience. (suggestion)
Line 3: Use parentheses judiciously. (suggestion)
Line 3: Spell out 'VPV', if it's unfamiliar to the audience. (suggestion)
Line 14: Use 'tap' instead of 'touch'. (warning)
Line 18: Use parentheses judiciously. (suggestion)
Line 18: Spell out 'VPV', if it's unfamiliar to the audience. (suggestion)
... and 8 more issues

site/about/fine-print/data-privacy-policy.qmd

Line 12: Try to avoid using first-person plural like 'our'. (warning)
Line 19: Try to avoid using first-person plural like 'we'. (warning)
Line 21: Try to avoid using first-person plural like 'Our'. (warning)
Line 21: Try to avoid using first-person plural like 'our'. (warning)
Line 21: Try to avoid using first-person plural like 'our'. (warning)
Line 26: Try to avoid using first-person plural like 'our'. (warning)
Line 26: Try to avoid using first-person plural like 'we'. (warning)
Line 26: Try to avoid using first-person plural like 'our'. (warning)
Line 34: Use 'what's' instead of 'What is'. (suggestion)
Line 36: Try to avoid using first-person plural like 'our'. (warning)
... and 49 more issues

site/about/fine-print/license-agreement.qmd

Line 9: Spell out 'READ', if it's unfamiliar to the audience. (suggestion)
Line 9: Spell out 'THIS', if it's unfamiliar to the audience. (suggestion)
Line 9: Use parentheses judiciously. (suggestion)
Line 9: Spell out 'THIS', if it's unfamiliar to the audience. (suggestion)
Line 9: Spell out 'USING', if it's unfamiliar to the audience. (suggestion)
Line 9: Spell out 'THE', if it's unfamiliar to the audience. (suggestion)
Line 9: Spell out 'USING', if it's unfamiliar to the audience. (suggestion)
Line 9: Spell out 'THE', if it's unfamiliar to the audience. (suggestion)
Line 9: Spell out 'YOU', if it's unfamiliar to the audience. (suggestion)
Line 9: Spell out 'ARE', if it's unfamiliar to the audience. (suggestion)
... and 115 more issues

site/about/glossary/_ai.qmd

Line 1: Spell out 'IBM', if it's unfamiliar to the audience. (suggestion)
Line 1: Use parentheses judiciously. (suggestion)
Line 3: Use parentheses judiciously. (suggestion)
Line 7: Use parentheses judiciously. (suggestion)
Line 9: Use parentheses judiciously. (suggestion)
Line 10: In general, use active voice instead of passive voice ('were trained'). (suggestion)
Line 12: Use parentheses judiciously. (suggestion)
Line 12: Spell out 'LLM', if it's unfamiliar to the audience. (suggestion)
Line 13: Use parentheses judiciously. (suggestion)

site/about/glossary/_attestation.qmd

Line 2: Did you really mean 'validator'? (error)
Line 2: In general, use active voice instead of passive voice ('are met'). (suggestion)
Line 5: In general, use active voice instead of passive voice ('is triggered'). (suggestion)
Line 14: Did you really mean 'validators'? (error)

site/about/glossary/_developer-tools.qmd

Line 2: Use parentheses judiciously. (suggestion)
Line 2: Use 'capability' or 'feature' instead of 'functionality'. (warning)
Line 15: Use 'that's' instead of 'that is'. (suggestion)
Line 20: Try to avoid using first-person plural like 'our'. (warning)
Line 30: Use parentheses judiciously. (suggestion)
Line 32: Use parentheses judiciously. (suggestion)

site/about/glossary/_model-documentation.qmd

Line 1: Spell out 'MODEL', if it's unfamiliar to the audience. (suggestion)
Line 1: Spell out 'NEEDS', if it's unfamiliar to the audience. (suggestion)
Line 1: In general, use active voice instead of passive voice ('BE ADDED'). (suggestion)
Line 1: Spell out 'ADDED', if it's unfamiliar to the audience. (suggestion)
Line 3: Use parentheses judiciously. (suggestion)
Line 4: Spell out 'ABC', if it's unfamiliar to the audience. (suggestion)

site/about/glossary/_models.qmd

Line 4: Use parentheses judiciously. (suggestion)
Line 7: In general, use active voice instead of passive voice ('are derived'). (suggestion)
Line 7: In general, use active voice instead of passive voice ('is achieved'). (suggestion)
Line 11: Use parentheses judiciously. (suggestion)
Line 15: Use 'it's' instead of 'it is'. (suggestion)
Line 15: In general, use active voice instead of passive voice ('is decommissioned'). (suggestion)
Line 15: Use parentheses judiciously. (suggestion)
Line 22: Use parentheses judiciously. (suggestion)
Line 22: Spell out 'MRM', if it's unfamiliar to the audience. (suggestion)
Line 23: In general, use active voice instead of passive voice ('are developed'). (suggestion)

site/about/glossary/_monitoring.qmd

Line 1: Spell out 'NEEDS', if it's unfamiliar to the audience. (suggestion)
Line 1: In general, use active voice instead of passive voice ('BE ADDED'). (suggestion)
Line 1: Spell out 'ADDED', if it's unfamiliar to the audience. (suggestion)
Line 3: Use parentheses judiciously. (suggestion)
Line 4: Spell out 'ABC', if it's unfamiliar to the audience. (suggestion)

site/about/glossary/_mrm.qmd

Line 3: Spell out all ordinal numbers ('1st') in text. (error)
Line 3: Put a nonbreaking space between the number and the unit in '1s'. (error)
Line 4: Don't use plurals in parentheses such as in 'unit(s)'. (error)
Line 4: Use parentheses judiciously. (suggestion)
Line 4: Put a nonbreaking space between the number and the unit in '1s'. (error)
Line 4: Spell out all ordinal numbers ('1st') in text. (error)
Line 4: Use 'they're' instead of 'they are'. (suggestion)
Line 6: Spell out all ordinal numbers ('2nd') in text. (error)
Line 7: Spell out all ordinal numbers ('2nd') in text. (error)
Line 7: Did you really mean 'validators'? (error)
... and 11 more issues

site/about/glossary/_validation-reports.qmd

Line 1: Spell out 'NEEDS', if it's unfamiliar to the audience. (suggestion)
Line 1: In general, use active voice instead of passive voice ('BE ADDED'). (suggestion)
Line 1: Spell out 'ADDED', if it's unfamiliar to the audience. (suggestion)
Line 3: Use parentheses judiciously. (suggestion)
Line 4: Spell out 'ABC', if it's unfamiliar to the audience. (suggestion)

site/about/glossary/_validmind-features.qmd

Line 7: In general, use active voice instead of passive voice ('are used'). (suggestion)
Line 7: Use parentheses judiciously. (suggestion)

site/about/glossary/_validmind.qmd

Line 3: In general, use active voice instead of passive voice ('are intertwined'). (suggestion)
Line 5: Use parentheses judiciously. (suggestion)
Line 6: Use 'open source' instead of 'open-source'. (warning)
Line 6: Use parentheses judiciously. (suggestion)
Line 6: Did you really mean 'overfit'? (error)
Line 8: Use parentheses judiciously. (suggestion)
Line 9: Use parentheses judiciously. (suggestion)
Line 9: Did you really mean 'APIs'? (error)

site/about/glossary/glossary.qmd

Line 7: Spell out 'NEW', if it's unfamiliar to the audience. (suggestion)
Line 7: Spell out 'TERM', if it's unfamiliar to the audience. (suggestion)
Line 7: Spell out 'NEEDS', if it's unfamiliar to the audience. (suggestion)
Line 7: In general, use active voice instead of passive voice ('BE ADDED'). (suggestion)
Line 7: Spell out 'ADDED', if it's unfamiliar to the audience. (suggestion)
Line 9: Spell out 'ABC', if it's unfamiliar to the audience. (suggestion)
Line 9: Use parentheses judiciously. (suggestion)
Line 9: Use 'for example' instead of 'e.g.'. (error)
Line 10: Spell out 'KEY', if it's unfamiliar to the audience. (suggestion)
Line 10: Spell out 'TERMS', if it's unfamiliar to the audience. (suggestion)
... and 9 more issues

site/about/glossary/key_concepts/_docs.qmd

Line 4: Use 'app' instead of 'application'. (warning)

site/about/glossary/key_concepts/_inputs.qmd

Line 2: In general, use active voice instead of passive voice ('be evaluated'). (suggestion)
Line 4: In general, use active voice instead of passive voice ('been initialized'). (suggestion)
Line 4: Use parentheses judiciously. (suggestion)
Line 5: In general, use active voice instead of passive voice ('been initialized'). (suggestion)
Line 5: Use parentheses judiciously. (suggestion)
Line 6: In general, use active voice instead of passive voice ('is used'). (suggestion)
Line 7: In general, use active voice instead of passive voice ('is used'). (suggestion)
Line 7: Use parentheses judiciously. (suggestion)

site/about/glossary/key_concepts/_key-concepts.qmd

Line 1: Spell out 'KEY', if it's unfamiliar to the audience. (suggestion)
Line 1: Spell out 'NEEDS', if it's unfamiliar to the audience. (suggestion)
Line 1: In general, use active voice instead of passive voice ('BE ADDED'). (suggestion)
Line 1: Spell out 'ADDED', if it's unfamiliar to the audience. (suggestion)
Line 3: Use parentheses judiciously. (suggestion)
Line 5: Use parentheses judiciously. (suggestion)
Line 5: Use 'for example' instead of 'e.g.'. (error)
Line 5: Spell out 'ABC', if it's unfamiliar to the audience. (suggestion)

site/about/glossary/key_concepts/_metrics.qmd

Line 2: Use 'don't' instead of 'do not'. (suggestion)
Line 2: In general, use active voice instead of passive voice ('be registered'). (suggestion)
Line 2: In general, use active voice instead of passive voice ('be used'). (suggestion)
Line 4: In general, use active voice instead of passive voice ('be thought'). (suggestion)

site/about/glossary/key_concepts/_monitoring-template.qmd

Line 2: In general, use active voice instead of passive voice ('be tracked'). (suggestion)
Line 2: In general, use active voice instead of passive voice ('be conducted'). (suggestion)
Line 2: In general, use active voice instead of passive voice ('be displayed'). (suggestion)
Line 4: Did you really mean 'boilerplates'? (error)

site/about/glossary/key_concepts/_outputs.qmd

Line 2: Use parentheses judiciously. (suggestion)
Line 2: 's.D' should have one space. (error)

site/about/glossary/key_concepts/_parameters.qmd

Line 2: In general, use active voice instead of passive voice ('be passed'). (suggestion)

site/about/glossary/key_concepts/_template.qmd

Line 2: In general, use active voice instead of passive voice ('be run'). (suggestion)
Line 2: In general, use active voice instead of passive voice ('be displayed'). (suggestion)
Line 4: Did you really mean 'boilerplates'? (error)

... and 574 more files with issues

github-actions · 2025-06-02T18:27:28Z

Validate docs site

✓ INFO: A live preview of the docs site is available — Open the preview

github-actions · 2025-06-02T18:30:17Z

Lighthouse check results

⚠️ WARN: Average accessibility score is 0.78 (required: >0.9) — Check the workflow run

Show Lighthouse scores

Folder depth level checked: 0

Commit SHA: b13afa3

Modify the workflow to check a different depth:

0: Top-level navigation only — /index.html, /guide/guides.html, ...
1: All first-level subdirectories — /guide/.html, /developer/.html, ...
2: All second-level subdirectories — /guide/attestation/*.html, ...

Page	Accessibility	Performance	Best Practices	SEO
/developer/validmind-library.html	0.75	0.79	1.00	0.89
/get-started/get-started.html	0.75	0.73	1.00	0.90
/guide/guides.html	0.76	0.84	1.00	0.90
/index.html	0.79	0.81	1.00	0.80
/releases/all-releases.html	0.85	0.88	1.00	0.80
/support/support.html	0.82	0.85	1.00	0.90
/training/training.html	0.73	0.68	0.96	0.80

validbeck and others added 18 commits May 22, 2025 12:20

Merge remote-tracking branch 'origin/main' into staging

3a3be04

Merge pull request #730 from validmind/update-staging-15195042251

2722ef6

Merge main into staging

Merge remote-tracking branch 'origin/main' into staging

e727d35

Merge pull request #733 from validmind/update-staging-15215353914

5d18396

Merge main into staging

Merge remote-tracking branch 'origin/main' into staging

85c0eef

Merge pull request #736 from validmind/update-staging-15306334463

5fb51db

Merge main into staging

Merge remote-tracking branch 'origin/main' into staging

28f438e

Merge pull request #738 from validmind/update-staging-15312034754

1682838

Merge main into staging

+ IF condition for workflow success in deploy to staging & prod (#737)

54ad880

* if condition for workflow success * Add retries to gh pr merge step * Add space before ellipsis, the shame ... --------- Co-authored-by: Nik Richers <nik@validmind.ai>

Merge remote-tracking branch 'origin/main' into staging

2ba5bc1

Merge pull request #739 from validmind/update-staging-15332351733

5a9ab98

Merge main into staging

Merge remote-tracking branch 'origin/main' into staging

0235943

Merge pull request #741 from validmind/update-staging-15398832712

089faa2

Merge main into staging

validbeck self-assigned this Jun 2, 2025

validbeck added the internal Not to be externalized in the release notes label Jun 2, 2025

validbeck merged commit 20af028 into prod Jun 2, 2025
6 checks passed

Conversation

validbeck commented Jun 2, 2025

Internal Notes for Reviewers

Uh oh!

github-actions bot commented Jun 2, 2025

Vale source linter

site/404.qmd

site/about/contributing/style-guide/conventions.qmd

site/about/contributing/style-guide/style-guide.qmd

site/about/contributing/style-guide/voice-and-tone.qmd

site/about/contributing/validmind-community.qmd

site/about/deployment/_deployment-available-options.qmd

site/about/deployment/deployment-options.qmd

site/about/deployment/multi-tenant-cloud.qmd

site/about/deployment/virtual-private-validmind.qmd

site/about/fine-print/data-privacy-policy.qmd

site/about/fine-print/license-agreement.qmd

site/about/glossary/_ai.qmd

site/about/glossary/_attestation.qmd

site/about/glossary/_developer-tools.qmd

site/about/glossary/_model-documentation.qmd

site/about/glossary/_models.qmd

site/about/glossary/_monitoring.qmd

site/about/glossary/_mrm.qmd

site/about/glossary/_validation-reports.qmd

site/about/glossary/_validmind-features.qmd

site/about/glossary/_validmind.qmd

site/about/glossary/glossary.qmd

site/about/glossary/key_concepts/_docs.qmd

site/about/glossary/key_concepts/_inputs.qmd

site/about/glossary/key_concepts/_key-concepts.qmd

site/about/glossary/key_concepts/_metrics.qmd

site/about/glossary/key_concepts/_monitoring-template.qmd

site/about/glossary/key_concepts/_outputs.qmd

site/about/glossary/key_concepts/_parameters.qmd

site/about/glossary/key_concepts/_template.qmd

Uh oh!

github-actions bot commented Jun 2, 2025

Validate docs site

Uh oh!

github-actions bot commented Jun 2, 2025

Lighthouse check results

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants