Trim open standards intro #447
Conversation
index.html
Outdated
| @@ -226,7 +226,7 @@ <h3 class="section-header">Currently in use at</h3> | |||
| <div class="architecturedescription"> | |||
| <img src="assets/architectureicon2.svg" class="section-icon" alt="icon to represent jupyter architecture"> | |||
| <h3 class="section-header">Open Standards for Interactive Computing</h3> | |||
| <h4 class="support-paragraph">The Jupyter Notebook is based on a set of open standards for interactive computing. Think HTML and CSS for interactive computing on the web. These open standards can be leveraged by third party developers to build customized applications with embedded interactive computing.</h4> | |||
| <h4 class="support-paragraph">Project Jupyter is based on open standards that third-party developers can leverage to build customized applications. Think HTML and CSS for interactive computing on the web.</h4> | |||
There was a problem hiding this comment.
The original reads like it was specifically talking about the application called "Jupyter Notebook" and not the notebook format or "Project Jupyter" more generally.
I like the idea of shortening this paragraph, but I think this ambiguity between Project Jupyter (a community of people and also lots of individual applications and tools) vs. one or more applications that Project Jupyter has built (Jupyter Notebook, JupyterLab, JupyterHub, IPython, etc.) needs to be resolved.
There was a problem hiding this comment.
Gotcha. Makes sense. Do you think that calling out "The Jupyter Notebook" specifically suggests that it doesn't apply to JupyterLab? That's what tripped me up.
There was a problem hiding this comment.
I think you're right that it creates that question. I'm open to suggestion here, I don't really have a good one myself 😅
There was a problem hiding this comment.
Maybe something like "Project Jupyter promotes open standards..."?
There was a problem hiding this comment.
@afshin, I've made an edit to address your concerns. What do you think?
|
The conflicts here have been resolved. |
|
@palewire I know it's annoying but mind fixing these conflicts and we can merge? Apologies that this PR got missed earlier |
|
This is done. I'll merge. |
The copy here contains some redundancies and is a little long. I've proposed a trim. It doesn't change the message, just tightens it up.