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

Feature Request: new_post function / RStudio Addin #22

Open
christian-million opened this issue Jul 19, 2022 · 2 comments · May be fixed by #171
Open

Feature Request: new_post function / RStudio Addin #22

christian-million opened this issue Jul 19, 2022 · 2 comments · May be fixed by #171
Labels
enhancement New feature or request
Milestone

Comments

@christian-million
Copy link

A function and/or RStudio Addin that allows users to create the skeleton for a new blog post. I used the new_post functionality in blogdown a lot and would love to incorporate a quarto version into my workflow.

Quarto comes with a "website:blog" project type, which signals a common-enough use case for this kind of functionality. For now, it could just create a new post in the posts directory (by default). Eventually it might use a dedicated "website:blog" yaml parameter to indicate which directory the new post should be located in?

Something like:
(using quarto-web directory as example)

website:
  blog: docs/blog/posts

and then quarto::new_post("my_new_post") would create docs/blog/posts/my_new_post/index.qmd

@njtierney
Copy link

I would also really like some capacity to add this feature!

@mccarthy-m-g
Copy link

I made an RStudio new post addin for {distill} through the {distilltools} package awhile back (inspired by {blogdown}). Just mentioning it here since Quarto is a spiritual successor to {distill}, so some of the work there might be helpful in the implementation for this package. Here’s the relevant PR.

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

Successfully merging a pull request may close this issue.

4 participants