optimize rmarkdown template

[henrywangnl]

Optimized the rmarkdown template for writing post to save my life.

---
params:
  post_title: "The Post Title"
title: "`r params$post_title`"
date: "`r format(Sys.time(), '%Y-%m-%dT%H:%M:%S')`"
output: hugodown::md_document
slug: "`r gsub(' ', '-', tolower(params$post_title))`"
status: "publish"
comment_status: "open"
categories:
  - category1
  - category2
tags:
  - tag1
  - tag2
  - tag3
---

[maelle]

(and thank you!!)

[henrywangnl]

hmmm, the R CMD Check failed because of slugify package I think.

[maelle]

wait should this be kept? the users could still want to choose their own slug?

[henrywangnl]

Be default we will handle slug in wp_post() but users can still overwrite it if they manually provide slug in the YAML header. However, slug is not shown in the default template. What do you think?

[maelle]

sorry for the delay, I think I'd like to keep it in the template because folks might wonder how to add it?

[henrywangnl]

Hmmm, if we keep it in the header, people can either change it or delete it? In that case, I'm afraid they would never know we can handle it by default in `wp_post()` . Instead they would most likely choose to change slugs manually every time. What do you think?

…

On Thu, Nov 26, 2020, 9:26 AM Maëlle Salmon ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In inst/rmarkdown/templates/template-name/skeleton/skeleton.Rmd <#30 (comment)>: > output: hugodown::md_document status: "publish" -slug: "the-post-slug" sorry for the delay, I think I'd like to keep it in the template because folks might wonder how to add it? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#30 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE7BXKB26R4PD2DQ5OSJHX3SRYGMVANCNFSM4TONXG6Q> .

[maelle]

ok then! :-)