CodeYourFuture · FarancisGH · Jan 26, 2026 · Feb 7, 2026 · Feb 7, 2026 · Feb 7, 2026
diff --git a/Wireframe/index.html b/Wireframe/index.html
@@ -1,33 +1,68 @@
 <!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>ReadMe, Wireframe and Branches</h1>
+    <p>
+      Below we will be discussing on what the purpose of a Readme file is,
+      the purpose of a wireframe and what a branch is and what a branch
+      in git is. But first, lets look at this image.
+    </p>
+  </header>
+  <main>
+    <article>
+      <img src="https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcQJS8HBwSIm--Dd_YOAfCSDnQUexFj_Qa8W_A&s"
+        alt="Image of a ReadMe file" />
+      <h2>ReadMe</h2>
       <p>
-        This is the default, provided code and no changes have been made yet.
+        A ReadMe file is a document that provides essential information about a project, software, or repository. It
+        serves as a guide for users and developers, offering details such as installation instructions, usage
+        guidelines, features, and licensing information. The primary purpose of a ReadMe file is to help users
+        understand what the project is about, how to use it effectively, and how to contribute if applicable.
       </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://www.geeksforgeeks.org/git/what-is-readme-md-file/" id="section1link">Click to learn more</a>
+    </article>
+    <article id="articleOne">
+      <img
+        src="https://cdn.sanity.io/images/599r6htc/regionalized/4c8605ad998d69b03a6eefb850cce5e23a0a96dc-2880x1440.png?w=2880&h=1440&q=75&fit=max&auto=format"
+        alt="Image of a wireframe" />
+      <h2>Wireframe</h2>
       <p>
-        This is the default, provided code and no changes have been made yet.
+        A wireframe is a visual representation or blueprint of a website, application, or user interface. It outlines
+        the basic structure, layout, and functionality of a design without focusing on detailed aesthetics. Wireframes
+        are typically created in the early stages of the design process to help designers, developers, and stakeholders
+        visualize the overall structure and flow of a project. They often include placeholders for content, navigation
+        elements, and interactive features, allowing for easy communication and collaboration among team members before
+        moving on to more detailed design and development phases.
       </p>
-    </footer>
-  </body>
-</html>
+      <a href="https://www.interaction-design.org/literature/topics/wireframing" id="section2link">Click to learn
+        more</a>
+    </article>
+    <article>
+      <img
+        src="https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/d/0d19837bbaf82a71ab35b2a62c5f8776af8e900a.png"
+        alt="Image of git branches" />
+      <h2>Branches</h2>
+      <p>
+        In version control systems like Git, a branch is a separate line of development that allows multiple developers
+        to work on different features or fixes simultaneously without affecting the main codebase. Branches enable teams
+        to isolate changes, experiment with new ideas, and collaborate more effectively. When a feature or fix is
+        complete, the changes made in the branch can be merged back into the main branch (often called "main" or
+        "master"). This process helps maintain a clean and stable codebase while allowing for parallel development
+        efforts.
+      </p>
+      <a href="https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell">Click to learn more.</a>
+    </article>
+
+  </main>
+</body>
+
+</html>
diff --git a/Wireframe/style.css b/Wireframe/style.css
@@ -1,89 +1,69 @@
-/* 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);
   --font: 100%/1.5 system-ui;
   --space: clamp(6px, 6px + 2vw, 15px);
-  --line: 1px solid;
-  --container: 1280px;
+  --line: 3px solid; word-spacing: 1px; 
+  /* --container: 1280px; */
+  /* padding: 50px; */
+  --padding: 50px;
+  width: 80%;
+  margin-left: auto;
+  margin-right: auto;
+
+}
+
+header {
+  text-align: center;
+  width : 90%;
+  padding: 5%;
+
 }
-/* ====== Base Elements ======
- General rules for basic HTML elements in any context */
 body {
+  width: 100%;
   background: var(--paper);
   color: var(--ink);
   font: var(--font);
+  /* overflow: hidden; */
+
+  /* padding: 10px; */
+  /* overflow-x: hidden; */
+
 }
+
 a {
-  padding: var(--space);
+  padding: 1px;
+  border-radius: 10px;
   border: var(--line);
-  max-width: fit-content;
+  /* max-width: fit-content; */
 }
-img,
-svg {
-  width: 100%;
-  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 {
   display: grid;
+  /* padding: 50px; */
+  border : 50px solid var(--paper); 
+  color: black;
   grid-template-columns: 1fr 1fr;
   gap: var(--space);
   > *: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);
+  border: var(--line); 
+  width: 100%;
+  border-radius: 12px;
+  /* padding-bottom: 20px;  */
   text-align: left;
+  padding: 1px;
   display: grid;
-  grid-template-columns: var(--space) 1fr var(--space);
+  grid: template columns 1fr; var(--space) 2fr var(--space);
   > * {
-    grid-column: 2/3;
+    grid-column: 1;
   }
   > img {
-    grid-column: span 3;
+    grid-column: span 100%;
+    width: 400px;
+    justify-self: center;
   }
-}
+}