Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[end of jan merge] feat(blog): 2024 recap blog #545

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

lwasser
Copy link
Member

@lwasser lwasser commented Jan 7, 2025

What's missing

  • proper captions for figure (or remove captions!)
  • alt tags for figures
  • add links and acknowledgment to advisory council, executive council and editorial board

@lwasser lwasser marked this pull request as ready for review January 7, 2025 17:47
@lwasser lwasser changed the title feat(blog): 2024 recap blog [end of jan merge] feat(blog): 2024 recap blog Jan 8, 2025
---
layout: single
title: "2024: A Transformative Year for pyOpenSci"
excerpt: "2024 was a transformative year for pyOpenSci—we broke down barriers to open source participation with training events, collaborative tutorials, and peer review. Thanks to our incredible community, we’ve doubled our contributors, expanded our ecosystem, and created free educational resources for scientists worldwide. Learn more about our 2024 adventures and what's next for 2025."

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

incredible community -> incredible community and supporters


## Introduction

In 2024, pyOpenSci’s vibrant community led efforts to break down barriers to participation in open source scientific software. We empowered scientists to create, contribute to, and discover better software through beginner-friendly training events, collaborative tutorials, and peer review.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

scientists -> people

@tracykteal
Copy link

I really like your three bullet points!

  • A new Training Initiative
  • Expanded Software Peer Review Program
  • Co-created a package template, guide and tutorials

The content in the post matches these too. Could you use these as the three main headers, and present them in the same order in the text as in the bullet points? That will help guide people through the post.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants