quarto-dev / quarto-dev/quarto-cli
Confluence, Only Publish Changed
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
Description: When publishing Confluence sites, only published changed documents.
Steps to Reproduce:
- Create a Confluence site
- Publish to Confluence
- Notice all pages are published
- Make one edit on a single document
- Publish to Confluence
Desired Result:
- Only one page is published.
Actual Result:
- The entire site is re-published
As posted here: https://github.com/quarto-dev/quarto-web/discussions/673#discussioncomment-6006768
"One question/feature request: Can I publish the minimal changes possible? For example, if I have 200 documents already published in Confluence using Quarto and I need to add one more, can I just publish that one document without having to re-render and publish all of them again?
For example, I have Confluence integration with Slack, and every time I publish, I get notifications for all documents..."
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Confluence publishing flow described here: publish a site, change one document, and publish again. Trace the publishing entry point and determine how changed documents are identified; done means a single changed page is published without republishing the entire site.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100