Hello Quarto

share • collaborate • teach • reimagine

mine çetinkaya-rundel
julia stewart lowndes

mine.quarto.pub/hello-quarto

artwork by allison horst

Thank you so much, we’re excited to be here! Mine and I have been using Quarto for the last year; she has been teaching and contributing to the development of Quarto it since its earliest days and Openscapes has been the first external users of Quarto. As we’ve woven it into our work we realize we love it, and we’re thrilled to welcome you to Quarto.

Hello, Quarto?

But also, we know you have questions. We did too. What is Quarto? Why is Quarto? And how does it relate to R Markdown and the workflows you already have?

–> Well

Quarto unifies and extends
the R Markdown ecosystem

Quarto unifies & extends the R Markdown ecosystem.

Quarto unifies and extends
the R Markdown ecosystem

unifies for people who love R Markdown

extends for people who don’t know R Markdown

It unifies it for people who love R Markdown by reducing little points of friction, so that websites, books, and slides all have a common approach.

And it extends it for people who don’t know RMarkdown by being a friendly way to work reproducibly and publish documents that have text and code in the same place

Quarto is a new, open-source,
scientific and technical
publishing system

Quarto is a new open-source scientific and technical publishing system.

Quarto is a new, open-source,
scientific and technical
publishing system

the goal is to make the process of creating
and collaborating dramatically better

The goal is to make the process of creating and collaborating dramatically better.

–> It handles inputs in multiple languages, and outputs in multiple formats, all going through the same machinery.

–> In our talk today, we’ll introduce you to Quarto with stories and demos.

First Mine will focus on how Quarto unifies the R Markdown ecosystem through stories of sharing and teaching

Then I will focus on how Quarto extends the R Markdown ecosystem through collaborating and reimagining

Julie: We’re excited to get started!

NEXT - So let’s let Mine kick it off to talk about sharing with Quarto.

Share

Julie: We’re excited to get started! So lets starts off with how Quarto enables sharing. Over to you Mine

Mine: Thanks Julie! I’m very excited to have this opportunity to talk to you about Quarto, which I’ve had the pleasure to live and breathe over the last year.

I work at the intersection of education, research, and development.

The word educator might make you think I’m in front of students lecturing 24/7 but, in reality, I spend most of my time in front of my computer authoring and creating materials to share with people in various ways. Whatever it is that I create, I share them all openly - that is, with an open license that allows for free use, reuse, and adaptation. More often than not I’m thinking “web first” for wider reach, but I also still live in the confines of traditional journal publishing and academia, which means I regularly need to create PDF versions of my work as well.

Therefore an authoring system that allows for multiple types of outputs from a single source that contains both code and prose is not only a time saver, but it’s basically essential for me to carry on my existence. And for the last decade, that tool for me has been R Markdown.

In fact, I remember vividly the first time I’ve heard of knitr, now 10 years ago, at Yihui and JJ’s 2012 useR keynote, when they presented on a “new” tool for reproducible authoring. It must have been no more than 3 slides into their talk that I started to converting my teaching materials to use knitr. And by the end of that keynote I was already brainstorming ways of teaching it to my intro stats students.

So, I’ll call this talk a success if some of you are already firing up Quarto right now, instead of listening to me, to see what all the hype is about!

But I hope you’ll continue to listen with one ear and take in the beautiful illustrations by Allison Horst. And if you just want to enjoy the talk, feel free to go to this link: mine.quarto.pub/hello-quarto

sit back,

and I’ll advance the slides for you.

The R Markdown ecosystem

Julie mentioned unifying the R Markdown ecosystem so let’s dig a bit more into what that means…

Think of all the packages from the R Markdown universe that you’ve come to love and rely on over the years. Each package addresses a different need and offers a different output: for example, you can use blogdown or distill for creating websites and blogs, bookdown for writing a book, rticles for writing journal articles, etc.

Quarto: Next generation R Markdown

Quarto unifies the functionality from these packages,

building on Pandoc on the technical side

and on the human side – over a decade of experience developing, maintaining, and tweaking these packages as well as community feedback R Markdown extension packages.

Such a unification effort presents a fantastic opportunity to identify and address gaps functionality and inefficiencies in user experience, and the process of building Quarto has been no different.

Quarto highlights

Consistent implementation of attractive and handy features across outputs: tabsets, code-folding, syntax highlighting, etc.

More accessible defaults as well as better support for accessibility

Guardrails, particularly helpful for new learners: YAML completion, informative syntax errors, etc.

Support for other languages like Python, Julia, Observable, and more via Jupyter engine for executable code chunks.

Some highlights of these improvements include

–> consistent implementation of attractive and handy features across all outputs, like tabsets, code-folding, and syntax highlighting,

–> more accessible defaults as well as better support for creating accessible documents,

–> guardrails that are particularly helpful for new learners, like YAML completion and informative syntax errors,

–> and perhaps most excitingly for those who are not coming from the R ecosystem, Quarto offers support for other languages like Python, Julia, Observable, and more via the Jupyter engine for executable code chunks. And it’s designed to be expandable to more engines and languages, even those that might not exist today.

[pause] So by now I’m assuming many of you have already started playing with Quarto, or you’re waiting for me to do that. So, let’s dive in and see what all the Quarto fuss is about!

• Open hello.Rmd with source editor -> knit
• Change to visual editor -> knit
• Close file -> change file type to .qmd -> open + render
• Change output: html_document to format: html -> render
• Click on Render on save
• Change to format: pdf -> render -> then change back
• Add chunk option echo: false to the first chunk
• Add execute > echo: false to the yaml
• Add alt text to figure in second code chunk -> save to render
• Change to format: revealjs -> save to render
• Add H2 to break slides
• Change to format: html
• Add index.qmd with File > New Quarto Document
• Add _quarto.yml for website
• Relaunch project
• Show new Build tab
• Render site, show _site folder
• Add freeze to _quarto.yml
• From terminal: quarto publish

Quarto CLI orchestrates
each step of rendering

Now that you’ve all had a chance to see Quarto in action, you might be wondering, “how are R Markdown and Quarto different”?

The main difference is that with R Markdown, the R package rmarkdown does the heavy lifting of going from the source Rmd file to the the output, using knitr for evaluating the code chunks.

–> With Quarto, on the other hand, the Quarto command line interface, or the Quarto CLI, does the orchestration of processing executable code chunks with either knitr or jupyter and then converting the resulting markdown file to the desired output.

While this is technically impressive, I’ll be honest, it’s not exactly what sparked my interest in Quarto in the first place.

Quarto makes moving between formats straightforward

Document

lesson-1.qmd

title: "Lesson 1"
format: html

Presentation

lesson-1.qmd

title: "Lesson 1"
format: revealjs

Website

_quarto.yml

project:
  type: website

website: 
  navbar: 
    left:
      - lesson-1.qmd

What did spark my interest was how how straightforward it is with Quarto to move between output formats.

As an educator, two things are of utmost importance to me about the tools I use to create my materials: reproducibility and ease of transition between output formats, like documents to slides to websites to books.

Over the last year of using Quarto for pretty much everything, I’ve felt like I’ve finally found the tool that lets me go from one output type to the other with minimal, if any, futzing around with my source code beyond the yaml. For example, here are common things I produce

–> a lesson in document form
–> the same content in presentation form
–> the same content on a page in a website,

and you can see that all that needed to change going between these formats is a few lines in the yaml. Nothing in the content part of my document. No slide breaks to remove, no citation style to change, no headings to re-level. This ease of transition has freed up time to focus my time on content, and that, folks, is the dream!

Quarto facilitates open sharing

Tooling that makes it easy to share what you do
with the world on the web is incredibly useful

It’s useful not just to you, but to the world
as it facilitates open sharing of knowledge
for learning and for reuse

Ultimately, easily creating reproducible artifacts is great.

But for the sharing story to be complete, the tool also needs to support easily sharing those artifacts, like with a simple command like quarto publish, and hopefully soon a button RStudio that does the same thing.

–> I think that tooling that makes it easy to share what you do with the world on the web is incredibly useful.

–> And it’s not just useful to you, the creator, but to the world, as it facilitates open sharing of knowledge for learning and for reuse.

[Pause]

I’ve been talking just about me and my work so far, but I, like many of you, don’t operate in a silo disconnected from others.

[Mine continue on next slide]

Collaborate

Mine: Much of my work, and much of Julie’s work is collaborative. So, over to you Julie, for collaborating with Quarto.

Julie: Thank you Mine -

I work at the intersection of actionable environmental science, data science, and open science. What I absolutely love doing is mentoring, teaching, and empowering communities, having learned from so many of you in the R and Mozilla communities, and wanting to pay this forward and welcome others.

I’ve made this my job through Openscapes.

Openscapes is an approach and a movement that I launched in 2018 and have built together with my partner Erin Robinson.

Our flagship activity is mentoring research teams in open science. We think of open science as a landscape full of open source software, data, and communities, and many paths forward.

We help people move from the sad lonely animals like the foreground in the bottom right so that they start to explore and navigate this landscape safely, without too much trampling. Our role is to welcome them at the trail head, helping them seem themselves as a team and identify where they are all starting from

We work with professional research groups in government, academia, nonprofits, and we help these teams modernize their workflows and shift culture with their teams and organization through open software and practices. Adyan Rios from NOAA Fisheries and she’s described Openscapes as saying:

“As fisheries scientists, we know that when we’re in rough seas, it’s important to keep the ship afloat AND get out of the storm. Openscapes helps teams steer out of the storm of email chains with 37 versions of the same spreadsheet and to the calmer waters of open science and meaningful collaboration, using tools like R”

Adyan Rios
NOAA Southeast Fisheries Science Center

Adyan Rios says “As fisheries scientists, we know that when we’re in rough seas, it’s important to keep the ship afloat AND get out of the storm. Openscapes helps teams steer out of the storm of email chains with 37 versions of the same spreadsheet and to the calmer waters of open science and meaningful collaboration, using tools like R”

I have the best job - mentoring teams like Adyan’s who are doing really critical work and we help them do better science by connecting them to the tools and resources you all make.

It really blends mentoring and collabortion, and that is definitely true of our story with NASA.

With NASA you probably think about outer space, but they also collects an unbelievable amount of data about Earth. Researchers use NASA Earthdata in many ways including to understand and address impacts to the heat waves and wildfires like we’re increasingly seeing in summers due to climate change.

These data are freely available from 12 different NASA data centers - but researchers have to download it to analyze it locally - which puts a lot of burden on research groups.

Now, following years of the preparation, these data are migrating to the Cloud, and NASA data centers are supporting researchers who will be migrating their analytical workflows to the Cloud too.

Develop a mentor community across
NASA Earth science data centers

Co-create and teach common tutorials
to support researchers as they migrate analytical workflows to the Cloud

My partner Erin had 10 years of experience working with the NASA Earthdata community and she brought NASA and Openscapes together in a 3 year project to help this transition.

Our focus is in developing a mentor community across those 12 data centers to co-create and teach common tutorials with NASA Earthdata Cloud.

So let me just stop here and say this is big project.

And, it was really intimidating to me. NASA is an org I’ve looked up to my whole life, and I wasn’t familiar with the types and size of Earthdata, types of research questions, or cloud infrastructure

<> And an additional intimidating thing to me -

Many Earth scientists
use Python
😬

Many Earth scientists use python and jupyter notebooks. And my role leading NASA Openscapes was not to learn python from the ground-up, but I needed to be able to collaborate and support python users.

Transition: But I also brought over 6 years of experience and confidence that I’ve developed using RMarkdown. I think of RMarkdown like a superpower

And Quarto let me bring this superpower to python.

Quarto was emerging right when we needed it, and I asked J.J. Allaire if we could use for NASA Openscapes. This became a really exciting collaboration with the Quarto developer team and the NASA Mentors and we were able to use it basically out of the box but also we motivated certain features, particularly in the freeze feature that just Mine introduced.

This Quarto site we made for our first teaching event.

This is where we really found traction in working together as a Mentor community: we were able to make a beautiful collection of tutorials that was helpful for our own development and was a friendly place for our learners.

Quarto was also something for us all to learn together. And that was really important bc it turned out I wasn’t the only person feeling intimidated about all the moving parts. We were able to identify other skills to learn together.

So from this investment in our workflow and learning -

We were able to do with this same workflow and and extend for new audiences.

There’s 2 things I want to highlight here -

Quarto enables collaborating
across coding languages

_quarto.yml

contents:
  - section: in-development/index.qmd
    contents:
      - in-development/earthdata-access-demo.ipynb
      - in-development/nsidc/icesat2-cmr-onprem-vs-cloud.ipynb
      - in-development/lpdaac/lpdaac_ecostress_lste_kerchunk.ipynb
      - in-development/matlab-aws.qmd
      - in-development/earthdata-python-r-handoff.rmd  
  - section: contributing/onboarding.qmd
    contents: 
      - contributing/quarto-website-tutorial.md

Quarto enables collaborating across coding languages. This is a simplified view of the yaml it’s collection of different file types. It’s mostly ipynbs Jupyter notebooks.

And, as we work with more research teams we’ve found that there is indeed a substantial R community using NASA Earthdata Cloud data. And we’re positioned to support R users too

Quarto enables contributing
from our current tools

we’re all able to contribute from whatever tool we’re already comfortable with. In our group some use RStudio, some use JupyterLab some VS Code, some directly edit documents on GitHub.

And this was important because of all the new things we were learning together, we didn’t also need people to shift their software tools.

transtion: Let me show you how to use Quarto with Jupyter with ipynb notebooks

• Orient to JupyterLab. This is a JupyterHub managed by our collaborators at 2i2c
• Open Mine’s example site, quarto preview
• add .ipynb
• Add .ipynb to _quarto.yml
• View website - new page is added to website
• Add fig captions
• margin plots: a style prefrred by many now in jupyter notebook

Teach

Julie: Transition: And this has teaching implications that Mine will talk about next.

Mine:Over the last decade I have thoroughly loved teaching R Markdown. It’s amazing when students hit that Knit button, see their code and their prose come together – you can often hear a “wow, that’s so cool” in the classroom the first time that happens. I’ve also loved that this is a tool that they can pick up easily on the first day of an intro course, and it grows with them as their statistical and computational expertise grows. However, as students’ expertise in these areas grow, the computation gets more resource intensive (and even sometimes involving multiple languages) and they end up needing different output formats to support their needs, like PDFs in specific journal styles or a thesis with multiple chapters. A pleasant surprise in teaching with Quarto has been how much less steep the learning curve is for making this transition from single, simple document to a multi-document projects. Let me tell you the story of one of my thesis students.

Quantifying
Art Historical
Narratives

Holland Stam

Art History +
Visual and Media Studies

Class of 2022

Duke University

Last semester I had an art history student, Holland Stam, working on a pretty quantitative research project. Her thesis explored the representation of artists from different genders and ethinicities in foundational art history books and how this representation has changed, if at all, through editions. If you’ve ever taken an art history course you might be familiar with them: Garner’s Art Through The Ages and Janson’s History of Art. She meticulously collected data from numerous editions of each of the textbooks and measured, page by page, how much space each featured artwork was given and joined that with demographic information on the artists. When I met Holland in my regression course she had only one semester of data science as a background, where she learned R Markdown, and then she started using Quarto as part of coursework in my class. In both classes her experience with computational documents was limited to a single document per assignment, writing a bit of code to analyze data then writing some text to interpret findings. In a sense, this is exactly what her thesis entailed as well, but of course there was more. Multiple chapters, millions of citations in a very specific style that art historians use, captioned figures and tables, and not having to rerun the whole thesis code with each minor edit. With a bit of Googling and a bit of my help, she pretty quickly figured out how to bring chapters of her thesis written in Quarto together with a yaml file, and voiola! She had a thesis written in Quarto. Sure, this took a bit of trial and error and at times frustration, but the fact that she could caption her figures while creating them with code and insert citations without manual text styling, she was sold! It is always so heartwarming to see your students push what you’re teaching them and use them to solve their problems, it’s especially heartening when this happens with a new thing you’re teaching for the first time while the thing is still in active development!

Quantifying
Art Historical
Narratives

Holland Stam

Art History +
Visual and Media Studies

Class of 2022

Duke University

with Sara Lemus

And, by the way, if you’re interested in the data, Holland and another student of my, Sara Lemus, packaged it up as “arthistory”. Sara is a stats major who had a lot more experience with R and was working with me for updating some data packages I maintain to learn about package development. She got interested in Holland’s thesis during our lab meetings and it was clear the two of them, with their newly acquired skills and enthusiasm, should team up and make the data available to more researchers, and packaged it up and even got it on CRAN!

But, back to Quarto… like for Holland, Quarto has provided simple but effective solutions for so many of my problems as an instructor too. Instead of telling you about them, let me show you!

For learning:

• RStudio comes with everything, no additional install needed
• visual editor – Julie will say more
• code-link
• yaml errors

For teaching:

• revealjs
• Show hamburger menu outline and print to PDF
• chalkboard
• multiplex: Slides / scroll for audience
• execute > echo: true
• Add code line highlighting to plotting chunk

Features that are useful for research:

• quarto journals

Quarto flattens the learning curve

So, in regards to teaching, I’ve talked about a much less steep hill students need to climb as their projects grow. I’ve also said this was a pleasant surprise as it was not something I had thought about when I started teaching with Quarto. But, in hindsight, this was no coincidence. Quarto’s features like consistent citation syntax, more intentional control over when computations should run or rerun, and a single, minimal yaml that controls inputs, layouts, theming, etc. all contribute to flattening this learning curve.

Quarto can grow with learners in a profound way

And beyond learners growing and expanding the scope of their work easily with Quarto, Quarto can grow with them in a profound way as well.

–> The fact that Quarto is language and authoring tool independent offers an opportunity for folks to take Quarto with them on their data science journey, wherever that journey takes them. I mean.. I’m almost tempted to finally learn Python to see it in action in Quarto. But who I know is learning Python, and Julia, and other languages are my students in their Computer Science courses. To imagine that they could learn R in RStudio using Quarto in my course, and then continue to use Quarto in Jupyter in their CS courses… That sounds like such a bright future to me!

[Pause] And a bright future includes things we can’t even imagine yet.

[Mine continue on next slide]

Reimagine

Mine: So Julie will now tell us a bit about reimagining with Quarto.

Julie: Thanks Mine. We’ve seen already how much Quarto enables with teach/collab/share

And now I want to push it a bit further. What if we could reimagine open science and open source as part of the climate movement. We know what this R community is capable of, what if

To address our climate emergency, we must rapidly, radically reshape society. We need every solution and every solver.

Ayana Elizabeth Johnson & Katharine Wilkinson
All We Can Save

Because we are in a climate emergency. We must rapidly, radically reshape society. We need every solution and every solver. Hard, big. My hope lies in what we have here and what we can do with it. This is a big movement -

Let’s think about this with 3 user groups if you will

scientist working direct w climate - hard and stuck. Openscapes

R/open source - stuck, Posit 100 yrs

extensible beyond

Every solution, every solver. Across all facets and geographies, skills, expertise. We need more women. We need more people of color. We need more perspectives on every level. Dial up inclusion and culture change and welcome at an unprecedented level

Requires slowing to speed up

But when it speeds up it’s like a flywheel

My colleague Ileana Fenwick is a marine ecologist who particpated in Openscapes last year and beautifully describes this

Because of Openscapes, I have renewed hope in how we can bring about a kinder future in science. I see a commitment in the open science community to bridging the gaps where we’ve left members of our community behind, and it inspires me.

Ileana Fenwick
University of North Carolina, Openscapes

Because of Openscapes, I have renewed hope in how we can bring about a kinder future in science. I see a commitment in the open science community to bridging the gaps where we’ve left members of our community behind, and it inspires me.

Culture shifts:
technical + human

We’re talking about a profound culture shift that involves real deliberate work on the tech and human side

Let’s focus on the human side: We can build inclusion into our daily work. Let’s think about your team and collagues because I bet they’re not different from the teams we mentor

This means talking and reflecting with your colleagues: how do we work? shared workflows, where is friction? who contributes, how do they contributes? Handoffs?

This means asking questions and really listening. might not have the language to describe where they’re stuck. Not assuming, not solutioneering. But listening for understanding to meet them where they are

This means being braver to say I don’t know, I need help

A practice, not a checklist.

A practical example -

Fay Lab Manual is a site created by Gavin Fay’s Group UMass D They are quant fisheries ecologists: data and code: work with managers: food systems and climate Bc formal training in data science is uncommon in env, range of skills incoming This site: lab culture, code of conduct, info about how they name files, how to learn the software they use

It’s a living doc online, and it’s imperfect

It is radical in many ways, here are 3:

1. Make the implicit explicit

2. Onboard learners as contributors

3. Psychological safety & growth mindset

Makes the implicit explicit all be clear on how their group works together and it also puts the values forward and to welcome people who might be interested in joining the

onboards learners as contributors As you read the manual you’re also instructed how to contribute. So it’s through learning tools like Quarto to fix a typo that empowers learners in a lasting way.

psychological safety & growth mindset deliberately for example prioritzing time to check in during meetings and screensharing/live coding.

Reimagining within one lab and that idea is catching at bigger scales -

We forked this idea back Here are 2 more examples: our Approach Guide which is how we onboard ourselves and others to grow the movement

And NOAA Fisheries is using Quarto to building open science community across their science centers

Using quarto for culture change

Quarto enables collaborating
across coding comfort levels

Quarto enables collaborating across coding comfort levels, which means it’s a friendly tool Also means we can broaden our idea of collaborators substantially and earlier.

And, then RStudio IDE Visual Editor further lowers barriers

I’ll do one final demo here - Friendly for new learners, also for experienced users.

Think about how you might use this yourself, and teach a colleague

• i can write and paste formatted text
• Add image, caption, alt text
• source editor
• citations 2 ways: @ from my Zotero, forward-slash citation for doi
• Also: Call-outs
• Add extension:

transition: throughtout talk, focus on quarto enables teach/collab/sharing. culture. Let’s end with what we can all enable -

We all can enable reimagining

“We” speaks to the collective, to collaboration, to community, to the relational work at hand. Addressing the climate crisis…will take everyone.

We cannot, we must not, go it alone.

Ayana Elizabeth Johnson & Katharine Wilkinson
All We Can Save

We can all enable reimagining at levels. We can all play our part We can do this in our daily work, with teams, scale it beyond. We invite you to reimagine too -

And we cannot, we must not go it alone.

mine.quarto.pub/hello-quarto

If you would like to start sharing, collaborating, teaching, and reimagining with Quarto by picking up where we left off, go to this link and scroll forward to see the next few slides where we share resources for learning as well as references for the works we presented today. And if you have any questions about Quarto or R Markdown, please stop by the Open Source table in the Lounge between 12-3pm today. And don’t miss the Quarto session at 3:20pm!

Thank you

Thank you so much for joining us this morning, here in person or from wherever you are tuning in to the live stream. We’ve talked about our experiences using Quarto and all the problems it has helped us solve and reimagine, but while Quarto is stable and ready for use, it’s also a baby that you too can be a part of its growth. So start using Quarto, and get involved by asking questions, reporting issues, providing feedback, and even building extensions for it. We can’t wait to see what you create!

Say hello to Quarto!

• Pick up where we left off: github.com/mine-cetinkaya-rundel/hello-quarto-demo

• Coming up at rstudio::conf(2022) – Quarto deep dive - Potomac C - 3:20pm:

  • Tracy Teal - These are a few of my favorite things (about Quarto presentations)
  • Hamel Husain - Literate Programming With Jupyter Notebooks and Quarto
  • Devin Pastoor - Websites & Books & Blogs, oh my! Creating Rich Content with Quarto

• Video: Reproducible authoring with Quarto

• Video: Openscapes: Hello Quarto with NASA Openscapes, RLadies Santa Barbara, and JJ Allaire

• Quarto documentation: quarto.org

• Quarto gallery: quarto.org/docs/gallery

• Quarto tip a day: rstd.io/quartotip

Engage, empower, amplify with Openscapes

• Coming up at rstudio::conf(2022)

  • Ileana Fenwick - A Journey to Data Science: Tools for Equity and Diversity in STEM. 1:30pm - 1:50pm EDT

• Openscapes: openscapes.org

  • Champions Lesson Series
  • Approach Guide
  • Quarto Website Tutorial

• NASA Openscapes: nasa-openscapes.github.io

• NMFS Openscapes: nmfs-openscapes.github.io

• Supercharge your research: a ten-week plan for open data science (Lowndes et al. 2019)

• Our path to better science in less time using open data science tools (Lowndes et al. 2017)

• Open Software Means Kinder Science

Earthrise by Amanda Gorman¹

So, earth, pale blue dot
We will fail you not.

Just as we chose to go to the moon
We know it’s never too soon
To choose hope.
We choose to do more than cope
With climate change
We choose to end it—
We refuse to lose.
Together we do this and more
Not because it’s very easy or nice
But because it is necessary,
Because with every dawn we carry
the weight of the fate of this celestial body orbiting a star.
And as heavy as that weight sounded, it doesn’t hold us down,
But it keeps us grounded, steady, ready,
Because an environmental movement of this size
Is simply another form of an earthrise.

NASA, Apollo 8, 1968

1. Full text and video for Earthrise by Amanda Gorman

Annotated Notes: Share

Mine Çetinkaya-Rundel PhD https://mine-cr.com

• Hex logos: https://github.com/rstudio/hex-stickers

• How it works: https://quarto.org/docs/get-started/hello/rstudio.html#how-it-works

Annotated Notes: Collaborate

Julia Stewart Lowndes PhD https://jules32.github.io

Openscapes

https://openscapes.org

NASA Images

• Spinning Globe Earthdata: https://svs.gsfc.nasa.gov/30701
• NASA Hyperwall: https://eospso.nasa.gov/content/about-nasas-hyperwall

NASA-Openscapes

• nasa-openscapes.github.io

• 2021 Cloud Hackathon

• 2021 Cloud Workshop at AGU

• 2022 SWOT Ocean Hackathon

Demo: JupyterLab JupyterHub managed by 2i2c https://2i2c.org

Other Rey with Quarto, throwback to https://jules32.github.io/useR-2019-keynote

Annotated Notes: Teach

• Photo credit for Holland Stam: https://undergraduateresearch.duke.edu/news/data-scraping-art-history-survey-texts

• 📦 arthistory: https://saralemus7.github.io/arthistory

Annotated Notes: Reimagine

All We Can Save: https://www.allwecansave.earth

How to answer the Q of “What should I do to fight climate change?”
A: “What are you good at? Do that. Do that in the service of climate” - (ayanaeliza)

FayLab Manual

• Learning by doing: migrating to Quarto from Bookdown
• Re: Tara Robertson on psychological safety A Chat with Tara Robertson
• Re: Gavin Fay on psychological safety: Openscapes is Awesome! Building lab resources to sustain future us with tools from open data science

Quarto Mosaic

See also: 3 takeaways for planning for the year of open science

• https://openscapes.github.io/approach-guide
• https://nmfs-openscapes.github.io

NASA images

• https://twitter.com/nasaearth
• https://twitter.com/UNOOSA/status/803692453358424064/photo/1
• https://www.doi.gov/blog/earth-art-stunning-landsat-images