HACKATHON: Class Website

Collectively build a site about the "People" in our class

Prototype

We have developed a prototype for this site using Wintersmith, a static website generator based on JavaScript. Currently, this prototype has a landing page that displays a list of individuals. Each link points to an individual’s page showing some basic information about the individual.

list-twopeople one-person

The Github repository for this site is

https://github.com/ucdd2-sp15/people

Time

1 hour

Specifications

By the end of the hackathon, we want the website to meet the following specifications:

  • Every student in the class should have a page about the student
  • The page should provide basic information about each student
  • The page should visually document each student’s learning challenge deliverables
  • The landing page should show a complete list of links to everyone’s page.

Process

Each week’s hackathon will use a two-level fork/pull process similar to the process used in team-based co-learning you have just done. Because this process is new and could be complex to some students who may be using Github for the first time, we will practice one more time here.

Team

Continue to work in the same team.

Fork

As a class, we will divide-and-conquer to get the site completed and achieve the hackathon’s objectives. This divide-and-conquer will proceed in two levels.

First, at the level of teams, each team will make only one fork from the source repository. The team leader is responsible for making this fork.

Second, at the level of individuals, each team member will make a personal fork from the team’s fork. In effect, each person will be working on his or her own fork of a fork.

Pull

After your work is done, first, make a pull request to your team’s fork. The team leader is responsible for accepting and merging this pull request.

After all the edits from individual forks are merged into your team’s work, the team leader will make a final pull request to the source respository. Then, the teaching staff will merge each team’s pull request.

Thorugh this two-step process, we hope to have everyone’s page added to this website.

Contents

Personal Page

  1. Create a new directory contents/people/[your-name] where [your-name] should be replaced by your real name.
  2. Take a look at contents/people/tomyeh. You will find index.md. Use this file as an example. This is written using Markdown. Copy this file to your directory and start making changes.
  3. Copy the screenshots you took earlier to this directory. Add references to these images in index.md.

Landing Page

Once you’ve created a new directory under contents/people and the index.md file in the directory, this new page will be automatically detected by Wintersmith’s build engine and a new link will be added to the landing page. You do not need to write any extra code for this to happen. You just need to check whether this does happen.

Milestones

  1. Have made a team’s fork as a team
  2. Have made your personal fork from the team’s fork
  3. Have previewed the skeleton website via your own computer’s localhost.
  4. Have created a new directory for yourself (e.g., contents/people/[your-name]) and create a file index.md in the directory
  5. Have added some information about yourself
  6. Have added a series screenshots about your learning challenges deliverables
  7. Have previewed the updated website with your personal page
  8. Have made a pull request to your team’s fork
  9. Have your pull request merged into your team’s fork
  10. Have everyone’s personal fork merged into your team’s fork
  11. Have everyone’s name to appear on the landing page in your team’s fork
  12. Have made a pull request from your team’s fork to the class’s repository