CodeYourFuture · Mona-Eltantawy · Jan 17, 2026 · Jan 17, 2026 · Jan 20, 2026 · Jan 24, 2026
diff --git a/Wireframe/index.html b/Wireframe/index.html
@@ -1,33 +1,72 @@
 <!DOCTYPE html>
 <html lang="en">
-  <head>
-    <meta charset="UTF-8" />
-    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <title>Wireframe</title>
-    <link rel="stylesheet" href="style.css" />
-  </head>
-  <body>
-    <header>
-      <h1>Wireframe</h1>
+
+<head>
+  <meta charset="UTF-8" />
+  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+  <title>Wireframe</title>
+  <link rel="stylesheet" href="style.css" />
+</head>
+
+<body>
+  <header class="header">
+    <h1 class="title">Wireframe</h1>
+    <p>The skeleton for your website.</p>
+  </header>
+
+  <main>
+    <article>
+      <img src="placeholder.svg" alt="README file illustration" />
+      <h2>What is the purpose of a README file?</h2>
       <p>
-        This is the default, provided code and no changes have been made yet.
+        A README file's purpose is to be a project's welcome mat, providing essential information for users and
+        developers,
+        including what the project does, how to install and use it, contribution guidelines, and licensing. It ensures
+        clarity, accessibility, and smooth collaboration by serving as the primary documentation and entry point.
       </p>
-    </header>
-    <main>
-      <article>
-        <img src="placeholder.svg" alt="" />
-        <h2>Title</h2>
-        <p>
-          Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam,
-          voluptates. Quisquam, voluptates.
-        </p>
-        <a href="">Read more</a>
-      </article>
-    </main>
-    <footer>
+      <a href="https://datamanagement.hms.harvard.edu/collect-analyze/documentation-metadata/readme-files">
+        Learn more about README files
+      </a>
+    </article>
+
+    <article>
+      <img
+        src="https://cdn.sanity.io/images/599r6htc/regionalized/4c8605ad998d69b03a6eefb850cce5e23a0a96dc-2880x1440.png?q=75&fit=max&auto=format&dpr=0.75"
+        alt="Wireframe layout example" />
+      <h2>What is the purpose of a wireframe?</h2>
       <p>
-        This is the default, provided code and no changes have been made yet.
+        The purpose of a wireframe is to create a skeletal blueprint of a digital product (website or app) to define
+        its structure, layout, and functionality before visual design. This ensures user-friendliness, alignment among
+        teams (designers, developers, clients), efficient feedback, and prevents costly revisions by focusing on content
+        hierarchy and user flow early on. It's the foundational stage that focuses on what goes where, not the final
+        look.
       </p>
-    </footer>
-  </body>
-</html>
+      <a href="https://www.figma.com/resource-library/what-is-wireframing/">
+        Learn more about wireframing
+      </a>
+    </article>
+
+    <article>
+      <img class="img2" src="https://miro.medium.com/v2/resize:fit:750/format:webp/1*e6EkEBIDZcOmlwPqCnsJKg.jpeg"
+        alt="Git branching diagram" />
+      <h2>What is a branch in Git?</h2>
+      <p>
+        According to the official documentation from Git, “Branching means you diverge from the main line of development
+        and continue to do work without messing with that main line.” This means a new copy of the main repository is
+        made,
+        and after it is split off from the original path, it is free to be modified without making permanent changes to
+        the original “main” branch. There are many different branching strategies that projects use, each offering
+        benefits for different workflows.
+      </p>
+      <a href="https://medium.com/@jacoblogan98/understanding-git-branching-5d01f3dda541">
+        Learn more about Git branching
+      </a>
+    </article>
+  </main>
+
+  <footer>
+    <p>This is a website by Mona Eltantawy.</p>
+  </footer>
+</body>
+
+</html>
diff --git a/Wireframe/style.css b/Wireframe/style.css
@@ -1,89 +1,104 @@
-/* Here are some starter styles
-You can edit these or replace them entirely 
-It's showing you a common way to organise CSS 
-And includes solutions to common problems 
-As well as useful links to learn more */
-
-/* ====== Design Palette ======
- This is our "design palette".
- It sets out the colours, fonts, styles etc to be used in this design 
- At work, a designer will give these to you based on the corporate brand, but while you are learning
- You can design it yourself if you like
- Inspect the starter design with Devtools
- Click on the colour swatches to see what is happening
- I've put some useful CSS you won't have learned yet
- For you to explore and play with if you are interested
- https://web.dev/articles/min-max-clamp
- https://scrimba.com/learn-css-variables-c026
-====== Design Palette ====== */
 :root {
   --paper: oklch(7 0 0);
-  --ink: color-mix(in oklab, var(--color) 5%, black);
+  --ink: black;
   --font: 100%/1.5 system-ui;
   --space: clamp(6px, 6px + 2vw, 15px);
-  --line: 1px solid;
+  --line: 1px solid black;
   --container: 1280px;
 }
-/* ====== Base Elements ======
- General rules for basic HTML elements in any context */
+
+
+.header h1 {
+ background: #2c3e50; 
+  color: #ffffff;
+  margin: 10px 100px;
+  padding: 10px;
+  text-align: center;
+  font-family: Georgia, "Times New Roman", Times, serif;
+  font-size: 2rem;
+  font-weight: bold;
+}
+
+.header p {
+  text-align: center;
+  font-family: Georgia, "Times New Roman", Times, serif;
+  font-size: 1.125rem;
+  font-weight: bold;
+  color: rgb(39, 36, 36);
+}
+
 body {
-  background: var(--paper);
-  color: var(--ink);
-  font: var(--font);
+  background-color: rgb(178, 203, 203);
+  font-family: serif;
+  font-size: 1rem;
+  width: 100%;
+  margin: 0;
 }
+
 a {
-  padding: var(--space);
+  padding: 2px 6px;
   border: var(--line);
+  text-decoration: none;
+  display: inline-block;
   max-width: fit-content;
 }
+
+a:hover,
+a:focus {
+  color: #0a2a66;
+  outline-offset: 2px;
+}
+
 img,
 svg {
   width: 100%;
+  height: auto;
   object-fit: cover;
 }
-/* ====== Site Layout ====== 
-Setting the overall rules for page regions
-https://www.w3.org/WAI/tutorials/page-structure/regions/
-*/
+
+
 main {
   max-width: var(--container);
-  margin: 0 auto calc(var(--space) * 4) auto;
-}
-footer {
-  position: fixed;
-  bottom: 0;
-  text-align: center;
-}
-/* ====== Articles Grid Layout ====
-Setting the rules for how articles are placed in the main element.
-Inspect this in Devtools and click the "grid" button in the Elements view
-Play with the options that come up.
-https://developer.chrome.com/docs/devtools/css/grid
-https://gridbyexample.com/learn/
-*/
-main {
+  margin: 0 auto calc(var(--space) * 4);
   display: grid;
-  grid-template-columns: 1fr 1fr;
+  grid-template-columns: repeat(2, 1fr);
   gap: var(--space);
-  > *:first-child {
-    grid-column: span 2;
-  }
+  overflow: hidden;
+}
+
+main > *:first-child {
+  grid-column: span 2;
 }
-/* ====== Article Layout ====== 
-Setting the rules for how elements are placed in the article. 
-Now laying out just the INSIDE of the repeated card/article design.
-Keeping things orderly and separate is the key to good, simple CSS.
-*/
+
+
 article {
   border: var(--line);
   padding-bottom: var(--space);
   text-align: left;
   display: grid;
   grid-template-columns: var(--space) 1fr var(--space);
-  > * {
-    grid-column: 2/3;
-  }
-  > img {
-    grid-column: span 3;
-  }
+}
+
+article > * {
+  grid-column: 2 / 3;
+}
+
+article > img {
+  grid-column: 1 / -1;
+  height: 300px;
+}
+
+footer {
+  position: fixed;
+  bottom: 0;
+  left: 50%;
+  transform: translateX(-50%);
+  text-align: center;
+  font-size: 1rem;
+  border: var(--line);
+  box-sizing: border-box;
+   background: #2c3e50;
+  color: #ffffff;
+  box-shadow: 0 4px 10px rgba(0, 0, 0, 0.1);
+  width: 50%;
 }