learn-co-curriculum / deploy-on-day-1 Goto Github PK

Page points to a lot of dead links.
Basics points to http://flatironschool.com/program.html

This lab just needs the website files for students to edit and upload.

the lab instructs one student to fork and add the other students as collaborators, but they don't have access to add collaborators to forks from learn-co students. need to come up with a better system for collaborating and include that in the instructions.

The instructions are for merging branches that are not part of a fork. There should be instructions on creating a pull request to the master of the fork (a lot of students were creating a pull request of their branch directly to master of learn-co-students).

cname file causes issues when deploying to GH pages. Suggest removing it

"Everyone at the table should then clone this forked repo."
I think we should be more explicit that students are cloning from the fork––maybe change it to:

Everyone at the table should clone the repo from the fork that one person at your table created. Do not clone directly from learn-co-curriculum.

/alumni is now a page of alumni stories, so these aren't good examples

The individual instructions regarding checking out a new branch could be a little more explicit. I think adding one extra line should clear things up:

"If you haven't already, switch to the branch you created. To make sure you're where you need to be, type git branch in your terminal. It should return the name of your assigned student emphazised with an asterisk and master. The asterisk indicates which branch you're on. It should not be master"