<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Blogdown on rostrum.blog</title>
    <link>https://www.rostrum.blog/tags/blogdown/</link>
    <description>Recent content in Blogdown on rostrum.blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Sun, 07 May 2023 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.rostrum.blog/tags/blogdown/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Automate {blogdown} to Quarto</title>
      <link>https://www.rostrum.blog/2023/05/07/bd2q/</link>
      <pubDate>Sun, 07 May 2023 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2023/05/07/bd2q/</guid>
      <description>gRaPhIc DeSiGn Is My PaSsIoN.  tl;dr I’ve written a quick R package, {bd2q}, to help me convert my {blogdown} blog to Quarto. Whether I’ll actually complete the conversion is another story.
 Upside blogdown It is destiny: no-one is ever completely happy with their blog.
This site was built five years ago1 with {blogdown}, which lets you write R Markdown files and have them knitted into a blog. I ignored the newer {distill} package2, but Quarto may be worth the switch.</description>
    </item>
    
    <item>
      <title>Blogging with R on Raspberry Pi</title>
      <link>https://www.rostrum.blog/2020/07/11/raspberry/</link>
      <pubDate>Sat, 11 Jul 2020 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2020/07/11/raspberry/</guid>
      <description>Raspberry Pi 2 Model B (rostrum.blog limited edition)  tl;dr I installed R on a Raspberry Pi and set it up to use {blogdown}. This post was written from my Pi.
 Update
Since I wrote this post it’s become much easier to get started with R on the Raspberry Pi with r4pi.org by Mark Sellors, along with VS Code. Read on for a more terminal-based experience.
  A delicious Raspberry Pi The hardware The Raspberry Pi is a small, inexpensive, single-board computer designed to make computing and coding accessible to all.</description>
    </item>
    
    <item>
      <title>Packages that Sparked Joy in 2019</title>
      <link>https://www.rostrum.blog/2019/12/27/pkgs-2019/</link>
      <pubDate>Fri, 27 Dec 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2019/12/27/pkgs-2019/</guid>
      <description>Marie Kondo (Netflix via Giphy)  Thank you package-makers I’ve used a lot of packages in 2019 and many have brought great joy to my R experience. Thank you to everyone who has created, maintained or contributed to a package this year.
Some particular packages of note for me have been:
 🤖 {usethis} by Hadley Wickham and Jenny Bryan 🦆 {drake} by Will Landau 🐈 {purrr} by Lionel Henry and Hadley Wickham  And some honourable mentions are:</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>
    
    <item>
      <title>{blogdown}: add metadata to Lithium-themed posts</title>
      <link>https://www.rostrum.blog/2019/09/06/lithium-metadata/</link>
      <pubDate>Fri, 06 Sep 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2019/09/06/lithium-metadata/</guid>
      <description>Modifying lithium metal with heat (via Giphy)
 tl;dr Add author name, categories and tags to the posts of your Lithium-themed {blogdown} site. Might work for other themes.
 Lithium This blog is generated using Yihui Xie’s {blogdown}, which is built on the Hugo framework.
A number of site-wide themes have been ported for use with {blogdown}. This site uses the clean and simple Lithium theme by Jonathan Rutheiser, modified for {blogdown} by Yihui.</description>
    </item>
    
    <item>
      <title>Change your {blogdown} fonts</title>
      <link>https://www.rostrum.blog/2018/11/29/fontface-lithium/</link>
      <pubDate>Thu, 29 Nov 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2018/11/29/fontface-lithium/</guid>
      <description>Lithium by Nirvana (via Giphy)  tl;dr Want to change the font for your {blogdown} site? I’ve been using this workflow:
Find a font on the Google Fonts site Search for the font name on the independent Google Web Fonts Helper Download the zip file from the Helper, then copy all the files to static/fonts/ folder Copy the CSS from the Helper into your static/css/fonts.css file   Not my type You can change the default font face for your {blogdown} blog with freely-available files from Google Fonts.</description>
    </item>
    
  </channel>
</rss>