notebooks: Reorganization in preparation for editing

[validbeck]

Pull Request Description

What and why?

sc-14582

In preparation for editing the rest of our Jupyter Notebooks, I shuffled some of our notebooks around and better defined the categories in which the notebooks live in hopes of making the user journey for finding topics and samples more intuitive.

OLD	NEW

Major changes

1. Renamed code_samples/ to use_cases/

• All content under notebooks/code_samples/ was moved to notebooks/use_cases/.
• This affects the domain-specific demo notebooks: agents/, capital_markets/, code_explainer/, credit_risk/, model_validation/, nlp_and_llm/, ongoing_monitoring/, regression/, and time_series/.
• The only exceptions were the custom_tests/ notebooks, which were moved to how_to/ instead (refer to below).

2. Reorganized how_to/ into topic-based subdirectories

The flat notebooks/how_to/ folder was reorganized into a nested structure with clear subcategories:

New subdirectory	Content moved in
how_to/data_and_datasets/	Dataset feature config, loading predictions, raw data, dataset/model objects
how_to/metrics/	Unit metrics, logging metrics over time
how_to/scoring/	Score assignment tutorial
how_to/security/	PII detection
how_to/tests/explore_tests/	Exploring tests and test suites
how_to/tests/run_tests/	Running dataset-based and comparison tests
how_to/tests/run_tests/configure_tests/	Filtering columns, multiple datasets, customizing descriptions
how_to/tests/run_tests/documentation_tests/	Running documentation sections/tests with config, multiple results
how_to/tests/custom_tests/	Implementing custom tests, external test providers (moved from code_samples/custom_tests/)

3. Moved images attached to notebooks into the same directories that the notebooks live in

• Instead of images living loose in notebooks/images I just shuffled them into the same (sub)directories that the notebooks live in as that is easier to associate and find.
• Misc. images that didn't seem to be used anywhere I just plunked in code_sharing/images for now.

4. Updated all internal references

• Fixed cross-notebook links (e.g., code_samples/ references updated to use_cases/, how-to links updated to new paths) across quickstart, tutorial, template, and code-sharing notebooks.
• Updated scripts/run_e2e_notebooks.py so the e2e test runner points to the correct new paths.
• Updated notebooks/README.md with revised folder descriptions.
• Updated the image paths for notebooks that have images.

Why

The previous structure had some naming/organizational issues:

• code_samples/ was a vague name — renaming it to use_cases/ better describes that these are end-to-end examples for specific domains (credit risk, NLP/LLM, time series, etc.).
• how_to/ was a flat folder with many unrelated notebooks at the same level — grouping them into topic-based subdirectories (data_and_datasets, metrics, tests, security, etc.) makes it much easier to navigate and find relevant guides.
• Custom test notebooks were under code_samples/ but are really "how to" content about using a ValidMind feature, so they were moved to how_to/tests/custom_tests/ where they logically belong.

How to test

n/a

What needs special review?

Important

Please make sure that the new categories assigned to notebooks make sense and are logical as I don't have as deep of an understanding of our notebook content as I'd like.

Dependencies, breaking changes, and deployment notes

Note

Links to the moved notebooks have also all been updated notebook side — they will be updated documentation side once this PR is approved and I am able to pull the new notebooks in.

Release notes

Release notes will go out with the documentation side PR as there will be additional navigation changes for how the notebooks are linked/structured in the docs.

Checklist

• What and why
• Screenshots or videos (Frontend)
• How to test
• What needs special review
• Dependencies, breaking changes, and deployment notes
• Labels applied
• PR linked to Shortcut
• Unit tests added (Backend)
• Tested locally
• Documentation updated (if required)
• Environment variable additions/changes documented (if required)

[github-actions]

PR Summary

This pull request refactors the documentation and notebook asset paths throughout the repository. The changes involve updating hard-coded paths and URLs in markdown cells and code comments to reflect the new directory structure. Specifically, references previously pointing to folders such as /code_samples/ have been updated to /use_cases/, and links in notebooks and associated metadata have been re-pointed to new locations under /how_to/tests/ and /how_to/metrics/. These updates ensure that links to resources (such as custom test implementations, external test providers, and apples-to-apples comparisons of notebooks) are aligned with the new structural organization. The modifications affect multiple notebooks, YAML templates, and configuration files, ensuring consistency in how documentation and examples are organized and linked across the project.

Test Suggestions

• Run all end-to-end notebook execution tests to verify that the updated paths resolve correctly.
• Manually review key notebooks to ensure that all image links and embedded documentation links work as expected.
• Perform regression tests on documentation generation to confirm that links in the published docs point to the right new folder locations.