closes #338 docorator blog post

[bzkrouse]

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!

[manciniedoardo]

Great post! Just some minor formatting comments to ease publishing.

[bms63]

@aaehmann FYI @chrisprice-phuse needs to approve each blog post before publishing. he is super quick.

something to add to the PR template and README #309

[bms63]

@manciniedoardo these are commented out so the link package won't make the auto-links for packages and functions anymore.

[bzkrouse]

@manciniedoardo thank you for the review - I just made some edits accordingly. Please let me know if any other changes are needed!

[bms63]

@bzkrouse can you style your code and add any spelling exemptions to the inst/WORDLIST.txt file. You can use the R/CICD.R file for spelling.

don't worry about links. if the code and spelling style fail for other files don't worry about them

[bzkrouse]

@bms63 done!! please let me know if anything else is needed :)