You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Blog post authors have to keep a couple things in mind, especially when it comes to the front matter. For now, we try to document this in the readme. That puts the burden on our authors.
Instead, we could have a little program that prompts authors interactively when they're creating a new post.
There is a crate called inquire or something that should make this nice.
With a cargo alias (inspired by cargo xtask) authos could run e.g. cargo blog to generate a new post.
Questions might include:
title (then auto-generate slug and filename from it)
date (placeholder if unknown)
inside-rust yes/no
release post (-> auto-generate aliases)
team (if yes, also prompt for url)
At the end, valid usable front matter should be generated with minimal effort from the author.
Lastly, as a bonus, the generated post could include some boilerplate markdown that shows all the features available. (I for one always forget how to do footnotes in markdown)
The text was updated successfully, but these errors were encountered:
Blog post authors have to keep a couple things in mind, especially when it comes to the front matter. For now, we try to document this in the readme. That puts the burden on our authors.
Instead, we could have a little program that prompts authors interactively when they're creating a new post.
There is a crate called inquire or something that should make this nice.
With a cargo alias (inspired by cargo xtask) authos could run e.g.
cargo blog
to generate a new post.Questions might include:
At the end, valid usable front matter should be generated with minimal effort from the author.
Lastly, as a bonus, the generated post could include some boilerplate markdown that shows all the features available. (I for one always forget how to do footnotes in markdown)
The text was updated successfully, but these errors were encountered: