Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

proposed wording for user facing nb7 messaging #110

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

paddymul
Copy link

@paddymul paddymul commented May 3, 2023

I'm trying to collaborate/propose tighter messaging around NB7

@paddymul
Copy link
Author

paddymul commented May 3, 2023

I'm making this PR to tighten up the wording of the user facing messaging about NB7.

I'm trying to consider the following user groups

  1. Active users of Jupyter. This group is much less familiar with the day to day goings on of jupyterlab development
  2. Current extension developers. They want to know what changes need to be made to their projects for compatibility.
  3. Future extension developers. They need to be able to quickly understand the Jupyter ecosystem to know which extension system it makes sense to target their extension to. They can deal with more details of the internals than active users.

## User facing messaging for Jupyter Notebook and Jupyter Lab

### Main message
The Jupyter Notebook application offers a _document-centric user experience_. The Jupyter Lab application offers a _development-centric user experience_. With the Jupyter Lab 4 release and the Notebook v7 release these two experiences will be provided on top of the same Jupyter Lab codebase. The most popular Notebook extensions of nbgrader, rise, and JUPYext will work at the release date. We will work with maintainers to port over other extensions over the coming months.
Copy link
Author

Choose a reason for hiding this comment

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

This is my best stab at a tight paragraph for users. very open to other suggestions if I didn't capture the intent of the project creators.

with notebook v7, this become largely a matter of personal preference

### When should I not move to v7
if you depend on an unsupported extension
Copy link
Author

Choose a reason for hiding this comment

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

In the interest of a clear story with tight messaging, I think talking about legacy use cases should be described separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant