Skip to content
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

feat: Add blog post for GitHub Pages #1545

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

mcanouil
Copy link
Contributor

Introduce a new blog post along with a featured image for publication on GitHub Pages.

Originally published on mickael.canouil.fr.

@cwickham
Copy link
Collaborator

/deploy-preview

Copy link
Contributor

🚀 Deployed on https://deploy-preview-1545.quarto.org

@cderv cderv requested a review from cwickham March 11, 2025 10:51
Copy link
Collaborator

@cwickham cwickham left a 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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants