Prerelease

.github/workflows/actions/release-info/action.yml

@@ -27,5 +27,5 @@ inputs:
     required: true
 
 runs:
-  using: "node16"
+  using: "node20"
   main: "index.js"

.github/workflows/preview.yml

@@ -8,8 +8,9 @@ name: Deploy Preview
 
 concurrency:
   # Use github.event.pull_request.number on pull requests, so it's unique per pull request
+  # Use github.event.issue.number on issue comments, so it's unique per comment
   # Use github.ref on other branches, so it's unique per branch
-  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.event.issue.number || github.ref }}
+  group: ${{ github.workflow }}-${{ (github.event.pull_request && format('PR-{0}', github.event.pull_request.number)) || ( github.event.issue && format('comment-{0}', github.event.issue.number) ) || github.ref }}
   cancel-in-progress: true
 
 jobs:

.github/workflows/publish.yml

@@ -47,14 +47,16 @@ jobs:
       - name: Render 
         uses: quarto-dev/quarto-actions/render@v2
         env:
-          QUARTO_PROFILE: ${{ (inputs.prerelease == 'true' || (contains(fromJSON('["push", "workflow_dispatch"]'), github.event_name) && github.ref == 'refs/heads/prerelease')) && 'prerelease-docs' || '' }}
+          QUARTO_PROFILE: ${{ (inputs.prerelease || (contains(fromJSON('["push", "workflow_dispatch"]'), github.event_name) && github.ref == 'refs/heads/prerelease')) && 'prerelease-docs' || '' }}
 
       - name: Publish release website
         # Only do this step if 
         # - workflow is called for release deploy, with inputs.prerelease being false. It should not trigger if inputs.prerelease is null.
         #   and in GHA null == false is true. That is why we convert to string and compare.
         # - workflow is triggered by push event on main branch
-        if: ${{ format('{0}', inputs.prerelease) == 'false' || (contains(fromJSON('["push", "workflow_dispatch"]'), github.event_name) && github.ref == 'refs/heads/main') }}
+        # - workflow is triggered by workflow_dispatch event 
+        #   (we need to protect also from workflow_dispatch inherited from workflow_call event - where inputs.prerelease is defined)
+        if: ${{ format('{0}', inputs.prerelease) == 'false' || (!inputs.prerelease && contains(fromJSON('["push", "workflow_dispatch"]'), github.event_name) && github.ref == 'refs/heads/main') }}
         uses: quarto-dev/quarto-actions/publish@v2
         with:
           target: netlify
@@ -66,7 +68,9 @@ jobs:
         # - workflow is called for release deploy with inputs.prerelease being true. It should not trigger if inputs.prerelease is null.
         #   Though as in GHA null means false, no need to cast to string
         # - workflow is triggered by push event on main branch
-        if: ${{ inputs.prerelease || (contains(fromJSON('["push", "workflow_dispatch"]'), github.event_name) && github.ref == 'refs/heads/prerelease') }}
+        # - workflow is triggered by workflow_dispatch event 
+        #   (we need to protect also from workflow_dispatch inherited from workflow_call event - where inputs.prerelease is defined)
+        if: ${{ inputs.prerelease || (format('{0}', inputs.prerelease) != 'false' && contains(fromJSON('["push", "workflow_dispatch"]'), github.event_name) && github.ref == 'refs/heads/prerelease') }}
         id: netlify-deploy
         uses: nwtgck/actions-netlify@v3
         env:

.github/workflows/upload-algolia.rb

@@ -1,3 +1,4 @@
+gem 'algolia', '=2.3.4'
 require 'json'
 require 'algolia'
 require 'open-uri'

.github/workflows/upload-index.yml

@@ -17,7 +17,7 @@ jobs:
           ruby-version: 3.0.2
       - name: Install Algolia API Dependencies
         run: |
-          gem install algolia
+          gem install algolia -v 2.3.4
       - name: Upload Index for release website
         run: |
           pwd

DESCRIPTION

@@ -11,6 +11,7 @@ Depends:
     htmltools,
     knitr,
     leaflet,
+    magick,
     openintro,
     palmerpenguins,
     readr,

_freeze/docs/blog/posts/2022-02-17-advanced-layout/index/execute-results/html.json

@@ -1,7 +1,8 @@
 {
-  "hash": "8a1317ba31af020c6b35bf3c53f60b5c",
+  "hash": "050f4857f79b6ad8db96b5cb0e3a9f1b",
   "result": {
-    "markdown": "---\ntitle: Positioning Content in the Margin\nsubtitle: Create 'Tufte' style documents with sidenotes, margin tables and figures, and other margin content\ndescription: |\n  This post demonstrates a few of the capabilities for positioning content in the margin of the page. You can read more about the complete capabilities in the the [Article Layout Guide](/docs/authoring/article-layout.qmd).\nauthor: Charles Teague\ndate: 2/17/2022\ncategories:\n  - Features\n  - Layout\nimage: margin-content.png\nimage-alt: \"Screenshot of two sections of post: Margin Figures, which has a plot in the margin; and Arbitrary Margin Content, which has text with a LaTeX equation in the margin.\"\nreference-location: margin\ncitation-location: margin\n---\n\n\nQuarto supports a variety of page layout options that enable you to author content that\n\n-   Fills the main content region\n-   Overflows the content region\n-   Spans the entire page\n-   Occupies the document margin\n\nThis post will demonstrate a few of the capabilities for positioning content in the margin of the page. You can read more about the complete capabilities in the the [Article Layout Guide](/docs/authoring/article-layout.qmd).\\\n\n## Margin Figures\n\nFigures that you create using code cells can be placed in the margin by using the `column: margin` code cell option. If the code produces more than one figure, each of the figures will be placed in the margin.\n\n\n::: {.cell .column-margin}\n\n````{.cell-code}\n```{{r}}\n#| label: fig-mtcars\n#| fig-cap: \"MPG vs horsepower, colored by transmission.\"\n#| column: margin\n\nlibrary(ggplot2)\nmtcars2 <- mtcars\nmtcars2$am <- factor(\n  mtcars$am, labels = c('automatic', 'manual')\n)\nggplot(mtcars2, aes(hp, mpg, color = am)) +\n  geom_point() +  geom_smooth(formula = y ~ x, method = \"loess\") +\n  theme(legend.position = 'bottom')\n```\n````\n\n::: {.cell-output-display}\n![MPG vs horsepower, colored by transmission.](index_files/figure-html/fig-mtcars-1.png){#fig-mtcars width=672}\n:::\n:::\n\n\n## Margin Tables\n\nYou an also place tables in the margin of your document by specifying `column: margin`.\n\n\n::: {.cell .column-margin}\n\n````{.cell-code}\n```{{r}}\n#| column: margin\n\nknitr::kable(\n  mtcars[1:3, 1:3]\n)\n```\n````\n\n::: {.cell-output-display}\n|              |  mpg| cyl| disp|\n|:-------------|----:|---:|----:|\n|Mazda RX4     | 21.0|   6|  160|\n|Mazda RX4 Wag | 21.0|   6|  160|\n|Datsun 710    | 22.8|   4|  108|\n:::\n:::\n\n\n## Other Content\n\nYou can also place content in the margin by targeting the margin column using a div with the .`column-margin` class. For example:\n\n``` md\n::: {.column-margin}\nWe know from *the first fundamental theorem of calculus* that for $x$ in $[a, b]$:\n\n\n$$\\frac{d}{dx}\\left( \\int_{a}^{x} f(u)\\,du\\right)=f(x).$$\n\n:::\n```\n\n::: column-margin\nWe know from *the first fundamental theorem of calculus* that for $x$ in $[a, b]$:\n\n\n$$\\frac{d}{dx}\\left( \\int_{a}^{x} f(u)\\,du\\right)=f(x).$$\n\n:::\n\n## Margin References\n\nFootnotes and the bibliography typically appear at the end of the document, but you can choose to have them placed in the margin by setting the following option\\[\\^1\\] in the document front matter:\n\n``` yaml\n---\nreference-location: margin\ncitation-location: margin\n---\n```\n\nWith these options set, footnotes and citations will (respectively) be automatically be placed in the margin of the document rather than the bottom of the page. As an example, when I cite @xie2018, the citation bibliography entry itself will now appear in the margin.\n\n### Asides\n\nAsides allow you to place content aside from the content it is placed in. Asides look like footnotes, but do not include the footnote mark (the superscript number). [This is a span that has the class `aside` which places it in the margin without a footnote number.]{.aside}\n\n``` markdown\n[This is a span that has the class aside which places it in the margin without a footnote number.]{.aside}\n```\n\n## Margin Captions\n\nFor figures and tables, you may leave the content in the body of the document while placing the caption in the margin of the document. Using `cap-location: margin` in a code cell or document front matter to control this. For example:\n\n\n::: {.cell .caption-margin}\n\n````{.cell-code}\n```{{r}}\n#| label: fig-cap-margin\n#| fig-cap: \"MPG vs horsepower, colored by transmission.\"\n#| cap-location: margin\n\nlibrary(ggplot2)\nmtcars2 <- mtcars\nmtcars2$am <- factor(\n  mtcars$am, labels = c('automatic', 'manual')\n)\nggplot(mtcars2, aes(hp, mpg, color = am)) +\n  geom_point() +  geom_smooth(formula = y ~ x, method = \"loess\") +\n  theme(legend.position = 'bottom')\n```\n````\n\n::: {.cell-output-display}\n![MPG vs horsepower, colored by transmission.](index_files/figure-html/fig-cap-margin-1.png){#fig-cap-margin width=672}\n:::\n:::\n",
+    "engine": "knitr",
+    "markdown": "---\ntitle: Positioning Content in the Margin\nsubtitle: Create 'Tufte' style documents with sidenotes, margin tables and figures, and other margin content\ndescription: |\n  This post demonstrates a few of the capabilities for positioning content in the margin of the page. You can read more about the complete capabilities in the [Article Layout Guide](/docs/authoring/article-layout.qmd).\nauthor: Charles Teague\ndate: \"2/17/2022\"\ncategories:\n  - Features\n  - Layout\nimage: margin-content.png\nimage-alt: \"Screenshot of two sections of post: Margin Figures, which has a plot in the margin; and Arbitrary Margin Content, which has text with a LaTeX equation in the margin.\"\nreference-location: margin\ncitation-location: margin\n---\n\n\n\nQuarto supports a variety of page layout options that enable you to author content that\n\n-   Fills the main content region\n-   Overflows the content region\n-   Spans the entire page\n-   Occupies the document margin\n\nThis post will demonstrate a few of the capabilities for positioning content in the margin of the page. You can read more about the complete capabilities in the [Article Layout Guide](/docs/authoring/article-layout.qmd).\\\n\n## Margin Figures\n\nFigures that you create using code cells can be placed in the margin by using the `column: margin` code cell option. If the code produces more than one figure, each of the figures will be placed in the margin.\n\n\n\n::: {.cell .column-margin}\n\n````{.cell-code}\n```{{r}}\n#| label: fig-mtcars\n#| fig-cap: \"MPG vs horsepower, colored by transmission.\"\n#| column: margin\n\nlibrary(ggplot2)\nmtcars2 <- mtcars\nmtcars2$am <- factor(\n  mtcars$am, labels = c('automatic', 'manual')\n)\nggplot(mtcars2, aes(hp, mpg, color = am)) +\n  geom_point() +\n  geom_smooth(formula = y ~ x, method = \"loess\") +\n  theme(legend.position = 'bottom')\n```\n````\n\n::: {.cell-output-display}\n![MPG vs horsepower, colored by transmission.](index_files/figure-html/fig-mtcars-1.png){#fig-mtcars width=672}\n:::\n:::\n\n\n\n## Margin Tables\n\nYou an also place tables in the margin of your document by specifying `column: margin`.\n\n\n\n::: {.cell .column-margin}\n\n````{.cell-code}\n```{{r}}\n#| column: margin\n\nknitr::kable(\n  mtcars[1:3, 1:3]\n)\n```\n````\n\n::: {.cell-output-display}\n\n\n|              |  mpg| cyl| disp|\n|:-------------|----:|---:|----:|\n|Mazda RX4     | 21.0|   6|  160|\n|Mazda RX4 Wag | 21.0|   6|  160|\n|Datsun 710    | 22.8|   4|  108|\n\n\n:::\n:::\n\n\n\n## Other Content\n\nYou can also place content in the margin by targeting the margin column using a div with the .`column-margin` class. For example:\n\n``` md\n::: {.column-margin}\nWe know from *the first fundamental theorem of calculus* that for $x$ in $[a, b]$:\n\n$$\\frac{d}{dx}\\left( \\int_{a}^{x} f(u)\\,du\\right)=f(x).$$\n:::\n```\n\n::: column-margin\nWe know from *the first fundamental theorem of calculus* that for $x$ in $[a, b]$:\n\n$$\\frac{d}{dx}\\left( \\int_{a}^{x} f(u)\\,du\\right)=f(x).$$\n:::\n\n## Margin References\n\nFootnotes and the bibliography typically appear at the end of the document, but you can choose to have them placed in the margin by setting the following option\\[\\^1\\] in the document front matter:\n\n``` yaml\n---\nreference-location: margin\ncitation-location: margin\n---\n```\n\nWith these options set, footnotes and citations will (respectively) be automatically be placed in the margin of the document rather than the bottom of the page. As an example, when I cite @xie2018, the citation bibliography entry itself will now appear in the margin.\n\n### Asides\n\nAsides allow you to place content aside from the content it is placed in. Asides look like footnotes, but do not include the footnote mark (the superscript number). [This is a span that has the class `aside` which places it in the margin without a footnote number.]{.aside}\n\n``` markdown\n[This is a span that has the class aside which places it in the margin without a footnote number.]{.aside}\n```\n\n## Margin Captions\n\nFor figures and tables, you may leave the content in the body of the document while placing the caption in the margin of the document. Using `cap-location: margin` in a code cell or document front matter to control this. For example:\n\n\n\n::: {.cell .caption-margin}\n\n````{.cell-code}\n```{{r}}\n#| label: fig-cap-margin\n#| fig-cap: \"MPG vs horsepower, colored by transmission.\"\n#| cap-location: margin\n\nlibrary(ggplot2)\nmtcars2 <- mtcars\nmtcars2$am <- factor(\n  mtcars$am, labels = c('automatic', 'manual')\n)\nggplot(mtcars2, aes(hp, mpg, color = am)) +\n  geom_point() +\n  geom_smooth(formula = y ~ x, method = \"loess\") +\n  theme(legend.position = 'bottom')\n```\n````\n\n::: {.cell-output-display}\n![MPG vs horsepower, colored by transmission.](index_files/figure-html/fig-cap-margin-1.png){#fig-cap-margin width=672}\n:::\n:::\n",
     "supporting": [
       "index_files"
     ],