Skip to content

Merge main into staging#1370

Closed
validbeck wants to merge 5 commits into
stagingfrom
update-staging-manual
Closed

Merge main into staging#1370
validbeck wants to merge 5 commits into
stagingfrom
update-staging-manual

Conversation

@validbeck

@validbeck validbeck commented Jun 18, 2026

Copy link
Copy Markdown
Collaborator

Summary

Manually syncs staging with main after the automated merge workflow failed on a rename conflict in link-external-records.qmd (June 5).

Conflicts were resolved by preferring main.

Test plan

  • Merge this PR
  • Confirm Deploy docs site to staging runs on the resulting push to staging
  • Confirm Execute training notebooks for staging runs after deploy succeeds

Made with Cursor

Edit

Fixed by #1371, closing.

validbeck added 5 commits June 5, 2026 12:51
…rimary-record-types-final

docs: PRT final audit — Integrations
* Add: Set field step

* Edit

* edity
* Setup > View settings activity

* Integrations analytics WIP

* reverting integrations and LLM changes for now

* wip

* Save

* Save

* save

* save

* Working with documents > Managing documents

* updated member removal from group

* edit

* save

* save

* View settings activity

* save

* setup for training

* moving View record activity into reporting

* save

* training done

* regen sitemap

* oops i somehow committed some rendered files

* FAQ wip

* save

* save

* save

* save

* faq: integrations

* save

* FAQ: attestations

* edit

* Configure analytics exports > Configure data exports

* edit

* edit

* save

* Move private connectivity to its own accordian

* update sitemap

* proof

* more proofreading

* fix

* edit

* cleanup

* Edit

* Edit: Filtering settings activity

* proofreading
* Editing shared views

* Setup for field views

* save

* save

* save

* edit

* proof

* Edit

* Edit

* cleanup

* proof

* proof-reading

* edits per JAM

* Edit

* edits

* save

* save

* Edit: New inventory record type selection

* proofreadinh

* smallcaps > title casing pt1

* smallcaps > title casing pt2

* smallcaps > title casing pt3

* smallcaps > title casing pt4

* smallcaps > title casing pt5

* smallcaps > title casing pt6

* proofreading

* proofreading

* proofreading

* proofreading

* proofreading

* proofreading

* edit

* pulling in latest notebooks
@github-actions

Copy link
Copy Markdown
Contributor

Pull requests must include at least one of the required labels: internal, highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

@github-actions

Copy link
Copy Markdown
Contributor

PR Summary

This pull request provides extensive updates across many documentation and UI text files in the ValidMind Platform project. The changes are primarily focused on standardizing terminology and capitalization to improve consistency and clarity. For example, strings previously marked as [document]{.smallcaps} are now rendered as Document, and similar updates have been applied for terms such as Record Owner, Inventory Record, Template, Workflow Start, etc. Several links have been updated to point from legacy routes (e.g. /guide/inventory/view-record-activity.qmd) to newer routes (e.g. /guide/reporting/view-record-activity.qmd). These changes span multiple sections including Inventory registration, workflow steps (such as Wait, Approval, Webhook, and User Action), document templates, and integration configuration. The overall goal is to harmonize the language used across the platform’s help files, training materials, and developer notebooks so that users see a uniform and modernized user interface and documentation structure.

Test Suggestions

  • Manually navigate through the Inventory registration process and verify that the drop-down labels now display 'Document' or 'Record Owner' as updated.
  • Check that all links updated from the legacy documentation paths (e.g., for record activity, integration, and document management) correctly resolve to the new routes.
  • Review a several workflow and document templates to ensure the new capitalizations (e.g., 'Template' instead of 'DOCUMENT') display consistently.
  • Verify that interactive elements (buttons, action menus, etc.) display the expected new terms and that tooltips and help texts are intact.
  • Run end-to-end tests for developer notebooks to confirm that code snippets referencing the UI elements (like copy snippet actions) work as expected.

@validbeck validbeck self-assigned this Jun 18, 2026
@validbeck validbeck added the internal Not to be externalized in the release notes label Jun 18, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Validate docs site

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

@github-actions

Copy link
Copy Markdown
Contributor

Execute training notebooks for PRs

✓ INFO: Live previews are available —

@validbeck validbeck closed this Jun 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal Not to be externalized in the release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant