From f72f66082624d5048f1fd8c98b1125097504bb01 Mon Sep 17 00:00:00 2001
From: Robert Lanzafame <R.C.Lanzafame@tudelft.nl>
Date: Sun, 1 Sep 2024 15:40:39 +0200
Subject: [PATCH] add content 1

---
 _config.yml          |   4 +-
 _config_draft.yml    |   2 +-
 assignments.md       |  31 +++++++++++
 assignments_group.md | 120 +++++++++++++++++++++++++++++++++++++++++++
 exams.md             |  67 ++++++++++++++++++++++++
 home.md              |  20 +++++---
 info.md              |  96 ++++++++++++++++++++++++++++++++++
 multiyear.md         |  18 +++++++
 shedule.md           |  20 ++++++++
 staff.md             |  29 +++++++++++
 10 files changed, 396 insertions(+), 11 deletions(-)
 create mode 100644 assignments.md
 create mode 100644 assignments_group.md
 create mode 100644 exams.md
 create mode 100644 info.md
 create mode 100644 multiyear.md
 create mode 100644 shedule.md
 create mode 100644 staff.md

diff --git a/_config.yml b/_config.yml
index 23d90c7..9bdb1f8 100644
--- a/_config.yml
+++ b/_config.yml
@@ -13,9 +13,9 @@
 # you will see them accessed via {{ site.title }}, {{ site.github_repo }}, and so on.
 # You can create any custom variable you would like, and they will be accessible
 # in the templates via {{ site.myvariable }}.
-title: MUDE 2024 website
+title: MUDE Website 2024
 tagline: CEGM1000 Modelling, Uncertainty, and Data Analysis for Engineers
-description: Course website for TU Delft CEGM1000, or Modelling, Uncertainty, and Data Analysis for Engineers
+description: Website for TU Delft Module CEGM1000, or Modelling, Uncertainty, and Data Analysis for Engineers
 author: By MUDE Teachers and the Student Army
 baseurl: /2024 # the subpath of your site, e.g. /blog
 url: https://mude.citg.tudelft.nl # the base hostname & protocol for your site, e.g. http://example.com
diff --git a/_config_draft.yml b/_config_draft.yml
index 23ce034..dbd7bcf 100644
--- a/_config_draft.yml
+++ b/_config_draft.yml
@@ -100,4 +100,4 @@ compress_html:
   profile: false
 
 is_draft: true
-draft_banner: "This is the DRAFT version of the MUDE 2024 website. Content may change frequently."
+draft_banner: "This is the draft version of the MUDE 2024 website. Content may change frequently."
diff --git a/assignments.md b/assignments.md
new file mode 100644
index 0000000..76a0a7f
--- /dev/null
+++ b/assignments.md
@@ -0,0 +1,31 @@
+---
+layout: page
+title: Assignments
+description: Types of assignments, graded and not graded.
+nav_order: 5
+nav_exclude: false
+---
+
+# Assignments
+
+**Assignments** is a generic term for the set of regularly-schedule activities that we provide each week. There are two types of assignments that you are must submit for feedback, and contribute to your Project Portfolio grade:
+- Programming Assignments (PA)
+- Projects (P): described on [this page](../projects)
+
+Both types of assignments will be submitted using GitLab; feedback will also be provided using GitLab. More instructions on the procedure for doing this will be provided in week 3. The assignment instructions and solutions will be provided via this course website, but any data or specialty code that is required for the assignments, will be provided via GitLab.
+
+In addition to Programming Assignments and Projects, other types of non-graded assignments may be provided each week to help you study the material: **Workshops** (WS) are for the in-class activities on Wednesday, whereas any other assignments for doing outside of class time will be called **homework** (HW). These are all optional (but encouraged!).
+
+## Programming Assignments (PA)
+
+A Programming Assignment is provided each week to introduce a few relevant concepts that are expected to be applied directly in the project for that week. For the first two weeks these are not submitted for feedback, however, starting in week 3 the programming assignments will begin and collectively make up 20% of the project portfolio (i.e., 10% of the total MUDE grade). Programming Assignments are automatically graded after submitting them to GitLab and are assessed on a pass/no pass basis. You may resubmit as many times as needed to pass the assignment before the deadline at the end of each quarter.
+
+We will use a _static check_ to evaluate your work on a regular basis. This involves the teaching team making a clone of your repository and checking to see if you have met a few basic requirements. For example, did you use the right file name, and does your notebook run without error? These criteria will be specified for each assignment, and if you did not meet the criteria, you will get a report in a `static_check.md` file notifying you of any issues. We will make every attempt to run the static checks for the Programming Assignments every Monday, Wednesday and Friday at 8:45; however, depending on personnel, the times will be somewhat irregular. For practical purposes, you can assume that if your assignment is ready by 8:45 on Monday, Wednesday or Friday it will be checked by the end of the day.
+
+All Programming Assignments for a given quarter will be checked on Monday, Wednesday and Friday, until the last check of the quarter, which will be the **Monday of week 9**. At this point, you will get full credit (2.5 pts) for all Programming Assignments that have passed the static check. See the point breakdown on the [Project page](../projects) for how the Programming Assignments are included in the Project Portfolio.
+
+**Note about deadlines:** the times specified for the static are the _earliest_ time at which we will collect your work; it is your responsibility to make sure that your work is pushed to GitLab by this time, or you risk the chance of it not being checked until the next run. If you have made changes to your repository and the feedback in the static check file does not make sense, make sure you look at the time and day when it was run last, to see if your updates were actually taken into account.
+
+## Projects (P)
+
+Described on the [Project page](../projects).
\ No newline at end of file
diff --git a/assignments_group.md b/assignments_group.md
new file mode 100644
index 0000000..cd12bb2
--- /dev/null
+++ b/assignments_group.md
@@ -0,0 +1,120 @@
+---
+layout: page
+title: Group Assignments
+description: Overview of Group Assignments and policies for report writing, directory structure and code documentation.
+nav_order: 6
+nav_exclude: false
+permalink: /group_assignments/
+# math: mathjax
+---
+# Group Assignments
+
+Overview of projects and module policies for report writing, directory structure and code documentation.
+
+Group Assignments consist of the following elements:
+1. A set of digitial files in the form of a working directory that you work on with your group members and submit every Friday at the end of the in-class sessions.
+2. BuddyCheck, a weekly questionnaire administered via Brightspace to evaluate yourself and your group members.
+3. Weekly reflections to improve the performance of your group and keep issues from becoming serious; recommended to occur at the beginning of the Wednesday in-class sessions, but this can be flexible.  
+
+## Assessment
+
+Each project is assessed on four categories using a discrete set of numeric criteria (4) for each, described in the sections below, with the total grade computed as a weighted sum. Every project receives equal weight, except Project 1, which is not included in the grade. 
+
+### Deadlines for Feedback
+
+Feedback will be provided during the week after each project submission, and will be based on the files you submit via your GitLab repository. 
+- The deadline for submission is always Friday, 12:30 during the second week (although you can edit your GitLab repository until 13:30 to take care of technical issues, for example, fixing a merge conflict or uploading a file). Edits after that time will not be used for grading (this will be applied strictly starting with Project 4; Project 3 is an exception).
+- Some groups may be asked to make some changes based on the static check, but you will be only allowed to fix the issues reported in the `static_check.md`.
+
+Regarding questions about when you are allowed to make changes to your files:
+- You are _always_ allowed to continue working on your files, and to ask teachers about the content (this is highly encouraged!).
+- You are _not allowed_ to make changes to the answers and technical content (theory and code) of your files after Friday at 12:30 during the second week.
+
+We will use a _static check_ to evaluate your work after each Friday session. This involves the teaching team making a clone of your repository and checking to see if you have met a few basic requirements. For example, did you use the right file name, and does your notebook run without error? These criteria will be specified for each assignment, and if you did not meet the criteria, you will get a report in a `static_check.md` file notifying you of any issues.
+
+> Students that are just joining the Q2 projects as part of the completion of a previous year of MUDE are strongly encouraged to work through programming assignments PA03 and PA04 which introduce tips on how we encourage groups collaborate using _GitLab_. 
+
+### Grading Categories
+
+* **Documentation:** Readable and well-structured presentation of your results.
+* **Application:** Project specifications have been met and demonstrated.
+* **Programming:** Ensure that the implementation adequately commented and clear.
+* **Interpretation:** Findings reported based on good evidence and sound reasoning with good eng/sci insight displayed.
+
+Additional details about each grading category will be specified in the project description, and will be cumulative throughout the semester (especially for programming and documentation). For example, ifc week 1 focuses on using markdown cells and week 2 focuses on well-formatted figures as part of Project 1, you will be expected to produce markdown cells and well-formatted formatted figures in addition to the items specified in Project 2 during weeks 3 and 4.
+
+
+
+### Grading Criteria: Individual Project Reports
+
+> Updated for Q2 (Q1 used equal weights for each category)
+
+| Category | No Submission | Insufficient | Sufficient | Very good | Default Weight |
+|:------------:|:---:|:---:|:---:|:---:|:---:|
+| Documentation  | 0 | 1 | 3 | 5 | **0.15** |
+| Application  | 0 | 1 | 3 | 5 | **0.15** |
+| Programming  | 0 | 1 | 3 | 5 | **0.15** |
+| Interpretation  | 0 | 1 | 3 | 5 | **0.55** |
+
+This default assessment weight will be applied for each category, but this may vary based on the project. If different, actual weights will be specified in the project description.
+
+In general, we will expect you to submit a `Report.md` in markdown format. This file should be well-formatted with figures and text as necessary and any auxiliary files (like images) in a sub-directory. This document should summarize all findings in a clear and concise manner and will be the primary assessment piece. The `*.ipynb` will be checked to see how the findings have been determined. 
+
+
+### Grading Criteria: Project Portfolio
+
+The Project Portfolio will be determined based on a 200 point scale, which consists of the following elements:
+- Projects: Generally speaking, 10 points per week; projects are graded for a max. of 140 points (Project 1 excluded).
+- Programming Assignments: 2.5 points each for a maximum of 35 points (PA01 and PA02 not graded). 
+- Buddycheck: 2 points each for a maximum of 12 points (Projects 1 and 2 not included).
+- Free points: 13
+- Total: 200 points
+
+Because the projects are graded with a coarse +/-2 point scale, and the objective is to give you quick feedback about your progress for the week, the project portfolio grades are allocated using a discrete scale, as illustrated in the following table: 
+
+| Project Portfolio Grade | Points |
+| :---: | :---: |
+| <5.0 | <104 |
+| 5.0 | 104--123 |
+| 6.5 | 124--145 |
+| 7.5 | 146--161 |
+| 8.5 | 162--171 |
+| 9.0 | 172--181 |
+| 9.5 | 182--191 |
+| 10.0 | 192--200 |
+
+### Peer Feedback with Buddycheck
+
+*Buddycheck* is a learning tool designed to help peer evaluation amongst your group in a constructive and transparent way. A Buddycheck form must be submitted every week (you will recieve an announcement via Brightspace).
+
+In addition to providing an opportunity for you to reflect on the performance of your group, and your role therein, the MUDE team will monitor the results and help guide those that may not be contributing in a productive and/or conscientious way. MUDE instructors may reach out to groups or individuals throughout the module, if necessary, and may alter the terms of projects for individuals. If after an initial warning, a second warning is issued, it may elicit in removal from the group, and the project portfolio for that quarter must be [completed individually](#as-an-individual-student).
+
+## Documentation: Group Assignment Reports
+
+There are a number of requirements that will be enforced for the **Project Reports**, which will be submitted as a combination of **Jupyter Notebooks**, **Python** and **Markdown** files. While providing the capability to present a wide variety of rich formatting, as well as facilitating computation, it is easy to produce documents that are simply un-readable --- these reporting requirements are designed to prevent that. Despite being part of your project grade, these are generally good practices, and you will benefit by getting into the habit of applying these (and the [Golden Rules](../golden-rules)) in your daily practice. 
+
+To help you get familiar with notebooks and how they can be used to write readable reports, we will slowly introduce concepts to you throughout the module. For example, the project during weeks 1 and 2 will give you a mostly-completed notebook to start with, whereas by the end of Q2 you will be creating your own notebooks from scratch.
+
+We will go deeper into the expectations and requirements as the module progresses. 
+
+## Procedures and Conduct
+
+### As a Group
+
+Option 1 (default---and strongly recommended!)
+* submit each project report as specified (generally each Friday at 12:30) and participate fairly with your group and you will receive timely feedback and keep up with the course contents
+
+Option 2: you don't submit a project (or are unable to do so for any valid reason)
+* notify instructors as soon as possible that you are not able to submit a project
+
+If you receive an insufficient score for a single project you are not allowed an opportunity to repair this, unless you also have an insufficient for the entire Q1 or Q2 project portfolio.
+
+If you receive an insufficient (<5.8) for the Project Portfolio (both quarters combined), you must notify the instructors that you would like to do a resit prior to the first day of the 3rd quarter. A new assignment and timeline will be communicated to you shortly thereafter; this approach will result in maximum grade of 6.0 for the Project Portfolio.
+
+### As an Individual Student
+
+Students that have been removed from their group for any reason will complete the project portfolio for that quarter individually. This can be done in either quarter, with a maximum grade of 6.0. Completing the project portfolio in one quarter does not preclude participating in a group and receiving the group grade for the other quarter. The assignment scope and timeline will be communicated to you on a case-by-case basis.
+
+### Students from Previous Years
+
+You may find it useful to specifically review *Programming assignments PA03 and PA04* that concern the usage of Git into the projects and effective collaboration. If you did not follow the Git tutorial last year, you may find this a little confusing to navigate, so it may be worthwhile reviewing these and mentioning this to your project team.   
diff --git a/exams.md b/exams.md
new file mode 100644
index 0000000..fdf3cdf
--- /dev/null
+++ b/exams.md
@@ -0,0 +1,67 @@
+---
+layout: page
+title: Exams
+description: Overview of what to expect for the MUDE Q1 & Q2 Exams.
+nav_order: 7
+nav_exclude: false
+# math: mathjax
+---
+
+# Written Exams
+
+The exam schedules can be found in [MyTimetable](https://mytimetable.tudelft.nl/schedule) (but note that the exam room may change up to 1 week prior to the exam). Most importantly, remember:
+
+1. you must register for each MUDE exam separately, and 
+2. don't wait until the last minute---registration closes 2 weeks before the exam!
+
+[Exam registration requirements can be found here](https://www.tudelft.nl/en/student/education/courses-and-examinations/examinations/registration-for-examinations).
+
+## Exam Format
+
+Both exams (and resits) are paper-based. Scrap paper is provided, but answers will be written on the printed exam paper. Pre-programmed calculators, books and lectures notes are not allowed. The student must only bring writing and drawing materials, and a scientific calculator.
+
+Programming-specific questions will make up a maximum of 10% of the total exam grade and will be based on the topics and applications covered in the weekly Programming Assignments and Group Assignments. However, note that questions related to the non-programming part of the course may rely on code and programming concepts (for example, illustrating a numerical result in the form of Python output), so if you skip the programming part of the course entirely, you may impact much more than 10% of your exam grade. In other words: _complete your Programming Assignments and participate actively in the Group Assignments and you won't have a problem._
+
+As the exam is closed-book, we will provide equations as needed either with a **formula sheet** or directly in the printed exam document. You can find a sample exam [here](https://mude.citg.tudelft.nl/2023/files/Exams/){:target="_blank"} in the course files, which was printed on A4 paper for the exam.
+
+If you have questions about which formulas may be provided during the exam, use the Answers Platform (link in top right).
+
+## Sample Exams
+
+Exams and resits from last year are given here as an example of the format and content (they are also available via the general Files page). The PDF file shows the exam format that the student can expect in the exam (i.e., if printed on A4 paper, this is exactly where the answers would be written). The HTML files illustrate the exam questions and answers. 
+
+Note that for the 2022-2023 academic year the format of the module and specific topics were significantly different. This is indicated below. 
+
+Programming questions from previous years illustrate how programming will be asked, but not necessarily the content. As the scope of Programming Assignments changes from year to year, you may see topics that are unfamiliar to you. In this case, remember: _the content from the Programming Assignments this year dictates the scope of programming questions on the exam!_
+
+Where changes have been made, an indication is provided for which questions in each exam are relevant for Q1 and Q2 this year. See the following section for more details on changes from year to year.
+
+- **Exam Q1 2022:** [PDF Exam (no solution)](https://mude.citg.tudelft.nl/2023/files/Exams/22_Q1.pdf){:target="_blank"}and [HTML (solution)](https://mude.citg.tudelft.nl/2023/files/Exams/22_Q1.html){:target="_blank"}.
+  - Questions that apply for Q1 this year: 3 to 8.
+  - Questions that apply for Q2 this year: 2.
+- **Resit Q1 2022:** [PDF Exam (no solution)](https://mude.citg.tudelft.nl/2023/files/Exams/22_Q1_resit.pdf){:target="_blank"} and [HTML (solution)](https://mude.citg.tudelft.nl/2023/files/Exams/22_Q1_resit.html){:target="_blank"}.
+  - Questions that apply for Q1 this year: 3 to 8.
+  - Questions that apply for Q2 this year: 2.
+- **Exam Q2 2022:** [PDF Exam (no solution)](https://mude.citg.tudelft.nl/2023/files/Exams/22_Q2.pdf){:target="_blank"} and [HTML (solution)](https://mude.citg.tudelft.nl/2023/files/Exams/22_Q2.html){:target="_blank"}.
+  - Question that apply for Q1 this year: 2.
+  - Question that apply for Q2 this year: 3 to 10.
+- **Resit Q2 2022:** [PDF Exam (no solution)](https://mude.citg.tudelft.nl/2023/files/Exams/22_Q2_resit.pdf){:target="_blank"} and [HTML (solution)](https://mude.citg.tudelft.nl/2023/files/Exams/22_Q2_resit.html){:target="_blank"}.
+  - Question that apply for Q1 this year: 2
+  - Question that apply for Q2 this year: 3 to 12.
+
+### Detailed Overview of Changes from Previous Years
+
+The purpose of this section is to help you determine which exam questions from the sample exams are relevant for you this year. You are not expected to study the changes in MUDE contentss from year to year.
+
+The biggest change was between the 2022-2023 and 2023-2024 academic years. Specific differences include:
+- Inclusion of one week of finite volume method.
+- Finite difference no longer included in study material for Q2 (now in Q1).
+- Finite element material is reduced, relative to 2022.
+- Extreme value analysis is material is in Q2, but you have already covered it in Q1 of 2022.   
+
+Please also keep in mind the following when using the exams from 2022-2023:
+- Tthere were around 8 or 9 "Questions" on the exam, each with multiple sub-questions. This year there will be fewer "Questions," which of course means the value (in points) will be more for each of them.
+- The style of questions in the sample exams is representative of the style of questions you will see this year.
+- Some questions or portions of questions may make reference to topics that have not been covered in the current academic year. For example, 'W-test' in sensing in observation theory was not covered, so you may exclude this topic for your studies.
+- The scope of the exam is governed by the contents of the online textbook, and exceptions are stated in the book. If you see a discrepancy between the textbook and the sample exams, the textbook governs.
+- A portion of the questions this year will take inspiration from the assignments we have done on Wednesday and Friday (but not all of the questions); it would be wise to review this when preparing for the exam.
\ No newline at end of file
diff --git a/home.md b/home.md
index 7947bd6..c7563e5 100644
--- a/home.md
+++ b/home.md
@@ -14,18 +14,22 @@ seo:
 
 MUDE is a module at the Civil Engineering and Geosciences faculty of Delft University of Technology: {{ site.tagline }}, taken by all first year students in the MSc degree programs Applied Earth Sciences (AES), Environmental Engineering (EE) and Civil Engineering (CE).
 
-We hope you are looking forward to kicking off your MSc program with the first MUDE lecture on Tuesday, September 3rd!
 
-More information about the module will be provided in that session. For now you can see general information about the module [here](https://studiegids.tudelft.nl/a101_displayCourse.do?course_id=69347){:target="_blank"} as well as the course schedule via [MyTimetable](https://mytimetable.tudelft.nl/schedule){:target="_blank"}.
+## This Week
 
-We know you are busy getting ready for the start of the year, but if you have any free time we encourage you to take a look at [this page for incoming students](https://mude.citg.tudelft.nl/incoming/){:target="_blank"} and try reviewing some of the material, depending on your prior experience.
+*This page shows the most recent announcement and calendar. Frequently used pages are found via the links at the top right.*
 
-If you have personal questions, you may send a request to MUDE-CEG@tudelft.nl. Please reserve general questions about the module until the end of the first lecture.
+*See [Calendar](/2023/calendar) and [Weekly Schedule]({{ site.baseurl }}/schedule) for additional explanation.*
 
-If you would like more information about the course contents before the first lecture, you can take a look at the [contents from last year](https://mude.citg.tudelft.nl/2023/){:target="_blank"}, or our [interactive online textbook](https://mude.citg.tudelft.nl/2023/book/intro.html){:target="_blank"}, but please note there will be significant changes, so only use it to get a general idea for what to expect!
+### Most recent announcement
 
-We look forward to meeting you on Tuesday!
+{% if site.announcements %}
+{{ site.announcements.last }}
+[Previous Announcements](announcements){: .btn .btn-outline .fs-3 }
+{% endif %}
 
-Kind regards, 
 
-The MUDE Team.
\ No newline at end of file
+### Calendar for this week
+
+{{ site.modules.first }}
+[Previous Calendars](calendar){: .btn .btn-outline .fs-3 }
\ No newline at end of file
diff --git a/info.md b/info.md
new file mode 100644
index 0000000..68a4544
--- /dev/null
+++ b/info.md
@@ -0,0 +1,96 @@
+---
+layout: page
+title: Module Information
+description: General information about MUDE.
+nav_order: 1
+nav_exclude: false
+---
+
+<!-- <a href="" target="_blank"></a> -->
+<!-- [](.md) -->
+
+# Module Information
+
+An overview of the module and some key policies are described on this page, adding to the description provided in the <a href="https://studiegids.tudelft.nl/a101_displayCourse.do?course_id=69347" target="_blank">Study Guide</a>.
+
+_Updates to the material on this page will be accompanied by announcements in class during the Monday lectures and and via the [Announcements](..announcements/) page on this website._
+
+MUDE is built on a repetetive and consistent weekly schedule, which is illustrated on the [Schedule page](./schedule), along with a list of topics, by week.
+
+## Assessment
+
+Your total MUDE grade consists of 3 assessments:	
+- Exam at end of Q1 (resit in Q2) (25%)
+- Exam at end of Q2 (resit in Q3) (25%)
+- Assignment Portfolio (50%)
+
+You will pass the module if you obtained at least a 5.8 for the three individual components. There will be a resit opportunity for the exams. If the grade for your Assignment Portfolio is below 5.8, you will get the opportunity to submit a revised version for which you will get a 6.0 if judged sufficient.
+
+The exams are described further on the [Exam page of this website](./exams).
+
+The Assignment Portfolio consists of three components:
+
+**FILL ME IN**
+
+
+
+### Assignment Portfolio
+
+Assignment Portfolio includes weekly Group Assignments (80%) and Programming Assignments (20%). Note that the BuddyChecks are also required and make up 10% of the Group Assignments (10% overall MUDE grade). The ultimate deadline to submit all of the components of the Assignment Portfolio is the last Friday of instruction for the quarter (week 8) at 12:30 (the end of the last Friday classroom session). Please note, however, that a consistent weekly schedule has been incorporated into the course activities, in particular: bi-weekly feedback on the Group Assignment reports and weekly grading of the Programming Assignments. In addition, failure to cooperate with your group members may result in the requirement that you submit the Group Assignments individually. Please see the relevant pages on this website for further details.
+
+### Assignment Portfolio
+
+PA and GA.
+
+
+
+
+## MUDE Resources
+
+There are several primary resources for this module, each of which is also available with a quick-link in the top right corner of this website:
+- **MUDE Textbook**: this is where assigned reading is located, along with interactive exercises to practice and study the material. 
+- **Answers Platform** ([answers.citg.tudelft.nl](https://answers.citg.tudelft.nl/)) a [stack-exchange](https://stackexchange.com/){:target="_blank"} style question and answer platform; a place to collaborate with your teachers and fellow students. Everyone is encouraged to post questions _and_ answers!
+- **Course Files** ([mude.citg.tudelft.nl/2023/files/](https://mude.citg.tudelft.nl/2023/files/)): key files for the module are available at this URL for easy access, for example, weekly instructions, solutions or Group Assignments instructions. Often notebook files (`*.ipynb`) will be converted to HTML for easy online viewing; however the complete set of files required for an assignment (e.g., `*.py` or data files) will only be available via GitLab.
+- **GitLab**: starting in week 3 this will be our primary platform for sharing and submitting assignments, as well as receiving feedback. In Weeks 1 and 2 you will download your assignments from GitLab, but not submit them.
+- **Collegerama**: Our Monday lectures are available to stream online [here](https://collegeramavideoportal.tudelft.nl/catalogue/cegm1000/?academicYear=2023-2024-cegm1000).
+- **Brightspace:** this platform is used to ensure students receive important annoucements about the module contents and activities in a timely manner; however, they will typically be links to announcements made on this website. General announcements such as exam registration reminders will be posted to Brightpsace only. To make sure you never miss an announcement, get the Pulse app! An overview with instructions can be found [here](https://teaching-support.tudelft.nl/how-to-use-pulse/).
+
+Please note that content in the online textbook will be added throughout the module, and changes will be announced and documented as needed. When new content is added, it will be done in large chunks. Changes will not be made retroactively that impact the scope of the exams (in other words, you will never need to re-study material because it changed prior to the exam). Notifications of errors, corrections and suggestions for improvement are glady welcomed via the Answers platform and/or via the MUDE email address.
+
+## Questions and Answers
+
+There are a variety of ways to obtain answers to your MUDE-y questions, described in the sections below. Please try to be considerate when asking questions and provide enough detail and context to make it easier to understand what it is you need help with. In addition, don't forget to check the Answers platform to see if someone has already asked the same question, and to use the search function in the online textbook to look for relevant key words. do your best to Jupyter Book search function.  If you find a good resource online (i.e., outside the textbook), you can also share that via the Answers platform.
+
+
+### Answers Platform
+
+This is your go-to place to ask a question about technical content in the course, as well as other non-technical quesions, for example, exam or absence policies. We strongly encourage you to use the platform to both ask and answer questions. The platform works by providing (and discussing) answers to questions, then voting whether or not you find the answer to be useful. You can also track statistics as you participate in the platform, giving it a bit of a competitive side: we will be periodically awarding prizes to students who make exceptional contributions to the Answers platform throughout the semester! In addition, this is also a useful metric we have for selecting future MUDE TA's.
+
+Use the [Meta tab](https://answers.citg.tudelft.nl/categories/15){:target="_blank"} if you have questions for how the platform works (this is especially well-developed on the [page for the math department](https://answers.ewi.tudelft.nl/categories/2){:target="_blank"}).
+
+### Open Question Hours (Tuesday)
+
+Beginning in week 2, every Tuesday there is an optional question hour. Teachers and teaching assistants will be present to help you with any of your MUDE or programming questions. There are no teacher-led activities here, so you must come prepared with questions. Although we will do our best to answer them, it is recommended to post tto the Answers platform first. We will monitor the questions and be able to come to the session better prepared. Who knows---perhaps a fellow classmate or teacher will answer your question first!
+
+### Contacting MUDE Teachers
+
+Please avoid sending general questions about the module contents to the MUDE email address or individual teachers. You will be asked to post to the Answers platform. Worse, you deprive your fellow classmates the opportunity to learn from your question and answers, and to help each other learn the material. 
+
+### Personal Situations
+
+For relatively common situations such as missing an occasional lecture or in-class session, check the Answers platform and policy information on this website. If you still have a question about your personal situation, use the email address MUDE-CEG@tudelft.nl. This is monitored by multiple instructors and is your best chance to get a quick reply.
+
+## Attendance
+
+Attendance in class is highly encouraged for the Monday and Wednesday sessions to stay on top of the material. However, attendance is mandatory only for the Group Assignment sessions on Friday. You are allowed to miss one session without obtaining prior permission (and we don't need to know the reason), but you should inform MUDE staff by sending an email to MUDE-CEG@tudelft.nl. Perhaps more importantly, you should also inform your group members in advance! You are free to arrange with each other to share the workload and catch up if a group member misses a Friday session. If you expect to miss more than one Friday session, you should inform MUDE staff immediately.
+
+
+## Conduct
+
+We expect all students and staff to adhere to the TU Delft [Code of Conduct](https://www.tudelft.nl/en/about-tu-delft/strategy/integrity-policy/tu-delft-code-of-conduct).
+
+In terms of student work, we also expect an honest effort and integrity for all assignments. We will run plagiarism checks throughout the semester on your work, and incidents will be reported directly to the Board of Examiners (you can learn more about the policy <a href="https://www.tudelft.nl/en/student/ceg-student-portal/education/education-information/academic-attitude" target="_blank">here</a>). In order to avoid this, please follow the following guidelines when working on and submitting your MUDE assignments:
+- Reading and looking at each others work is OK, but avoid copy and paste of a) entire files, and b) small pieces of text or code
+- Using material from fellow students or the internet is OK to get inspiration and ideas, but if this is more than a small number of sentences or lines you should be clear and honest. For example, write down the names of students with whom you worked or note whether or not you developed a piece of the code from a ChatGPT answer.
+- Re-use material with a suitable license (for example, <a href="https://creativecommons.org/licenses/by/2.0/" target="_blank">Creative Commons CC-BY</a> allows re-use with proper acknowledgement).
+- Always: a) write code yourself as much as possible, and 2) understand what it is you are writing: this is a much better strategy for learning, and, while it may be slow at first, you will find that in the long run you will need to copy/paste less often!
diff --git a/multiyear.md b/multiyear.md
new file mode 100644
index 0000000..aea6b8d
--- /dev/null
+++ b/multiyear.md
@@ -0,0 +1,18 @@
+---
+layout: page
+title: Multiyear Students
+description: Policies and advice for students who are from previous years than the current one.
+# nav_order: 7
+nav_exclude: false
+# math: mathjax
+---
+
+# Students from Previous Years
+
+## Exams
+
+Students resitting the exam from previous years of MUDE are expected to write the the exam as-is; no alternative exam will be prepared. Review the Programming Assignments, Group Assignments and [online textbook](https://mude.citg.tudelft.nl/book/intro.html) to identify the changes; you can also ask the instructors in office hours. 
+
+It is also recommended that you follow activities, such as the workshops (WS) on Wednesday's, the Group Assignments (GA) on Friday's, and the weekly Programming Assignments (PA) as these are meant to help learn topics covered for the exam.
+
+Please talk to an instructor if you would like to find other students from previous years to work with. Unless you can commit to following the entire module as a "normal" student from this year, it is not possible to put you in a group with current students.
\ No newline at end of file
diff --git a/shedule.md b/shedule.md
new file mode 100644
index 0000000..1137816
--- /dev/null
+++ b/shedule.md
@@ -0,0 +1,20 @@
+---
+layout: page
+title: Schedule
+description: The weekly schedule and list of topics.
+nav_order: 2
+nav_exclude: false
+---
+
+<!-- Note that it is possible to assign flashy colours to the different kinds of events by editing `_sass/custom/schedule.scss` (N.B.: they match with the colours under the “Modules” tab!).
+It is relatively easy to update the events, their timings, or their locations, by editing `_schedules/weekly.md`. -->
+
+# Weekly Schedule and Overview of Topics
+
+## Weekly Schedule
+
+Below you can find an example outline of the typical weekly course schedule. One exception is Week 1 of Q1, which starts on a Tuesday.
+
+**INSERT IMAGE HERE**
+
+## Overview of Topics
\ No newline at end of file
diff --git a/staff.md b/staff.md
new file mode 100644
index 0000000..aff274c
--- /dev/null
+++ b/staff.md
@@ -0,0 +1,29 @@
+---
+layout: page
+title: Staff
+description: A listing of the MUDE Team.
+nav_order: 11
+---
+
+# Staff
+
+<!-- Staff information is stored in the `_staffers` directory and rendered according to the layout file, `_layouts/staffer.html`. -->
+
+## Instructors
+
+{% assign instructors = site.staffers | where: 'role', 'Instructor' %}
+{% for staffer in instructors %}
+{{ staffer }}
+{% endfor %}
+
+{% assign teaching_assistants = site.staffers | where: 'role', 'Teaching Assistant' %}
+{% assign num_teaching_assistants = teaching_assistants | size %}
+{% if num_teaching_assistants != 0 %}
+## The Student Army: our Teaching Assistants
+
+MUDE wouldn't be possible without our amazing team of teaching assistants!
+
+{% for staffer in teaching_assistants %}
+{{ staffer }}
+{% endfor %}
+{% endif %}
-- 
GitLab