quarto-dev / quarto-dev/quarto-cli

sitemap.xml generation incorrect date?

Open
#3,251 5 comments 2 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

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

Description

Bug description

When I use the command 'quarto publish' every post/page is recreated/updated in html, regardless of whether the page/content changed or not.

  • Is this the correct/expected behavior?

image

using the above method, dates on the sitemap are not reflecting when the content was most changed

  • how do you publish updates to some pages but not all pages (i.e. so the sitemap and dates are correct)?

another scenerio is you might change or remove a category on one page, quarto publish would regenerate every since post page and the sitemap. the underlying content technically didn't change on the pages, only meta-data displayed in one page

  • why does this scenario record that the page/post content change for every page?

it seems that sitemap updated dates should relate to content, not navigation/meta-data ?

Thanks

Tom

vscode+extension
windows 11
github/actions

Checklist
  • Please include a minimal, fully reproducible example in a single .qmd file? Please provide the whole file rather than the snippet you believe is causing the issue.
  • Please format your issue so it is easier for us to read the bug report.
  • Please document the RStudio IDE version you're running (if applicable), by providing the value displayed in the "About RStudio" main menu dialog?
  • Please document the operating system you're running. If on Linux, please provide the specific distribution.

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.