Conversation
📝 Preview Deployment🔍 Full site preview: https://deploy-preview-1879.quarto.org 🔄 Modified Documents |
|
Thanks for the review !!
My experience is that we definitely to work on adding some Happy to discuss that with you @cwickham ! |
This will prepare for the idea of migrating from one service to the other
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.
cderv
left a comment
cderv
left a comment
There was a problem hiding this comment.
I made a few changes as I agree with all your comments. This improve the usability of the include by leveraging when-meta
If you think this is too complex, feel free to amend and then merge
📝 Preview Deployment🔍 Full site preview: https://deploy-preview-1879.quarto.org 🔄 Modified Documents |
📝 Preview Deployment🔍 Full site preview: https://deploy-preview-1879.quarto.org 🔄 Modified Documents |
2 participants
Changes:
I wondered if we should change the order of the publishing providers (in the table on
docs/publishing/index.qmd, in the sidebar, and inguide.yml) to demote Quarto Pub - being listed first may mean it's the first place new users land. Is now the right time to do that?Could we have used the
_publish-command.mdinclude for Publish Command section? I think we could have, but I can see why you didn't (e.g. the Posit Connect doc doesn't). Is this something we need to give more direction to Claude on?