Skip to content

Cleanup the traditional ML landing page#18799

Merged
BenWilson2 merged 2 commits intomlflow:masterfrom
BenWilson2:classic-ml-landing
Nov 13, 2025
Merged

Cleanup the traditional ML landing page#18799
BenWilson2 merged 2 commits intomlflow:masterfrom
BenWilson2:classic-ml-landing

Conversation

@BenWilson2
Copy link
Member

@BenWilson2 BenWilson2 commented Nov 12, 2025 •
edited by github-actions bot
Loading

🛠 DevTools 🛠

Open in GitHub Codespaces

Install mlflow from this PR

# mlflow
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/18799/merge
# mlflow-skinny
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/18799/merge#subdirectory=libs/skinny

For Databricks, use the following command:

%sh curl -LsSf https://raw.githubusercontent.com/mlflow/mlflow/HEAD/dev/install-skinny.sh | sh -s pull/18799/merge

Related Issues/PRs

#xxx

What changes are proposed in this pull request?

Cleanup and standardize the landing page for traditional ML. Add a little UI graphic showing HPO.

How is this PR tested?

  • Existing unit/integration tests
  • New unit/integration tests
  • Manual tests

Does this PR require documentation update?

  • No. You can skip the rest of this section.
  • Yes. I've updated:
    • Examples
    • API references
    • Instructions

Release Notes

Is this a user-facing change?

  • No. You can skip the rest of this section.
  • Yes. Give a description of this change to be included in the release notes for MLflow users.

What component(s), interfaces, languages, and integrations does this PR affect?

Components

  • area/tracking: Tracking Service, tracking client APIs, autologging
  • area/models: MLmodel format, model serialization/deserialization, flavors
  • area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
  • area/scoring: MLflow Model server, model deployment tools, Spark UDFs
  • area/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflows
  • area/gateway: MLflow AI Gateway client APIs, server, and third-party integrations
  • area/prompts: MLflow prompt engineering features, prompt templates, and prompt management
  • area/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionality
  • area/projects: MLproject format, project running backends
  • area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
  • area/build: Build and test infrastructure for MLflow
  • area/docs: MLflow documentation pages

How should the PR be classified in the release notes? Choose one:

  • rn/none - No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" section
  • rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
  • rn/feature - A new user-facing feature worth mentioning in the release notes
  • rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
  • rn/documentation - A user-facing documentation change worth mentioning in the release notes

Should this PR be included in the next patch release?

Yes should be selected for bug fixes, documentation updates, and other small changes. No should be selected for new features and larger changes. If you're unsure about the release classification of this PR, leave this unchecked to let the maintainers decide.

What is a minor/patch release?
  • Minor release: a release that increments the second part of the version number (e.g., 1.2.0 -> 1.3.0).
    Bug fixes, doc updates and new features usually go into minor releases.
  • Patch release: a release that increments the third part of the version number (e.g., 1.2.0 -> 1.2.1).
    Bug fixes and doc updates usually go into patch releases.
  • Yes (this PR will be cherry-picked and included in the next patch release)
  • No (this PR will be included in the next minor release)

@BenWilson2
fix traditional ML landing page
a7e3610 
Signed-off-by: Ben Wilson <benjamin.wilson@databricks.com>
@BenWilson2 BenWilson2 requested a review from Copilot November 12, 2025 04:18
@github-actions github-actions bot added area/docs Documentation issues rn/documentation Mention under Documentation Changes in Changelogs. labels Nov 12, 2025
@BenWilson2 BenWilson2 requested a review from B-Step62 November 12, 2025 04:18
Copilot AI reviewed Nov 12, 2025
View reviewed changes
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR cleans up and modernizes the traditional ML landing page by simplifying the content structure and adding visual enhancements. The page is reduced from verbose explanatory sections to a more concise, navigation-focused layout.

  • Replaces lengthy explanatory content with concise descriptions and clear call-to-action tiles
  • Adds a new UI graphic (traditional-ml-ui.gif) showcasing hyperparameter optimization
  • Restructures navigation using TilesGrid and TileCard components instead of Tabs and PageCard

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@github-actions
Copy link
Contributor

github-actions bot commented Nov 12, 2025 •
edited
Loading

Documentation preview for 43b874e is available at:

Changed Pages (1)
More info
  • Ignore this comment if this PR does not change the documentation.
  • The preview is updated when a new commit is pushed to this PR.
  • This comment was created by this workflow run.
  • The documentation was built by this workflow run.

B-Step62
B-Step62 approved these changes Nov 13, 2025
View reviewed changes
Copy link
Collaborator

@B-Step62 B-Step62 left a comment

Choose a reason for hiding this comment

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

LGTM, love this simplification!

docs/docs/classic-ml/traditional-ml/index.mdx Outdated
iconSize={48}
title="Hyperparameter Tuning"
description="Optimize models with GridSearchCV, RandomizedSearchCV, and Optuna integration."
href="/ml/traditional-ml/tutorials/hyperparameter-tuning"
Copy link
Collaborator

@B-Step62 B-Step62 Nov 13, 2025

Choose a reason for hiding this comment

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

Can we link to https://pr-18799--mlflow-docs-preview.netlify.app/docs/latest/ml/getting-started/hyperparameter-tuning/? I feel /ml/traditional-ml/tutorials/hyperparameter-tuning is too complex.

@BenWilson2
update
43b874e 
Signed-off-by: Ben Wilson <benjamin.wilson@databricks.com>
@BenWilson2 BenWilson2 added this pull request to the merge queue Nov 13, 2025
Merged via the queue into mlflow:master with commit 22fda8c Nov 13, 2025
45 checks passed
@BenWilson2 BenWilson2 deleted the classic-ml-landing branch November 13, 2025 22:40
mprahl pushed a commit to opendatahub-io/mlflow that referenced this pull request Nov 21, 2025
@BenWilson2 @mprahl
Cleanup the traditional ML landing page (mlflow#18799)
448c590 
Signed-off-by: Ben Wilson <benjamin.wilson@databricks.com>
Tian-Sky-Lan pushed a commit to Tian-Sky-Lan/mlflow that referenced this pull request Nov 24, 2025
@BenWilson2 @Tian-Sky-Lan
Cleanup the traditional ML landing page (mlflow#18799)
0a52546 
Signed-off-by: Ben Wilson <benjamin.wilson@databricks.com>
Signed-off-by: Tian Lan <sky.blue266000@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot Copilot left review comments

@B-Step62 B-Step62 B-Step62 approved these changes

Assignees

No one assigned

Labels

area/docs Documentation issues rn/documentation Mention under Documentation Changes in Changelogs. v3.6.1

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@BenWilson2 @B-Step62