quarto-dev / quarto-dev/quarto-cli

profiles: What should happen with partial renders?

Open
#11,985 1 comment 1 reaction 1 assignee View on GitHub

@cscheid is already working on this.

Since Jan 29, 2025.

bug projects
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

From an exchange in our internal Slack

to me it’s simply wrong doing but here is an example:

$ quarto create project website
_quarto.yml
project:
  type: website

website:
  title: "demo"
  announcement: 
    icon: info-circle
    dismissable: true
    content: "**Alert** - this is some information that you should pay attention to"
    type: primary
  navbar:
    left:
      - text: Home
        href: index.html
      - text: About
        href: about.html
    right:
      - about.qmd
      - icon: github
        href: https://github.com/
      - icon: twitter
        href: https://twitter.com/
format:
  html:
    theme:
      - cosmo
      - brand
    css: styles.css
_quarto-preview.yml
project:
  type: website

website:
  title: "demo"
  announcement: 
    icon: info-circle
    dismissable: true
    content: "**Preview** "
    type: danger
  navbar:
    left:
      - text: Home
        href: index.html
format:
  html:
    theme:
      - vapor
      - brand
    css: styles.css

Then:

quarto render

quarto render index.qmd --profile preview

You get a “working” website.

You don’t get the “preview” navigation, the styling and the announcement bar.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.