A lot of tutorials I find on blogs are written in v4 or v3 of D3, but a lot of the content on Observable is written in v5. We call d3.treemap and set some parameters: We make it fullscreen; Set some paddings to make the rectangles nicely separated Every Azle function takes a “target_class” and target_instance to add an element to the DOM. The API also provides an image URL of the selected book, so we will show the book cover when the user searches by ISBN: We’ll stitch together Observable and Google’s Book API into a real application using Azle. 11.3 Observable Observable, created by D3 author Mike Bostock, is the official D3 web tool for creating and sharing D3 code. D3.js is a JavaScript library for manipulating documents based on data. Our tasks involved creating a quick layout based off 2 simple mockups, crafting and targeting components, embedding an Observable table and bar chart inside frames, communicating between app and Observable using message posting and event handlers, and finally using Google’s Book API to populate the bar chart and show the book cover after searching by ISBN. We will discuss this in the next section. Like many others, I found myself on this thread as a result of a lot of frustration. For this to succeed, code must become more approachable, which means breaking a few eggs. Forcing everyone who want to learn D3 must learn how to use Observablehq.com first? Since this is a vertical bar graph, the chart width will be fixed and the bar width will be variable depending on the dataset size. The purpose was to encourage moving beyond stand-alone visuals and get people prototyping fuller applications. I think that being able to compare old with new would drastically ease the learning process for so many people. Javascript and D3.js Tutorial. Is that ok? Thanks for your encouragement, I would stick with Observable for a while and try to understand. A separate issue is that the code in observable is fragmented into independent cells, which makes it difficult to copy / paste all in one swoop. It was through that library’s homepage that I discovered Observable, a new site that enables users to publish self-contained collections of code with little effort. Paulo Zemek: 29-Jun-15 9:16 : I saw that part of the article. I agree that Observable may be the way to go, and I do agree with a lot of the advantages being presented - but the problem is (and I think I see many others expressing similar views): why, oh why, can’t we have the copies of the ‘regular’ code that we are used to, in addition to the observable versions? So it is a little bit difficult to learn D3 and JS. In this article we’ll look at the following topics: You can view the simple application here. The Observable community has been really caring and helpful toward me. Maybe a tool, or a tutorial, could help with the necessary changes — things like replacing require by