Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TECH ED] Cakes Co #51

Open
Priscilla-MacGatus opened this issue Sep 16, 2024 · 0 comments
Open

[TECH ED] Cakes Co #51

Priscilla-MacGatus opened this issue Sep 16, 2024 · 0 comments
Labels
HTML-CSS📅 🏕 Priority Mandatory This work is expected 🦑 Size Large 4-8 hours 🎯 Topic Iteration Prototyping, testing, analysing, and refining in a cycle of development 🎯 Topic Problem-Solving Breaking down problems and building up solutions 🎯 Topic Requirements Interpreting requirements with precision and accuracy 📅 Week 2 Assigned during Week 2 of this module

Comments

@Priscilla-MacGatus
Copy link
Owner

@sairaheta1 cloned issue Migracode-Barcelona/Module-HTML-CSS#38 on 2024-07-17:

Link to the coursework

https://github.com/CodeYourFuture/Module-HTML-CSS/tree/main/Cakes-Co

Why are we doing this?

This project is thinking about "mobile first" design. Developers build sites on computers/laptops, but most users are on phones. So we should make our designs work first on a phone, and then expand them for larger screens.

https://explodingtopics.com/blog/mobile-internet-traffic

(In some sectors this is more like 90%. Your company will track their own statistics on this with a tool like Google Analytics.)

Maximum time in hours

8

How to get help

Share your blockers in your class channel. Use the opportunity to refine your skill in Asking Questions like a developer.

Creating a Week 2 branch in Git

We previously learned about using branches in Git. To recap, branches are useful to "test" a set of commits. The main branch is treated as a special branch, where it only contains commits that all of your colleagues have agreed on.

To allow us to easily understand what has changed on your branch, it should always start from the main branch, not another branch. In other words, your branch should only contain commits for that one branch, not any other branches.

In your coursework, we want you to practice using Git in the way that you will when working as a developer. Because of this, when starting the Week 2 (or Week 3, Week 4, etc) coursework you should switch to the main branch before creating a new branch.

To do this:

  1. Using this clip, switch to the main branch 👉 https://youtube.com/clip/Ugkx2OzD279ry4XKFNpeyqJTeBqtrbGJfgRq

  2. Create a new branch as you learned previously

How to submit

  1. Fork to your Github account.

  2. Make a branch for this project. Make sure you have switched to the main branch first!

  3. Make regular small commits in this branch with clear messages.

  4. When you are ready, open a PR to the CYF repo, following the instructions in the PR template.

There are several projects in this repo. Make a new branch for each project.

gitGraph

    commit id: "start"

    branch feature/cakes-co

    commit id: "skeleton page code"

    commit id: "Fonts and colours"

    commit id: "mobile layout"

    commit id: "lighthouse audit revisions mobile"

    commit id: "desktop layout"

    commit id: "lighthouse audit revisions desktop"

    checkout main

    merge feature/cakes-co

Loading

How to review

  1. Complete your PR template

  2. Ask for review from a classmate or mentor

  3. Make changes based on their feedback

  4. Review and refactor again next week

Anything else?

https://css-tricks.com/how-to-develop-and-test-a-mobile-first-design-in-2021/

https://codepen.io/LucyMac/pen/MWvNBLo

Stretch: If you are already familiar with media queries, try using container queries to develop your learning.

@Priscilla-MacGatus Priscilla-MacGatus added 🏕 Priority Mandatory This work is expected 🦑 Size Large 4-8 hours 🎯 Topic Iteration Prototyping, testing, analysing, and refining in a cycle of development 🎯 Topic Requirements Interpreting requirements with precision and accuracy 🎯 Topic Problem-Solving Breaking down problems and building up solutions 📅 Week 2 Assigned during Week 2 of this module HTML-CSS📅 labels Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
HTML-CSS📅 🏕 Priority Mandatory This work is expected 🦑 Size Large 4-8 hours 🎯 Topic Iteration Prototyping, testing, analysing, and refining in a cycle of development 🎯 Topic Problem-Solving Breaking down problems and building up solutions 🎯 Topic Requirements Interpreting requirements with precision and accuracy 📅 Week 2 Assigned during Week 2 of this module
Projects
Status: Done
Development

No branches or pull requests

1 participant