|
1 | 1 | <!DOCTYPE html> |
2 | 2 | <html lang="en"> |
3 | 3 | <head> |
4 | | - <meta charset="UTF-8" /> |
5 | | - <meta name="viewport" content="width=device-width, initial-scale=1.0" /> |
6 | | - <title>Wireframe</title> |
7 | | - <link rel="stylesheet" href="style.css"/> |
| 4 | + <meta charset="utf-8" /> |
| 5 | + <meta http-equiv="X-UA-Compatible" content="IE=edge" /> |
| 6 | + <title>My form exercise</title> |
| 7 | + <meta name="description" content="" /> |
| 8 | + <meta name="viewport" content="width=device-width, initial-scale=1" /> |
8 | 9 | </head> |
9 | 10 | <body> |
10 | 11 | <header> |
11 | | - <h1> Project Wireframe</h1> |
12 | | - <p> |
13 | | - Articles are a great way to share information and ideas with others. They can be used to educate, inform, or entertain readers on a wide range of topics. Whether you're writing about current events, technology, health, or any other subject, articles provide a platform for you to express your thoughts and insights. With the right research and writing skills, you can create engaging and informative articles that resonate with your audience and contribute to meaningful discussions. Here are some articles to get you started. I have chosen some articles from Git/Github to enchance your knowledge of some of the files etc. |
14 | | - </p> |
| 12 | + <h1>Product Pick</h1> |
15 | 13 | </header> |
16 | 14 | <main> |
17 | | - <article id="article1"> |
18 | | - <img src="https://ubc-lib-geo.github.io/gis-workshop-waml-template/content/img/readme3.png" alt="Readme file" /> |
19 | | - <h2>Purpose of Read me File</h2> |
20 | | - <p> |
21 | | - The primary purpose of a README file on GitHub is to serve as the first point of documentation for your project, introducing it to visitors and explaining how to use it. GitHub automatically renders and displays this file at the bottom of your repository's main page to provide immediate context before someone explores the code. |
22 | | - </p> |
23 | | - <a href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes">Read more</a> |
24 | | - </article> |
25 | | - <article id="article2"> |
26 | | - <img src="https://minimum-viable-product.github.io/marshmallow-docs/images/training/app-navigation-screen-planning-exhaustive-map.png" alt="" /> |
27 | | - <h2>Purpose of Wireframe </h2> |
28 | | - <p> |
29 | | - |
30 | | - </p> |
31 | | - <a href="https://minimum-viable-product.github.io/marshmallow-docs/training/design-navigation/wireframing.html">Read more</a> |
32 | | - </article> |
33 | | - <article id="article3"> |
34 | | - <img src="https://framerusercontent.com/images/jmGsErVaXE9HMnmsIjHDba05DSg.png?width=1600&height=900" alt="" /> |
35 | | - <h2>Purpose of Branch</h2> |
36 | | - <p> |
37 | | - Branches allow you to develop features, fix bugs, or safely experiment with new ideas in a contained area of your repository. You always create a branch from an existing branch. Typically, you might create a new branch from the default branch of your repository. |
38 | | - |
39 | | - </p> |
40 | | - <a href="https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches"> |
41 | | - Read more</a> |
42 | | - </article> |
| 15 | + <form> |
| 16 | + <!-- write your html here--> |
| 17 | + <!-- |
| 18 | + try writing out the requirements first as comments |
| 19 | + this will also help you fill in your PR message later--> |
| 20 | + </form> |
43 | 21 | </main> |
44 | 22 | <footer> |
45 | | - <p> |
46 | | - Wireframe project by Mandip Sanger. This project is a simple demonstration of how to create a wireframe for a website using HTML and CSS. |
47 | | - </p> |
| 23 | + <!-- change to your name--> |
| 24 | + <p>By HOMEWORK SOLUTION</p> |
48 | 25 | </footer> |
49 | 26 | </body> |
50 | 27 | </html> |
0 commit comments