diff --git a/GitHomeworkTest b/GitHomeworkTest
new file mode 160000
index 000000000..e31b81cc7
--- /dev/null
+++ b/GitHomeworkTest
@@ -0,0 +1 @@
+Subproject commit e31b81cc731b43748c6be5036de3181be3d66516
diff --git a/Joma Alrzini.md b/Joma Alrzini.md
new file mode 100644
index 000000000..e69de29bb
diff --git a/Wireframe/Git.png b/Wireframe/Git.png
new file mode 100644
index 000000000..914616135
Binary files /dev/null and b/Wireframe/Git.png differ
diff --git a/Wireframe/ReadMe.jpg b/Wireframe/ReadMe.jpg
new file mode 100644
index 000000000..10e8d93af
Binary files /dev/null and b/Wireframe/ReadMe.jpg differ
diff --git a/Wireframe/Wireframe1.png b/Wireframe/Wireframe1.png
new file mode 100644
index 000000000..cce5f4673
Binary files /dev/null and b/Wireframe/Wireframe1.png differ
diff --git a/Wireframe/index.html b/Wireframe/index.html
index 0e014e535..4d28b4f66 100644
--- a/Wireframe/index.html
+++ b/Wireframe/index.html
@@ -1,33 +1,88 @@
 <!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.
-      </p>
-    </header>
-    <main>
+
+<head>
+  <meta charset="UTF-8" />
+  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+  <title>CYF sprint 1</title>
+  <link rel="stylesheet" href="style.css" />
+</head>
+
+<body>
+  <header>
+    <h1>My First Program</h1>
+
+    <h2>What is the purpose of a README file?</h2>
+    <p>
+      The purpose of a README file is to explain what a project is and how to use it. Furthermore, it helps anyone who
+      read the project understand the project quickly.
+    </p>
+
+  </header>
+  <main>
+    <article>
+      <img src="ReadMe.jpg" alt="ReadMe" width="100" height="400">
+    </article>
+  </main>
+
+  <section class="grid">
+
+    <main class="article-row">
+      <article>
+        <img src="Wireframe1.png" alt="ReadMe" width="70" height="400">
+        <p>
+        <h2>What is the purpose of a wireframe? </h2>
+        </p>
+
+        <button onclick="toggleText()" class="button1">Read Me</button>
+
+        <p id="ReadMe1" style="display:none;">
+          A wireframe is used to plan the basic structure and layout of a webpage or
+          application before design and development begin. It focuses on functionality and
+          content placement rather than colours or styling, helping to visualise how users
+          will interact with the page. Wireframes improve communication between designers
+          and developers, support better user experience planning, and save time by
+          identifying issues early
+          while also guiding the structure of the HTML used in development.
+        </p>
+        <script>
+          function toggleText() {
+            const text = document.getElementById("ReadMe1");
+            text.style.display = text.style.display === "none" ? "block" : "none";
+          }
+        </script>
+      </article>
       <article>
-        <img src="placeholder.svg" alt="" />
-        <h2>Title</h2>
+        <img src="Git.png" alt="ReadMe" width="70" height="400">
         <p>
-          Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam,
-          voluptates. Quisquam, voluptates.
+        <h2>What is a branch in Git? </h2>
         </p>
-        <a href="">Read more</a>
+        <button onclick="toggleText1()" class="button1">Read Me</button>
+
+        <p id="ReadMe2" style="display:none;">
+          A branch enables developers to implement changes, test new ideas,
+          and commit work independently. After completion and review, the branch is merged into
+          the main branch, commonly referred to as main or master. This process facilitates team
+          collaboration, version management, and maintains the stability of the main
+          codebase during ongoing development.</p>
+
+        <script>
+          function toggleText1() {
+            const text = document.getElementById("ReadMe2");
+            text.style.display = text.style.display === "none" ? "block" : "none";
+          }
+        </script>
       </article>
     </main>
-    <footer>
+
+
+
+    <footer class="page-footer">
       <p>
-        This is the default, provided code and no changes have been made yet.
+
+        <a href="https://www.w3schools.com/html/ ">This is link to W3shool</a>
       </p>
     </footer>
-  </body>
-</html>
+</body>
+
+</html>
\ No newline at end of file
diff --git a/Wireframe/style.css b/Wireframe/style.css
index be835b6c7..0d3241cf7 100644
--- a/Wireframe/style.css
+++ b/Wireframe/style.css
@@ -74,6 +74,22 @@ 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-grid {
+  display: grid;
+  grid-template-columns: repeat(2, 1fr);
+  gap: 20px;
+}
+.article-row {
+  display: flex;
+  gap: 20px;
+  grid-template-columns: 1fr 1fr;
+  height: 920px;
+}
+
+.article-row article {
+  flex: 1;
+}
 article {
   border: var(--line);
   padding-bottom: var(--space);
@@ -87,3 +103,19 @@ article {
     grid-column: span 3;
   }
 }
+.button1 {
+  padding: 4px 8px;
+  align-items:left;
+  font-size: 12px;
+  width: 80px;
+  height: 20px;
+}
+
+.page-footer {
+  position: relative;
+  display: flex;
+  width: 100%;
+  text-align: center;
+  font-size: 0.9em;
+  justify-content: center;
+}
