render and freeze lessons/demo.qmd

_freeze/lessons/demo/execute-results/html.json

@@ -1,8 +1,8 @@
 {
-  "hash": "a1c645e528cd68c7ae21d914002f5526",
+  "hash": "1088a745449606fcf8927a940f9e1516",
   "result": {
     "engine": "knitr",
-    "markdown": "---\ntitle: \"`demo.qmd` Quarto Practice\"\n---\n\n\nQuarto enables you to weave together content and executable code into a finished document.\n\nThis `demo.qmd` file has Markdown-formatted text, examples for adding hyperlinks and inserting images with alt-text, and a Python code chunk.\n\n-   Headers. Headers are powerful in Quarto because they let you organize on the side of the page. They let you share a specific section of a page by copying the URL\n-   hyperlink something (cite the Cookbook and hyperlink it). Hyperlinking is done like this; lets you cite and give credit\n-   inspect this image with alt-txt\n-   Python code. manage echo, run\n\nStef will demo then it's your turn.\n\n## Task 1a: Edit a `.qmd` page\n\n*TODO: Edit down to what we need, duplicated under each name header*\n\n::: callout-note\nOnly make changes to the section under your name header (to prevent conflicts at a later stage)\n:::\n\nNow let's practice Markdown in this Quarto file and commit an edit to this file.\n\nMake an edit, preview, edit etc\n\n### Stefanie\n\nYour first edit? Fix this tpyo.\n\n#### **Headers**\n\nWe can make headers using `## Name`, `### Name`, etc. Headers are powerful in Quarto because they let you organize your content. You can share a specific subsection of a page by copying its URL.\n\n#### **Hyperlinks**\n\nWe can make hyperlinks using the `[]()` pattern: you name the hyperlink in `[]` and put the URL in `()`. For example, here's a link to [Markdown Basics](https://quarto.org/docs/authoring/markdown-basics.html). Hyperlinking lets us cite and give credit to our sources, like the NASA Earthdata Cloud Cookbook ([Barrett et al.](https://nasa-openscapes.github.io/earthdata-cloud-cookbook/)).\n\n#### **Images**\n\nWe can include an image with the same `[]()` pattern, by adding a preceding exclamation point: `![]()`. The `[]` contain the caption and `()` contain the path to the image file. Other attributes like image size, alt text, and a hyperlink, are also set in this example:\n\n[![The Openscapes logo](/images/openscapes_hex.png){fig-alt=\"Openscapes logo. A hexagonal shape with orange border, yellow background, the word openscapes in orange above a cartoon evoking a landscape of data plots\" width=\"150\"}](https://openscapes.org/)\n\n#### **Code**\n\nWhen you **Render**, a document will be generated that includes both content and the output of embedded code. You can embed code like this:\n\n*TODO: day before clinic, make this Python code (don't add screenshot - fewer files to for folks to get distracted with, lighter weight repo)*\n\n\n::: {.cell}\n::: {.cell-output .cell-output-stdout}\n\n```\n[1] 4\n```\n\n\n:::\n:::\n\n\nYou can add options to executable code. The `echo: false` option disables the printing of code (only output is displayed).\n\n### Julie\n\nFix this tpyo.\n\n*TODO: copy activities text under each participant heading when it's settled*\n\n### Andy\n\nFix this tpyo.\n\n## Your turn!\n\nChange or add something to this file under your Name header and save the file.\n",
+    "markdown": "---\ntitle: \"`.qmd` file for practice\"\n---\n\n\nThis `demo.qmd` file has [Markdown](https://quarto.org/docs/authoring/markdown-basics.html)-formatted text, examples for adding headers, hyperlinks, and inserting images with alt-text, and a Python code chunk.\n\n-   Headers are powerful in Quarto because they let you organize on the side of the page. In a Quarto site, headers let you share a specific section of a page by clicking on a header and copying the URL.\n-   Hyperlinking lets us cite our sources and inspirations and give credit.\n-   Python code in a `.qmd` file will be executed automatically.\n\nWe can all practice Markdown in this Quarto file. Make an edit, preview how it will look in the site (`quarto preview`), edit, repeat.\n\nOnly make changes to the section below under *your* name header (to prevent conflicts with other people's edits)\n\n## Ideas for contributions\n\n#### Headers\n\nWe can make headers using `## Name`, `### Name`, etc. Headers are powerful in Quarto because they let you organize your content. You can share a specific subsection of a page by copying its URL.\n\n#### Hyperlinks\n\nWe can make hyperlinks using the `[]()` pattern: you name the hyperlink in `[]` and put the URL in `()`. For example, here's a link to [Markdown Basics](https://quarto.org/docs/authoring/markdown-basics.html). Hyperlinking lets us cite and give credit to our sources, like the NASA Earthdata Cloud Cookbook ([Barrett et al.](https://nasa-openscapes.github.io/earthdata-cloud-cookbook/)).\n\n#### Images\n\nWe can include an image with the same `[]()` pattern, by adding a preceding exclamation point: `![]()`. The `[]` contain the caption (optional) and `()` contain the path to the image file.\n\n![The Openscapes logo](/images/openscapes_hex.png){alt=\"The Openscapes logo\" width=\"150\"}\n\nAdditional attributes like image size, alt text, and linking the image to a URL, are set inside `{}` in this example:\n\n![The Openscapes logo](/images/openscapes_hex.png){alt=\"The Openscapes logo\" fig-alt=\"Openscapes logo. A hexagonal shape with orange border, yellow background, the word openscapes in orange above a cartoon evoking a landscape of data plots\" width=\"150\"}\n\n#### Code\n\nWhen you **Render**, a document will be generated that includes both content and the output of embedded code. You can embed code like this:\n\n*TODO: day before clinic, make this Python code (don't add screenshot - fewer files to for folks to get distracted with, lighter weight repo)*\n\n\n::: {.cell}\n\n```{.r .cell-code}\n2 * 2\n```\n\n::: {.cell-output .cell-output-stdout}\n\n```\n[1] 4\n```\n\n\n:::\n:::\n\n\nYou can add options to executable code. The `echo: false` option disables the printing of code (only output is displayed).\n\n## Stefanie\n\nFor your first edit, you could fix this tpyo and preview how it will look in the site.\n\n## Alexis\n\nFor your first edit, you could fix this tpyo and preview how it will look in the site.\n\n## Andy\n\nFor your first edit, you could fix this tpyo and preview how it will look in the site.\n\n## Eric\n\nFor your first edit, you could fix this tpyo and preview how it will look in the site.\n\n## Guoqing\n\nFor your first edit, you could fix this tpyo and preview how it will look in the site.\n\n## Ian\n\nFor your first edit, you could fix this tpyo and preview how it will look in the site.\n\n## Jessica\n\nFor your first edit, you could fix this tpyo and preview how it will look in the site.\n\n## Juan\n\nFor your first edit, you could fix this tpyo and preview how it will look in the site.\n\n## Julie\n\nFor your first edit, you could fix this tpyo and preview how it will look in the site.\n\n## Katherine\n\nFor your first edit, you could fix this tpyo and preview how it will look in the site.\n\n## Kytt\n\nFor your first edit, you could fix this tpyo and preview how it will look in the site.\n\n## Luis\n\nFor your first edit, you could fix this tpyo and preview how it will look in the site.\n\n## Michele\n\nFor your first edit, you could fix this tpyo and preview how it will look in the site.\n\n## Navaneeth\n\nFor your first edit, you could fix this tpyo and preview how it will look in the site.\n\n## Rhys \n\nFor your first edit, you could fix this tpyo and preview how it will look in the site.\n\n## Ritika\n\nFor your first edit, you could fix this tpyo and preview how it will look in the site.\n\n## Rupesh\n\nFor your first edit, you could fix this tpyo and preview how it will look in the site.\n\n## Roosevelt\n\nFor your first edit, you could fix this tpyo and preview how it will look in the site.\n\n## Scott\n\nFor your first edit, you could fix this tpyo and preview how it will look in the site.\n",
     "supporting": [],
     "filters": [
       "rmarkdown/pagebreak.lua"