Closed ghost closed 1 year ago
Thanks for tackling this issue!
It may be that the solution depends on whether we are dealing with on-premise Confluence vs Confluence Cloud?
Yes.
If so, is it possible to detect this, or have this as an additional option specified in yaml header?
I agree with you, but I'm afraid I don't have bandwidth to maintain both options...
Off-topic, I'm considering archiving this package because it seems Quarto is serious about supporting Confluence. I'm not sure how mature the implementation is at the moment, but it looks promising.
https://github.com/quarto-dev/quarto-cli/tree/main/src/resources/extensions/quarto/confluence https://github.com/quarto-dev/quarto-cli/tree/main/src/publish/confluence
OK. Thanks anyway. I'll keep this fork till we can transition to quarto.
Attempt to resolve #152
It may be that the solution depends on whether we are dealing with on-premise Confluence vs Confluence Cloud? If so, is it possible to detect this, or have this as an additional option specified in yaml header?