CodeYourFuture · KKtech06 · Jan 14, 2026 · Jan 18, 2026 · Jan 18, 2026 · Jan 18, 2026
diff --git a/Wireframe/index.html b/Wireframe/index.html
@@ -1,33 +1,77 @@
 <!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>
-      <p>
-        This is the default, provided code and no changes have been made yet.
+      <h1> Github Development</h1>
+      <p 
+       id="p1">
+       <em>
+        Welcome to the Github Development Page
+        </em>
       </p>
     </header>
+
+    <!--Article 1 README file -->
+
     <main>
       <article>
-        <img src="placeholder.svg" alt="" />
-        <h2>Title</h2>
+        <img src="https://miro.medium.com/v2/resize:fit:571/1*enNiXvUd5xWCMGrq89Jgog.png" 
+        alt="README file example" />
+        <h2>What is the purpose of a README file?</h2>
+        <p>
+          A README file contains descriptions and instructions within a project
+          and explains how it works.
+
+        </p>
+        <a href="https://medium.com/@fulton_shaun/readme-rules-structure-style-and-pro-tips-faea5eb5d252"
+        > Read More about Readme</a>
+      </article>
+
+      <!--Article 2 Wireframe-->
+
+      <article>
+        <img src="https://cdn.codegym.cc/images/article/d7ebea93-ecd2-476a-a9ac-468e5e9ca650/512.jpeg" alt=" Read More about Wireframe" />
+        <h2>What is the purpose of a wireframe?</h2>
+        <p>
+          A wireframe is a planning step used before coding 
+          to decide the layoutand structure of a webpage.
+
+        </p>
+        <a href="https://www.codecademy.com/article/learn-wireframing"
+        >Read More about Wireframe
+        </a>
+      </article>
+
+      <!--Article 3 Branch in Git-->
+
+      <article>
+        <img src="https://cdn.textstudio.com/output/graphic/preview/large/0/6/9/9/9960_a863ac94.webp" 
+        alt="Git branch diagram" />
+        <h2>What is a branch in Git?</h2>
         <p>
-          Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam,
-          voluptates. Quisquam, voluptates.
+          A Git branch is more like a copy of your code where others
+          can change and add to it without affecting your main code.
         </p>
-        <a href="">Read more</a>
+        <a href="https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches"
+        >Read More about Git Branches</a>
       </article>
+
     </main>
     <footer>
       <p>
-        This is the default, provided code and no changes have been made yet.
+      <strong>
+        © 2026 Github Development build by Karim M'hamdi
+        </strong>
       </p>
     </footer>
   </body>
-</html>
+</html>
diff --git a/Wireframe/style.css b/Wireframe/style.css
@@ -1,21 +1,4 @@
-/* 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);
@@ -24,12 +7,20 @@ As well as useful links to learn more */
   --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);
+  background-color: antiquewhite;
+}
+
+#p1{
+  text-align: center;
+}
+
+h1{
+  text-align: center;
 }
 a {
   padding: var(--space);
@@ -41,39 +32,43 @@ svg {
   width: 100%;
   object-fit: cover;
 }
-/* ====== Site Layout ====== 
-Setting the overall rules for page regions
-https://www.w3.org/WAI/tutorials/page-structure/regions/
-*/
+
+article img{
+  height: 220px;
+  object-fit: cover;
+}
+
+
 main {
   max-width: var(--container);
   margin: 0 auto calc(var(--space) * 4) auto;
 }
-footer {
+
+
+footer{
   position: fixed;
-  bottom: 0;
+  bottom: 0%;
+  left: 0%;
+  width: 100%;
   text-align: center;
+  background-color: blanchedalmond;
+  color:rgb(18, 18, 47);
+  padding: 18px;
+  margin-top: calc(var(--space) * 2);
 }
-/* ====== 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;
   }
+  padding-bottom: 90px ;
 }
-/* ====== 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);