CodeYourFuture · Alex-Os-Dev-Lab · Feb 2, 2026 · Feb 2, 2026 · Feb 2, 2026 · Feb 2, 2026
diff --git a/Wireframe/README Article Image.png b/Wireframe/README Article Image.png
diff --git a/Wireframe/Wireframe Article Image.png b/Wireframe/Wireframe Article Image.png
diff --git a/Wireframe/git-branches Article Image.png b/Wireframe/git-branches Article Image.png
diff --git a/Wireframe/index.html b/Wireframe/index.html
@@ -6,27 +6,109 @@
     <title>Wireframe</title>
     <link rel="stylesheet" href="style.css" />
   </head>
+   <!--  
+
+    Using the provided wireframe and resources, write a new webpage explaining:
+
+      1. What is the purpose of a README file?
+
+      2. What is the purpose of a wireframe?
+
+      3. What is a branch in Git?
+
+Modify the HTML and CSS files to meet the acceptance criteria. 
+You must check this criteria yourself before you submit your work.
+
+## Acceptance Criteria
+
+- [ ] Semantic HTML tags are used to structure the webpage.
+- [ ] The page scores 100 for Accessibility in the Lighthouse audit.
+- [ ] The page header includes a title and description.
+- [ ] The articles section has three unique articles, each including an image, title, summary, and a link.
+- [ ] The page footer is fixed to the bottom of the viewport.
+- [ ] The webpage is styled using a linked .css file.
+- [ ] The webpage is properly committed and pushed to a branch on GitHub.
+
+    -->
   <body>
     <header>
-      <h1>Wireframe</h1>
+      <h1>Essential Documentation & Design Tools for Developers</h1>
       <p>
-        This is the default, provided code and no changes have been made yet.
+        Master 3 essential tools every developer needs
+        for documentation and design before writing production code.
       </p>
     </header>
     <main>
+
+      <!--
+      Article 1: README File
+      -->
+
       <article>
-        <img src="placeholder.svg" alt="" />
-        <h2>Title</h2>
+
+        <figure>
+          <img src="README Article Image.png" 
+          alt="Purpose of README file article illustration" />
+
+          <figcaption>README file illustration for the Purpose of README file article</figcaption>
+        </figure>
+
+        <h2>README.md: Preventing "What Does This Button Do?" Since 1970</h2>
         <p>
-          Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam,
-          voluptates. Quisquam, voluptates.
+          Think of a README file as the front door to your project. 
+          It is a simple text document that tells other humans 
+          what your code does, how to install it, and why it exists.<br /><br />
+          Without a README, your project is just a mysterious pile of files; with one, it's a professional tool.
         </p>
-        <a href="">Read more</a>
+        <a href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes">Read more</a>
+      </article>
+
+      <!--
+      Article 2: Wireframe  
+      -->
+
+      <article>
+        <figure>
+          <img src="Wireframe Article Image.png" 
+          alt="Purpose of Wireframe article illustration" />
+
+          <figcaption>Wireframe illustration for the Purpose of Wireframe article</figcaption>
+        </figure> 
+        <h2>Wireframes: Because Changing a Drawing is Cheaper Than Changing Code</h2>
+        <p>
+           A wireframe is a two-dimensional, low-fidelity outline of your interface.
+           It focuses on functionality and hierarchy rather than colors and fonts. <br\>
+           By "gray-boxing" your ideas first, you can catch logic flaws and user-flow issues
+           before a single pixel is polished or a single &#60div> is styled.
+        </p>
+        <a href="https://www.productplan.com/glossary/wireframe/">Read more</a>
+      </article>
+
+      <!--
+      Article 3: Git Branch
+      -->
+
+      <article>
+        <figure>
+          <img src="Git Branch Article Image.png" 
+          alt="Git Branch article illustration" />
+
+          <figcaption>Git Branch illustration for the Git Branch article</figcaption>
+        </figure> 
+        <h2>Git Branches: How to Experiment Without Blowing up the App!</h2>
+        <p>
+           In Git, a branch is a lightweight, moveable pointer to a specific commit.
+           Think of it as a parallel dimension where you can build a new feature or fix a bug
+           without touching the "Main" timeline of your project. If the experiment works, you merge it back;
+           if it fails, you can delete that timeline and pretend it never happened.
+           It is the ultimate "undo" button for collaborative development.
+        </p>
+        <a href="https://programming.codeyourfuture.io/onboarding/sprints/1/prep/#branching">Read more</a>
       </article>
     </main>
     <footer>
       <p>
-        This is the default, provided code and no changes have been made yet.
+        WEBPAGE BY ALEX OKOREFE
       </p>
     </footer>
   </body>

diff --git a/Wireframe/style.css b/Wireframe/style.css
@@ -17,9 +17,10 @@ As well as useful links to learn more */
  https://scrimba.com/learn-css-variables-c026
 ====== Design Palette ====== */
 :root {
-  --paper: oklch(7 0 0);
+  --paper: #f4f4f9;
   --ink: color-mix(in oklab, var(--color) 5%, black);
-  --font: 100%/1.5 system-ui;
+  --accent: #0056b3;
+  --font: 100%/1.6 "Segoe UI", Roboto, Helvetica, Arial, sans-serif;
   --space: clamp(6px, 6px + 2vw, 15px);
   --line: 1px solid;
   --container: 1280px;
@@ -31,6 +32,20 @@ body {
   color: var(--ink);
   font: var(--font);
 }
+
+header {
+  text-align: center;
+  padding: 10px;
+  background-color: white; /* distinct header area */
+  margin-bottom: 20px;
+  border-bottom: 1px solid #eee;
+}
+
+header h1 {
+  margin-bottom: 0.5rem;
+  color: var(--accent); /* Brand color for title */
+}
+
 a {
   padding: var(--space);
   border: var(--line);
@@ -52,7 +67,13 @@ main {
 footer {
   position: fixed;
   bottom: 0;
+ left: 0;
+  width: 100%; /* Ensures it spans the full width */
+  background-color: #222; /* Dark footer */
+  color: white; /* White text */
+  padding: 10px 0;
   text-align: center;
+  z-index: 100; /* Ensures it sits on top of other content */
 }
 /* ====== Articles Grid Layout ====
 Setting the rules for how articles are placed in the main element.
@@ -75,6 +96,7 @@ 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 {
+  background: white;
   border: var(--line);
   padding-bottom: var(--space);
   text-align: left;
@@ -87,3 +109,33 @@ article {
     grid-column: span 3;
   }
 }
+
+/* Reset figure margins so the image touches the edges */
+figure {
+  margin: 0;
+  grid-column: span 3; /* Ensure figure spans full width of card */
+}
+
+article > * {
+  grid-column: 2/3;
+}
+article > figure {
+  grid-column: 1 / -1; /* Spans full width */
+}
+
+a {
+  display: inline-block;
+  text-decoration: none;
+  background-color: var(--accent);
+  color: white;
+  padding: 10px 20px;
+  border-radius: 20px; /* Pill shape */
+  font-weight: bold;
+  border: none;
+  transition: background-color 0.3s ease;
+  margin-top: 10px;
+}
+
+a:hover {
+  background-color: #003d82; /* Darker blue on hover */
+}