diff --git a/Form-Controls/README.md b/Form-Controls/README.md deleted file mode 100644 index bfcdf6c0b..000000000 --- a/Form-Controls/README.md +++ /dev/null @@ -1,51 +0,0 @@ -# Form Controls - -## Learning Objectives - - - -- [ ] Interpret requirements and check against a list of criteria -- [ ] Write a valid form -- [ ] 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 size. - -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 - -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. Check each one off as you complete it. - -- [ ] I have used HTML only. -- [x] I have not used any CSS or JavaScript. - -### 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. - -## Resources - -- [MDN: Form controls](https://developer.mozilla.org/en-US/docs/Learn/Forms) -- [MDN: Form validation](https://developer.mozilla.org/en-US/docs/Learn/Forms/Form_validation) -- [Lighthouse](https://developers.google.com/web/tools/lighthouse) -- [Lighthouse Guide](https://programming.codeyourfuture.io/guides/testing/lighthouse) diff --git a/Form-Controls/index.html b/Form-Controls/index.html deleted file mode 100644 index 65a866cdb..000000000 --- a/Form-Controls/index.html +++ /dev/null @@ -1,27 +0,0 @@ - - - - - - My form exercise - - - - -
-

Product Pick

-
-
-
- - -
-
- - - diff --git a/Wireframe/background image.jpg b/Wireframe/background image.jpg new file mode 100644 index 000000000..6e80fe752 Binary files /dev/null and b/Wireframe/background image.jpg differ diff --git a/Wireframe/branch.svg b/Wireframe/branch.svg new file mode 100644 index 000000000..905d553e1 --- /dev/null +++ b/Wireframe/branch.svg @@ -0,0 +1,2 @@ + + \ No newline at end of file diff --git a/Wireframe/index1.html b/Wireframe/index1.html new file mode 100644 index 000000000..d36e9a6ff --- /dev/null +++ b/Wireframe/index1.html @@ -0,0 +1,71 @@ + + + + + + Wireframe + + + +
+

Wireframe

+

+ a short describtion of wireframe, branch, and README.md file. +

+
+
+
+ +

What is a branch in Git?

+

+ "What is a Git Branch? + In Git, a branch is like a separate workspace where you can make changes and try new ideas without affecting the main project. Think of it as a "parallel universe" for your code. + + Why Use Branches? + Branches let you work on different parts of a project, like new features or bug fixes, without interfering with the main branch. + + Common Reasons to Create a Branch + Developing a new feature + Fixing a bug + Experimenting with ideas" +

+ Read more +
+ +
+ +

Why do we use README.md file?

+

+ " A README.md is a key document in repositories, especially on GitHub. + It introduces the project, explains its purpose, setup, and usage, and helps users and developers contribute effectively." +

+ Read more +
+ +
+ +

What is the purpose of a wireframe?

+

+ "Wireframes are basic blueprints that help teams align on requirements, + keeping UX design conversations focused and constructive. + Think of your wireframe as the skeleton of your app, website, or other final product. + Your wireframe shows the design team and stakeholders the bare-bones outlines of essential webpages, + components, and features, including: + + Screen layouts + Navigation bars + Components of UX and UI design + Interactive elements" +

+ Read more +
+
+ + + \ No newline at end of file diff --git a/Wireframe/readme.md.png b/Wireframe/readme.md.png new file mode 100644 index 000000000..e418b5e13 Binary files /dev/null and b/Wireframe/readme.md.png differ diff --git a/Wireframe/style.css b/Wireframe/style.css index be835b6c7..3650fa3a7 100644 --- a/Wireframe/style.css +++ b/Wireframe/style.css @@ -30,11 +30,19 @@ body { background: var(--paper); color: var(--ink); font: var(--font); + background-color:aquamarine; + background-image: url("background image.jpg"); + position: relative; + left: 0; + bottom: 0; + width: 100%; + text-align: center; } a { padding: var(--space); border: var(--line); max-width: fit-content; + color: var(--ink); } img, svg { @@ -50,8 +58,10 @@ main { margin: 0 auto calc(var(--space) * 4) auto; } footer { - position: fixed; + position: relative; + left: 0; bottom: 0; + width: 100%; text-align: center; } /* ====== Articles Grid Layout ==== diff --git a/Wireframe/wireframe image.png b/Wireframe/wireframe image.png new file mode 100644 index 000000000..f7fa038c0 Binary files /dev/null and b/Wireframe/wireframe image.png differ