-
Notifications
You must be signed in to change notification settings - Fork 919
feat: Add blog post for GitHub Pages #1545
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
/deploy-preview |
🚀 Deployed on https://deploy-preview-1545.quarto.org |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there is some useful content in here but it's a bit buried.
The first two scenarios, Manual, and Automated - Quarto Publish GitHub Action, are what we describe in the docs. I think you could minimise their content and stick to "these work well in ___ cases". Then, really highlight the cases they don't work and use that to introduce the two scenarios in "Custom GitHub Actions Workflow".
I also think it would help if you called out the "new" steps in the workflows (maybe with code annotation). So, someone can easily see what is different, and also understand what each step is doing (especially those shell commands).
I almost forgot about this. |
Introduce a new blog post along with a featured image for publication on GitHub Pages.
Originally published on mickael.canouil.fr.