Skip to content

docs: refine homepage copy and fix layouts#4331

Open
chasecadet wants to merge 1 commit intokubeflow:masterfrom
chasecadet:fix/website-homepage-refinements
Open

docs: refine homepage copy and fix layouts#4331
chasecadet wants to merge 1 commit intokubeflow:masterfrom
chasecadet:fix/website-homepage-refinements

Conversation

@chasecadet
Copy link
Contributor

Description of Changes

Description
This PR provides a comprehensive overhaul of the Kubeflow homepage, refining the core messaging, introducing new community callouts, and modernizing the overall component layout.

Key Content Enhancements
Hero Section: Expanded the hero banner subtitle to better articulate the mission of Kubeflow (empowering practitioners to focus on models, not manifests).
Overview Structure: Refined the introductory paragraph to emphasize Platform Engineers' ability to effortlessly control infrastructure while meeting data science needs.
Workloads Section: Capitalized the heading to "What Workloads Run On Kubeflow?" and tightened the component descriptions for Pipeline, Dashboard, KServe, etc.
GenAI Integration: Introduced a brand-new callout section specifically highlighting GenAI use-cases, complete with dedicated navigation buttons to the Kubeflow Blog.
SDK Hyperlink: Added a direct inline navigation link pointing to the official kubeflow/sdk GitHub repository.
Layout & Navigational Cleanup
Motivation
These updates transform the homepage into a cohesive, highly professional landing pad that clearly communicates Kubeflow's modern value propositions (including GenAI) while resolving several UX/rendering bugs present on the current live site.

Related Issues

Closes: #

Related: #

Checklist

Screenshot 2026-03-01 231819 Screenshot 2026-03-01 231935 image image Screenshot 2026-03-01 232156 image image

- Removed 'Deploy Kubeflow' from top navigation bar
- Updated workload and GenAI callout text
- Corrected typos and polished architecture messaging
- Fixed HTML rendering bug hiding the Community section
- Removed duplicated Community section at the footer
@google-oss-prow
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign andreyvelich for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jaiakash
Copy link
Member

jaiakash commented Mar 3, 2026

Hi @chasecadet can you please review the DCO and PR title CI for this.

@StefanoFioravanzo
Copy link
Member

@chasecadet I like how you are trying to make our mission more explicit. I don't want to comment on specifics about the wording, since that would open an endless discussion. In terms of layout and intent, this is a very good direction!

IMHO I would be very happy to see these changes introduced in the website, and I am sure that we could then iterate more on the wording - which will never be perfect, but we need to start from somewhere.

nit1: I like the PyPI and GH stats, but what about making them smaller inside chips, maybe with a different highlight color, so that they occupy less real estate?

nit2: The paragraph below "An ecosystem of tool AND a cohesive platform" feels a bit like a wall of text. How about trying to reduce it just a little bit and using bold and emphasis to highlight some parts of the text?

@google-oss-prow
Copy link

@shivaylamba: changing LGTM is restricted to collaborators

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants