Update Kubeflow Index Page

[andreyvelich]

Followup on @thesuperzapper comment here: https://github.com/kubeflow/website/pull/3728#discussion_r1628261603

I updated Kubeflow index page in this PR. Please let me know what do you think about this statement ? For inspiration I checked one of the first Kubeflow videos that @aronchick presented before: https://youtu.be/R3dVF5wWz-g?t=875

/assign @thesuperzapper @kubeflow/kubeflow-steering-committee @StefanoFioravanzo @hbelmiro @franciscojavierarceo

/hold for review

[google-oss-prow[bot]]

[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 ask for approval from andreyvelich. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files: - **[OWNERS](https://github.com/kubeflow/website/blob/master/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[rimolive]

/lgtm

[thesuperzapper]

@andreyvelich Here are the key points that I think we should hit for the front-page "What is Kubeflow?" wording:

1. It should convey what Kubeflow does, and its key value proposition.
2. It should be no longer than 3 sentences.
3. It should make sense to a person in a leadership position (not just technical).
4. It should not use acronyms like AI and ML, but rather their full words.

Here are the key points that I think makes Kubeflow special:

• Kubeflow is for machine learning on Kubernetes.
• Kubeflow is not a single tool, we are an ecosystem of components for each stage in the ML lifecycle.
• It can run on any Kubernetes cluster.

Based on that, here is my proposed wording:

Kubeflow enables machine learning on Kubernetes at any scale. We are an ecosystem of components for each stage in the machine learning lifecycle.

Anywhere you run Kubernetes, you should be able to install Kubeflow.

Here is with full HTML:

Kubeflow enables machine learning on <a href="https://kubernetes.io/docs/concepts/overview/" target="_blank" rel="noopener">Kubernetes</a> at any scale.
We are an <em>ecosystem</em> of components for each stage in the <a href="/docs/started/architecture/#introducing-the-ml-lifecycle" target="_blank" rel="noopener">machine learning lifecycle</a>.
<br><br>
Anywhere you run Kubernetes, you should be able to <a href="/docs/started/installing-kubeflow/" target="_blank" rel="noopener">install Kubeflow</a>.

Here is a screenshot:

[andreyvelich]

Thank you for proposing this @thesuperzapper, I agree with some statements. However, don't you think that we should clearly say that Kubeflow is a bridge between ML and Cloud ecosystems ? We allow users to leverage cloud resources to scale their ML development and AI applications. For example, if folks want to run PyTorch on a cloud, they need to come to us.

Also, we might need to emphasize that Kubeflow is also for artificial intelligence not only for machine learning. For example, Kubeflow components are enabled AI running on the cloud.

Any other thoughts from the community @kubeflow/wg-data-leads @kubeflow/wg-pipeline-leads @kubeflow/wg-training-leads @kubeflow/wg-notebooks-leads @kubeflow/wg-manifests-leads @vikas-saxena02 @hbelmiro ?

[tarilabs]

proposal iterating from Mathew's suggestion:

Kubeflow enables machine learning on Kubernetes at scale. Kubeflow is an ecosystem of components for each stage in the machine learning lifecycle, tuned and orchestrated to work in cloud-native way.

Anywhere you run Kubernetes, you should be able to install Kubeflow.

I also like the statement about not-recreate components.

[juliusvonkohout]

@thesuperzapper

i would like to add to:

Here are the key points that I think makes Kubeflow special:

• Kubeflow is for machine learning on Kubernetes.
• Kubeflow is not a single tool, we are an ecosystem of components for each stage in the ML lifecycle.
• It can run on any Kubernetes cluster.
• It is open source and can be modified and extended as needed
• There is no vendor lock-in

[StefanoFioravanzo]

I like where @thesuperzapper is going with this.

On @andreyvelich 's comments:

However, don't you think that we should clearly say that Kubeflow is a bridge between ML and Cloud ecosystems ? We allow users to leverage cloud resources to scale their ML development and AI applications. For example, if folks want to run PyTorch on a cloud, they need to come to us.

You feel like the second sentence does not emphasize this enough?

Also, we might need to emphasize that Kubeflow is also for artificial intelligence not only for machine learning. For example, Kubeflow components are enabled AI running on the cloud.

Do you feel like we should word it as "Kubeflow enables Artificial Intelligence and Machine Learning on Kubernetes ..." ? With the goal of keeping our statement short and clear, what value does this bring to the message we want to convey?

[andreyvelich]

You feel like the second sentence does not emphasize this enough?

@StefanoFioravanzo Which sentence ?

With the goal of keeping our statement short and clear, what value does this bring to the message we want to convey?

That shows the value of Kubeflow to develop AI applications.

[vikas-saxena02]

The proposed changes looks good to me

[vikas-saxena02]

/lgtm

[thesuperzapper]

@vikas-saxena02 which proposal are you supporting?

Also, for others, let's continue discussing so we can converge on a wording (rather than LGTM the PR).

@andreyvelich perhaps you can mark this PR as a draft to indicate that we are still discussing.

[vikas-saxena02]

Thank you for proposing this @thesuperzapper, I agree with some statements. However, don't you think that we should clearly say that Kubeflow is a bridge between ML and Cloud ecosystems ? We allow users to leverage cloud resources to scale their ML development and AI applications. For example, if folks want to run PyTorch on a cloud, they need to come to us.

Also, we might need to emphasize that Kubeflow is also for artificial intelligence not only for machine learning. For example, Kubeflow components are enabled AI running on the cloud.

Any other thoughts from the community @kubeflow/wg-data-leads @kubeflow/wg-pipeline-leads @kubeflow/wg-training-leads @kubeflow/wg-notebooks-leads @kubeflow/wg-manifests-leads @vikas-saxena02 @hbelmiro ?

@thesuperzapper these ones

[thesuperzapper]

As I was saying in https://github.com/kubeflow/website/pull/3755#issuecomment-2163722592, the core purpose of the intro paragraph is to help users learn about what Kubeflow is:

Kubeflow enables machine learning on Kubernetes at any scale. We are an ecosystem of components for each stage in the machine learning lifecycle.

Anywhere you run Kubernetes, you should be able to install Kubeflow.

I am happy for people to suggest changes to the proposal I made.

---

Regarding the specific comments from @andreyvelich:

However, don't you think that we should clearly say that Kubeflow is a bridge between ML and Cloud ecosystems ? We allow users to leverage cloud resources to scale their ML development and AI applications. For example, if folks want to run PyTorch on a cloud, they need to come to us.

I think that message is already conveyed by the first paragraph, is there a specific wording change you are suggesting?

Also, "Kubernetes" is clearer than the word "Cloud" because Kubernetes can be run anywhere, and cloud is not really defined.

Also, we might need to emphasize that Kubeflow is also for artificial intelligence not only for machine learning. For example, Kubeflow components are enabled AI running on the cloud.

I don't think adding the words "Artificial Intelligence" will add any significant value and may actually detract from the simplicity of the wording. Furthermore, it's a largely undefined term that has lots of emotion associated to it right now.

[StefanoFioravanzo]

I agree with @thesuperzapper and I think the wording he proposed is already a great improvement over what we have now. I share your concerns on the use of "Artificial Intelligence".

If the intent of adding "Artificial Intelligence" is to hint at support for GenAI / LLM applications and use cases, I suggest thinking about a new section in the index page, maybe under components, that highlights supported use cases.

[andreyvelich]

@StefanoFioravanzo @thesuperzapper Why we don't want to add acronyms in our index page ? We can always explain what those acronyms mean in the introduction page. I think, AI/ML is the well-known statement today, and users who want to explore Kubeflow might already aware of AI and ML. Especially, with the existing value that Kubeflow brings for GenAI and LLM applications.

---

For the first statement, why you don't like this statement ?

The Kubeflow makes AI/ML on Kubernetes simple, portable and scalable.

---

For the second, I like what @thesuperzapper proposed with this modification:

We are an ecosystem of projects for each stage in the ML lifecycle

[juliusvonkohout]

Why we don't want to add acronyms in our index page ? We can always explain what those acronyms mean in the introduction page. I think, AI/ML is the well-known statement today, and users who want to explore Kubeflow might already aware of AI and ML. Especially, with the existing value that Kubeflow brings for GenAI and LLM applications.

I am usually a strong opponent of unnecessary acronyms and especially abbreviations because they lead to very ugly code and hurt the flow of text/speech, but in this case i am supporting the Idea of introducing them once at the beginning of the page and then just using them.