<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pkgdown on rostrum.blog</title>
    <link>https://www.rostrum.blog/tags/pkgdown/</link>
    <description>Recent content in Pkgdown on rostrum.blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Sun, 09 Aug 2020 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.rostrum.blog/tags/pkgdown/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>R-Package GitHub Actions via {usethis} and r-lib</title>
      <link>https://www.rostrum.blog/2020/08/09/ghactions-pkgs/</link>
      <pubDate>Sun, 09 Aug 2020 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2020/08/09/ghactions-pkgs/</guid>
      <description>A GitHub Action in action on GitHub.  tl;dr You can trigger GitHub Actions to build and test your R package after a push or pull request. Create .github/workflows/ in your repo and add pre-prepared actions by the r-lib team with usethis::use_github_action().
 Shortcut I refer back to this post a lot, so here’s some jump-links to the sections with the code I need:
Build check Test coverage Build {pkgdown} site  Otherwise read on for a more thorough explanation of GitHub Actions in the context of R packages.</description>
    </item>
    
    <item>
      <title>Build an R package with {usethis}</title>
      <link>https://www.rostrum.blog/2019/11/01/usethis/</link>
      <pubDate>Fri, 01 Nov 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2019/11/01/usethis/</guid>
      <description>Ossie, a Cabinet Office cat (via @cabinetofficeuk)  tl;dr  I gave a talk about creating an R package with helper functions from the {usethis} package In the session I created a new package from scratch called {cabinet} for identifying the cats that live in the UK Government’s Cabinet Office See the slides in a dedicated window or view their source See the {cabinet} package source and its website Jump to a list of other materials   Coffee packaging I gave a talk at a Cabinet Office Coffee &amp;amp; Coding session about building R packages from scratch.</description>
    </item>
    
    <item>
      <title>{blogsnip}: an RStudio addin package</title>
      <link>https://www.rostrum.blog/2019/10/22/blogsnip/</link>
      <pubDate>Tue, 22 Oct 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2019/10/22/blogsnip/</guid>
      <description>Inserting a details block with the {blogsnip} addin  tl;dr On my commute home I made {blogsnip}: a tiny package of RStudio addins that add snippets of R code to help me write blog posts.
Install with:
install.packages(&amp;quot;remotes&amp;quot;) remotes::install_github(&amp;quot;matt-dray/blogsnip&amp;quot;)  The problem I’m lazy.
There’s some bits of code I often want to put in my blog posts (written in R Markdown) but I can’t remember them.
In particular:
 an expandable ‘details’ section1, which sometimes contains R session information and the date of the post’s last update (see examples throughout this previous post) a way to add an image with a caption and alt text that differ (like the gif at the top of this post), something that makes the images more accessible for users of screen readers, for example a link that opens in a new tab, rather than in the tab where you’re reading a post (as per this tweet by Albert Y Kim)  Originally I stored them in a GitHub Gist, but this is sub-optimal: the internet connection on my commute can be patchy.</description>
    </item>
    
  </channel>
</rss>