Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions logistics/course-site.md
Original file line number Diff line number Diff line change
@@ -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

parent: Course Logistics
nav_order: 2
---

# Course Webpages

## Templates

- [Berkeley Class Site Template with Accessibility Checks](https://github.com/berkeley-cdss/berkeley-class-site)
- [CS 161 Course Site Template](https://github.com/cs161-staff/course-site-template)


## Accessibility Resources

You are responsible for ensuring that your webpage is accessible. This is both the right thing to do and a legal obligation.

- [Digital Accessibility Program](https://dap.berkeley.edu/)
- [WCAG Standards](https://www.w3.org/WAI/standards-guidelines/wcag/)
- [Color Contrast Checker](https://webaim.org/resources/contrastchecker/)
5 changes: 5 additions & 0 deletions logistics/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,3 +6,8 @@ has_children: true
---

# Course Logistics

## 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.

- [DSUS Instructor Hub](https://sites.google.com/berkeley.edu/dsusinstructorhub/home?pli=1&authuser=1)
Loading