<< Week 1 | Main Page | Week 3 >>
- Creating responsive designs
- Using Pull Requests for collaboration
- Pull Requests
- Git & GitHub for Poets
- The Net Ninja: 11, 12
Incrementally develop a simple responsive web page.
Step-by-step collaboration practice:
- Git Workflow for Two (main exercise)
- Pull Request & Merge (extra exercise)
Revisit the project you built last week, but with collaboration!
In groups of ~3, choose one team member to be the main repository owner. They will generate a new repo from the w3-validation-starter & copy-paste this development strategy and this wireframe) into the new repo.
Next, divide the different user stories between team members and fill in their names on the copied development-strategy file. Team members will now fork the main group repository. Each member will now work independently on their own fork to develop their user story, sending a pull request to the main repo when they have finished.
After everyone has sent their pull requests, get back together and review each pull request together. Did you have many conflicts? Were you able to resolve the conflicts into a working web page?
- What is Responsive Design?
- CSS Games
- FCC, Responsive Web Design: exercises, video
- mmtuts: HTML & CSS
- 🥚 html-css-git-exercises - Week 2
- Complete the exercises in
week-2 - Push your work regularly to GitHub
- Complete the exercises in
- 🐣 HTML-CSS-Practice-Problems
- 🐣 css-exercises
This week's project is to study the app-theme tutorial from Traversy Media.
Writing the same code as Mr. Traversy's code is not enough! You are expected to submit your code from his tutorial in a new repository generated from this starter template. Your repository should be named app-theme and should be cleanly developed with one branch per step. It's up to you to write the development strategy!
You will be assessed not only on your live demo, but also on the quality of your code, the correctness of your branches, and the completeness of your repository. Your repository must contain:
- A README describing your project in detail. Check out these articles to learn more about writing good README's: makeareadme.com, bulldogjob, meakaakka
- One well-named branch per user story. If we check out any branch, it should contain only the code necessary to make that step work. and it should work!
- A file called
development-strategy.mdin which you explain how you broke the project into user stories, describe each user story, and describe what code you wrote to implement this user story. Check out the tomato timer code-along for an example.
There are two general paths you can take to get this finished repo, neither is better or worse. And if you find another way go for it!
- Two-Stepping: First - follow the tutorial studying the code and understanding the project. Second - go through the tutorial another time, this time around focusing on using branches to create a finished repository.
- One-Stepping: Follow the tutorial once more slowly, carefully building your finished repository as you go.