Open
Conversation
(cherry picked from commit 8151bff)
(cherry picked from commit 97c164d)
* axe-check docs * darkmode tweaks * gitignore (cherry picked from commit e5ab976)
(cherry picked from commit eac74d6)
(cherry picked from commit 1c279a0)
Co-authored-by: Charlotte Wickham <charlotte.wickham@posit.co> (cherry picked from commit 060c968)
Co-authored-by: Charlotte Wickham <charlotte.wickham@posit.co> (cherry picked from commit 578612c)
(cherry picked from commit a191633)
(cherry picked from commit 0e9318d)
(cherry picked from commit b69b809)
In HTML dependencies section, the description of `link` has a typo where `ref` is written instead of `href` (cherry picked from commit 0aeac93)
* Remove `posit-cloud` as a publishing venue * Link to other venues * Remove from 1.4 sidebar too (cherry picked from commit c3d19c6) Co-authored-by: Charlotte Wickham <charlotte.wickham@posit.co>
* document q.metadata and q.variables * Update docs/extensions/lua-api.qmd Co-authored-by: Charlotte Wickham <charlotte.wickham@posit.co> * Update docs/extensions/lua-api.qmd Co-authored-by: Charlotte Wickham <charlotte.wickham@posit.co> * Update docs/extensions/lua-api.qmd Co-authored-by: Charlotte Wickham <charlotte.wickham@posit.co> --------- Co-authored-by: Charlotte Wickham <charlotte.wickham@posit.co> (cherry picked from commit dd9d840)
* QUARTO_EXECUTE_INFO documentation * remove some lines * Update docs/advanced/quarto-execute-info.qmd Co-authored-by: Charlotte Wickham <charlotte.wickham@posit.co> * Update docs/advanced/environment-vars.qmd Co-authored-by: Charlotte Wickham <charlotte.wickham@posit.co> * Update docs/advanced/quarto-execute-info.qmd Co-authored-by: Charlotte Wickham <charlotte.wickham@posit.co> * change to base_format, use fallthrough * add link to table content --------- Co-authored-by: Charlotte Wickham <charlotte.wickham@posit.co>
(cherry picked from commit 5bf9205)
Added a new Quarto extension for collapsing code cell outputs. (cherry picked from commit 9209760)
(cherry picked from commit 4a2fd16)
Use the correct prerelease feature include path /docs/prerelease/1.9/_pre-release-feature.qmd instead of the non-standard /docs/_require-1.9.qmd pattern. Delete the empty _require-1.9.qmd file that was added in error. Addresses PR review feedback from @cderv. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Reorder sections in book-output.qmd so LaTeX Output appears before Typst Output, maintaining consistency with the established format ordering in the documentation. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Change "brand system" to "_brand.yml" when referring to brand integration, following documentation conventions where _brand.yml refers to the actual file users create in their projects. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Change "brand system" to "_brand.yml" and fix "colors and logos" to "color and logo" to match the actual _brand.yml schema. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add Netlify redirect for veraPDF downloads Introduce netlify.toml with a :version/* wildcard redirect pointing to versioned veraPDF files on S3. This provides a stable, version-agnostic download URL for quarto-cli while allowing server-side version control. Include netlify.toml in Quarto resources so it is copied to _site/. (cherry picked from commit a074e90)
follow up on e6c7bea for documenting engine extension.
(cherry picked from commit a076872)
…1874) * syntax-highlighting is the new settings now * Add a conditional to add precision about main document option this is needed when we need to add some specific for a format while keeping the same global include for all doc * Update doc for reveal regarding syntax-highlighting * fix - fig-alt with a - * highlighting - add missing supported a11y them to the doc * Add callout for Typst default highlighting change in 1.9 Previously Typst used its own native code highlighting. Starting with 1.9, it uses Pandoc Skylighting by default (same as HTML/LaTeX). The old behavior is available via syntax-highlighting: idiomatic. * renv - colorspace is needed to gt-temps.qmd example * knitr - Re-render some output-formats example with gt
Update diagrams.qmd Chrome Install section to recommend chrome-headless-shell over legacy chromium. Update QUARTO_CHROMIUM env var description with browser discovery priority order. CLI reference docs will be regenerated from next prerelease build. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* add fansi R to run tools/reference-cli-generate-md.R * docs: Document chrome-headless-shell as primary browser install Update diagrams.qmd Chrome Install section to recommend chrome-headless-shell over legacy chromium. Update QUARTO_CHROMIUM env var description with browser discovery priority order. CLI reference docs will be regenerated from next prerelease build. * Mark `quarto install chrome-headless-shell` as 1.9 feature
Add Posit Connect Cloud publishing documentation
* Match structure of list to headings
* Tweaks
* Put Posit Connct Cloud first in publisher list and move Quarto Pub
This will prepare for the idea of migrating from one service to the other
* Use include for publish command to avoid duplication and easier maintainance
* Use shared include for publish command documentation
Posit Connect Cloud documentation now uses `_publish-command.md` include for consistency with Netlify and Quarto Pub.
This change was done including following improvements
- Refactor `_publish-command.md` to use nested metadata structure:
- `provider.id`, `provider.name`, `provider.publish-url`
- `provider.authorization.enabled`, `.description`, `.prompt`
- Add conditional authorization section using `when-meta="provider.authorization.enabled"`
- Update Netlify and Quarto Pub metadata to match nested structure
- Remove generic "Multiple Accounts" section from include (too provider-specific)
Each provider now handles account management documentation in its own way while
sharing the core publish command flow.
* Use new provider metadata schema
* Standardize provider metadata structure in publishing docs
Migrate provider documentation to use consistent nested YAML structure:
- Convert confluence.qmd, hugging-face.qmd, and github-pages.qmd from flat structure (provider: value, provider-name: value) to nested structure (provider.id, provider.name)
- Update _github-action-basics.md and _github-action-options.md to reference {{< meta provider.id >}} instead of {{< meta provider >}}
This enables consistent content reuse via metadata references across all provider documentation pages.
* Remove unused token metadata from provider frontmatter
The token field in netlify.qmd and github-pages.qmd has been unused since July 2022.
History:
- 3555fca (Jul 5, 2022): Added provider-token with {{< meta provider-token >}} usage in _github-action-executing-code.md
- 2337ba6 (Jul 7, 2022): Removed {{< meta provider-token >}} usage from _github-action-executing-code.md
The token field was never dynamically substituted into content after its usage was removed. Token names are hardcoded directly in GitHub Action examples.
* Change `provider` to `provider.id`
---------
Co-authored-by: Christophe Dervieux <christophe.dervieux@gmail.com>
Documents list table syntax including alignment, column widths, header rows, captions, cross-references, and complex cell content. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This reverts commit 56a2efa.
Split the standards table into format-specific versions using content-visible so each page only shows relevant standards, and remove the now-unnecessary Format Support column. Add document metadata bullet to accessibility section. Split document tagging bullet into format-specific content. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
12 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #1891