# New notebooks in Quickstart **URL:** \ **Category:** Announcements\ **Created:** [March 3, 2020, 3:30pm UTC](https://talk.observablehq.com/t/new-notebooks-in-quickstart/2897 "2020-03-03T15:30:27Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![thomasballinger](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/thomasballinger/32/2293_2.png) [@thomasballinger](https://talk.observablehq.com/u/thomasballinger)\ **Post date:** [March 3, 2020, 3:30pm UTC](https://talk.observablehq.com/t/new-notebooks-in-quickstart/2897/1 "2020-03-03T15:30:27Z")
Hello all, Since folks on the forum seem likely to have previously hidden the Quickstart section, I thought I’d let you know that some of the things we’re linking to there are new: 1. The new [D3 Gallery](https://observablehq.com/@d3/gallery) that @mbostock put together in the last couple weeks 2. [A Taste Of Observable](https://observablehq.com/@observablehq/a-taste-of-observable), a concise demonstration for new users of what Observable can do 3. [Observable for Jupyter Users](https://observablehq.com/collection/@observablehq/observable-for-jupyter-users), a series of notebooks introducing Observable in a way we hope Python users familiar with Jupyter will find useful. The Quickstart section has also been added to the unified homepage. Just as before, you can click the × close button to hide this section and use the horizontal ⋯ menu on your personal home page to bring the it back. Please let us know what you think of these new resources! Are they helpful to you? Do they help you explain Observable to someone else? ---
**Author:** ![Job](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/job/32/1185_2.png) [@Job](https://talk.observablehq.com/u/Job)\ **Post date:** [March 3, 2020, 4:01pm UTC](https://talk.observablehq.com/t/new-notebooks-in-quickstart/2897/2 "2020-03-03T16:01:20Z")
I’ll try to convince some of my former colleagues at Karolinska (who have fully embraced SciPy and Jupyter) to give the third link a shot 😉 (don’t hold your breath though, I’ve been trying to get them into Julia for ages too and that doesn’t seem to stick either) ---
**Author:** ![thomasballinger](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/thomasballinger/32/2293_2.png) [@thomasballinger](https://talk.observablehq.com/u/thomasballinger)\ **Post date:** [March 3, 2020, 4:05pm UTC](https://talk.observablehq.com/t/new-notebooks-in-quickstart/2897/3 "2020-03-03T16:05:58Z")
The second notebook in that series shows embedding an Observable visualization in Jupyter; hopefully this is both a bridging use case that brings people on board and a helpful example for people building visualizations for others to use! ---
**Author:** ![Job](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/job/32/1185_2.png) [@Job](https://talk.observablehq.com/u/Job)\ **Post date:** [March 3, 2020, 4:11pm UTC](https://talk.observablehq.com/t/new-notebooks-in-quickstart/2897/4 "2020-03-03T16:11:57Z")
By the way, I think the **“Observable is reactive”** section in that notebook would benefit from warning people about a gotcha that seems to hit every new Observable user, which is writing cells that are too large and depend on too many other cells. See for example this question I answered a while ago: > [@Update marker in map cell without cell refresh](https://talk.observablehq.com/t/update-marker-in-map-cell-without-cell-refresh/2815): > > Hi folks! Question on reacting to data changes without refreshing the entire cell. In my case, I have a map, and on that map I have a marker. If I want the marker’s position to be updated with the value of another cell, the entire map redraws when the value changes. [here’s the notebook](https://observablehq.com/@abenrob/untitled) Is it possible to have the map cell respond to the updated value without re-evaluating the entire cell? It took me a while myself to figure out that refactoring cells into smaller cells is an important habit to have to avoid excessive recomputation or “resetting” of cells. ---
**Author:** ![thomasballinger](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/thomasballinger/32/2293_2.png) [@thomasballinger](https://talk.observablehq.com/u/thomasballinger)\ **Post date:** [March 3, 2020, 8:44pm UTC](https://talk.observablehq.com/t/new-notebooks-in-quickstart/2897/5 "2020-03-03T20:44:52Z")
Great point. I mention that in the previous paragraph, > Because every cell has just one return value, you should break up big cells into little, focused ones. but I don’t hit quite the reasoning you’ve put forward here which I think is on point. ---
**Author:** ![cornhundred](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/cornhundred/32/1705_2.png) [@cornhundred](https://talk.observablehq.com/u/cornhundred)\ **Post date:** [March 5, 2020, 3:05pm UTC](https://talk.observablehq.com/t/new-notebooks-in-quickstart/2897/6 "2020-03-05T15:05:05Z")
Thanks for the notebooks, the Observable for Jupyter Users series is excellent! Our group is building a Jupyter Widget ([Clustergrammer2](https://github.com/ismms-himc/clustergrammer2)) and we’re excited about seeing how much of this workflow we can port over to Observable with the underlying JavaScript/WegGL library [Clustergrammer-GL](https://github.com/ismms-himc/clustergrammer-gl) library! ---
**Author:** ![thomasballinger](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/thomasballinger/32/2293_2.png) [@thomasballinger](https://talk.observablehq.com/u/thomasballinger)\ **Post date:** [March 5, 2020, 6:02pm UTC](https://talk.observablehq.com/t/new-notebooks-in-quickstart/2897/7 "2020-03-05T18:02:44Z")
Cool! Let me know if you run into any roadblocks, I’m thinking about ways to improve this embedding API, for Jupyter in particular.