Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion config/_default/markup.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -5,4 +5,5 @@ goldmark:
unsafe: true
parser:
attribute:
block: true
block: true
wrapStandAloneImageWithinParagraph: false
16 changes: 5 additions & 11 deletions content/blog/2026/sbarbara/index.en.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,9 +55,7 @@ And, perhaps unsurprisingly for a group of millennials, we gave this idea a hash
We went searching for clear, practical guidance on how folks actually stay up to date with changes in the R ecosystem...and came up mostly empty.
We even asked our communities on social media, and got \*crickets\*. 

![Screenshot of a post on Bluesky from R-Ladies Santa Barbara that writes: "Data scientist, analysts, folks who write code: we want to hear from you! We're brainstorming resources on how to keep up with the ever-evolving R ecosystem. What strategies do you use to keep code/software up to date? How do you find out what's new in R/your fave lang? Let us know!"](blog_fig_bluesky.png)

Our attempt to crowdsource on Bluesky.
![Screenshot of a post on Bluesky from R-Ladies Santa Barbara that writes: "Data scientist, analysts, folks who write code: we want to hear from you! We're brainstorming resources on how to keep up with the ever-evolving R ecosystem. What strategies do you use to keep code/software up to date? How do you find out what's new in R/your fave lang? Let us know!"](blog_fig_bluesky.png "Our attempt to crowdsource on Bluesky.")

At one point, we almost left this event idea on the back burner permanently.
But we were encouraged and inspired by what we did find: lots of folks in our data science communities could relate to these challenges and were genuinely interested in hearing how others keep their code and workflows current.
Expand All @@ -69,9 +67,7 @@ Some quotes:

> "I ran some R code again after not looking at it for \<2 years and encountered multiple tidyverse deprecation warnings...Not even 2 years!\...If I were to keep working on that project in earnest, I would want to be using the latest/greatest tidyverse, so updating my code would be required regardless."

# ![A tweet from Hadley Wickham saying "Happy reinstalling-all-your-R-packages day to all those who celebrate! #rstats"](blog_fig_hadley_kelly_tweet.png)

Even R-celebs struggle with these challenges!
![A tweet from Hadley Wickham saying "Happy reinstalling-all-your-R-packages day to all those who celebrate! #rstats"](blog_fig_hadley_kelly_tweet.png "Even R-celebs struggle with these challenges!")

Instead of trying to define a single "right" way to stay current in R, we decided to learn from our community through facilitated discussion.
The goal of this blog post is to share what we learned from one another and distill this information into a set of considerations.
Expand All @@ -81,16 +77,14 @@ We hope these ideas help you find an approach that works for you! 

## Who are we?

![Picture with R-Ladies Santa Barbara members](blog_fig_who_are_we.png) R-Ladies Santa Barbara members at our November 2025 meetup!
![Picture with R-Ladies Santa Barbara members](blog_fig_who_are_we.png "R-Ladies Santa Barbara members at our November 2025 meetup!")

We are a community of R enthusiasts connected through [R-Ladies Santa Barbara](https://www.meetup.com/rladies-santa-barbara/), representing a range of career stages, sectors, and experience levels.
Our contributors include academic staff, researchers, educators, industry practitioners, and data science learners.
Collectively, our self-identified R experience ranges from novice to proficient.

Our recommendations emerge from this collective mix of experience and perspectives.
While we don't claim to represent all R users or all use cases, we aimed 

to surface common challenges and practical considerations shared across our communities.
While we don't claim to represent all R users or all use cases, we aimed to surface common challenges and practical considerations shared across our communities.
By convening under R-Ladies Santa Barbara, we grounded this work in the values of inclusivity and community-driven knowledge building.

## Our process
Expand Down Expand Up @@ -299,4 +293,4 @@ Generative AI tools (e.g. ChatGPT) were used to assist with organizing and synth

- Ryan Munnikhuis

- * denotes the R-Ladies Santa Barbara co-organizing team, + indicates contributors to the writing and editing of this blog post. All others participated in the R-Ladies Santa Barbara Meetup discussion that inspired the content of this post.
\* denotes the R-Ladies Santa Barbara co-organizing team, + indicates contributors to the writing and editing of this blog post. All others participated in the R-Ladies Santa Barbara Meetup discussion that inspired the content of this post.
17 changes: 12 additions & 5 deletions themes/hugo-rladies/layouts/_default/_markup/render-image.html
Original file line number Diff line number Diff line change
@@ -1,8 +1,15 @@
{{- $alt := .PlainText -}}
{{- $src := .Destination | safeURL -}}
{{- $caption := .Title | default .PlainText -}}
{{- if .IsBlock -}}
<figure class="figure">
<img class="figure-img img-fluid rounded"
src="{{ .Destination | safeURL }}"
alt="{{ .Text }}">
<img class="figure-img img-fluid rounded"
src="{{ $src }}"
alt="{{ $alt }}">
<figcaption class="figure-caption">
{{ .Title | default .Text }}
{{ $caption }}
</figcaption>
</figure>
</figure>
{{- else -}}
<img class="img-fluid rounded" src="{{ $src }}" alt="{{ $alt }}"{{ with .Title }} title="{{ . }}"{{ end }}>
{{- end -}}
Loading