Closed sapols closed 8 months ago
@jibarnum is this better? With Events
?
I'd specifically wrestled with this idea when I was making this PR, but initially decided against it because any header I could think of was either redundant or inaccurate. (1) It's already the "Meetings" page so no point in having a second header that says "meetings", (2) Telecons are also "PyHC relevant meetings" so we can't use that, (3) "Events" is the best I can come up with, but "Community Meetings" are really more "meeting" than "event." "Other Meetings" might be more accurate but that sounds dumb.
@jibarnum is this better? With
Events
?I'd specifically wrestled with this idea when I was making this PR, but initially decided against it because any header I could think of was either redundant or inaccurate. (1) It's already the "Meetings" page so no point in having a second header that says "meetings", (2) Telecons are also "PyHC relevant meetings" so we can't use that, (3) "Events" is the best I can come up with, but "Community Meetings" are really more "meeting" than "event."
Totally, I can see how adding Meetings again in there is redundant. I just wanted something there to break up the flow. Even though meetings are more meetings than they are events, I still like the title "Events".
This PR cleans up our Meetings page by grouping things into subpages.
Now, everything that used to be below the calendar has been moved into one of 3 subpages:
These subpages are now listed in-between our telecon info and the calendar.
Implementation notes:
meetings/
folder, they go in one of 3 subfolders (community_meetings/
,conference_sessions/
,summer_schools/
).