-
Notifications
You must be signed in to change notification settings - Fork 96
March Newsletter #1690
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
March Newsletter #1690
Conversation
These URLS are probably typos with the trailing underscore: |
I've suggested changes in the .md file |
Co-authored-by: Ian Cosden <[email protected]>
Newsletter preview Post preview |
Newsletter preview Post preview |
@danielskatz thanks for all of this quick feedback! I'm integrating this and feedback from Sandra and Ian offline so stay tuned! |
…om December 31 to present, fixes a dead psyarxiv link to an accepted paper and removes a dea link for a job board that is since archived.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
I'm very happy with this first post at this stage and ready to convert it to in-review for the website: https://output.circle-artifacts.com/output/job/36bd30b6-069f-43dd-a5bc-b2bf5061a409/artifacts/0/usrse.github.io/2025-03-28-newsletter/index.html#conference2025 |
Fixes #1689
Description
This issue adds the March newsletter to the main page of the USRSE website. The newsletter is a summary of the latest news, events, and updates from the USRSE community. In addition to the usual content, this issue includes content or updates from @sandragesing, @danielskatz, @TinasheMTapera, @roelofsaj, and @JeffCarver. Importantly, it also adds Daniel's Community Travel Funds Report as a separate "News" item.
This is my (Tinashe's) first time creating a newsletter issue, so I would appreciate any feedback or suggestions for improvement. I look forward to creating more content with you all in the coming months!
Checklist:
When you are ready for a technical review/merge, post the for the link for the PR in the US-RSE Slack (#website) to ask for reviewers.