Curating for @WeAreRLadies on Twitter

This post was originally published on Shannon Pileggi’s personal blog.


In February 2021 I tweeted to a daunting >20k followers by curating for @WeAreLadies on Twitter. This was great opportunity to share knowledge, interact with others, and learn something in return, ultimately cultivating new connections and collaborations. From preparation to fruition, I hope this post helps you confidently enroll as a curator!

Added 2021-10-05: For a broad overview, check out the poster presentation Be great and curate! for the 2021 Women in Statistics and Data Science conference.

About @WeAreRLadies

The @WeAreRLadies rotating Twitter curator exists to “encourage and maintain Twitter engagement within the R-Ladies community,” and to “spotlight female and minority genders” working with R. R-Ladies has a comprehensive guide describing the program, procedures and protocols for the week, and tips for successful curation.

Overcoming imposter syndrome

You may be hesitant to sign up as a curator due to imposter syndrome - I certainly was. I was on Twitter for three years before I gathered the courage. However, you do not need to know everything about R nor Twitter in order to be a successful @WeAreRLadies curator - that is impossible! In fact,

Every R user, new or experienced, has a valuable perspective to share. I was particularly impressed when Danielle Brantley excellently curated in September 2020, after being an R user for one year! To help alleviate general R imposter syndrome check out Catlin Hudon’s blog post on imposter syndrome in data science; to increase comfort with Twitter, try Twitter for R Programmers by Oscar Baruffa and Veerle van Son.

My personal strategy for combating imposter syndrome is to prepare. For my curating week, my preparation involved reflecting on past curators and creating some content in advance. I hope this post helps you to prepare and motivates you to sign up. 😉


Here is my personal timeline to leading up to curation.

Time before curationAction taken
3 yearsBecame active on twitter
3 monthsSigned up to curate
3 weeksNotified manager; discussed work-related content
2 weeksResearched R-Ladies fonts and colors
1 weekStarted drafting tweets
1 dayFiddled with formats for code gifs

Selecting a date

You can view the schedule of upcoming curators to identify available dates; records of previous curators are also maintained here.

Being a curator will be time intensive, so be kind to yourself. Choose dates when you will have time to invest and a flexible work schedule. I chose Feb 15-20 because I hoped by then I would be recovered from an intense Q4 work cycle; additionally, Feb 15 (President’s Day) was a company holiday. You may want to select a date far enough in the future that allows you time to create content.

Another consideration is to schedule your curation to coincide with dates that align with your interests. For example, are you passionate about Black History Month in February, LGBT Pride Month in June, or Universal Human Rights Month in December? If so, take advantage of the @WeAreRLadies large platform as an opportunity to inform and educate others on issues that are important to you as they relate to the R community. Diversity best practices has a comprehensive list of calendar holidays and observances.

Signing up

You sign up by submitting a form - give yourself at least 30 minutes to sign up as part of the form includes filling out details that complete your curating profile.

There was a gap between when I filled out the form and when I was confirmed as a curator, which I suspect was due to timings and holidays. Be kind, be patient - all organizing R-Ladies are volunteers.

Notifying my manager

About three weeks before my curation, I started planning my curating efforts a bit more seriously. I notified my manager that I was curating, and I discussed potential work-related content with her. One idea was approved and another was reasonably denied. This honest conversation facilitated new awareness about my passions - my manager was not aware of R-Ladies, and she was enthusiastic and supportive.

Styling content

Additionally, I considered how to visually style content beyond text in a tweet. I asked on R-Ladies slack about R-Ladies styles, and I was directed to the xaringan R-Ladies css and the R-Ladies branding guides. You are not required to use R-Ladies style and branding, but it was convenient for me.

I developed two visual layouts using the Google slide template from R-Ladies branding (see tweets for blogdown vs distill and asking for help online).

I also created five R-Ladies styled code gifs with xaringan and flipbookr - methods and code are in this blog post. Here is an example code gif:

Drafting content

Leading up to my curation week, I regularly jotted down brief notes of content ideas. The week before curation, I started fleshing out those ideas into actual tweets and wrote them down in a document. Not all of my ideas ended up in a draft, and rarely did the draft get tweeted out exactly as I had written.

One challenge with drafting tweets in a document was being mindful of character limits and anticipating where the breaks would be for threads. I started copying content into a send tweet window to preview and then pasting it back into my draft document. There is software that facilitates drafting tweets - for example, Daphna Harel recommended to me the week of my curation. I also kept emojipedia open all week to easily copy and paste emojis into drafts.

Not all content was premeditated - I also tweeted in the moment. For example, the W.E.B. Du Bois’ #TidyTuesday visualizations were incredible that week, or when I realized a new colleague wasn’t yet taking advantage of RStudio projects.

Content inspiration

As I approached my curating week, I recalled previous @WeAreRLadies that were memorable for me, my previous experience as an educator, and some reflection questions to inspire content.

Inspiration sourceExample realization
1. Rotating curator Mine Çetinkaya-Rundel (@minebocek) tweets awesome gifsGifs for R code demos
2. Rotating curator Megan Stodel (@MeganStodel) tweets a project inspired by curatingAn R project to introduce myself as a curator
3. Rotating curator Julia Piaskowski (@SeedsAndBreeds) tweets a great technical thread on ANOVAA thread on blogging resources
4. Prior experience as an educatorStarting discussion with a question
5. What am I passionate about lately?Blogging
6. What did I have to overcome to be where I am today?Learning how to ask for help online
7. What have colleagues or students asked me about?What needs updating and when
8. What are some R functions or packages that have helped me recently?sortable package
9. What are R-Ladies voices I can amplify while I have this large platform?Quote tweeting questions


Reminiscing about my days teaching in large lectures halls with students actively participating in polling questions through clickers, I planned three polls for the week. Polls on twitter are open for 24 hours and allow up to four response options. The approach was to launch the poll, collect responses, and then discuss. Here are the three polls that I launched during my curation, with follow up discussion:

First and last tweets

The introduction and farewell tweets as a curator are important as this is when you actually tell people your name or personal twitter handle. To generate engagement, I aimed to create content-rich first and last tweets to give users more motivation to like or re-tweet, and I also connected the content with links to my blog so that users could easily learn more about me.


When you serve as a curator, you will be tweeting from TweetDeck, and it is hard to separate curator experience from the technology. Tweeting from TweetDeck can be overwhelming compared to the standard Twitter interface.

Moreover, there were limitations to the platform that added challenges to curating, which included:

  1. There was no + enabled to easily create threads (I had to send a tweet and then comment on the tweet, and it was initially hard to ensure the thread appeared in correct order). Yes, I deleted many out of order tweets.

  2. Consequently, I could not draft and save threads in TweetDeck to send later.

  3. I could not send polls from the curator account on TweetDeck; polls were sent from my personal account and then re-tweeted from the curator account. Adding this context can help better frame polls.

  4. Depending on the content already in the send tweet interface, sometimes other options in TweetDeck would disappear, like the emoji, gifs, and upload image buttons. I kept emojipedia open to easily copy and paste emojis into my tweets, and it took trial and error to get everything I wanted in a single tweet.

  5. When uploading local content, you can add descriptions to both gifs and images in the regular Twitter interface to create inclusive content for community members that use assistive reading technology; however, in TweetDeck, descriptions were enabled for images but not gifs.

  6. With TweetDeck, you can tweet from both your personal account and your curator account. You can set the options to default to the curator account, but there were still some instances where I still managed to inadvertently tweet from my personal account when I meant to tweet from the curator account. (I did delete the tweet and re-tweet from the correct account.)

I spent a lot of time my first couple of days as a curator getting used to TweetDeck, reaching out to other curators for tips, and researching alternative solutions and plug-ins that ultimately did not help. Twitter is targeting TweetDeck enhancements later in 2021, so I don’t think it is worth documenting all of my methods and work-arounds. However, if you are serving as a curator and struggling with TweetDeck, please reach out - I am happy to share what ended up working for me. You can also prepare yourself by practicing tweeting from TweetDeck with your personal account prior to curating.

What I would have done differently

It was a whirlwind week! Here a few things I would have done differently.

  1. Practice with TweetDeck in advance. Literally, force yourself to tweet from Tweetdeck at least a week before your curation. TweetDeck is very different than the standard Twitter interface, and it took me a few days to get used to it.

  2. Figure out how I wanted to style shared code in advance - my first couple of days would have gone smoother with this.

  3. Preface polls tweeted from my personal account with the context that they are for curator rotation.

  4. Prepare a tweet in honor of any holidays or significant events coinciding with your curation week. One regret that I do have from my curating week is failing to explicitly acknowledge Black History Month as I was tweeting in February. I wish had prepared at least one tweet or better amplified the voices of black members of the R community while I had the large platform.

Fleeting fame

When curating, your tweets in the moment are highly visible. But what persists afterward is fairly anonymous as your tweets are not linked to your personal profile unless you tag yourself. In a weird way, it actually becomes a safe place to put yourself out there with questions you might not have been comfortable asking from your own personal account. Take advantage of this fleeting fame not just to share your knowledge but also to ask your questions.

Supporting your curators

Just because a Twitter account has >20K followers, the likes, re-tweets, and comments don’t come automatically. You still have to earn engagement with your content. Many of the tweets I sent had little engagement, and that is okay. Supporting your curators by engaging with their tweets or sending notes of encouragement is much appreciated. I thank everyone who engaged with me during my curation, with a special shout out to Alison Hill who re-energized me mid-week with comments on the R-Ladies bloggers thread. I cannot emphasize this enough: every like, re-tweet, comment, and direct message helps!

In addition, if you have curated in the past, consider sending new curators a personal welcome message and an invitation to ask you any questions. Following my curation week, I offered camaraderie and tips to Ale Segura, and in return, she did the same for Shreya Louis following her.


Between prepared and ad-hoc content and discussions with followers, I tweeted a lot! (At least for me.) Here is a summary thread of my tweets for the week. My tweets were not perfect, and that is okay. I messed up threads, had typos, and shared deprecated code, among other things. Check out my blooper reel1 for tweets that I bungled.

Serving as a curator was intimidating and time consuming, but I am very glad I did it. Many good things have happened as direct result of that week, including:

  • discussing comparisons between {blogdown} and {distill} with Alison Hill.

  • collaborating with Silvia Canelón to style code gifs.

  • engaging with new people on Twitter that I want to continue to engage with.

  • learning about valuable new-to-me packages, functions, and work flows.

  • being invited to speak for R-Ladies Miami.

  • seeing my “Asking for help online” content re-used in Sharla Gelfand’s “make a reprex… please” presentation.

  • co-developing a unit testing workshop with Gordon Shotwell for R-Ladies Philly.

During my curating week I tried to embody the tweets that I value: honest questions, thoughtful discussion, generous sharing, supportive community, and humorous exchanges. To borrow from Vicki Boykis in the rstudio::global(2021) keynote, I created my own public garden that cultivated new connections and collaborations. And now, I am more confident in continuing these practices from my personal Twitter account.


Thank you to Maëlle Salmon and Alison Hill for encouraging me to write this - it might not have happened without you! Thank you also to Maëlle Salmon, Ale Segura, and Isabella Velásquez for your suggestions; I truly appreciate your sharp eyes and thoughtful feedback. 💜

  1. A blooper is an embarrassing mistake, often sports-related, and humorous in retrospect; a blooper reel is a compilation of multiple bloopers. ↩︎

Author: Shannon Pileggi

This post was last edited on 14 April 2024 with the message"add a production renv profile (fix #298) (#286)"