CodeYourFuture · FarancisGH · Jan 20, 2026 · Jan 20, 2026
diff --git a/Form-Controls/README.md b/Form-Controls/README.md
diff --git a/Form-Controls/index.html b/Form-Controls/index.html
diff --git a/Wireframe/index.html b/Wireframe/index.html
@@ -7,27 +7,37 @@
     <link rel="stylesheet" href="style.css" />
   </head>
   <body>
+    <footer>
     <header>
-      <h1>Wireframe</h1>
+      <strong><h1>ReadMe, Wireframe and Branches.</h1></strong>
       <p>
-        This is the default, provided code and no changes have been made yet.
-      </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="placeholder.svg" alt="" />
-        <h2>Title</h2>
+        <h2>ReadMe</h2>
         <p>
-          Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam,
-          voluptates. Quisquam, voluptates.
+          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. It often includes sections like an overview, prerequisites, installation steps, usage examples, and contact information for support.
         </p>
-        <a href="">Read more</a>
+        <img src="https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcQJS8HBwSIm--Dd_YOAfCSDnQUexFj_Qa8W_A&s" alt="Image"/>
+        <a href="https://www.geeksforgeeks.org/git/what-is-readme-md-file/">Click to learn more.</a>
+        <article>
+          <h2>Wireframe</h2>
+          <p>
+            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>
+          <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"/>
+          <a href="https://www.figma.com/resource-library/what-is-wireframing/">Click to learn more.</a>
+          <article>
+            <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>
+            <img src="https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/d/0d19837bbaf82a71ab35b2a62c5f8776af8e900a.png" alt="Image of git branches"/>
+            <a href="https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell">Click to learn more.</a>
       </article>
     </main>
-    <footer>
-      <p>
-        This is the default, provided code and no changes have been made yet.
-      </p>
-    </footer>
-  </body>
+  </footer>
+</body>
 </html>
diff --git a/Wireframe/style.css b/Wireframe/style.css
@@ -1,89 +1,33 @@
-/* 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;
-}
-/* ====== Base Elements ======
- General rules for basic HTML elements in any context */
 body {
-  background: var(--paper);
-  color: var(--ink);
-  font: var(--font);
+  margin: 0;
+  padding: 0;
+  font-family: Arial, sans-serif;
 }
-a {
-  padding: var(--space);
-  border: var(--line);
-  max-width: fit-content;
+main {
+  max-width: 900px;
+  margin: 0 auto;
+  padding: 20px;
 }
-img,
-svg {
-  width: 100%;
-  object-fit: cover;
+article {
+  margin-bottom: 40px;
+  text-align: center;
 }
-/* ====== 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;
+img {
+  display: block;         
+  max-width: 100%;        
+  height: auto;
+  margin: 20px auto;       
 }
-footer {
-  position: fixed;
-  bottom: 0;
+h1, h2 {
   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;
-  grid-template-columns: 1fr 1fr;
-  gap: var(--space);
-  > *:first-child {
-    grid-column: span 2;
-  }
+a {
+  display: inline-block;
+  margin-top: 10px;
+  color: #0066cc;
+  text-decoration: none;
 }
-/* ====== 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;
-  }
+
+a:hover {
+  text-decoration: underline;
 }