Best practices for saving drafts in blogdown

I enjoy using blogdown to manage my website, but I have found the process for managing unpublished drafts to be somewhat clunky.

The workflow I have in place right now is to save drafts in a folder within my blogdown project, and I list that drafts folder on my gitignore so that drafts are backed up but not publicly viewable on the public github repository for my blogdown website. I sync this drafts folder to Google Drive.

I am sure that other blogdown users do not like having drafts public in their github repos associated with their blogdown sites, but I would be interested to hear you workflow for managing drafts.

2 Likes

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.