CS 175: Project in AI (in Minecraft) Spring 2017
4.
If successful, your repo online,
github.com/USER/PROJECT
should have a
docs/
folder in it, which should
have the same structure as:
https://github.com/sameersingh/gh-skeleton/tree/master/docs
. If you
have any questions, post it on Piazza along with your repo URL, so that we can help you with it.
Once the
docs/
folder is created and contains the same structure as
https://github.com/sameersingh/
gh-skeleton/, it is time to make the website public! The owner, USER in this case, should now log in and:
1.
Go to Settings again, scroll down to the Github Pages section, and select the second option (master branch
/docs folder). If it is unavailable, you do not have a
docs/
folder in the root of your repo; ensure the file
structure is there, and return to this step.
2. Press Save, and it should say GitHub Pages source saved. at the top of the page.
3.
Now open a new tab, and go to
USER.github.io/PROJECT
. There should be a website there, and should
look exactly like http://sameersingh.github.io/gh-skeleton/.
Again, if you have any questions, post on Piazza how far you got, where you got stuck, and a link to the repository.
Now that your website is up, it’s time to make it yours. Any one of the group members can do the following:
1.
Edit
_
config.yml
and change the title from “PROJECT” to the name of the repository (do not make other
changes to this file unless you know what you’re doing). You can do these edits from Github website itself,
just navigate to the file and click the edit button (looks like a pencil icon). Commit and push your changes,
and in a few minutes, your website should change to reflect the new name on the front page and navigation
bar.
2.
(optional) Edit
index.md
to put whatever you want. If you use the Github website to make these edits, you
can use Preview button to see what the front page will look like. Just do not remove or edit the first four
lines (the stuff in between, and including, the
---
) unless you know what you are doing. Once you commit
and push your changes, you should see the website reflect it. The default text on this page has some basic
information about Markdown, and a link to a complete guide on how to format using Markdown.
3.
Edit
team.md
and replace the placeholders with your teammates and their UCINetIDs (
NOT
the student
ID number!). Unless you are familiar with Markdown, you don’t need to add anything else. If you want
to make more edits, or make it look prettier, just look up guides on Markdown, and edit it as you see fit.
For example, you can add more information if you like, such as photos, links to homepages, links to Github
profile, etc. Commit and push your changes, and in a few minutes, the team page of your website should
have the new information.
Advanced Users:
If you’re familiar with Github Pages, you can completely ignore
my skeleton (it’s pretty ugly and basic after all), and do whatever you like. The only
constraints are (1) you have to use the
docs/
method of Github Pages, (2) that
there should be a dedicated page for the team and one for the proposal (and later,
for other project submissions), and (3) the links to these pages should be obvious
from the main page.
2 Contents of the Proposal
2.1 Creating a Proposal Page (15 points)
You will notice that there is a greyed out link to the proposal in the navigation bar, that gives an error if you click
on it. This will change once you create a
docs/proposal.md
file with the following header as the first four lines:
1 ---
2 layout: default
3 title: Proposal
4 ---
The rest of the file should contain the rest of the proposal, using the Markdown format (headings start with
##
,
one for each section below, and regular text doesn’t need any formatting). Commit and push your new file, and the
link should be active in a few minutes. As long as you have a website and a proposal page, you’ll get these points.
Project Proposal UC Irvine 2/ 3