Skip to content

pdf accessibility blog post#1934

Merged
gordonwoodhull merged 9 commits intomainfrom
blog/pdf-a11y
Mar 5, 2026
Merged

pdf accessibility blog post#1934
gordonwoodhull merged 9 commits intomainfrom
blog/pdf-a11y

Conversation

@gordonwoodhull
Copy link
Collaborator

This replaces #1898

Blog post now destined for main, using meta shortcode to point to prerelease docs for now.

cc @cwickham

@github-actions github-actions bot temporarily deployed to pull request March 4, 2026 17:18 Inactive
@github-actions
Copy link
Contributor

github-actions bot commented Mar 4, 2026

📝 Preview Deployment

🔍 Full site preview: https://deploy-preview-1934.quarto.org

🔄 Modified Documents

@github-actions github-actions bot temporarily deployed to pull request March 4, 2026 17:33 Inactive
@github-actions
Copy link
Contributor

github-actions bot commented Mar 4, 2026

📝 Preview Deployment

🔍 Full site preview: https://deploy-preview-1934.quarto.org

🔄 Modified Documents

@cderv
Copy link
Collaborator

cderv commented Mar 4, 2026

I think I can tweak current improvement of #1932 I am doing to handle this use case.

We currently have {{< meta prerelease-subdomain >}} to be able to have link in doc inside prerelease branch to have links using prerelease.quarto.org while they will have quarto.org only when prerelease will be merged in main, without us doing anything in each file.

So I think we can come up with something similar here to have

  • doc in main being able to point to prerelease.quarto.org when for example rc profile is on
  • and then point to quarto.org when rc switch back to second profile.

I believe that would work if we want to avoid modifying the blog post YAML when making the merge of prerelease into main. And avoid forgetting to do it.

What do think @cwickham ?

@cwickham
Copy link
Collaborator

cwickham commented Mar 4, 2026

@cderv Yes, that sounds like a great idea. I like tying it to rc, that seems like the period we are likely to make these "coming soon" blog posts.

@github-actions github-actions bot temporarily deployed to pull request March 4, 2026 19:00 Inactive
@github-actions
Copy link
Contributor

github-actions bot commented Mar 4, 2026

📝 Preview Deployment

🔍 Full site preview: https://deploy-preview-1934.quarto.org

🔄 Modified Documents

@github-actions github-actions bot temporarily deployed to pull request March 4, 2026 19:24 Inactive
@github-actions
Copy link
Contributor

github-actions bot commented Mar 4, 2026

📝 Preview Deployment

🔍 Full site preview: https://deploy-preview-1934.quarto.org

🔄 Modified Documents

@cderv
Copy link
Collaborator

cderv commented Mar 4, 2026

@gordonwoodhull I added a meta to help in #1932

[PDF Accessibility](https://{{< meta prerelease-link-subdomain >}}quarto.org/docs/output-formats/pdf-accessibility.html)

I'll merge before this PR.

Also your last commit 5afe467 (this PR) makes me realize that we could also find a way to use some prerelease-aware meta to conditionnaly include the prerelease feature include file. Currently, it exists on prerelease but is empty on main.

::: {.callout-note}
## Pre-release Feature
This feature is new in the upcoming Quarto 1.9 release. To use the feature now, you'll need to [download](/docs/download/prerelease.qmd) and install the Quarto pre-release.
:::

https://github.com/quarto-dev/quarto-web/blob/41e5f27285e54d01be787416992d90ab1c34eac8/docs/prerelease/1.9/_pre-release-feature.qmd

I think we could avoid that - again to minimize what needs to be modified when docs is out.

@cderv
Copy link
Collaborator

cderv commented Mar 4, 2026

I merged it so you should be able to try it if you rebase on main

@github-actions github-actions bot temporarily deployed to pull request March 4, 2026 20:27 Inactive
@github-actions
Copy link
Contributor

github-actions bot commented Mar 4, 2026

📝 Preview Deployment

🔍 Full site preview: https://deploy-preview-1934.quarto.org

🔄 Modified Documents

@github-actions github-actions bot temporarily deployed to pull request March 4, 2026 20:46 Inactive
@github-actions
Copy link
Contributor

github-actions bot commented Mar 4, 2026

📝 Preview Deployment

🔍 Full site preview: https://deploy-preview-1934.quarto.org

🔄 Modified Documents

@github-actions github-actions bot temporarily deployed to pull request March 4, 2026 20:57 Inactive
@github-actions
Copy link
Contributor

github-actions bot commented Mar 4, 2026

📝 Preview Deployment

🔍 Full site preview: https://deploy-preview-1934.quarto.org

🔄 Modified Documents

Co-authored-by: Charlotte Wickham <charlotte.wickham@posit.co>
@github-actions github-actions bot temporarily deployed to pull request March 4, 2026 21:20 Inactive
@github-actions
Copy link
Contributor

github-actions bot commented Mar 4, 2026

📝 Preview Deployment

🔍 Full site preview: https://deploy-preview-1934.quarto.org

🔄 Modified Documents

cderv added a commit to cderv/quarto-web that referenced this pull request Mar 5, 2026
The `prerelease-link-subdomain` variable is phase-aware but not
version-aware — on the next RC cycle, old blog posts would incorrectly
point to prerelease.quarto.org even though those docs already moved
to quarto.org.

Add a `prerelease-docs-url` shortcode extension that compares a
version argument against the `version` key in `_quarto.yml` to decide
whether docs live on quarto.org or prerelease.quarto.org. On the
prerelease site (prerelease-docs profile), it always returns
"prerelease." regardless of version.

Follow-up to quarto-dev#1932, relates to quarto-dev#1934.
@gordonwoodhull gordonwoodhull merged commit 3bc2286 into main Mar 5, 2026
4 checks passed
@gordonwoodhull gordonwoodhull deleted the blog/pdf-a11y branch March 5, 2026 14:30
@github-actions
Copy link
Contributor

github-actions bot commented Mar 5, 2026

Successfully created backport PR for prerelease:

cderv added a commit that referenced this pull request Mar 5, 2026
The `prerelease-link-subdomain` variable is phase-aware but not
version-aware — on the next RC cycle, old blog posts would incorrectly
point to prerelease.quarto.org even though those docs already moved
to quarto.org.

Add a `prerelease-docs-url` shortcode extension that compares a
version argument against the `version` key in `_quarto.yml` to decide
whether docs live on quarto.org or prerelease.quarto.org. On the
prerelease site (prerelease-docs profile), it always returns
"prerelease." regardless of version.

Follow-up to #1932, relates to #1934.
cderv added a commit that referenced this pull request Mar 6, 2026
* Replace prerelease-link-subdomain with version-aware shortcode

The `prerelease-link-subdomain` variable is phase-aware but not
version-aware — on the next RC cycle, old blog posts would incorrectly
point to prerelease.quarto.org even though those docs already moved
to quarto.org.

Add a `prerelease-docs-url` shortcode extension that compares a
version argument against the `version` key in `_quarto.yml` to decide
whether docs live on quarto.org or prerelease.quarto.org. On the
prerelease site (prerelease-docs profile), it always returns
"prerelease." regardless of version.

Follow-up to #1932, relates to #1934.

* Update PDF accessibility blog post to use prerelease-docs-url shortcode
github-actions bot pushed a commit that referenced this pull request Mar 6, 2026
* Replace prerelease-link-subdomain with version-aware shortcode

The `prerelease-link-subdomain` variable is phase-aware but not
version-aware — on the next RC cycle, old blog posts would incorrectly
point to prerelease.quarto.org even though those docs already moved
to quarto.org.

Add a `prerelease-docs-url` shortcode extension that compares a
version argument against the `version` key in `_quarto.yml` to decide
whether docs live on quarto.org or prerelease.quarto.org. On the
prerelease site (prerelease-docs profile), it always returns
"prerelease." regardless of version.

Follow-up to #1932, relates to #1934.

* Update PDF accessibility blog post to use prerelease-docs-url shortcode

(cherry picked from commit 63a21f0)
cderv added a commit that referenced this pull request Mar 6, 2026
* Replace prerelease-link-subdomain with version-aware shortcode

The `prerelease-link-subdomain` variable is phase-aware but not
version-aware — on the next RC cycle, old blog posts would incorrectly
point to prerelease.quarto.org even though those docs already moved
to quarto.org.

Add a `prerelease-docs-url` shortcode extension that compares a
version argument against the `version` key in `_quarto.yml` to decide
whether docs live on quarto.org or prerelease.quarto.org. On the
prerelease site (prerelease-docs profile), it always returns
"prerelease." regardless of version.

Follow-up to #1932, relates to #1934.

* Update PDF accessibility blog post to use prerelease-docs-url shortcode

(cherry picked from commit 63a21f0)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants