@domoritz Here is the Jupyter Book PR. I moved the notebooks to the doc folder and added CI to rebuild the book upon changes to this folder. You can have a peak at the rendered book from my branch here. I used the logo from your github organization for the book and a slightly modified version of the readme for the landing page (but please edit if this is not appropriate).

close #13

Hi, I took the freedom to add those great Notebooks to Nextjournal! It has a nice way to publish notebooks and remembers all installed software, so all notebooks "just run" ;) If you already have an account, I can also transfer the ownership of those notebooks to you!

Best, Simon

For example, see: https://github.nextjournal.com/uwdata/visualization-curriculum/blob/master/altair_interaction.ipynb

Some of the chart views in the notebook are not properly sized (widgets are below the fold, or even whole charts are not properly captured). This may be a Nextjournal issue; don't know if there is something we can do on our end to fix this.

@domoritz any ideas? I haven't used Nextjournal before and I think you merged these additions?

Hello! We would like to remix much of the material from this repo into one of our university courses (with accreditation of course) and I just wanted to double check if this is OK. The remixing will mostly entail reordering to fit with our curriculum and extending the material where we see fit. I saw that the license is BSD-3 for the repo, but just wanted to double check before going ahead with this.

Per the latest release notes

The current use of rangeStep is causing an error for people trying to run this notebook with the latest version of Altair. I tried to make the most minimal change possible to the notebook so that the diffs are human-readable. 🙇 Thank you so much for this very useful tutorial.

cc/: @dansbecker

In https://github.com/uwdata/visualization-curriculum/blob/master/altair_introduction.ipynb, there is a section about renderers on the top of the page:

Yet, alt.renderers.enable('jupyterlab') call is actually happening when we call chart the first time.

Great tutorial, very clear and helpful. Thanks!

https://github.com/uwdata/visualization-curriculum/blob/master/altair_marks_encoding.ipynb

This code is used a number of times, but does not seem to be valid.

.properties(
    width={"step": 50} # adjust the step parameter
)

A numerical value does work: e.g. width=100 I could not find from the documentation how to apply the step

@jheer I really loved these tutorials on Altair, as they demystified Altair for me.

I'm working with Jeremy Howard (@jph00) on fastpages

The reason we created this is we wanted a blogging system that was easy to use but also open source, and where people could own their data. Plus, we wanted to support cool features like interactive charts & graphs in Altair! A summary of features is below, which can also be viewed on the README:

Sharing this incase it is interesting for your students, especially to share their cool visualization projects! Thank you 🙇

The "complete list of time units" link in the "Time Units" section of altair_data_transformation.ipynb is broken.

Should probably be replaced with: https://altair-viz.github.io/user_guide/transform/timeunit.html#user-guide-timeunit-transform

The University of Washington works hard to foster an inclusive and welcoming culture for everyone in the campus community.

Unfortunately, looking over your GitHub repositories, I have identified language that can be considered offensive due to its racist origins. Specifically the branch names, but I imagine if I looked at the code itself, I would find more.

Can you let me know when you’ll be adjusting the settings to be a inclusive product/service and follow University of Washington language guidelines?

Hi @domoritz! This adds the option to view & run these notebooks in Nextjournal. We made sure all notebooks are runnable as-is now. This supersedes #6.

like in https://vega.github.io/vega-lite/examples/layer_dual_axis.html

The current example in the notebook doesn't make it clear which variable is which mark

(It's ok for people who follow the tutorial as they created it themselves, but once they copy this example to create charts and share with other audience, it would be confusing.)