#335 pharmaverse examples

[orladoylenvs]

Thank you for your Pull Request! We have developed this task checklist to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your blog post.

Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the main branch until you have checked off each task.

• Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update), and make sure the corresponding issue is linked in the Development section on the right hand side
• Ensure your new post folder is of the form "posts/zzz_DO_NOT_EDIT_<your post title>". This is so that the post date can be auto-updated upon the merge into main.
• Run the script from CICD.R line by line to first check the spelling in your post and then to make sure your code is compatible with our code-style. Address any incongruences by following the instructions in the file!
• Choose (possibly several) tag(s) or categories from the current list: c("Metadata", "SDTM", "ADaM", "TLG", "Shiny", "Python", "Community", "Conferences", "Submissions", "Technical", "DEI") for your blog post. If you cannot find anything that fits your blog post, propose a new tag to the maintainers! Note: if you use a tag not from this list, the "Check Post Tags" CICD pipeline will error. We occasionally tidy up all tags for consistency.
• Add a short description for your blog post in the description field at the top of the markdown document.
• Blog post is short, personalized, reproducible and readable
• Add a disclaimer at the top of your post, if appropriate (example: Disclaimer
  This blog contains opinions that are of the authors alone and do not necessarily reflect the strategy of their respective organizations.)
• Address all merge conflicts and resolve appropriately
• Assign two of us (@bms63, @manciniedoardo, @StefanThoma, @kaz462) as reviewers in the PR.
• Pat yourself on the back for a job well done! Much love to your accomplishment!

[bms63]

Looks great - just a couple minor suggestions. Shall we get this out earlier than 2026?

[bms63]

@aaehmann FYI

[bms63]

@orladoylenvs be sure to put closes in PR Title so GH auto-closes the issue. Sometimes linking on the side doesn't always auto close it for some reason

[rossfarrugia]

Looks great Orla thanks! Only some minor comments

[rossfarrugia]

@orladoylenvs lets also include something on the latest cool feature of language translations: pharmaverse/examples#126 - i just merged this so should be live on the site soon

[orladoylenvs]

Thanks for the review! I need to do the linting, spelling, etc but hopefully the content is in good shape and I think addressed all your comments but do feel free to make additional suggestions!

[bms63]

@orladoylenvs I fixed the spelling and styling issues coming from other files.

@aaehmann is going to try and get someone from the new blog team to address the failing links. Those are from much older blog posts.

So no worries on the actions now. :)

[rossfarrugia]

thanks Orla! i made one minor change to one sentence just to make clear we meant spoken languages rather than programming languages, so people don't get confused that we don't currently offer these examples in python etc.

[bms63]

If this gets merged in it won't get published until the January date and that depends on someone publishing something on or after that date.

Do we want to change the date to today and merge in so it is published or wait to merge this in on January 12th?

[rossfarrugia]

Fine for me for this to be published anytime from now and not wait til after Jan 12th

[orladoylenvs]

Sounds good - should I merge already? and second question how do I change the publishing date?