CS2103 Website

Live Website (redirected)

Setting up

1. Clone this repo.
2. Run git submodule update --init --recursive to pull the content of the submodule.
3. Install MarkBind

Updating content

1. Checkout the branch of the course e.g., cs2103
2. Update content using MarkBind syntax (How to use MarkBind)
3. markbind serve to start the local server (to preview changes). This command also initiates the live-preview ability i.e., when any changes to the MarkBind code is saved, the site is auto-generated and the Web page (that was opened by the serve command) auto-refreshes to show the new content. This works well for small websites but not so well for this website. Recommended to shutdown the server (Ctrl+C) before doing further edits.
4. When you are happy with the edits, use the markbind deploy to deploy to the GitHub website at the origin repo.
   1. If the deployment failed due to a 'caching' issue, try deleting the cache generated by the previous deploy command (on Windows, the cache can be found in /c/Users/{user-name}/AppData/Roaming/npm/node_modules/markbind-cli/node_modules/gh-pages/.cache)
5. If you need to update contents inside the book folder,
   1. Post an issue in the se-edu/se-book issue tracker to request for the change
   2. After the change has been done, pull the sub-module, and commit the changes to sub-module reference (when you pull a sub-module, Git automatically updates the submodule reference which is seen as a change in the enclosing repo).

      $ cd book
      $ git pull origin master
      $ cd ..
      $ git commit -am "sync with book"
      

   3. Deploy the website to make the updated book content visible to students

Bug reports, suggestions, change requests

• MarkBind bug reports and suggestions https://github.com/MarkBind/markbind/issues
• SE-Book bug reports and change requests se-edu/se-book issue tracker

Notable pages

/schedule/week1/index.html /schedule/week2/index.html /schedule/week3/index.html /schedule/week4/index.html /schedule/week5/index.html /schedule/week6/index.html /schedule/week7/index.html /schedule/week8/index.html /schedule/week9/index.html /schedule/week10/index.html /schedule/week11/index.html /schedule/week12/index.html /schedule/week13/index.html

/admin/courseOverview.html /admin/usingThisWebsite.html /admin/courseExpectations.html /admin/courseBriefings.html /admin/weeklySchedule.html /admin/lectures.html /admin/tutorials.html /admin/instructors.html /admin/textbooks.html /admin/programmingLanguages.html /admin/standardsAndConventions.html /admin/peerEvaluations.html /admin/tools.html /admin/exams.html /admin/participation.html /admin/gradeBreakdown.html

/admin/ip-overview.html /admin/ip-w2.html /admin/ip-w3.html /admin/ip-w4.html /admin/ip-w5.html /admin/ip-w6.html /admin/ip-w7.html /admin/ip-w8.html /admin/ip-grading.html

/admin/tp-overview.html /admin/tp-expectations.html /admin/tp-timeline.html /admin/tp-constraints.html /admin/tp-teams.html /admin/tp-w3.html /admin/tp-w4.html /admin/tp-w5.html /admin/tp-w6.html /admin/tp-w7.html /admin/tp-w8.html /admin/tp-w9.html /admin/tp-w10.html /admin/tp-w11.html /admin/tp-w12.html /admin/tp-w13.html /admin/tp-deliverables.html /admin/tp-ped.html /admin/tp-pe.html /admin/tp-grading.html /admin/tp-supervision.html

/admin/appendixA-principles.html /admin/appendixB-policies.html /admin/appendixC-faq.html /admin/appendixD-help.html /admin/appendixE-gitHub.html /admin/appendixF-teamworkIssues.html /admin/appendixG-troubleshooting.html

/admin/appendixH-tipsFromStudents.html