Automated release blog post vaccineff - v1.0.0

[github-actions]

Automated changes by create-pull-request GitHub action

[netlify]

❌ Deploy Preview for tourmaline-marshmallow-241b40 failed.

Name	Link
🔨 Latest commit	17d28f7
🔍 Latest deploy log	https://app.netlify.com/sites/tourmaline-marshmallow-241b40/deploys/67506a5a2a264f0008c5ac0e

[Bisaloo]

@davidsantiagoquevedo, could you review this release blog post for correctness and completeness please?

For a first CRAN release, I would encourage you to consider a manual blog post if you have the bandwidth to do it soon.

[davidsantiagoquevedo]

Hi @Bisaloo I added some details to the description. However, some checks are not passing and I couldn't solve them. Could you please check it?

[Bisaloo]

Yes, the checks fail because the blog post contains R code to be rendered, which the netlify preview cannot do. You don't have to worry about it.

The blog post looks good. Would it make sense to add here some of the examples present in the package README so readers can have a feel of what the package can do for them, even before clicking on the link?

[davidsantiagoquevedo]

Yes, the checks fail because the blog post contains R code to be rendered, which the netlify preview cannot do. You don't have to worry about it.

The blog post looks good. Would it make sense to add here some of the examples present in the package README so readers can have a feel of what the package can do for them, even before clicking on the link?

Good idea! I added an example and a small explanation. Is it necessary to call library(vaccineff)? Or is this redundant?

[Bisaloo]

Thanks, this is great!

Is it necessary to call library(vaccineff)? Or is this redundant?

Yes, it's good to have library(vaccineff) so it can be copied/pasted and run directly.