Skip to content

Updated product terminology — documentation repo side#521

Merged
validbeck merged 46 commits intomainfrom
beck/sc-6647/update-product-terminology
Nov 13, 2024
Merged

Updated product terminology — documentation repo side#521
validbeck merged 46 commits intomainfrom
beck/sc-6647/update-product-terminology

Conversation

@validbeck
Copy link
Copy Markdown
Collaborator

@validbeck validbeck commented Nov 12, 2024

Internal Notes for Reviewers

sc-6647

LIVE PREVIEW

Major changes

Screenshot 2024-11-12 at 3 48 34 PM

File renames

Aliases have been set up for the old URLs:

Old New
site/developer/get-started-developer-framework.qmd site/developer/get-started-validmind-library.qmd
site/developer/model-documentation/install-and-initialize-client-library.qmd site/developer/model-documentation/install-and-initialize-validmind-library.qmd

To do

@validbeck validbeck added the internal Not to be externalized in the release notes label Nov 12, 2024
@validbeck validbeck self-assigned this Nov 12, 2024
@validbeck validbeck requested a review from nrichers November 12, 2024 23:48
@github-actions
Copy link
Copy Markdown
Contributor

PR Summary

This pull request refactors the documentation to update the naming conventions and references for the ValidMind product and platform. The changes include:

  • Replacing instances of "ValidMind Platform UI" with "ValidMind Platform".
  • Updating references from "ValidMind Developer Framework" to "ValidMind Library".
  • Changing "ValidMind AI risk platform" to "ValidMind".
  • Adjusting variable names and paths to reflect these changes across various documentation files, including markdown, YAML, and JSON files.
  • Updating images and alt text to align with the new naming conventions.
  • Modifying links and references to ensure consistency with the updated product and platform names.

These changes aim to improve clarity and consistency in the documentation, making it easier for users to understand and navigate the ValidMind product offerings.

Test Suggestions

  • Verify that all instances of the old product and platform names have been updated to the new names across all documentation files.
  • Check that all links and references to documentation sections are still valid and lead to the correct pages.
  • Ensure that all images and alt text have been updated to reflect the new naming conventions.
  • Test the documentation site to confirm that the changes do not break any existing functionality or navigation.
  • Review the updated documentation for any grammatical errors or inconsistencies introduced during the refactor.

Copy link
Copy Markdown
Collaborator

@nrichers nrichers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! I have some minor comments or questions but this looks to be a very thorough first pass over our docs site as we change to the new product name. 🚢 🚢 🚢

We will need a release notes entry at some point. Since this is the main PR to update the user guide, I’d recommend including it in this PR. (If there’s still outstanding stuff at the next release, we can always comment it out until ready.)

EDIT: Fix wording.

Copy link
Copy Markdown
Collaborator

@nrichers nrichers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While recording the videos for the developer experience I realized that there's a notebook missing from this PR: https://github.com/validmind/documentation/blob/beck/sc-6647/update-product-terminology/site/notebooks/tutorials/intro_for_model_developers_EXECUTED.ipynb

It's that special case again that invariably comes to bite you — this notebook lives only in the documentation repo and is use for the developer fundamentals training.

The underlying issue why we need this notebook still isn't fixed, see the newly opened Fix OAuth error when embedding JupyterHub in training module.

For now, I'm requesting changes to your PR but we might figure out some alternative for this issue if the non-_EXECUTED notebook has diverged from this one substantially. E.g. we could try to execute the on-_EXECUTED notebook on the fly when we run make get-source but we'd need to figure out how to get the code snippet into the notebook via dotenv.

See 5552c3b for my hacky workaround while recording the videos.

@github-actions
Copy link
Copy Markdown
Contributor

A PR preview is available: Preview URL

@validbeck
Copy link
Copy Markdown
Collaborator Author

validbeck commented Nov 13, 2024

We will need a release notes entry at some point. Since this is the main PR to update the user guide, I’d recommend including it in this PR. (If there’s still outstanding stuff at the next release, we can always comment it out until ready.)

There's already a story for this: sc-6648 (I was going to wait until the repo was renamed to do this one, as it is technically the final step.)

EDIT: Also, in the spirit of our "atomic" PRs, I vote doing this in a second PR just for my sanity's sake. This branch has already been open for a month!

While recording the videos for the developer experience I realized that there's a notebook missing from this PR: https://github.com/validmind/documentation/blob/beck/sc-6647/update-product-terminology/site/notebooks/tutorials/intro_for_model_developers_EXECUTED.ipynb

I forgot to add it to the list of "To dos," but I wasn't going to redo this until the notebook it originates from is merged into main. (I was just going to execute it again and replace it.) I will add it to the list.

@github-actions
Copy link
Copy Markdown
Contributor

A PR preview is available: Preview URL

Copy link
Copy Markdown
Collaborator

@nrichers nrichers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in the spirit of our "atomic" PRs, I vote doing this in a second PR just for my sanity's sake. This branch has already been open for a month!

Makes sense, let's just make sure it happens.

I forgot to add it to the list of "To dos," but I wasn't going to redo this until the notebook it originates from is merged into main. (I was just going to execute it again and replace it.) I will add it to the list.

Acknowledged, let me re-approve this PR.

@github-actions
Copy link
Copy Markdown
Contributor

A PR preview is available: Preview URL

@validbeck validbeck merged commit 462effd into main Nov 13, 2024
@validbeck validbeck deleted the beck/sc-6647/update-product-terminology branch November 13, 2024 17:55
This was referenced Nov 13, 2024
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.

2 participants