Skip to content

[docs] landing page (fixes #21750)#21859

Merged
richardliaw merged 17 commits intomasterfrom
mp_docs_intro
Jan 27, 2022
Merged

[docs] landing page (fixes #21750)#21859
richardliaw merged 17 commits intomasterfrom
mp_docs_intro

Conversation

@maxpumperla
Copy link
Copy Markdown
Contributor

@maxpumperla maxpumperla commented Jan 25, 2022

Preview: docs

More informative and attractive landing page with a focus on

  • Three core personas with clearer messaging
  • A better overview of what Ray is and what you can do with it
  • More instructive "get involved"
  • Adding a "what docs are for you?" guide

Screenshot 2022-01-25 at 16 40 49

@maxpumperla maxpumperla added the docs An issue or change related to documentation label Jan 25, 2022
@maxpumperla maxpumperla self-assigned this Jan 25, 2022
@maxpumperla maxpumperla requested a review from edoakes January 25, 2022 15:47
@maxpumperla
Copy link
Copy Markdown
Contributor Author

@richardliaw @ericl @edoakes wording matters here, please give me all your nitpicks.

@richardliaw
Copy link
Copy Markdown
Contributor

A couple stylistic changes to request:

Screen Shot 2022-01-25 at 11 17 54 AM

Can we avoid overlapping into the right sidebar?

Screen Shot 2022-01-25 at 11 18 40 AM

Can we make the buttons consistent?

Comment on lines +86 to +90
To help you, Ray Core provides a simple, universal API for building distributed applications.
And Ray's native libraries and tools enable you to run complex ML applications with Ray.
You can deploy these applications on any of the major cloud providers, including AWS, GCP, and Azure, or run them on your own servers.
Ray also has a growing [ecosystem of community integrations](ray-overview/ray-libraries), including [Dask](https://docs.ray.io/en/latest/data/dask-on-ray.html), [MARS](https://docs.ray.io/en/latest/data/mars-on-ray.html), [Modin](https://github.com/modin-project/modin), [Horovod](https://horovod.readthedocs.io/en/stable/ray_include.html), [Hugging Face](https://huggingface.co/transformers/main_classes/trainer.html#transformers.Trainer.hyperparameter_search), [Scikit-learn](ray-more-libs/joblib), [and others](ray-more-libs/index).
The following figure gives you an overview of the Ray ecosystem.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Right now this reads as a big paragraph; can we insert some linespaces?

---
**Run machine learning workflows with <img src="ray-overview/images/ray_svg_logo.svg" alt="ray" width="50px">ML**
^^^
With Ray ML you can run tasks like [distributed data loading and compute](data/dataset.rst),
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Ray ML is a toolkit for distributed machine learning. It provides libraries for distributed data processing, model training, tuning, reinforcement learning, model serving, and more. 

Perhaps we can add links to each, but I think we should condense the wording

---
**Deploy large-scale workloads with <img src="ray-overview/images/ray_svg_logo.svg" alt="ray" width="50px">Cluster**
^^^
With Ray Cluster you can deploy your workloads on [AWS, GCP, Azure](cluster/quickstart) or
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
With Ray Cluster you can deploy your workloads on [AWS, GCP, Azure](cluster/quickstart) or
With a Ray cluster, you can deploy your workloads on [AWS, GCP, Azure](cluster/quickstart) or


```{link-button} cluster/quickstart
:type: ref
:text: Get Started with Ray Cluster
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
:text: Get Started with Ray Cluster
:text: Get Started with Ray Clusters

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'm not sure about this. Can you give feedback on this particular element @edoakes @ericl ?

```

---
**Deploy large-scale workloads with <img src="ray-overview/images/ray_svg_logo.svg" alt="ray" width="50px">Cluster**
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
**Deploy large-scale workloads with <img src="ray-overview/images/ray_svg_logo.svg" alt="ray" width="50px">Cluster**
**Deploy large-scale workloads with <img src="ray-overview/images/ray_svg_logo.svg" alt="ray" width="50px">Clusters**

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Also consider removing the svg? Not sure if it scales well across devices.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

It's the size of the font, which does not change. can remove it later if people hate it.

@maxpumperla
Copy link
Copy Markdown
Contributor Author

@richardliaw I addressed your comments and added a getting started guide today. This should be good to go now.

Screenshot 2022-01-26 at 15 53 36

Screenshot 2022-01-26 at 15 53 46

@maxpumperla maxpumperla changed the title [docs] landing page [docs] landing page (fixes #21750) Jan 26, 2022
@zhe-thoughts zhe-thoughts linked an issue Jan 26, 2022 that may be closed by this pull request
2 tasks
title: "Tutorials and Examples"

- caption: Deploying Ray Clusters
- caption: Ray Clusters | Deployments
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

FYI, the caption says "Clusters" here but elsewhere we have "Ray Cluster", should we make that consistent?

Comment on lines +52 to +53
Ray Core provides a [simple and flexible API](ray-core/walkthrough.rst) for building and running your distributed applications.
You can often [parallelize](ray-core/walkthrough.rst) single machine code with little to zero code changes.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

nit to make these parts just a bit shorter (and reduce vertical height even more)

Copy link
Copy Markdown
Contributor

@richardliaw richardliaw left a comment

Choose a reason for hiding this comment

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

Looks good to me!

@richardliaw richardliaw merged commit b34099e into master Jan 27, 2022
@richardliaw richardliaw deleted the mp_docs_intro branch January 27, 2022 01:14
maxpumperla added a commit that referenced this pull request Feb 16, 2022
Co-authored-by: Richard Liaw <rliaw@berkeley.edu>
ericl added a commit that referenced this pull request Feb 17, 2022
* [docs] landing page (fixes #21750) (#21859)

Co-authored-by: Richard Liaw <rliaw@berkeley.edu>

* [Doc] Fix bad doc and recover doc of c++ api (#22213)

* [Docs] Ray Data docs target state (#21931)

Preview: [docs](https://ray--21931.org.readthedocs.build/en/21931/data/dataset.html)

The Ray Data project's docs now have a clearer structure and have partly been rewritten/modified. In particular we have

- [x] A Getting Started Guide
- [x] An explicit User / How-To Guide
- [x] A dedicated Key Concepts page
- [x] A consistent naming convention in `Ray Data` whenever is is referred to the project.

This surfaces quite clearly that, apart from the "Getting Started" sections, we really only have one real example. Once we have more, we can create an "Example" section like many other sub-projects have. This will be addressed in #21838.

* [Datasets] [Docs] Datasets library branding + positioning tweaks (#22067)

* [train] Minor fixes on Ray Train user guide doc (#22379)

Fixes some typos and format issues.

* [Doc] Fix bad links of dask and mars in ray-libraries.rst (#22210)

* merge

Signed-off-by: Max Pumperla <max.pumperla@googlemail.com>

* merge

Signed-off-by: Max Pumperla <max.pumperla@googlemail.com>

* merge

Signed-off-by: Max Pumperla <max.pumperla@googlemail.com>

* [docs] Clean up long titles in TOC (#22016)

* LINT

Signed-off-by: Max Pumperla <max.pumperla@googlemail.com>

Co-authored-by: Richard Liaw <rliaw@berkeley.edu>
Co-authored-by: Guyang Song <guyang.sgy@antfin.com>
Co-authored-by: Clark Zinzow <clarkzinzow@gmail.com>
Co-authored-by: Hao Chen <chenh1024@gmail.com>
Co-authored-by: Eric Liang <ekhliang@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs An issue or change related to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[docs] Improve the Getting Started section

3 participants