diff --git a/_freeze/lessons/demo/execute-results/html.json b/_freeze/lessons/demo/execute-results/html.json new file mode 100644 index 0000000..93ae46f --- /dev/null +++ b/_freeze/lessons/demo/execute-results/html.json @@ -0,0 +1,15 @@ +{ + "hash": "e2b8dc7268110cabdbda0c461f5e0d75", + "result": { + "engine": "knitr", + "markdown": "---\ntitle: \"`demo.qmd` aka 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 an Python code chunks, Markdown-formatted text, and examples for adding images and hyperlinks.\n\nTODO: edit this file to contain the content listed below\n\n### Edit and preview a demo.qmd file\n\n1. Edit a .qmd page (uses demo.qmd file that has markdown for text, add hyperlink, add image, run Python code)\n\n 1. Headers\n\n 1. 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\n 2. hyperlink something (cite the Cookbook and hyperlink it)\n\n 1. Hyperlinking is done like this; lets you cite and give credit\n\n 3. inspect this image with alt-txt\n\n 4. Python code\n\n 1. manage echo, run\n\n## Task: Edit a `.qmd` page\n\nTODO: Edit down to what we need.\n\nNow let's practice Markdown and commit an edit to this file.\n\nThis file is written in Markdown, which formats text on the web. To see the Markdown that results in the following formatting, click the pencil icon to edit, or click 'Raw' to inspect it. For example, with Markdown:\n\nWe can make words **bold** or *italic*.\n\n### We can make headers.\n\nWe can make lists – *note that lists need an empty line before list items!*\n\n1. bananas\n2. tamales\n3. cakes\n\nWe can make hyperlinks in [Markdown](https://quarto.org/docs/authoring/markdown-basics.html) using the `[]()` pattern: you put words to hyperlink in `[]` and the URL in `()`. For example:\n\n> [This twitter thread](https://twitter.com/allison_horst/status/1287772985630191617) describes the palmerpenguins R package. Learn more on the [palmerpenguins webpage](https://allisonhorst.github.io/palmerpenguins).\n\nWe can make an indented quote block with the `>` symbol, as in the example above.\n\nWe can include an image with the same `[]()` pattern, by adding a preceding exclamation point: `![]()`. For 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=\"250\"}](https://openscapes.org/)\n\n*Note how we can add alt text for the image, manage the image size, and link the image to a URL*\n\n:::{.callout-note}\nexample callout notes and their different types are so valuable\n:::\n\n\n\n## Running Code\n\nWhen you click the **Render** button a document will be generated that includes both content and the output of embedded code. You can embed code like this:\n\nYou can add options to executable code like this\n\nTODO: 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\nThe `echo: false` option disables the printing of code (only output is displayed).\n\n\nYour turn! Change or add something in Markdown and commit and push to GitHub.\n", + "supporting": [], + "filters": [ + "rmarkdown/pagebreak.lua" + ], + "includes": {}, + "engineDependencies": {}, + "preserve": {}, + "postProcess": true + } +} \ No newline at end of file diff --git a/_freeze/workflows/demo/execute-results/html.json b/_freeze/workflows/demo/execute-results/html.json new file mode 100644 index 0000000..93ae46f --- /dev/null +++ b/_freeze/workflows/demo/execute-results/html.json @@ -0,0 +1,15 @@ +{ + "hash": "e2b8dc7268110cabdbda0c461f5e0d75", + "result": { + "engine": "knitr", + "markdown": "---\ntitle: \"`demo.qmd` aka 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 an Python code chunks, Markdown-formatted text, and examples for adding images and hyperlinks.\n\nTODO: edit this file to contain the content listed below\n\n### Edit and preview a demo.qmd file\n\n1. Edit a .qmd page (uses demo.qmd file that has markdown for text, add hyperlink, add image, run Python code)\n\n 1. Headers\n\n 1. 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\n 2. hyperlink something (cite the Cookbook and hyperlink it)\n\n 1. Hyperlinking is done like this; lets you cite and give credit\n\n 3. inspect this image with alt-txt\n\n 4. Python code\n\n 1. manage echo, run\n\n## Task: Edit a `.qmd` page\n\nTODO: Edit down to what we need.\n\nNow let's practice Markdown and commit an edit to this file.\n\nThis file is written in Markdown, which formats text on the web. To see the Markdown that results in the following formatting, click the pencil icon to edit, or click 'Raw' to inspect it. For example, with Markdown:\n\nWe can make words **bold** or *italic*.\n\n### We can make headers.\n\nWe can make lists – *note that lists need an empty line before list items!*\n\n1. bananas\n2. tamales\n3. cakes\n\nWe can make hyperlinks in [Markdown](https://quarto.org/docs/authoring/markdown-basics.html) using the `[]()` pattern: you put words to hyperlink in `[]` and the URL in `()`. For example:\n\n> [This twitter thread](https://twitter.com/allison_horst/status/1287772985630191617) describes the palmerpenguins R package. Learn more on the [palmerpenguins webpage](https://allisonhorst.github.io/palmerpenguins).\n\nWe can make an indented quote block with the `>` symbol, as in the example above.\n\nWe can include an image with the same `[]()` pattern, by adding a preceding exclamation point: `![]()`. For 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=\"250\"}](https://openscapes.org/)\n\n*Note how we can add alt text for the image, manage the image size, and link the image to a URL*\n\n:::{.callout-note}\nexample callout notes and their different types are so valuable\n:::\n\n\n\n## Running Code\n\nWhen you click the **Render** button a document will be generated that includes both content and the output of embedded code. You can embed code like this:\n\nYou can add options to executable code like this\n\nTODO: 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\nThe `echo: false` option disables the printing of code (only output is displayed).\n\n\nYour turn! Change or add something in Markdown and commit and push to GitHub.\n", + "supporting": [], + "filters": [ + "rmarkdown/pagebreak.lua" + ], + "includes": {}, + "engineDependencies": {}, + "preserve": {}, + "postProcess": true + } +} \ No newline at end of file diff --git a/_quarto.yml b/_quarto.yml index 79bfee0..9969129 100644 --- a/_quarto.yml +++ b/_quarto.yml @@ -36,12 +36,17 @@ website: text: Welcome - href: explore.qmd text: Explore - - section: workflows/index.qmd + - section: lessons/index.qmd + text: Lessons contents: - - href: workflows/jupyter.qmd - text: From JupyterHub - - href: where-to-contribute.qmd - text: Where to Contribute + - href: lessons/part1-edit-quarto-site.qmd + text: Edit a Quarto site + - href: lessons/demo.qmd + text: Quarto practice file + - href: lessons/part2-share-via-github.qmd + text: Share via GitHub + - href: next-steps.qmd + text: Next Steps format: diff --git a/workflows/demo.qmd b/lessons/demo.qmd similarity index 66% rename from workflows/demo.qmd rename to lessons/demo.qmd index 208dbbb..44be909 100644 --- a/workflows/demo.qmd +++ b/lessons/demo.qmd @@ -2,32 +2,33 @@ title: "`demo.qmd` aka Quarto Practice" --- -Quarto enables you to weave together content and executable code into a finished document. +Quarto enables you to weave together content and executable code into a finished document. -This `demo.qmd` file has example R and python code chunks, Markdown-formatted text, and examples for adding images and hyperlinks. +This `demo.qmd` file has an Python code chunks, Markdown-formatted text, and examples for adding images and hyperlinks. -To learn more about Quarto see . +TODO: edit this file to contain the content listed below -## Running Code +### Edit and preview a demo.qmd file -When you click the **Render** button a document will be generated that includes both content and the output of embedded code. You can embed code like this: +1. Edit a .qmd page (uses demo.qmd file that has markdown for text, add hyperlink, add image, run Python code) -You can add options to executable code like this + 1. Headers -TODO: day before clinic, make this Python code (don't add screenshot - fewer files to for folks to get distracted with, lighter weight repo) + 1. 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 -```{r} -#| echo: false -2 * 2 -``` + 2. hyperlink something (cite the Cookbook and hyperlink it) + 1. Hyperlinking is done like this; lets you cite and give credit -The `echo: false` option disables the printing of code (only output is displayed). + 3. inspect this image with alt-txt + 4. Python code + + 1. manage echo, run ## Task: Edit a `.qmd` page -TODO: Edit down to what we need. +TODO: Edit down to what we need. Now let's practice Markdown and commit an edit to this file. @@ -53,7 +54,28 @@ We can include an image with the same `[]()` pattern, by adding a preceding excl [![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="250"}](https://openscapes.org/) -*Note how we can add alt text for the image, manage the image size, and link the image to a URL* +*Note how we can add alt text for the image, manage the image size, and link the image to a URL* + +:::{.callout-note} +example callout notes and their different types are so valuable +::: + + + +## Running Code + +When you click the **Render** button a document will be generated that includes both content and the output of embedded code. You can embed code like this: + +You can add options to executable code like this + +TODO: day before clinic, make this Python code (don't add screenshot - fewer files to for folks to get distracted with, lighter weight repo) + +```{r} +#| echo: false +2 * 2 +``` + +The `echo: false` option disables the printing of code (only output is displayed). -Your turn! Change or add something in Markdown and make another commit: write a human-readable commit message, and press the green button to commit changes. +Your turn! Change or add something in Markdown and commit and push to GitHub. diff --git a/workflows/images/github-commit.png b/lessons/images/github-commit.png similarity index 100% rename from workflows/images/github-commit.png rename to lessons/images/github-commit.png diff --git a/workflows/images/github-edit-index.png b/lessons/images/github-edit-index.png similarity index 100% rename from workflows/images/github-edit-index.png rename to lessons/images/github-edit-index.png diff --git a/workflows/images/github-preview-show-diff.png b/lessons/images/github-preview-show-diff.png similarity index 100% rename from workflows/images/github-preview-show-diff.png rename to lessons/images/github-preview-show-diff.png diff --git a/workflows/images/jupyter-execute-cell.png b/lessons/images/jupyter-execute-cell.png similarity index 100% rename from workflows/images/jupyter-execute-cell.png rename to lessons/images/jupyter-execute-cell.png diff --git a/workflows/images/jupyter-python-example.png b/lessons/images/jupyter-python-example.png similarity index 100% rename from workflows/images/jupyter-python-example.png rename to lessons/images/jupyter-python-example.png diff --git a/workflows/images/jupyter-raw-chunk.png b/lessons/images/jupyter-raw-chunk.png similarity index 100% rename from workflows/images/jupyter-raw-chunk.png rename to lessons/images/jupyter-raw-chunk.png diff --git a/workflows/images/jupyter-side-by-side.png b/lessons/images/jupyter-side-by-side.png similarity index 100% rename from workflows/images/jupyter-side-by-side.png rename to lessons/images/jupyter-side-by-side.png diff --git a/lessons/images/jupyterhub-2i2c-login.png b/lessons/images/jupyterhub-2i2c-login.png new file mode 100644 index 0000000..1227110 Binary files /dev/null and b/lessons/images/jupyterhub-2i2c-login.png differ diff --git a/lessons/images/jupyterhub-loading.png b/lessons/images/jupyterhub-loading.png new file mode 100644 index 0000000..db8aa1e Binary files /dev/null and b/lessons/images/jupyterhub-loading.png differ diff --git a/lessons/images/jupyterhub-server-options.png b/lessons/images/jupyterhub-server-options.png new file mode 100644 index 0000000..e802c6a Binary files /dev/null and b/lessons/images/jupyterhub-server-options.png differ diff --git a/lessons/images/jupyterhyb-clone-repo.png b/lessons/images/jupyterhyb-clone-repo.png new file mode 100644 index 0000000..5b954d1 Binary files /dev/null and b/lessons/images/jupyterhyb-clone-repo.png differ diff --git a/workflows/images/quarto-yml-site-side-by-side3.png b/lessons/images/quarto-yml-site-side-by-side3.png similarity index 100% rename from workflows/images/quarto-yml-site-side-by-side3.png rename to lessons/images/quarto-yml-site-side-by-side3.png diff --git a/workflows/images/rstudio-insert-image.png b/lessons/images/rstudio-insert-image.png similarity index 100% rename from workflows/images/rstudio-insert-image.png rename to lessons/images/rstudio-insert-image.png diff --git a/workflows/images/rstudio-orientation.png b/lessons/images/rstudio-orientation.png similarity index 100% rename from workflows/images/rstudio-orientation.png rename to lessons/images/rstudio-orientation.png diff --git a/workflows/images/rstudio-preview.png b/lessons/images/rstudio-preview.png similarity index 100% rename from workflows/images/rstudio-preview.png rename to lessons/images/rstudio-preview.png diff --git a/workflows/images/rstudio-source-editor.png b/lessons/images/rstudio-source-editor.png similarity index 100% rename from workflows/images/rstudio-source-editor.png rename to lessons/images/rstudio-source-editor.png diff --git a/workflows/images/rstudio-visual-edit-bar.png b/lessons/images/rstudio-visual-edit-bar.png similarity index 100% rename from workflows/images/rstudio-visual-edit-bar.png rename to lessons/images/rstudio-visual-edit-bar.png diff --git a/workflows/images/rstudio-visual-editor.png b/lessons/images/rstudio-visual-editor.png similarity index 100% rename from workflows/images/rstudio-visual-editor.png rename to lessons/images/rstudio-visual-editor.png diff --git a/workflows/index.qmd b/lessons/index.qmd similarity index 99% rename from workflows/index.qmd rename to lessons/index.qmd index 87812f3..ef6f146 100644 --- a/workflows/index.qmd +++ b/lessons/index.qmd @@ -1,5 +1,5 @@ --- -title: Workflows +title: Lessons --- ## Basic Workflow diff --git a/workflows/jupyter.qmd b/lessons/part1-edit-quarto-site.qmd similarity index 59% rename from workflows/jupyter.qmd rename to lessons/part1-edit-quarto-site.qmd index 01a2467..34935c8 100644 --- a/workflows/jupyter.qmd +++ b/lessons/part1-edit-quarto-site.qmd @@ -1,39 +1,61 @@ --- -title: From JupyterHub +title: "Part 1: Edit a Quarto site" --- -You can interact with Quarto through JupyterLab or JupyterHub. Your Jupyter setup will involve `.ipynb` notebooks and the command line. [Quarto's JupyterLab tutorials](https://quarto.org/docs/get-started/hello/jupyter.html) has great instructions on getting started with JupyterLab, including computations and authoring. +We will work through this Quarto Clinic site in the NASA Openscapes 2i2c JupyterHub ("the Hub"). The Hub has a python environment as well as Quarto installed. No further installations are required. -Here we will demonstrate how to work with this Quarto tutorial site in JupyterHub and add a Jupyter Notebook (`.ipynb` file). This example uses the NASA-Openscapes JupyterHub that already has all python environments as well as Quarto installed. +TODO: move Setup to setup.qmd. Add Setup after Welcome, then do Explore while Hub is initiating. Setup includes Hub login, clone, branch. Leave Preview in Edit Quarto site = step 1. ## Setup -TODO: add login to the Hub +TODO: Don't call this "Setup"; too vague. Decide if this file is just "demo 1" or all the content of Part 1 - demo and practice for: clone, branch, preview, make changes, add ipynb, edit \_quarto.yml, preview, END -### JupyterHub +### Log in to the Hub -Our JupyterHub is already setup with python environments as well as Quarto (through [nasa-openscapes/corn](https://github.com/nasa-openscapes/corn)), so there is no further installation required. +Go to the Hub https://openscapes.2i2c.cloud \> log in with your GitHub Account \> select the Python server. -### Clone your repo +[![Login page for the NASA Openscapes 2i2c JupyterHub, "the Hub"](images/jupyterhub-2i2c-login.png)](https://openscapes.2i2c.cloud/) -You'll start by cloning your repository into JupyterHub. +![Hub server options](images/jupyterhub-server-options.png) + +![](images/jupyterhub-loading.png) + +It takes a few minutes for the Hub to load. Please be patient! + +While the server starts up, we’ll explore the GitHub Clinic repo structure side by side with the website (go back to the [Explore](../explore.qmd) section). + +### Clone the Quarto Clinic repo + +You'll start by cloning your repository into the Hub. **Option A:** Use the Git tab to Clone repo -TODO: add screenshot from doc +![Clone a GitHub repository in the Hub](images/jupyterhyb-clone-repo.png) -**Option B:** Do this by opening a terminal (File > New > Terminal). In the Terminal, `git clone` your repository and `cd` into it: +**Option B:** Do this by opening a terminal (File \> New \> Terminal). In the Terminal, `git clone` your repository and `cd` into it: ``` bash git clone https://github.com/openscapes/quarto-clinic cd quarto-clinic ``` +### Make a branch +Working in a branch means you have your own version of the Quarto Clinic to edit and preview. Later, you might propose contributing your edits to the Main branch of the Clinic by making a "Pull Request". + +branch name = your name + +TODO screenshot and cmd line ## Preview the site (aka Quarto preview) -Let's start off by previewing our quarto site locally. In Terminal, type `quarto preview`, which will provide a URL with a preview of our site! +Let's start off by previewing our quarto site locally. + +quarto render does X + +quarto preview does Y + +In Terminal, type `quarto preview`, which will provide a URL with a preview of our site! ``` bash quarto preview @@ -50,19 +72,49 @@ TODO: add new screenshots Now that we have each set up our own GitHub clone of this Quarto Clinic website in the Openscapes 2i2c JupyterHub, we can practice editing and rendering `.qmd` and `ipynb` files. These are the workflows we use to contribute to the NASA Earthdata Cloud Cookbook and other Quarto websites and books. -### Make a small change and preview it +## Choose Task 1a or 1b (Activity) + +TODO: fill out Task 1a + +TODO: edit demo.md file to have only what we need + +### Task 1a: Edit and preview a demo.qmd file + +1. Edit a .qmd page (uses demo.qmd file that has markdown for text, add hyperlink, add image, run Python code) + + 1. Headers + + ``` + 1. 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 + ``` + + 2. hyperlink something (cite the Cookbook and hyperlink it) + + 1. Hyperlinking is done like this; lets you cite and give credit + + 3. inspect this image with alt-txt -TODO: move this below ipynb section? + 4. Python code + + 1. manage echo, run + +TODO: screenshot + +TODO: edit the text below re: "make a small change"; fix a typo + +#### Make a small change and preview it Now we'll be able to see live changes in the preview as we edit in our `.qmd` files. Let's try it: Change the date in `index.qmd` by opening it from the file directory. Change to today's date, and save. Your preview window will refresh automatically! If it does not, you can also refresh the page manually. The refreshed previewed site will now display your changes! -## Create a new `.ipynb` page +### Task 1b: Create a new `.ipynb` page + +Let's add a new page to our site. Instead of a `.qmd` file like the others, let's add a `.ipynb` file. -Let's add a new page to our site. Instead of an `.md` file like the others, let's add a `.ipynb` file. +File \> New \> Notebook. Accept the default kernel by clicking Select. -File > New > Notebook. Accept the default kernel by clicking Select. +TODO: screenshot -### First chunk: raw yaml +#### First chunk: raw yaml By default, this Notebook will give us a first chunk that is code. Let's change it to raw so that we can write our yaml at the top. @@ -76,7 +128,7 @@ title: Python Example --- ``` -### Second chunk: Markdown +#### Second chunk: Markdown Let's add a new chunk that is Markdown so we can write some description of what this page will be. @@ -84,13 +136,13 @@ Click the `+` symbol at the top of the document, and this will add a new chunk, Here, write a little bit of text in Markdown. Since your title is effectively a level-1 header, avoid using level-1 headers in the rest of your document. Here is some example text I wrote: -```bash +``` bash ## Introduction This example has some Python code that will be a part of our Quarto site. ``` -### Third chunk: Code +#### Third chunk: Code Now let's create a new chunk with the default Code setting. @@ -114,13 +166,17 @@ plt.show() Now, go ahead and execute this code chunk like you normally would, by clicking the cursor in a code block and clicking the sideways "play" triangle to run the selected cells (and advance to the next cell). This code produces a plot. -Note that the code runs as it normally would; the code options in the comments are just comments. +Note that the code runs as it normally would; the code options in the comments are just comments. -### Save your file +#### Save your file Save your document - I'll call mine `python-example.ipynb` in the main repository. -## Update `_quarto.yml` +## Preview your updates (Regroup, 10 min) + +**Demo**: If you created a new page, how do you get it in the book? Involves editing \_quarto.yml to have it show up in site + +### Update `_quarto.yml` Now we'll add `python-example.ipynb` to our `_quarto.yml` file; this is where we register of all files to include in our site. Let's add it after the section called "Basic Workflows". @@ -128,7 +184,7 @@ Open `_quarto.yml` by clicking on it from the file directory. Scroll down to review the current contents in the `sidebar:` section. It's there we see all the file arrangement that we see in the previewed site. -TODO: update screenshots and dont' use line # +TODO: update screenshots and dont' use line \# Add `- python-example.ipynb` to line 46, making sure that your indentation aligns with the other pages. @@ -136,14 +192,15 @@ Add `- python-example.ipynb` to line 46, making sure that your indentation align You'll see that our new page shows up in our Preview, and the code is executed since we did that in the Jupyter Notebook itself. By default, Quarto will not execute code chunks since your computations will likely become more complex and you will want to control when they are executed (or "run"). - Since Quarto is still previewing our website and the `python-example.ipynb`, the plot also displays in the notebook after the code is run and the file is saved, as shown below. ![](images/jupyter-execute-cell.png){fig-align="center"} So, your normal workflow for creating and running code blocks in your Jupyter Notebook is the same one you'll use as Quarto displays the preview. -## Quarto render +### Quarto render + +TODO: clarify preview vs render text So far we have used **Quarto preview** to view our website as we develop it. **Quarto render** will build the html elements of the website that we can see when we preview. Rendering will format the markdown text and code nicely as a website (or however is indicated in the `_quarto.yml`). @@ -162,24 +219,8 @@ cd quarto-website-tutorial quarto render python-example.ipynb --execute ``` -## Authoring tips +*TODO: move the below sections elsewhere. Here commit and push, then move to Part 2: Share via GitHub. I think the transition/ section break is when moving from JupyterHub to GitHub* -[Quarto.org](https://quarto.org) has details about authoring, including specific instructions about authoring in Jupyter: [quarto.org/docs/reference/cells/cells-jupyter](https://quarto.org/docs/reference/cells/cells-jupyter.html). - -## Commit and push! +## Commit and push to GitHub Committing and pushing will make the changes you see locally live on your website (using the [GitHub Action we set up earlier](/explore.qmd#setup-github-action)). - -## Troubleshooting - -### My changes don't show up in preview - -Make sure you've saved your file! There might be a slight delay depending on your JupyterHub/Lab setup. - -### Quarto render hangs / does not complete - -Check the specific notebook, are there any \`---\` throughout to denote line breaks rather than yaml? They might be causing the issue; consider deleting those. - -Also check how long the first raw cell is. Are there level-1 headers (`#`)? Try removing them. - - diff --git a/lessons/part2-share-via-github.qmd b/lessons/part2-share-via-github.qmd new file mode 100644 index 0000000..f4feb0d --- /dev/null +++ b/lessons/part2-share-via-github.qmd @@ -0,0 +1,5 @@ +--- +title: "Part 2: Share via GitHub" +--- + +Contribute your updates using GitHub diff --git a/next-steps.qmd b/next-steps.qmd new file mode 100644 index 0000000..bbcd3af --- /dev/null +++ b/next-steps.qmd @@ -0,0 +1,31 @@ +--- +title: Next Steps +--- + +## Troubleshooting + +### My changes don't show up in preview + +Make sure you've saved your file! There might be a slight delay depending on your JupyterHub setup. + +### Quarto render hangs / does not complete + +Check the specific notebook, are there any \`---\` throughout to denote line breaks rather than yaml? They might be causing the issue; consider deleting those. + +Also check how long the first raw cell is. Are there level-1 headers (`#`)? Try removing them. + +## Where to get help and learn more + +- + +- [A Quarto tip a day](https://mine-cetinkaya-rundel.github.io/quarto-tip-a-day/), by Mine Çetinkaya-Rundel, July 2022 + +## Where to contribute + +We can use these skills to contribute to many Quarto websites and books. + +- [NASA Earthdata Cloud Cookbook](https://nasa-openscapes.github.io/earthdata-cloud-cookbook/) +- [NASA Openscapes site](https://nasa-openscapes.github.io/) + - e.g. add a link to your slides or recording of a presentation +- [Openscapes Approach Guide](https://openscapes.github.io/approach-guide/) +- [Openscapes Champions Lessons Series](https://openscapes.github.io/series) diff --git a/where-to-contribute.qmd b/where-to-contribute.qmd deleted file mode 100644 index 956a060..0000000 --- a/where-to-contribute.qmd +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Where to contribute ---- - -We can use these skills to contribute to many Quarto websites and books. - -- [NASA Earthdata Cloud Cookbook](https://nasa-openscapes.github.io/earthdata-cloud-cookbook/) -- [NASA Openscapes site](https://nasa-openscapes.github.io/) -- [Openscapes Champions Lessons Series](https://openscapes.github.io/series) -- [Openscapes Approach Guide](https://openscapes.github.io/approach-guide/)