diff --git a/.github/FUNDING.yml b/.github/FUNDING.yml index b34cfcfc..335da9aa 100644 --- a/.github/FUNDING.yml +++ b/.github/FUNDING.yml @@ -1,13 +1,13 @@ -# These are supported funding model platforms - -github: CodeYourFuture -patreon: # Replace with a single Patreon username -open_collective: # Replace with a single Open Collective username -ko_fi: # Replace with a single Ko-fi username -tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel -community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry -liberapay: # Replace with a single Liberapay username -issuehunt: # Replace with a single IssueHunt username -otechie: # Replace with a single Otechie username -lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry -custom: https://codeyourfuture.io/donate +# These are supported funding model platforms + +github: CodeYourFuture +patreon: # Replace with a single Patreon username +open_collective: # Replace with a single Open Collective username +ko_fi: # Replace with a single Ko-fi username +tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel +community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry +liberapay: # Replace with a single Liberapay username +issuehunt: # Replace with a single IssueHunt username +otechie: # Replace with a single Otechie username +lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry +custom: https://codeyourfuture.io/donate diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml index 5fe8ffd0..3e43fc21 100644 --- a/.github/ISSUE_TEMPLATE/config.yml +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -1,14 +1,14 @@ -blank_issues_enabled: false -contact_links: - - name: CYF - url: contact@codeyourfuture.io - about: Please report serious issues here. - - name: Join CYF - url: https://codeyourfuture.io/volunteers/ - about: Join CYF here - - name: CYF Slack - url: codeyourfuture.slack.com - about: Come to #cyf-syllabus-tech and chat - - name: CYF Tech Ed - url: https://github.com/orgs/CodeYourFuture/teams/mentors - about: CYF mentors on Github +blank_issues_enabled: false +contact_links: + - name: CYF + url: contact@codeyourfuture.io + about: Please report serious issues here. + - name: Join CYF + url: https://codeyourfuture.io/volunteers/ + about: Join CYF here + - name: CYF Slack + url: codeyourfuture.slack.com + about: Come to #cyf-syllabus-tech and chat + - name: CYF Tech Ed + url: https://github.com/orgs/CodeYourFuture/teams/mentors + about: CYF mentors on Github diff --git a/.github/ISSUE_TEMPLATE/pd-assignment.yml b/.github/ISSUE_TEMPLATE/pd-assignment.yml index c8bd2298..3c739f74 100644 --- a/.github/ISSUE_TEMPLATE/pd-assignment.yml +++ b/.github/ISSUE_TEMPLATE/pd-assignment.yml @@ -1,59 +1,59 @@ -name: PD Coursework -description: Assign a piece of PD coursework -title: "[PD] " -labels: [PD, 🏝 Priority Stretch, 🐇 Size Small] -body: - - type: markdown - attributes: - value: | - Thanks for taking the time to assign this coursework! - - type: input - attributes: - label: Coursework content - validations: - required: true - - type: input - attributes: - label: Estimated time in hours - description: (PD has max 4 per week total) - validations: - required: true - - type: textarea - attributes: - label: What is the purpose of this assignment? - description: Clearly explain the purpose of this assignment and how trainees can evaluate this. - validations: - required: true - - type: textarea - attributes: - label: How to submit - description: State in clear steps how a trainee can submit this assignment. - placeholder: | - Copy the Google doc to your own Google Drive - Complete the work assigned - When you are ready, move your document to your class Drive - validations: - required: true - - type: textarea - attributes: - label: Anything else? - description: | - Links? References? Anything that will give more context - - Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in. - - type: markdown - attributes: - value: | - **Thank you so much.** - - Please now complete this ticket by filling in the options on the sidebar. - - 1. Update labels - - priority -- is this coursework key, mandatory, or stretch? - - size -- help trainees plan their time with rough estimation - 2. Add to project backlog - - add to the project named the same as this repo - - fill in custom fields -- priority, size, hours, week -- to match this issue - - Once your ticket is complete, you may like to check it out on the example project board attached to this repo. - This is so you understand how trainees will use your work. +name: PD Coursework +description: Assign a piece of PD coursework +title: "[PD] <title>" +labels: [PD, 🏝 Priority Stretch, 🐇 Size Small] +body: + - type: markdown + attributes: + value: | + Thanks for taking the time to assign this coursework! + - type: input + attributes: + label: Coursework content + validations: + required: true + - type: input + attributes: + label: Estimated time in hours + description: (PD has max 4 per week total) + validations: + required: true + - type: textarea + attributes: + label: What is the purpose of this assignment? + description: Clearly explain the purpose of this assignment and how trainees can evaluate this. + validations: + required: true + - type: textarea + attributes: + label: How to submit + description: State in clear steps how a trainee can submit this assignment. + placeholder: | + Copy the Google doc to your own Google Drive + Complete the work assigned + When you are ready, move your document to your class Drive + validations: + required: true + - type: textarea + attributes: + label: Anything else? + description: | + Links? References? Anything that will give more context + + Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in. + - type: markdown + attributes: + value: | + **Thank you so much.** + + Please now complete this ticket by filling in the options on the sidebar. + + 1. Update labels + - priority -- is this coursework key, mandatory, or stretch? + - size -- help trainees plan their time with rough estimation + 2. Add to project backlog + - add to the project named the same as this repo + - fill in custom fields -- priority, size, hours, week -- to match this issue + + Once your ticket is complete, you may like to check it out on the example project board attached to this repo. + This is so you understand how trainees will use your work. diff --git a/.github/ISSUE_TEMPLATE/tech-ed-assignment.yml b/.github/ISSUE_TEMPLATE/tech-ed-assignment.yml index 1bdba293..bb0a11bd 100644 --- a/.github/ISSUE_TEMPLATE/tech-ed-assignment.yml +++ b/.github/ISSUE_TEMPLATE/tech-ed-assignment.yml @@ -1,80 +1,80 @@ -name: Tech Ed Coursework -description: Assign a piece of technical coursework -title: "[TECH ED] <title>" -labels: [Tech Ed, 🏕 Priority Mandatory, 🐂 Size Medium] -body: - - type: markdown - attributes: - value: | - Thanks for taking the time to assign this coursework! - - To support our trainees with planning and prioritising their own learning journey, we want our coursework assignments to be more informative. - We don't just want to tell them what to do, we want to tell them stuff like: - - why we are doing it - - what it's "for" (problem-solving, debugging, etc) - - how long they should spend on it, maximum - - how to get help - - how to review it with answers - - how to get it reviewed from mentors and peers - - type: input - attributes: - label: Link to the coursework - validations: - required: true - - type: textarea - attributes: - label: Why are we doing this? - description: Clearly explain the purpose of this assignment - validations: - required: true - - type: input - attributes: - label: Maximum time in hours - description: (Tech has max 16 per week total) - validations: - required: true - - type: textarea - attributes: - label: How to get help - description: State simply how trainees can get help with this assignment - placeholder: | - Share your blockers in your class channel - https://syllabus.codeyourfuture.io/guides/asking-questions - - type: textarea - attributes: - label: How to submit - description: State in clear steps how a trainee can submit this assignment. - placeholder: | - Fork the repo to your own GitHub account - Make regular small commits with clear messages - When you are ready, open a Pull Request to the CYF repo - Make sure you fill in the PR template provided - validations: - required: true - - type: textarea - attributes: - label: How to review - description: How to get code review and how to self-review - - type: textarea - attributes: - label: Anything else? - description: | - Links? References? Anything that will give more context - - Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in. - - type: markdown - attributes: - value: | - **Thank you so much.** - - Please now complete this ticket by filling in the options on the sidebar. - - 1. Update labels - - priority -- is this coursework key, mandatory, or stretch? Pick one. - - size -- help trainees plan their time with rough estimation. Pick one - - topics -- add all that seem relevant to you. - 2. Add to milestone - - week 1,2,3,4 - - Once your ticket is complete, you may like to add it to the example project board attached to this repo. - This is so you understand how trainees will use your work. Nobody has built a board copier yet, so trainees will be doing this step themselves. +name: Tech Ed Coursework +description: Assign a piece of technical coursework +title: "[TECH ED] <title>" +labels: [Tech Ed, 🏕 Priority Mandatory, 🐂 Size Medium] +body: + - type: markdown + attributes: + value: | + Thanks for taking the time to assign this coursework! + + To support our trainees with planning and prioritising their own learning journey, we want our coursework assignments to be more informative. + We don't just want to tell them what to do, we want to tell them stuff like: + - why we are doing it + - what it's "for" (problem-solving, debugging, etc) + - how long they should spend on it, maximum + - how to get help + - how to review it with answers + - how to get it reviewed from mentors and peers + - type: input + attributes: + label: Link to the coursework + validations: + required: true + - type: textarea + attributes: + label: Why are we doing this? + description: Clearly explain the purpose of this assignment + validations: + required: true + - type: input + attributes: + label: Maximum time in hours + description: (Tech has max 16 per week total) + validations: + required: true + - type: textarea + attributes: + label: How to get help + description: State simply how trainees can get help with this assignment + placeholder: | + Share your blockers in your class channel + https://syllabus.codeyourfuture.io/guides/asking-questions + - type: textarea + attributes: + label: How to submit + description: State in clear steps how a trainee can submit this assignment. + placeholder: | + Fork the repo to your own GitHub account + Make regular small commits with clear messages + When you are ready, open a Pull Request to the CYF repo + Make sure you fill in the PR template provided + validations: + required: true + - type: textarea + attributes: + label: How to review + description: How to get code review and how to self-review + - type: textarea + attributes: + label: Anything else? + description: | + Links? References? Anything that will give more context + + Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in. + - type: markdown + attributes: + value: | + **Thank you so much.** + + Please now complete this ticket by filling in the options on the sidebar. + + 1. Update labels + - priority -- is this coursework key, mandatory, or stretch? Pick one. + - size -- help trainees plan their time with rough estimation. Pick one + - topics -- add all that seem relevant to you. + 2. Add to milestone + - week 1,2,3,4 + + Once your ticket is complete, you may like to add it to the example project board attached to this repo. + This is so you understand how trainees will use your work. Nobody has built a board copier yet, so trainees will be doing this step themselves. diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index 9b9cc912..a64cec1f 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -1,32 +1,32 @@ -<!-- - -You must title your PR like this: - -COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK - -For example, - -NW4 | Carol Owen | HTML-CSS-Module | Week1 - -Complete the task list below this message. -If your PR is rejected, check the task list. - ---> - -## Learners, PR Template - -Self checklist - -- [ ] I have committed my files one by one, on purpose, and for a reason -- [ ] I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK -- [ ] I have tested my changes -- [ ] My changes follow the [style guide](https://syllabus.codeyourfuture.io/guides/code-style-guide/) -- [ ] My changes meet the [requirements](./README.md) of this task - -## Changelist - -Briefly explain your PR. - -## Questions - -Ask any questions you have for your reviewer. +<!-- + +You must title your PR like this: + +COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK + +For example, + +NW4 | Carol Owen | HTML-CSS-Module | Week1 + +Complete the task list below this message. +If your PR is rejected, check the task list. + +--> + +## Learners, PR Template + +Self checklist + +- [ ] I have committed my files one by one, on purpose, and for a reason +- [ ] I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK +- [ ] I have tested my changes +- [ ] My changes follow the [style guide](https://syllabus.codeyourfuture.io/guides/code-style-guide/) +- [ ] My changes meet the [requirements](./README.md) of this task + +## Changelist + +Briefly explain your PR. + +## Questions + +Ask any questions you have for your reviewer. diff --git a/.gitignore b/.gitignore index 04ad57f2..44b6361c 100644 --- a/.gitignore +++ b/.gitignore @@ -1,4 +1,4 @@ -**/.DS_Store -.DS_Store -node_modules/ +**/.DS_Store +.DS_Store +node_modules/ .vscode/ \ No newline at end of file diff --git a/.prettierrc b/.prettierrc index 59bb3b44..b0985c10 100644 --- a/.prettierrc +++ b/.prettierrc @@ -1,19 +1,19 @@ -{ - "arrowParens": "always", - "bracketSpacing": true, - "embeddedLanguageFormatting": "auto", - "htmlWhitespaceSensitivity": "css", - "insertPragma": false, - "jsxBracketSameLine": false, - "jsxSingleQuote": false, - "printWidth": 80, - "proseWrap": "preserve", - "quoteProps": "as-needed", - "requirePragma": false, - "semi": true, - "singleQuote": false, - "tabWidth": 2, - "trailingComma": "es5", - "useTabs": false, - "vueIndentScriptAndStyle": false -} +{ + "arrowParens": "always", + "bracketSpacing": true, + "embeddedLanguageFormatting": "auto", + "htmlWhitespaceSensitivity": "css", + "insertPragma": false, + "jsxBracketSameLine": false, + "jsxSingleQuote": false, + "printWidth": 80, + "proseWrap": "preserve", + "quoteProps": "as-needed", + "requirePragma": false, + "semi": true, + "singleQuote": false, + "tabWidth": 2, + "trailingComma": "es5", + "useTabs": false, + "vueIndentScriptAndStyle": false +} diff --git a/.vscode/extensions.json b/.vscode/extensions.json index 25549074..e5d4ef3e 100644 --- a/.vscode/extensions.json +++ b/.vscode/extensions.json @@ -1,10 +1,10 @@ -{ - "recommendations": [ - "esbenp.prettier-vscode", - "dbaeumer.vscode-eslint", - "streetsidesoftware.code-spell-checker", - "eamodio.gitlens", - "ritwickdey.LiveServer", - "vsliveshare.vsliveshare" - ] -} +{ + "recommendations": [ + "esbenp.prettier-vscode", + "dbaeumer.vscode-eslint", + "streetsidesoftware.code-spell-checker", + "eamodio.gitlens", + "ritwickdey.LiveServer", + "vsliveshare.vsliveshare" + ] +} diff --git a/Cakes-Co/index.html b/Cakes-Co/index.html index e288162a..9f2c47ed 100644 --- a/Cakes-Co/index.html +++ b/Cakes-Co/index.html @@ -1,58 +1,58 @@ -<!DOCTYPE html> -<html lang="en"> - <head> - <meta charset="UTF-8" /> - <meta name="viewport" content="width=device-width, initial-scale=1.0" /> - <meta http-equiv="X-UA-Compatible" content="ie=edge" /> - <title>Responsive Cake webpage - - - - - -
- logo -
- - -

The best cakes in town delivered to your door

-
-
- -
-
-

Welcome

-

- Lorem ipsum dolor sit amet consectetur, adipisicing elit. Quae - voluptatem accusantium, necessitatibus cum accusamus, id cumque harum - voluptates ipsum nisi vero illo dolore! Doloribus, quae hic. Facilis - voluptate nobis eum. -

-
-
- vanilla chocolate cake -
-
- - - - -
-
- - - - - - - + + + + + + + Responsive Cake webpage + + + + + +
+ logo +
+ + +

The best cakes in town delivered to your door

+
+
+ +
+
+

Welcome

+

+ Lorem ipsum dolor sit amet consectetur, adipisicing elit. Quae + voluptatem accusantium, necessitatibus cum accusamus, id cumque harum + voluptates ipsum nisi vero illo dolore! Doloribus, quae hic. Facilis + voluptate nobis eum. +

+
+
+ vanilla chocolate cake +
+
+ + + + +
+
+ + + + + + + diff --git a/Cakes-Co/readme.md b/Cakes-Co/readme.md index fda14034..55d06ba8 100644 --- a/Cakes-Co/readme.md +++ b/Cakes-Co/readme.md @@ -1,70 +1,70 @@ -# Cakes Co STRETCH - -The objective of this exercise is to create a responsive webpage showcasing your imaginary cake business. You are not required to found an actual cake business, but cakes brought to class this week will be welcomed with joy. - -## Learning Objectives - -- Translate wireframe designs to a fully featured web page. -- Implement a responsive design using the Mobile First approach -- Adapt the page layout for larger screens using media queries -- Select appropriate fonts and color schemes to create an aesthetically pleasing design -- Use hover/focus effects to add interactivity to buttons and images - -## Requirements - -This project develops your skills in creating responsive webpages using the Mobile First approach. You are expected to have a basic understanding of HTML and CSS. - -Start by implementing the mobile design in HTML and CSS. Then use media queries to adapt the layout for larger screens. Use `min-width` for your media queries and create three different variants of the layout using two different breakpoints. - -Choose appropriate fonts and colors and find visually appealing cake pictures to replace the placeholders in the wireframes. You are encouraged to add hover/focus effects to buttons and images to enhance interactivity. - -Make sure that all elements are visible and functional on both mobile and desktop devices. - -## Acceptance Criteria - -- [ ] The webpage is responsive and follows the Mobile First approach -- [ ] The layout adapts appropriately for larger screens using media queries -- [ ] Fonts and colors are selected appropriately and cake pictures are visually appealing -- [ ] The webpage includes hover effects to add interactivity -- [ ] All elements are visible and function as intended on both mobile and desktop devices according to the wireframes -- [ ] Your page scores 100 on Lighthouse Accessibility -- [ ] Your site is deployed to Netlify and the link is included in your PR message. - -## Tips for success - -When you're ready to start coding: - -### Start with mobile - -- Write the HTML following the mobile design -- Then write your CSS for everything to look great on mobile -- Remember to link your CSS file to your HTML file inside the `` in `index.html` -- You don't need to use any media queries yet, because we're following a [Mobile First](https://www.invisionapp.com/inside-design/mobile-first-design/) approach! - -### Then adapt the page for larger screens - -- Now add media queries to your CSS, and change the layout and sizing of elements so they make better use of a wider screen (see the desktop wireframe design below). -- To follow Mobile First principles, we will only be using `min-width` in our media queries (no max-width!) -- You should **use 2 different breakpoints**, meaning you should have **3** different variants of your layout. Here's an example. - - If we have the following **2 breakpoints**: - - > - breakpoint 1 --> 540px - > - breakpoint 2 --> 900px - - Then our CSS code will be split into **3**: - - > 1. **"default"**: default styles, should implement the mobile design (no media query used for these). These styles will apply to all screen sizes by default. - > 2. **"medium"**: Our first media query `@media (min-width: 540px) {...}` **will overwrite our default styles** for screens at least 540px wide. Screens _below_ 540px will apply the styles from the "default". - > 3. **"large"**: Our second media query `@media (min-width: 900px) {...}` **will overwrite our default AND medium styles** for screens at least 900px wide (no upper limit). - -### Define your own style - -- Choose 1-2 fonts to use (lots of [free fonts here](https://fonts.google.com/)) -- Choose 2-3 colours that you think go together well, and try to limit yourself to those in your CSS ([look here at palettes](https://coolors.co/palettes/trending) for inspiration) -- Select some nice cake pictures to replace the placeholders in the wireframes (good [photo source here](https://unsplash.com/images/food/cake)). -- Get creative! Can you add some cool hover/focus effects to buttons and [images](https://www.wix.com/website-template/view/html/1911?siteId=c1c72d26-c040-41f2-80ce-0b0f8aef01b4&metaSiteId=5d77fab8-f068-4228-8b61-4181af054ca6&originUrl=https%3A%2F%2Fwww.wix.com%2Fwebsite%2Ftemplates&tpClick=view_button)? - -### Also - -- It's up to you to find a solution for any elements that are visible in desktop and not on mobile - and vice versa. +# Cakes Co STRETCH + +The objective of this exercise is to create a responsive webpage showcasing your imaginary cake business. You are not required to found an actual cake business, but cakes brought to class this week will be welcomed with joy. + +## Learning Objectives + +- Translate wireframe designs to a fully featured web page. +- Implement a responsive design using the Mobile First approach +- Adapt the page layout for larger screens using media queries +- Select appropriate fonts and color schemes to create an aesthetically pleasing design +- Use hover/focus effects to add interactivity to buttons and images + +## Requirements + +This project develops your skills in creating responsive webpages using the Mobile First approach. You are expected to have a basic understanding of HTML and CSS. + +Start by implementing the mobile design in HTML and CSS. Then use media queries to adapt the layout for larger screens. Use `min-width` for your media queries and create three different variants of the layout using two different breakpoints. + +Choose appropriate fonts and colors and find visually appealing cake pictures to replace the placeholders in the wireframes. You are encouraged to add hover/focus effects to buttons and images to enhance interactivity. + +Make sure that all elements are visible and functional on both mobile and desktop devices. + +## Acceptance Criteria + +- [ ] The webpage is responsive and follows the Mobile First approach +- [ ] The layout adapts appropriately for larger screens using media queries +- [ ] Fonts and colors are selected appropriately and cake pictures are visually appealing +- [ ] The webpage includes hover effects to add interactivity +- [ ] All elements are visible and function as intended on both mobile and desktop devices according to the wireframes +- [ ] Your page scores 100 on Lighthouse Accessibility +- [ ] Your site is deployed to Netlify and the link is included in your PR message. + +## Tips for success + +When you're ready to start coding: + +### Start with mobile + +- Write the HTML following the mobile design +- Then write your CSS for everything to look great on mobile +- Remember to link your CSS file to your HTML file inside the `` in `index.html` +- You don't need to use any media queries yet, because we're following a [Mobile First](https://www.invisionapp.com/inside-design/mobile-first-design/) approach! + +### Then adapt the page for larger screens + +- Now add media queries to your CSS, and change the layout and sizing of elements so they make better use of a wider screen (see the desktop wireframe design below). +- To follow Mobile First principles, we will only be using `min-width` in our media queries (no max-width!) +- You should **use 2 different breakpoints**, meaning you should have **3** different variants of your layout. Here's an example. + + If we have the following **2 breakpoints**: + + > - breakpoint 1 --> 540px + > - breakpoint 2 --> 900px + + Then our CSS code will be split into **3**: + + > 1. **"default"**: default styles, should implement the mobile design (no media query used for these). These styles will apply to all screen sizes by default. + > 2. **"medium"**: Our first media query `@media (min-width: 540px) {...}` **will overwrite our default styles** for screens at least 540px wide. Screens _below_ 540px will apply the styles from the "default". + > 3. **"large"**: Our second media query `@media (min-width: 900px) {...}` **will overwrite our default AND medium styles** for screens at least 900px wide (no upper limit). + +### Define your own style + +- Choose 1-2 fonts to use (lots of [free fonts here](https://fonts.google.com/)) +- Choose 2-3 colours that you think go together well, and try to limit yourself to those in your CSS ([look here at palettes](https://coolors.co/palettes/trending) for inspiration) +- Select some nice cake pictures to replace the placeholders in the wireframes (good [photo source here](https://unsplash.com/images/food/cake)). +- Get creative! Can you add some cool hover/focus effects to buttons and [images](https://www.wix.com/website-template/view/html/1911?siteId=c1c72d26-c040-41f2-80ce-0b0f8aef01b4&metaSiteId=5d77fab8-f068-4228-8b61-4181af054ca6&originUrl=https%3A%2F%2Fwww.wix.com%2Fwebsite%2Ftemplates&tpClick=view_button)? + +### Also + +- It's up to you to find a solution for any elements that are visible in desktop and not on mobile - and vice versa. diff --git a/Cakes-Co/style.css b/Cakes-Co/style.css index 5dccf293..bbcf4376 100644 --- a/Cakes-Co/style.css +++ b/Cakes-Co/style.css @@ -1,153 +1,153 @@ -* { - margin: 0px; - padding: 0px; -} -*::before, -*::after { - box-sizing: border-box; - margin: 0px; - padding: 0px; -} -img { - width: 100%; - height: 100%; -} -:root { - --bar-width: 30px; - --bar-height: 5px; - --gap: 30px; -} - -.logo-img { - width: 100px; - height: 100px; - align-self: center; -} -header { - background-color: blanchedalmond; - width: auto; - height: 140px; - display: flex; - justify-content: space-between; - align-items: stretch; - padding: 30px; -} -.inner-header { - display: flex; - flex-direction: column; - justify-content: space-between; - align-items: flex-end; -} -.motto-p { - text-align: right; - max-width: 20ch; -} - -.ham-label { - display: flex; - flex-direction: column; - gap: 5px; - z-index: 3; -} - -.ham-label input, -.ham-label::before, -.ham-label::after { - content: ""; - width: var(--bar-width); - height: var(--bar-height); - background-color: black; -} - -.ham-label input { - appearance: none; - outline: none; - pointer-events: none; -} - -.menu-aside { - position: absolute; - background-color: grey; - width: 220px; - height: 400px; - top: 0px; - right: 0px; - z-index: 2; - display: none; -} - -.ham-label:has(input:checked) + .menu-aside { - display: block; -} - -nav { - width: 100%; - height: 100%; - display: flex; - flex-direction: column; - align-items: center; - justify-content: center; -} - -main { - display: grid; - grid-template-columns: 1fr; - grid-template-rows: repeat(3, auto); - gap: var(--gap); -} - -.p-sec { - grid-column: 1/-1; - grid-row: 1/2; -} -.hero-sec { - grid-column: 1/-1; - grid-row: 2/3; -} -.img-sec { - grid-column: 1/-1; - grid-row: 3/-1; - - display: grid; - grid-template-columns: repeat(2, 1fr); - grid-template-rows: repeat(2, auto); - gap: var(--gap); -} - -@media screen and (min-width: 640px) { - main { - margin-top: 100px; - grid-template-columns: repeat(2, 1fr); - grid-template-rows: 2fr 1fr; - } - .p-sec { - grid-column: 2/-1; - grid-row: 1/2; - } - .hero-sec { - grid-column: 1/2; - grid-row: 1/2; - } - - .img-sec { - grid-column: 1/-1; - grid-row: 2/-1; - - grid-template-columns: repeat(4, 1fr); - grid-template-rows: auto; - } - - .ham-label { - display: none; - } - .menu-aside { - position: absolute; - background-color: grey; - width: 220px; - height: 400px; - top: 0px; - right: 0px; - z-index: 2; - display: block; - } -} +* { + margin: 0px; + padding: 0px; +} +*::before, +*::after { + box-sizing: border-box; + margin: 0px; + padding: 0px; +} +img { + width: 100%; + height: 100%; +} +:root { + --bar-width: 30px; + --bar-height: 5px; + --gap: 30px; +} + +.logo-img { + width: 100px; + height: 100px; + align-self: center; +} +header { + background-color: blanchedalmond; + width: auto; + height: 140px; + display: flex; + justify-content: space-between; + align-items: stretch; + padding: 30px; +} +.inner-header { + display: flex; + flex-direction: column; + justify-content: space-between; + align-items: flex-end; +} +.motto-p { + text-align: right; + max-width: 20ch; +} + +.ham-label { + display: flex; + flex-direction: column; + gap: 5px; + z-index: 3; +} + +.ham-label input, +.ham-label::before, +.ham-label::after { + content: ""; + width: var(--bar-width); + height: var(--bar-height); + background-color: black; +} + +.ham-label input { + appearance: none; + outline: none; + pointer-events: none; +} + +.menu-aside { + position: absolute; + background-color: grey; + width: 220px; + height: 400px; + top: 0px; + right: 0px; + z-index: 2; + display: none; +} + +.ham-label:has(input:checked) + .menu-aside { + display: block; +} + +nav { + width: 100%; + height: 100%; + display: flex; + flex-direction: column; + align-items: center; + justify-content: center; +} + +main { + display: grid; + grid-template-columns: 1fr; + grid-template-rows: repeat(3, auto); + gap: var(--gap); +} + +.p-sec { + grid-column: 1/-1; + grid-row: 1/2; +} +.hero-sec { + grid-column: 1/-1; + grid-row: 2/3; +} +.img-sec { + grid-column: 1/-1; + grid-row: 3/-1; + + display: grid; + grid-template-columns: repeat(2, 1fr); + grid-template-rows: repeat(2, auto); + gap: var(--gap); +} + +@media screen and (min-width: 640px) { + main { + margin-top: 100px; + grid-template-columns: repeat(2, 1fr); + grid-template-rows: 2fr 1fr; + } + .p-sec { + grid-column: 2/-1; + grid-row: 1/2; + } + .hero-sec { + grid-column: 1/2; + grid-row: 1/2; + } + + .img-sec { + grid-column: 1/-1; + grid-row: 2/-1; + + grid-template-columns: repeat(4, 1fr); + grid-template-rows: auto; + } + + .ham-label { + display: none; + } + .menu-aside { + position: absolute; + background-color: grey; + width: 220px; + height: 400px; + top: 0px; + right: 0px; + z-index: 2; + display: block; + } +} diff --git a/Form-Controls/README.md b/Form-Controls/README.md index a163d4de..bc001c42 100644 --- a/Form-Controls/README.md +++ b/Form-Controls/README.md @@ -1,66 +1,66 @@ -# HTML/ CSS - -## Forms, styling forms, and Devtools - -## Aims - -- Interpret requirements -- Write a valid form -- Style form controls -- Test with Devtools -- Refactor using Devtools - -## Task - -We are selling t-shirts. Write a form to collect the following data: - -Our customers already have accounts, so we know their addresses and charging details already. We don't need to collect that data. We want to confirm they are the right person, then get them to choose a colour and then pick a delivery date. - -Writing that out as a series of questions to ask yourself: - -1. What is the customer's name? I must collect this data, and validate it. But what is a valid name? I must decide something. -2. What is the customer's email? I must make sure the email is valid. Email addresses have a consistent pattern. -3. What colour should this t-shirt be? I must give 3 options. How will I make sure they don't pick other colours? -4. What size does the customer want? I must give the following 6 options: XS, S, M, L, XL, XXL -5. When do they want the t-shirt to be delivered? I must collect a date and make sure that date is in the next four weeks. How will I do this? How will I make sure there are no mistakes about the date? - -All fields are required. -Do not write a form action for this project. - -## Developers must test their work. - -Let's write out our testable criteria: - -- [ ] I have used HTML and CSS only. - -### HTML - -- [ ] My form is semantic html. -- [ ] All inputs have associated labels. -- [ ] My Lighthouse Accessibility score is 100. -- [ ] I require a valid name. I have defined a valid name as a text string of two characters or more. -- [ ] I require a valid email. -- [ ] I require one colour from a defined set of 3 colours. -- [ ] I require one size from a defined set of 6 sizes. -- [ ] I require one date from a constrained date range. - -### CSS - -- [ ] I show which element is focused. -- [ ] My Lighthouse Accessibility score is 100. - -## Extension Task - -If you have done all these things and you would like a really big challenge, run a further test and refactor your code. - -- In Chrome Devtools, open the Command Palette - https://developer.chrome.com/docs/devtools/command-menu/ -- Type 'coverage' and open the Coverage drawer - https://developer.chrome.com/docs/devtools/coverage/ -- Refactor your code until you have no unused CSS, or as close to that as you can get. Prettier will prevent you minifying your code so the last few bytes are out of your reach, sorry! -- This challenge isn't about writing less CSS, it's about writing less _pointless_ CSS, so don't remove code that is actually being used in your layout. -- Insider tip: you might have to select some elements so their focus states don't get miscounted as unused. You can force state in Devtools: - https://twitter.com/ChromeDevTools/status/986992837127319552 -- Take a screenshot of your coverage stats. - -Sanity check: this extension is tough! Try it in your own time and don't let it hold up your coursework submission. +# HTML/ CSS + +## Forms, styling forms, and Devtools + +## Aims + +- Interpret requirements +- Write a valid form +- Style form controls +- Test with Devtools +- Refactor using Devtools + +## Task + +We are selling t-shirts. Write a form to collect the following data: + +Our customers already have accounts, so we know their addresses and charging details already. We don't need to collect that data. We want to confirm they are the right person, then get them to choose a colour and then pick a delivery date. + +Writing that out as a series of questions to ask yourself: + +1. What is the customer's name? I must collect this data, and validate it. But what is a valid name? I must decide something. +2. What is the customer's email? I must make sure the email is valid. Email addresses have a consistent pattern. +3. What colour should this t-shirt be? I must give 3 options. How will I make sure they don't pick other colours? +4. What size does the customer want? I must give the following 6 options: XS, S, M, L, XL, XXL +5. When do they want the t-shirt to be delivered? I must collect a date and make sure that date is in the next four weeks. How will I do this? How will I make sure there are no mistakes about the date? + +All fields are required. +Do not write a form action for this project. + +## Developers must test their work. + +Let's write out our testable criteria: + +- [ ] I have used HTML and CSS only. + +### HTML + +- [ ] My form is semantic html. +- [ ] All inputs have associated labels. +- [ ] My Lighthouse Accessibility score is 100. +- [ ] I require a valid name. I have defined a valid name as a text string of two characters or more. +- [ ] I require a valid email. +- [ ] I require one colour from a defined set of 3 colours. +- [ ] I require one size from a defined set of 6 sizes. +- [ ] I require one date from a constrained date range. + +### CSS + +- [ ] I show which element is focused. +- [ ] My Lighthouse Accessibility score is 100. + +## Extension Task + +If you have done all these things and you would like a really big challenge, run a further test and refactor your code. + +- In Chrome Devtools, open the Command Palette + https://developer.chrome.com/docs/devtools/command-menu/ +- Type 'coverage' and open the Coverage drawer + https://developer.chrome.com/docs/devtools/coverage/ +- Refactor your code until you have no unused CSS, or as close to that as you can get. Prettier will prevent you minifying your code so the last few bytes are out of your reach, sorry! +- This challenge isn't about writing less CSS, it's about writing less _pointless_ CSS, so don't remove code that is actually being used in your layout. +- Insider tip: you might have to select some elements so their focus states don't get miscounted as unused. You can force state in Devtools: + https://twitter.com/ChromeDevTools/status/986992837127319552 +- Take a screenshot of your coverage stats. + +Sanity check: this extension is tough! Try it in your own time and don't let it hold up your coursework submission. diff --git a/Form-Controls/index.html b/Form-Controls/index.html index 4344b144..ee534b22 100644 --- a/Form-Controls/index.html +++ b/Form-Controls/index.html @@ -1,28 +1,64 @@ - - - - - - My form exercise - - - - - -
-

Product Pick

-
-
-
- - -
- -
- - - + + + + + + My form exercise + + + + + +
+

Product Pick

+
+
+
+
+ + +
+
+ + +
+ +
+ + +
+
+ + +
+
+ + +
+ + + + +
+ +
+ + + \ No newline at end of file diff --git a/Form-Controls/styles.css b/Form-Controls/styles.css index e69de29b..fefe00b4 100644 --- a/Form-Controls/styles.css +++ b/Form-Controls/styles.css @@ -0,0 +1,40 @@ +body { + background: rgb(211, 198, 198); + text-align: center; + +} + +.form { + text-align: left; + margin: auto; + font-size: 30px; + width: 500px; + padding: 20px; + background-color: #f4f4f4; + border-radius: 8px; +} + +.form input { + margin: 10px; + padding: 10px; + width: 80%; + +} + +select { + margin: 10px; + width: 90%; + padding: 10px; + font-size: 20px; +} + +button { + margin: 20px; + padding: 10px 12px; + background: rgb(190, 178, 178); + border: none; + border-radius: 5px; + color: #3b3f44; + font-weight: bolder; + font-size: 20px; +} \ No newline at end of file diff --git a/HOW_TO_REVIEW.md b/HOW_TO_REVIEW.md index 5e4a009f..bce1ba2e 100644 --- a/HOW_TO_REVIEW.md +++ b/HOW_TO_REVIEW.md @@ -1,62 +1,62 @@ -# Everyone reviews code at CYF - -https://curriculum.codeyourfuture.io/guides/reviewing/ - -Mentors and participants all review code, and collaborate on improving code quality. We are all helping each other to talk, write, and think about code more clearly. - -We are not reviewing code as if we were to merge this PR into production; we are opening a technical conversation for the purpose of insight and development. - -## Key points: - -1. Ask questions instead of making statements: - - **YES:** "Is there another element you could use to group a set of fields in a form? Why might someone use a different element in a form?" - **NO:** "Use fieldset not divs" - -2. Encourage simplicity, clarity, and precision: - - **YES** "There are 15,0000 files in this changelist. Which files should be reviewed?" - **NO** "It doesn't matter; I can try to figure out what you meant." - -3. Respect everyone's work and time: - - **YES** "I think there's some more to do here. Thanks for sharing where you're up to." - **NO** "This is rubbish. Try harder." - -## Getting your pull request reviewed -We're using GitHub Labels in our Code Review process. In order for a volunteer to review a pull request, a participant will need to add a "Needs Review" label to it. - -To add a label to a pull request: -- Open the pull request -- In the right sidebar, click Labels, then select the label you'd like to add - for example: "Needs Review" - -Take a look at our code review process from beginning to end. Let us know if you have any questions or need help! -![Code Review Flow](code-review-flow.png) - -## Labels for feedback - -Reviewers, please add labels (provided) to the PR once you've reviewed. This helps to focus the participant on the areas they should work on, and gives an overview for mentors on what the whole cohort needs to work on. - -## Solutions - -### Where to find solutions? - -You can find the solutions for the module on the `solutions` branch. - -### Solutions branch - -The solutions branch typically contains: - -#### Sample solutions - -Solutions are example answers not the only correct answers. - -#### Common responses guides. - -Everyone is invited to contribute commonly encountered problems, mistakes, misunderstandings, and mental-model errors to our common responses documents. - -Use these resources to inform your code review, get unstuck, and improve your understanding. - -## Guides - -https://curriculum.codeyourfuture.io/guides/reviewing/ +# Everyone reviews code at CYF + +https://curriculum.codeyourfuture.io/guides/reviewing/ + +Mentors and participants all review code, and collaborate on improving code quality. We are all helping each other to talk, write, and think about code more clearly. + +We are not reviewing code as if we were to merge this PR into production; we are opening a technical conversation for the purpose of insight and development. + +## Key points: + +1. Ask questions instead of making statements: + + **YES:** "Is there another element you could use to group a set of fields in a form? Why might someone use a different element in a form?" + **NO:** "Use fieldset not divs" + +2. Encourage simplicity, clarity, and precision: + + **YES** "There are 15,0000 files in this changelist. Which files should be reviewed?" + **NO** "It doesn't matter; I can try to figure out what you meant." + +3. Respect everyone's work and time: + + **YES** "I think there's some more to do here. Thanks for sharing where you're up to." + **NO** "This is rubbish. Try harder." + +## Getting your pull request reviewed +We're using GitHub Labels in our Code Review process. In order for a volunteer to review a pull request, a participant will need to add a "Needs Review" label to it. + +To add a label to a pull request: +- Open the pull request +- In the right sidebar, click Labels, then select the label you'd like to add - for example: "Needs Review" + +Take a look at our code review process from beginning to end. Let us know if you have any questions or need help! +![Code Review Flow](code-review-flow.png) + +## Labels for feedback + +Reviewers, please add labels (provided) to the PR once you've reviewed. This helps to focus the participant on the areas they should work on, and gives an overview for mentors on what the whole cohort needs to work on. + +## Solutions + +### Where to find solutions? + +You can find the solutions for the module on the `solutions` branch. + +### Solutions branch + +The solutions branch typically contains: + +#### Sample solutions + +Solutions are example answers not the only correct answers. + +#### Common responses guides. + +Everyone is invited to contribute commonly encountered problems, mistakes, misunderstandings, and mental-model errors to our common responses documents. + +Use these resources to inform your code review, get unstuck, and improve your understanding. + +## Guides + +https://curriculum.codeyourfuture.io/guides/reviewing/ diff --git a/LICENSE.txt b/LICENSE.txt index 4cf154a2..0746fa31 100644 --- a/LICENSE.txt +++ b/LICENSE.txt @@ -1,386 +1,386 @@ -Attribution 4.0 International - -======================================================================= - -Creative Commons Corporation ("Creative Commons") is not a law firm and -does not provide legal services or legal advice. Distribution of -Creative Commons public licenses does not create a lawyer-client or -other relationship. Creative Commons makes its licenses and related -information available on an "as-is" basis. Creative Commons gives no -warranties regarding its licenses, any material licensed under their -terms and conditions, or any related information. Creative Commons -disclaims all liability for damages resulting from their use to the -fullest extent possible. - -Using Creative Commons Public Licenses - -Creative Commons public licenses provide a standard set of terms and -conditions that creators and other rights holders may use to share -original works of authorship and other material subject to copyright -and certain other rights specified in the public license below. The -following considerations are for informational purposes only, are not -exhaustive, and do not form part of our licenses. - - Considerations for licensors: Our public licenses are - intended for use by those authorized to give the public - permission to use material in ways otherwise restricted by - copyright and certain other rights. Our licenses are - irrevocable. Licensors should read and understand the terms - and conditions of the license they choose before applying it. - Licensors should also secure all rights necessary before - applying our licenses so that the public can reuse the - material as expected. Licensors should clearly mark any - material not subject to the license. This includes other CC- - licensed material, or material used under an exception or - limitation to copyright. More considerations for licensors: - wiki.creativecommons.org/Considerations_for_licensors - - Considerations for the public: By using one of our public - licenses, a licensor grants the public permission to use the - licensed material under specified terms and conditions. If - the licensor's permission is not necessary for any reason--for - example, because of any applicable exception or limitation to - copyright--then that use is not regulated by the license. Our - licenses grant only permissions under copyright and certain - other rights that a licensor has authority to grant. Use of - the licensed material may still be restricted for other - reasons, including because others have copyright or other - rights in the material. A licensor may make special requests, - such as asking that all changes be marked or described. - Although not required by our licenses, you are encouraged to - respect those requests where reasonable. More_considerations - for the public: - wiki.creativecommons.org/Considerations_for_licensees - -======================================================================= - -Creative Commons Attribution 4.0 International Public License - -By exercising the Licensed Rights (defined below), You accept and agree -to be bound by the terms and conditions of this Creative Commons -Attribution 4.0 International Public License ("Public License"). To the -extent this Public License may be interpreted as a contract, You are -granted the Licensed Rights in consideration of Your acceptance of -these terms and conditions, and the Licensor grants You such rights in -consideration of benefits the Licensor receives from making the -Licensed Material available under these terms and conditions. - -Section 1 -- Definitions. - -a. Adapted Material means material subject to Copyright and Similar -Rights that is derived from or based upon the Licensed Material -and in which the Licensed Material is translated, altered, -arranged, transformed, or otherwise modified in a manner requiring -permission under the Copyright and Similar Rights held by the -Licensor. For purposes of this Public License, where the Licensed -Material is a musical work, performance, or sound recording, -Adapted Material is always produced where the Licensed Material is -synched in timed relation with a moving image. - -b. Adapter's License means the license You apply to Your Copyright -and Similar Rights in Your contributions to Adapted Material in -accordance with the terms and conditions of this Public License. - -c. Copyright and Similar Rights means copyright and/or similar rights -closely related to copyright including, without limitation, -performance, broadcast, sound recording, and Sui Generis Database -Rights, without regard to how the rights are labeled or -categorized. For purposes of this Public License, the rights -specified in Section 2(b)(1)-(2) are not Copyright and Similar -Rights. - -d. Effective Technological Measures means those measures that, in the -absence of proper authority, may not be circumvented under laws -fulfilling obligations under Article 11 of the WIPO Copyright -Treaty adopted on December 20, 1996, and/or similar international -agreements. - -e. Exceptions and Limitations means fair use, fair dealing, and/or -any other exception or limitation to Copyright and Similar Rights -that applies to Your use of the Licensed Material. - -f. Licensed Material means the artistic or literary work, database, -or other material to which the Licensor applied this Public -License. - -g. Licensed Rights means the rights granted to You subject to the -terms and conditions of this Public License, which are limited to -all Copyright and Similar Rights that apply to Your use of the -Licensed Material and that the Licensor has authority to license. - -h. Licensor means the individual(s) or entity(ies) granting rights -under this Public License. - -i. Share means to provide material to the public by any means or -process that requires permission under the Licensed Rights, such -as reproduction, public display, public performance, distribution, -dissemination, communication, or importation, and to make material -available to the public including in ways that members of the -public may access the material from a place and at a time -individually chosen by them. - -j. Sui Generis Database Rights means rights other than copyright -resulting from Directive 96/9/EC of the European Parliament and of -the Council of 11 March 1996 on the legal protection of databases, -as amended and/or succeeded, as well as other essentially -equivalent rights anywhere in the world. - -k. You means the individual or entity exercising the Licensed Rights -under this Public License. Your has a corresponding meaning. - -Section 2 -- Scope. - -a. License grant. - - 1. Subject to the terms and conditions of this Public License, - the Licensor hereby grants You a worldwide, royalty-free, - non-sublicensable, non-exclusive, irrevocable license to - exercise the Licensed Rights in the Licensed Material to: - - a. reproduce and Share the Licensed Material, in whole or - in part; and - - b. produce, reproduce, and Share Adapted Material. - - 2. Exceptions and Limitations. For the avoidance of doubt, where - Exceptions and Limitations apply to Your use, this Public - License does not apply, and You do not need to comply with - its terms and conditions. - - 3. Term. The term of this Public License is specified in Section - 6(a). - - 4. Media and formats; technical modifications allowed. The - Licensor authorizes You to exercise the Licensed Rights in - all media and formats whether now known or hereafter created, - and to make technical modifications necessary to do so. The - Licensor waives and/or agrees not to assert any right or - authority to forbid You from making technical modifications - necessary to exercise the Licensed Rights, including - technical modifications necessary to circumvent Effective - Technological Measures. For purposes of this Public License, - simply making modifications authorized by this Section 2(a) - (4) never produces Adapted Material. - - 5. Downstream recipients. - - a. Offer from the Licensor -- Licensed Material. Every - recipient of the Licensed Material automatically - receives an offer from the Licensor to exercise the - Licensed Rights under the terms and conditions of this - Public License. - - b. No downstream restrictions. You may not offer or impose - any additional or different terms or conditions on, or - apply any Effective Technological Measures to, the - Licensed Material if doing so restricts exercise of the - Licensed Rights by any recipient of the Licensed - Material. - - 6. No endorsement. Nothing in this Public License constitutes or - may be construed as permission to assert or imply that You - are, or that Your use of the Licensed Material is, connected - with, or sponsored, endorsed, or granted official status by, - the Licensor or others designated to receive attribution as - provided in Section 3(a)(1)(A)(i). - -b. Other rights. - - 1. Moral rights, such as the right of integrity, are not - licensed under this Public License, nor are publicity, - privacy, and/or other similar personality rights; however, to - the extent possible, the Licensor waives and/or agrees not to - assert any such rights held by the Licensor to the limited - extent necessary to allow You to exercise the Licensed - Rights, but not otherwise. - - 2. Patent and trademark rights are not licensed under this - Public License. - - 3. To the extent possible, the Licensor waives any right to - collect royalties from You for the exercise of the Licensed - Rights, whether directly or through a collecting society - under any voluntary or waivable statutory or compulsory - licensing scheme. In all other cases the Licensor expressly - reserves any right to collect such royalties. - -Section 3 -- License Conditions. - -Your exercise of the Licensed Rights is expressly made subject to the -following conditions. - -a. Attribution. - - 1. If You Share the Licensed Material (including in modified - form), You must: - - a. retain the following if it is supplied by the Licensor - with the Licensed Material: - - i. identification of the creator(s) of the Licensed - Material and any others designated to receive - attribution, in any reasonable manner requested by - the Licensor (including by pseudonym if - designated); - - ii. a copyright notice; - - iii. a notice that refers to this Public License; - - iv. a notice that refers to the disclaimer of - warranties; - - v. a URI or hyperlink to the Licensed Material to the - extent reasonably practicable; - - b. indicate if You modified the Licensed Material and - retain an indication of any previous modifications; and - - c. indicate the Licensed Material is licensed under this - Public License, and include the text of, or the URI or - hyperlink to, this Public License. - - 2. You may satisfy the conditions in Section 3(a)(1) in any - reasonable manner based on the medium, means, and context in - which You Share the Licensed Material. For example, it may be - reasonable to satisfy the conditions by providing a URI or - hyperlink to a resource that includes the required - information. - - 3. If requested by the Licensor, You must remove any of the - information required by Section 3(a)(1)(A) to the extent - reasonably practicable. - - 4. If You Share Adapted Material You produce, the Adapter's - License You apply must not prevent recipients of the Adapted - Material from complying with this Public License. - -Section 4 -- Sui Generis Database Rights. - -Where the Licensed Rights include Sui Generis Database Rights that -apply to Your use of the Licensed Material: - -a. for the avoidance of doubt, Section 2(a)(1) grants You the right -to extract, reuse, reproduce, and Share all or a substantial -portion of the contents of the database; - -b. if You include all or a substantial portion of the database -contents in a database in which You have Sui Generis Database -Rights, then the database in which You have Sui Generis Database -Rights (but not its individual contents) is Adapted Material; and - -c. You must comply with the conditions in Section 3(a) if You Share -all or a substantial portion of the contents of the database. - -For the avoidance of doubt, this Section 4 supplements and does not -replace Your obligations under this Public License where the Licensed -Rights include other Copyright and Similar Rights. - -Section 5 -- Disclaimer of Warranties and Limitation of Liability. - -a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE -EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS -AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF -ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, -IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, -WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR -PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, -ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT -KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT -ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. - -b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE -TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, -NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, -INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, -COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR -USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN -ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR -DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR -IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. - -c. The disclaimer of warranties and limitation of liability provided -above shall be interpreted in a manner that, to the extent -possible, most closely approximates an absolute disclaimer and -waiver of all liability. - -Section 6 -- Term and Termination. - -a. This Public License applies for the term of the Copyright and -Similar Rights licensed here. However, if You fail to comply with -this Public License, then Your rights under this Public License -terminate automatically. - -b. Where Your right to use the Licensed Material has terminated under -Section 6(a), it reinstates: - - 1. automatically as of the date the violation is cured, provided - it is cured within 30 days of Your discovery of the - violation; or - - 2. upon express reinstatement by the Licensor. - - For the avoidance of doubt, this Section 6(b) does not affect any - right the Licensor may have to seek remedies for Your violations - of this Public License. - -c. For the avoidance of doubt, the Licensor may also offer the -Licensed Material under separate terms or conditions or stop -distributing the Licensed Material at any time; however, doing so -will not terminate this Public License. - -d. Sections 1, 5, 6, 7, and 8 survive termination of this Public -License. - -Section 7 -- Other Terms and Conditions. - -a. The Licensor shall not be bound by any additional or different -terms or conditions communicated by You unless expressly agreed. - -b. Any arrangements, understandings, or agreements regarding the -Licensed Material not stated herein are separate from and -independent of the terms and conditions of this Public License. - -Section 8 -- Interpretation. - -a. For the avoidance of doubt, this Public License does not, and -shall not be interpreted to, reduce, limit, restrict, or impose -conditions on any use of the Licensed Material that could lawfully -be made without permission under this Public License. - -b. To the extent possible, if any provision of this Public License is -deemed unenforceable, it shall be automatically reformed to the -minimum extent necessary to make it enforceable. If the provision -cannot be reformed, it shall be severed from this Public License -without affecting the enforceability of the remaining terms and -conditions. - -c. No term or condition of this Public License will be waived and no -failure to comply consented to unless expressly agreed to by the -Licensor. - -d. Nothing in this Public License constitutes or may be interpreted -as a limitation upon, or waiver of, any privileges and immunities -that apply to the Licensor or You, including from the legal -processes of any jurisdiction or authority. - -======================================================================= - -Creative Commons is not a party to its public -licenses. Notwithstanding, Creative Commons may elect to apply one of -its public licenses to material it publishes and in those instances -will be considered the “Licensor.” The text of the Creative Commons -public licenses is dedicated to the public domain under the CC0 Public -Domain Dedication. Except for the limited purpose of indicating that -material is shared under a Creative Commons public license or as -otherwise permitted by the Creative Commons policies published at -creativecommons.org/policies, Creative Commons does not authorize the -use of the trademark "Creative Commons" or any other trademark or logo -of Creative Commons without its prior written consent including, -without limitation, in connection with any unauthorized modifications -to any of its public licenses or any other arrangements, -understandings, or agreements concerning use of licensed material. For -the avoidance of doubt, this paragraph does not form part of the -public licenses. - -Creative Commons may be contacted at creativecommons.org. +Attribution 4.0 International + +======================================================================= + +Creative Commons Corporation ("Creative Commons") is not a law firm and +does not provide legal services or legal advice. Distribution of +Creative Commons public licenses does not create a lawyer-client or +other relationship. Creative Commons makes its licenses and related +information available on an "as-is" basis. Creative Commons gives no +warranties regarding its licenses, any material licensed under their +terms and conditions, or any related information. Creative Commons +disclaims all liability for damages resulting from their use to the +fullest extent possible. + +Using Creative Commons Public Licenses + +Creative Commons public licenses provide a standard set of terms and +conditions that creators and other rights holders may use to share +original works of authorship and other material subject to copyright +and certain other rights specified in the public license below. The +following considerations are for informational purposes only, are not +exhaustive, and do not form part of our licenses. + + Considerations for licensors: Our public licenses are + intended for use by those authorized to give the public + permission to use material in ways otherwise restricted by + copyright and certain other rights. Our licenses are + irrevocable. Licensors should read and understand the terms + and conditions of the license they choose before applying it. + Licensors should also secure all rights necessary before + applying our licenses so that the public can reuse the + material as expected. Licensors should clearly mark any + material not subject to the license. This includes other CC- + licensed material, or material used under an exception or + limitation to copyright. More considerations for licensors: + wiki.creativecommons.org/Considerations_for_licensors + + Considerations for the public: By using one of our public + licenses, a licensor grants the public permission to use the + licensed material under specified terms and conditions. If + the licensor's permission is not necessary for any reason--for + example, because of any applicable exception or limitation to + copyright--then that use is not regulated by the license. Our + licenses grant only permissions under copyright and certain + other rights that a licensor has authority to grant. Use of + the licensed material may still be restricted for other + reasons, including because others have copyright or other + rights in the material. A licensor may make special requests, + such as asking that all changes be marked or described. + Although not required by our licenses, you are encouraged to + respect those requests where reasonable. More_considerations + for the public: + wiki.creativecommons.org/Considerations_for_licensees + +======================================================================= + +Creative Commons Attribution 4.0 International Public License + +By exercising the Licensed Rights (defined below), You accept and agree +to be bound by the terms and conditions of this Creative Commons +Attribution 4.0 International Public License ("Public License"). To the +extent this Public License may be interpreted as a contract, You are +granted the Licensed Rights in consideration of Your acceptance of +these terms and conditions, and the Licensor grants You such rights in +consideration of benefits the Licensor receives from making the +Licensed Material available under these terms and conditions. + +Section 1 -- Definitions. + +a. Adapted Material means material subject to Copyright and Similar +Rights that is derived from or based upon the Licensed Material +and in which the Licensed Material is translated, altered, +arranged, transformed, or otherwise modified in a manner requiring +permission under the Copyright and Similar Rights held by the +Licensor. For purposes of this Public License, where the Licensed +Material is a musical work, performance, or sound recording, +Adapted Material is always produced where the Licensed Material is +synched in timed relation with a moving image. + +b. Adapter's License means the license You apply to Your Copyright +and Similar Rights in Your contributions to Adapted Material in +accordance with the terms and conditions of this Public License. + +c. Copyright and Similar Rights means copyright and/or similar rights +closely related to copyright including, without limitation, +performance, broadcast, sound recording, and Sui Generis Database +Rights, without regard to how the rights are labeled or +categorized. For purposes of this Public License, the rights +specified in Section 2(b)(1)-(2) are not Copyright and Similar +Rights. + +d. Effective Technological Measures means those measures that, in the +absence of proper authority, may not be circumvented under laws +fulfilling obligations under Article 11 of the WIPO Copyright +Treaty adopted on December 20, 1996, and/or similar international +agreements. + +e. Exceptions and Limitations means fair use, fair dealing, and/or +any other exception or limitation to Copyright and Similar Rights +that applies to Your use of the Licensed Material. + +f. Licensed Material means the artistic or literary work, database, +or other material to which the Licensor applied this Public +License. + +g. Licensed Rights means the rights granted to You subject to the +terms and conditions of this Public License, which are limited to +all Copyright and Similar Rights that apply to Your use of the +Licensed Material and that the Licensor has authority to license. + +h. Licensor means the individual(s) or entity(ies) granting rights +under this Public License. + +i. Share means to provide material to the public by any means or +process that requires permission under the Licensed Rights, such +as reproduction, public display, public performance, distribution, +dissemination, communication, or importation, and to make material +available to the public including in ways that members of the +public may access the material from a place and at a time +individually chosen by them. + +j. Sui Generis Database Rights means rights other than copyright +resulting from Directive 96/9/EC of the European Parliament and of +the Council of 11 March 1996 on the legal protection of databases, +as amended and/or succeeded, as well as other essentially +equivalent rights anywhere in the world. + +k. You means the individual or entity exercising the Licensed Rights +under this Public License. Your has a corresponding meaning. + +Section 2 -- Scope. + +a. License grant. + + 1. Subject to the terms and conditions of this Public License, + the Licensor hereby grants You a worldwide, royalty-free, + non-sublicensable, non-exclusive, irrevocable license to + exercise the Licensed Rights in the Licensed Material to: + + a. reproduce and Share the Licensed Material, in whole or + in part; and + + b. produce, reproduce, and Share Adapted Material. + + 2. Exceptions and Limitations. For the avoidance of doubt, where + Exceptions and Limitations apply to Your use, this Public + License does not apply, and You do not need to comply with + its terms and conditions. + + 3. Term. The term of this Public License is specified in Section + 6(a). + + 4. Media and formats; technical modifications allowed. The + Licensor authorizes You to exercise the Licensed Rights in + all media and formats whether now known or hereafter created, + and to make technical modifications necessary to do so. The + Licensor waives and/or agrees not to assert any right or + authority to forbid You from making technical modifications + necessary to exercise the Licensed Rights, including + technical modifications necessary to circumvent Effective + Technological Measures. For purposes of this Public License, + simply making modifications authorized by this Section 2(a) + (4) never produces Adapted Material. + + 5. Downstream recipients. + + a. Offer from the Licensor -- Licensed Material. Every + recipient of the Licensed Material automatically + receives an offer from the Licensor to exercise the + Licensed Rights under the terms and conditions of this + Public License. + + b. No downstream restrictions. You may not offer or impose + any additional or different terms or conditions on, or + apply any Effective Technological Measures to, the + Licensed Material if doing so restricts exercise of the + Licensed Rights by any recipient of the Licensed + Material. + + 6. No endorsement. Nothing in this Public License constitutes or + may be construed as permission to assert or imply that You + are, or that Your use of the Licensed Material is, connected + with, or sponsored, endorsed, or granted official status by, + the Licensor or others designated to receive attribution as + provided in Section 3(a)(1)(A)(i). + +b. Other rights. + + 1. Moral rights, such as the right of integrity, are not + licensed under this Public License, nor are publicity, + privacy, and/or other similar personality rights; however, to + the extent possible, the Licensor waives and/or agrees not to + assert any such rights held by the Licensor to the limited + extent necessary to allow You to exercise the Licensed + Rights, but not otherwise. + + 2. Patent and trademark rights are not licensed under this + Public License. + + 3. To the extent possible, the Licensor waives any right to + collect royalties from You for the exercise of the Licensed + Rights, whether directly or through a collecting society + under any voluntary or waivable statutory or compulsory + licensing scheme. In all other cases the Licensor expressly + reserves any right to collect such royalties. + +Section 3 -- License Conditions. + +Your exercise of the Licensed Rights is expressly made subject to the +following conditions. + +a. Attribution. + + 1. If You Share the Licensed Material (including in modified + form), You must: + + a. retain the following if it is supplied by the Licensor + with the Licensed Material: + + i. identification of the creator(s) of the Licensed + Material and any others designated to receive + attribution, in any reasonable manner requested by + the Licensor (including by pseudonym if + designated); + + ii. a copyright notice; + + iii. a notice that refers to this Public License; + + iv. a notice that refers to the disclaimer of + warranties; + + v. a URI or hyperlink to the Licensed Material to the + extent reasonably practicable; + + b. indicate if You modified the Licensed Material and + retain an indication of any previous modifications; and + + c. indicate the Licensed Material is licensed under this + Public License, and include the text of, or the URI or + hyperlink to, this Public License. + + 2. You may satisfy the conditions in Section 3(a)(1) in any + reasonable manner based on the medium, means, and context in + which You Share the Licensed Material. For example, it may be + reasonable to satisfy the conditions by providing a URI or + hyperlink to a resource that includes the required + information. + + 3. If requested by the Licensor, You must remove any of the + information required by Section 3(a)(1)(A) to the extent + reasonably practicable. + + 4. If You Share Adapted Material You produce, the Adapter's + License You apply must not prevent recipients of the Adapted + Material from complying with this Public License. + +Section 4 -- Sui Generis Database Rights. + +Where the Licensed Rights include Sui Generis Database Rights that +apply to Your use of the Licensed Material: + +a. for the avoidance of doubt, Section 2(a)(1) grants You the right +to extract, reuse, reproduce, and Share all or a substantial +portion of the contents of the database; + +b. if You include all or a substantial portion of the database +contents in a database in which You have Sui Generis Database +Rights, then the database in which You have Sui Generis Database +Rights (but not its individual contents) is Adapted Material; and + +c. You must comply with the conditions in Section 3(a) if You Share +all or a substantial portion of the contents of the database. + +For the avoidance of doubt, this Section 4 supplements and does not +replace Your obligations under this Public License where the Licensed +Rights include other Copyright and Similar Rights. + +Section 5 -- Disclaimer of Warranties and Limitation of Liability. + +a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE +EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS +AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF +ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, +IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, +WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR +PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, +ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT +KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT +ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. + +b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE +TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, +NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, +INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, +COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR +USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN +ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR +DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR +IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + +c. The disclaimer of warranties and limitation of liability provided +above shall be interpreted in a manner that, to the extent +possible, most closely approximates an absolute disclaimer and +waiver of all liability. + +Section 6 -- Term and Termination. + +a. This Public License applies for the term of the Copyright and +Similar Rights licensed here. However, if You fail to comply with +this Public License, then Your rights under this Public License +terminate automatically. + +b. Where Your right to use the Licensed Material has terminated under +Section 6(a), it reinstates: + + 1. automatically as of the date the violation is cured, provided + it is cured within 30 days of Your discovery of the + violation; or + + 2. upon express reinstatement by the Licensor. + + For the avoidance of doubt, this Section 6(b) does not affect any + right the Licensor may have to seek remedies for Your violations + of this Public License. + +c. For the avoidance of doubt, the Licensor may also offer the +Licensed Material under separate terms or conditions or stop +distributing the Licensed Material at any time; however, doing so +will not terminate this Public License. + +d. Sections 1, 5, 6, 7, and 8 survive termination of this Public +License. + +Section 7 -- Other Terms and Conditions. + +a. The Licensor shall not be bound by any additional or different +terms or conditions communicated by You unless expressly agreed. + +b. Any arrangements, understandings, or agreements regarding the +Licensed Material not stated herein are separate from and +independent of the terms and conditions of this Public License. + +Section 8 -- Interpretation. + +a. For the avoidance of doubt, this Public License does not, and +shall not be interpreted to, reduce, limit, restrict, or impose +conditions on any use of the Licensed Material that could lawfully +be made without permission under this Public License. + +b. To the extent possible, if any provision of this Public License is +deemed unenforceable, it shall be automatically reformed to the +minimum extent necessary to make it enforceable. If the provision +cannot be reformed, it shall be severed from this Public License +without affecting the enforceability of the remaining terms and +conditions. + +c. No term or condition of this Public License will be waived and no +failure to comply consented to unless expressly agreed to by the +Licensor. + +d. Nothing in this Public License constitutes or may be interpreted +as a limitation upon, or waiver of, any privileges and immunities +that apply to the Licensor or You, including from the legal +processes of any jurisdiction or authority. + +======================================================================= + +Creative Commons is not a party to its public +licenses. Notwithstanding, Creative Commons may elect to apply one of +its public licenses to material it publishes and in those instances +will be considered the “Licensor.” The text of the Creative Commons +public licenses is dedicated to the public domain under the CC0 Public +Domain Dedication. Except for the limited purpose of indicating that +material is shared under a Creative Commons public license or as +otherwise permitted by the Creative Commons policies published at +creativecommons.org/policies, Creative Commons does not authorize the +use of the trademark "Creative Commons" or any other trademark or logo +of Creative Commons without its prior written consent including, +without limitation, in connection with any unauthorized modifications +to any of its public licenses or any other arrangements, +understandings, or agreements concerning use of licensed material. For +the avoidance of doubt, this paragraph does not form part of the +public licenses. + +Creative Commons may be contacted at creativecommons.org. diff --git a/MultiPage-Clone/README.md b/MultiPage-Clone/README.md index 6c760357..0510412e 100644 --- a/MultiPage-Clone/README.md +++ b/MultiPage-Clone/README.md @@ -1,98 +1,98 @@ -# Make a multi-page responsive website using CSS Grid STRETCH - -Choose one of the designs below, and re-create the design to perfection, using CSS Grid, and media queries to make the site fully responsive. - -## Learning Objectives - -1. Create a mobile-first, responsive website -2. Use CSS Grid and flexbox for layouts and alignment -3. Save fonts and colours in CSS variables - -## Style guide - -Here are 3 designs to choose from, along with suggested fonts and colours to use for your chosen projects: - -### **DESIGN 1: Prickles & Co** - -**An e-commerce site selling plants** - -![Prickles & Co homepage](./designs/Cactus%20shop.png) - -Live demo here: https://www.wix.com/website-template/view/html/1995 - -### Fonts - -**Headings:** Fjalla One - Regular 400 -https://fonts.google.com/specimen/Fjalla+One -**Subheadings:** Outfit - Extra-light 200 -https://fonts.google.com/specimen/Outfit -**Body:** Outfit - Extra-light 200 -https://fonts.google.com/specimen/Outfit - -### Colors - -Red Brown: #A05941 -Green Black: #133032 -Light Grey: #EDEDEE -White: #FFF -Transparent White: rgba(0,0,0,0.75) - -===================================== - -### **DESIGN 2: Resume** - -**A website to showcase skills and projects** - -![Business resume homepage](./designs/Business%20portfolio.png) - -Live demo here: https://www.wix.com/website-template/view/html/2622 - -### Fonts - -**Headings:** Poppins - Semi-bold 600 -https://fonts.google.com/specimen/Poppins -**Body:** Quicksand - Light 300 -https://fonts.google.com/specimen/Quicksand - -### Colors - -Dark beige: #E6DACD -Light beige: #F4ECE6 -Royal blue: #0150FD -Black: #000 -White: #FFF - -===================================== - -### **DESIGN 3: Juice Bar** - -**An e-commerce site for fruit juices** - -![Juice Bar homepage](./designs/Juice%20bar.png) - -Live demo here: https://www.wix.com/website-template/view/html/2962 - -### Fonts - -**Headings and subheadings:** Questrial - Regular 400 -https://fonts.google.com/specimen/Questrial -**Buttons:** Raleway - Regular 400 -https://fonts.google.com/specimen/Raleway -**Body:** Roboto - Light 300 -https://fonts.google.com/specimen/Roboto - -### Colors - -Black: #000 -White: #FFF -Lylac: #f5e8ff -Light Green: #E6FAC0 -Medium Green: #5E7D1F -Dark Green: #394B2A - -===================================== - -## **Crediting** - -Very important: please credit the designer in your footer with the sentence -"This website design was created by Wix.com, and is used here for strictly educational purposes." +# Make a multi-page responsive website using CSS Grid STRETCH + +Choose one of the designs below, and re-create the design to perfection, using CSS Grid, and media queries to make the site fully responsive. + +## Learning Objectives + +1. Create a mobile-first, responsive website +2. Use CSS Grid and flexbox for layouts and alignment +3. Save fonts and colours in CSS variables + +## Style guide + +Here are 3 designs to choose from, along with suggested fonts and colours to use for your chosen projects: + +### **DESIGN 1: Prickles & Co** + +**An e-commerce site selling plants** + +![Prickles & Co homepage](./designs/Cactus%20shop.png) + +Live demo here: https://www.wix.com/website-template/view/html/1995 + +### Fonts + +**Headings:** Fjalla One - Regular 400 +https://fonts.google.com/specimen/Fjalla+One +**Subheadings:** Outfit - Extra-light 200 +https://fonts.google.com/specimen/Outfit +**Body:** Outfit - Extra-light 200 +https://fonts.google.com/specimen/Outfit + +### Colors + +Red Brown: #A05941 +Green Black: #133032 +Light Grey: #EDEDEE +White: #FFF +Transparent White: rgba(0,0,0,0.75) + +===================================== + +### **DESIGN 2: Resume** + +**A website to showcase skills and projects** + +![Business resume homepage](./designs/Business%20portfolio.png) + +Live demo here: https://www.wix.com/website-template/view/html/2622 + +### Fonts + +**Headings:** Poppins - Semi-bold 600 +https://fonts.google.com/specimen/Poppins +**Body:** Quicksand - Light 300 +https://fonts.google.com/specimen/Quicksand + +### Colors + +Dark beige: #E6DACD +Light beige: #F4ECE6 +Royal blue: #0150FD +Black: #000 +White: #FFF + +===================================== + +### **DESIGN 3: Juice Bar** + +**An e-commerce site for fruit juices** + +![Juice Bar homepage](./designs/Juice%20bar.png) + +Live demo here: https://www.wix.com/website-template/view/html/2962 + +### Fonts + +**Headings and subheadings:** Questrial - Regular 400 +https://fonts.google.com/specimen/Questrial +**Buttons:** Raleway - Regular 400 +https://fonts.google.com/specimen/Raleway +**Body:** Roboto - Light 300 +https://fonts.google.com/specimen/Roboto + +### Colors + +Black: #000 +White: #FFF +Lylac: #f5e8ff +Light Green: #E6FAC0 +Medium Green: #5E7D1F +Dark Green: #394B2A + +===================================== + +## **Crediting** + +Very important: please credit the designer in your footer with the sentence +"This website design was created by Wix.com, and is used here for strictly educational purposes." diff --git a/MultiPage-Clone/css/main.css b/MultiPage-Clone/css/main.css index aa561706..0397cc29 100644 --- a/MultiPage-Clone/css/main.css +++ b/MultiPage-Clone/css/main.css @@ -1,3 +1,3 @@ -/* Add your CSS here */ - -/* Dont' forget to link this file to your HTML in the */ +/* Add your CSS here */ + +/* Dont' forget to link this file to your HTML in the */ diff --git a/MultiPage-Clone/index.html b/MultiPage-Clone/index.html index cd704c69..d3e9e6ca 100644 --- a/MultiPage-Clone/index.html +++ b/MultiPage-Clone/index.html @@ -1,21 +1,21 @@ - - - - - - - - - Responsive grid project - - - - - - - - -

This website design was created by Wix.com, and is used here for strictly educational purposes.

- - + + + + + + + + + Responsive grid project + + + + + + + + +

This website design was created by Wix.com, and is used here for strictly educational purposes.

+ + \ No newline at end of file diff --git a/MultiPage-Clone/main.js b/MultiPage-Clone/main.js index 11e6b744..86917b8a 100644 --- a/MultiPage-Clone/main.js +++ b/MultiPage-Clone/main.js @@ -1,4 +1,4 @@ - -const OVERFLOW = $('#toggle1'); - + +const OVERFLOW = $('#toggle1'); + OVERFLOW.click(e => e.target.checked ? $("body").css("overflow-y", "hidden") : $("body").css("overflow-y", "auto")); \ No newline at end of file diff --git a/Wireframe/README.md b/Wireframe/README.md index 83b77c7e..b4c1f180 100644 --- a/Wireframe/README.md +++ b/Wireframe/README.md @@ -1,42 +1,42 @@ -# Wireframe - -![Wireframe](./wireframe.png) - -Using the provided wireframe, create a new webpage explaining: - -1. What is Git? -2. Why do developers need Git? -3. What is a branch in Git? - -The page should NOT use any framework like Bootstrap. - -## Learning Objectives - -- Apply a consistent color scheme to links and text on the webpage -- Use semantic HTML tags to structure the webpage -- Create a page header with a title and description -- Create an articles section with three articles, each including a title, summary, and a link -- Create a page footer and fix it to the bottom of the viewport -- Use the :first-child pseudo-class to style the first article so that it stands out from the others -- Use version control by committing often and pushing regularly to GitHub -- Don't use any frameworks; write your own layout using HTML and CSS - -Use the wireframe sketch provided to lay out the page. Please note that this is just a sketch - you can choose the colors, fonts, and images that you want to use on the page. - -## Acceptance Criteria - -- [ ] The webpage has a consistent color scheme for links and text. -- [ ] Semantic HTML tags are used to structure the webpage. -- [ ] The page header includes a title and description. -- [ ] The articles section has three articles, each including a title, summary, and a link. -- [ ] The page footer is fixed to the bottom of the viewport. -- [ ] The first article is styled using the :first-child pseudo-class. -- [ ] The webpage is styled using a linked .css file. -- [ ] The webpage is properly committed and pushed to a branch on GitHub. -- [ ] The webpage does not use any frameworks such as Bootstrap. - -## Resources - -- [Wireframe](https://www.productplan.com/glossary/wireframe/) -- [Semantic HTML](https://www.w3schools.com/html/html5_semantic_elements.asp) -- [:first-child](https://developer.mozilla.org/en-US/docs/Web/CSS/:first-child) +# Wireframe + +![Wireframe](./wireframe.png) + +Using the provided wireframe, create a new webpage explaining: + +1. What is Git? +2. Why do developers need Git? +3. What is a branch in Git? + +The page should NOT use any framework like Bootstrap. + +## Learning Objectives + +- Apply a consistent color scheme to links and text on the webpage +- Use semantic HTML tags to structure the webpage +- Create a page header with a title and description +- Create an articles section with three articles, each including a title, summary, and a link +- Create a page footer and fix it to the bottom of the viewport +- Use the :first-child pseudo-class to style the first article so that it stands out from the others +- Use version control by committing often and pushing regularly to GitHub +- Don't use any frameworks; write your own layout using HTML and CSS + +Use the wireframe sketch provided to lay out the page. Please note that this is just a sketch - you can choose the colors, fonts, and images that you want to use on the page. + +## Acceptance Criteria + +- [ ] The webpage has a consistent color scheme for links and text. +- [ ] Semantic HTML tags are used to structure the webpage. +- [ ] The page header includes a title and description. +- [ ] The articles section has three articles, each including a title, summary, and a link. +- [ ] The page footer is fixed to the bottom of the viewport. +- [ ] The first article is styled using the :first-child pseudo-class. +- [ ] The webpage is styled using a linked .css file. +- [ ] The webpage is properly committed and pushed to a branch on GitHub. +- [ ] The webpage does not use any frameworks such as Bootstrap. + +## Resources + +- [Wireframe](https://www.productplan.com/glossary/wireframe/) +- [Semantic HTML](https://www.w3schools.com/html/html5_semantic_elements.asp) +- [:first-child](https://developer.mozilla.org/en-US/docs/Web/CSS/:first-child) diff --git a/Wireframe/css/style.css b/Wireframe/css/style.css index e69de29b..1eeb6025 100644 --- a/Wireframe/css/style.css +++ b/Wireframe/css/style.css @@ -0,0 +1,58 @@ +body { + + color: brown; + text-align: center; + margin: auto; +} + +h1{ + font-size: 80px; +} + +header p { + font-size: 30px; +} +h1, h2 { + font-family: Arial, Helvetica, sans-serif; + color: black; +} + +#flex-container { + display: flex; + flex-direction: column; + align-items: center; + margin: 60px; + background-image: linear-gradient(pink,rgb(145, 145, 218)); + +} + +.article-1:hover { + background-color: rgb(239, 242, 164); + width: 900px; + + } + +.article-1, .article-2, .article-3 { + background-color: bisque; + padding: 40px; + margin: 20px; + width: 800px; + border-radius: 10px; + font-size: 20px; + box-shadow: 10px; +} +a { + text-decoration: none; +} +a:hover { + color: rgb(115, 255, 105); + } + +footer{ + font-size: 20px; + position: fixed; + bottom: 0; + background: white; + width: 100vw; + +} diff --git a/Wireframe/index.html b/Wireframe/index.html index 67544158..9927577e 100644 --- a/Wireframe/index.html +++ b/Wireframe/index.html @@ -1,13 +1,72 @@ - - - - - - Wireframe - - - - - - + + + + + + Wireframe + + + +
+

Github

+

GitHub is a cloud-based platform that uses Git for version control and collaboration. It provides a space where developers can host their Git repositories, collaborate on projects, and share code with others.

+
+ +
+ +
+
+

What is Git?

+
+ Git Definition +

+ is a distributed version control system (DVCS) that helps developers track changes to code, collaborate efficiently, and maintain different versions of a project. It allows teams to work simultaneously on the same codebase without overwriting each other’s work. By keeping a complete history of changes, Git makes it easy to revert to previous versions and work offline. It also supports code reviews and ensures code quality by enabling collaborative workflows. +

+

+ More about git +

+
+
+
+ +
+
+

Why do developers need Git

+
+ Importance of Git +

+ Developers need Git because it enhances teamwork, provides a backup of the codebase, and makes it easier to track changes. It supports branching and merging, which allows developers to work on separate features or fixes without affecting the main project. This means parallel development can happen without interference. +

+

+ More about importance of git +

+
+
+
+ +
+
+

What is a branch in Git?

+
+ branch Definition +

+ A branch in Git is an isolated version of the repository where developers can work on new features, bug fixes, or experiments. Branches help in maintaining a stable main codebase while allowing independent development. Once changes are finalized, the branch can be merged back into the main project. This approach ensures that experimental work doesn’t affect production code until it’s ready. +

+

+ More about branching in git +

+
+
+
+ +
+ + + + +