rapidsai/cudf

[DOC] Split `cudf/source/user_guide/10min.ipynb` into 2 notebooks for cuDF and Dask-cuDF

Open

#21374 opened on Feb 6, 2026

View on GitHub
 (2 comments) (0 reactions) (1 assignee)C++ (6,000 stars) (735 forks)batch import
docgood first issue

Description

Report incorrect documentation

Location of incorrect documentation cudf/source/user_guide/10min.ipynb

Describe the problems or issues found in the documentation Currently this notebook (and other notebooks that use Dask) isn't being validated in our CI https://github.com/rapidsai/cudf/blob/62387458abe94670c386460a39c877c7530d544d/ci/test_notebooks.sh#L52

And it's likely that https://github.com/rapidsai/cudf/pull/20925 broke something in this notebook when run by-hand.

Suggested fix for documentation

  1. Create 2, 10 minutes to [cuDF|Dask-cuDF] notebooks so we can at least validate a (probably commonly seen) introductory cuDF notebook
  2. Investigate other notebooks that might be running Dask and split them out into other notebooks if appropriate. (The CI currently only skips validating 10min.ipynb because of Dask usage)

Contributor guide

Tech stack
python
Domain
documentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
PythonJupyter
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Examine the current notebook at cudf/source/user guide/10min.ipynb to understand its content and structure. Review the CI script at ci/test notebooks.sh to see how notebooks are validated for correct execution. Investigate the changes introduced in PR #20925 that may have broken the notebook when run manually. Create two separate notebooks: one for cuDF only and one for Dask cuDF, and update the CI script to validate both new notebooks.