Skip to content

Logistics Links#14

Merged
pancakereport merged 2 commits into
mainfrom
misc-links
May 13, 2025
Merged

Logistics Links#14
pancakereport merged 2 commits into
mainfrom
misc-links

Conversation

@pancakereport
Copy link
Copy Markdown
Collaborator

No description provided.

@pancakereport pancakereport requested a review from phrdang May 8, 2025 17:54
@pancakereport pancakereport mentioned this pull request May 8, 2025
@pancakereport
Copy link
Copy Markdown
Collaborator Author

Course Webpages can be expanded to also discuss how to set up main landing page (https://github.com/data-8/data-8.github.io at data8.org) and semester pages (https://github.com/data-8/sp25 at data8.org/sp25)

Comment thread logistics/course-site.md
@@ -0,0 +1,22 @@
---
layout: page
title: Course Webpages
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This is a great addition! I think it would fit better under a "Course Software" section rather than logistics though (see my comment in #16 ). I added a Course Software section in #9 , if that makes sense to you we can merge that PR in and move this stuff over to that section.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

isn't the website part of setting up the course at the beginning of the semester (hence logistics as you described)?

maybe it's worthwhile to pull stuff out according to when it's relevant. semester set up happens at a very different than exams and the other things (DSP, group projects) happens throughout the semester. there's also things that happen once mainly and then are used throughout the semester (like managing SPAs)

in conclusion: too many ways to organize this site 😵‍💫

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

oof yeah maybe we should just merge things into individual pages for now like you were saying over slack and then reorganize later?

one could also argue some parts of course website do not occur at the beginning of the semester though (like archiving or weekly updates to the website), and I guess I should clarify that by "beginning of the semester setup" I was thinking more along the lines of "wrangling data and people" such as syncing bCourses/Gradescope/OkPy rosters, room bookings for OH/sections/exams, etc. But one could also argue those things go in different places too

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

another thing to consider is just putting things where we feel like they make the most sense and then linking to different parts of the website as applicable

Comment thread logistics/index.md

## Quick Links

- [CS 161 Pedagogy Blog](https://pedagogy.cs161.org/)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I'm honestly not super sure where the 161 pedagogy blog goes because it touches on so many things aside from course logistics, but I think it's probably fine to leave here for now.

@pancakereport pancakereport merged commit 692af41 into main May 13, 2025
5 checks passed
@pancakereport pancakereport deleted the misc-links branch May 13, 2025 20:24
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