Add: events section to website & scipy workshop 2024 #442
Conversation
| @@ -10,7 +10,7 @@ header: | |||
| author_profile: false | |||
| --- | |||
|
|
|||
| ## Recent pyOpenSci Posts! | |||
| ## Recent pyOpenSci Posts | |||
There was a problem hiding this comment.
delete exuberance (breaking change) <3
There was a problem hiding this comment.
@sneakers-the-rat best review comment ever.
_posts/events/2024-06-25-create-your-first-python-package-scipy-2024.md
Outdated
Show resolved
Hide resolved
| --- | ||
| layout: single | ||
| title: "Workshop: pyOpenSci @ SciPy 2024 -- Create Your First Python Package" | ||
| excerpt: "Python packaging can be tricky to navigate. pyOpenSci will lead a workshop on creating your first Python package at SciPy 2024. The goal of this workshop is to help scientists learn how to package and make code installable and shareable. Read on to learn more!" |
There was a problem hiding this comment.
should this be in future tense if the event has already happened?
There was a problem hiding this comment.
oh yes good point. we should think about that. we will want to have these pages in the future up before an event but become a long lasting record of our activities too. i don't think we want to switch tenses post event. but what we can do it automate something to add a section to the page if the event already happened and list them that way too.
if you agree that might work we can then open an issue about that point so it's clear to users.
There was a problem hiding this comment.
that makes sense. I think if the idea is to have them up ahead of time, then leaving it in future tense makes sense. love the idea of having an automated section added to indicate the event has happened!
There was a problem hiding this comment.
yes. so the plan is to put these events up before it is held. we are just behind because i literally needed to create an events page to be able to put things up. but we will be ahead for the upcoming fall festival!
| comments: true | ||
| --- | ||
|
|
||
| ## Create Your First Python Package: Make Your Python Code Easier to Share and Use |
There was a problem hiding this comment.
leaving this as is, however we've traditionally used sentence case rather than all caps (previous discussion)
There was a problem hiding this comment.
i wonder if we can set this up for Vale to catch that for me. if i have a took checking things i'll do a better job with these small but important consistency pieces. maybe we can ask Felipe in slack about it as he setup vale for us and it's been great for other things like capitalization.
There was a problem hiding this comment.
that would be great! I know I constantly have to go back and re-edit mine as well.
_posts/events/2024-06-25-create-your-first-python-package-scipy-2024.md
Outdated
Show resolved
Hide resolved
_posts/events/2024-06-25-create-your-first-python-package-scipy-2024.md
Outdated
Show resolved
Hide resolved
_posts/events/2024-06-25-create-your-first-python-package-scipy-2024.md
Outdated
Show resolved
Hide resolved
_posts/events/2024-06-25-create-your-first-python-package-scipy-2024.md
Outdated
Show resolved
Hide resolved
_posts/events/2024-06-25-create-your-first-python-package-scipy-2024.md
Outdated
Show resolved
Hide resolved
_posts/events/2024-06-25-create-your-first-python-package-scipy-2024.md
Outdated
Show resolved
Hide resolved
_posts/events/2024-06-25-create-your-first-python-package-scipy-2024.md
Outdated
Show resolved
Hide resolved
lwasser
force-pushed
the
scipy-workshop-2024
branch
from
6d99460 to
56900ae
Compare
|
hey @kierisi i have created a really basic (not pretty) template here and i've added now the scipy and our online workshop to the events page. we can make it prettier later. but thinking about the fall festival - what template should we use for events? the pages will be put up BEFORE an event but then of course the language will be dated as it is a past event. that is ok as it's easy for me to create a section for upcoming vs past events once we have enough content. we should come up with an events page template that we use to events are consistent. have a look at the build here and let me know what you think. i just copied language from the post on our first workshop which is not ideal. but i think a solid template will make creating these pages easier in the future. |
|
@kierisi one other note - i believe that i captures all of the your work here: blog in this PR however i did this on the plane and it looks like i wasn't careful about brining over the commits from your other pr. but all of the work is here. are you comfortable with closing the other pr - #427 in favor of this one without the commits themselves? again the work is captured. I think i just moved too quickly around scipy because i was running out of time. (and this never got to be publish prior to the event anyway) |
|
this template works for me! I think as we do more events we'll be able to better evaluate what changes might be helpful to the template. |
sounds good! just to clarify, I can close the PR and it's all good to go? |
Co-authored-by: Jesse Mostipak <[email protected]>
lwasser
force-pushed
the
scipy-workshop-2024
branch
from
4885b29 to
ba8fbf3
Compare
yes! i think i closed it earlier today. but all of the work you did in that PR is here now! and i've made things prettier with the event cards. i'll add dates later this week and then i think we can merge once we have a date for the fall festival. |
|
ok - @kierisi this is i think ready to go. there are some changes in how we handle events -- i've added an Yaml section that will allow us to populate event details and it will be automatically displayed in the events listing page. We will likely need to adjust this over time to meet our needs events:
start_date:
end_date:
cost: For now, I will merge this PR. The events pages will need some work so i will open an asana task for you to
|
This PR adds an events section to our website so we can post events as we hold them and link to setup instructions as needed.