CodeYourFuture · dcostaprakash · Feb 3, 2026
diff --git a/Wireframe/BranchinGit.png b/Wireframe/BranchinGit.png
diff --git a/Wireframe/Instruction.svg b/Wireframe/Instruction.svg
diff --git a/Wireframe/ReadmeImage.jpg b/Wireframe/ReadmeImage.jpg
diff --git a/Wireframe/ReadmoreGitBranch.html b/Wireframe/ReadmoreGitBranch.html
@@ -0,0 +1,29 @@
+<!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>
+    <main>
+      <article>
+        <h1>What is a branch in Git</h1>
+        <p>
+In Git, a branch is like a separate workspace where you can make changes and try new ideas without affecting the main project. Think of it as a "parallel universe" for your code.</p>
+
+<h2>Why Use Branches?</h2>
+<p>Branches let you work on different parts of a project, like new features or bug fixes, without interfering with the main branch.</p>
+<p>
+<h2>Common Reasons to Create a Branch</h2>
+<ul>
+<li>Developing a new feature</li>
+<li>Fixing a bug</li>
+<li>Experimenting with ideas</li></ul>
+        </p>
+        <a href="C:\Users\praka\Module-Onboarding\Wireframe\webpage.html">Close/Back</a>
+      </article>
+    </main>
+  </body>
+</html>
diff --git a/Wireframe/ReadmoreReadme.html b/Wireframe/ReadmoreReadme.html
@@ -0,0 +1,29 @@
+<!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>
+    <main>
+      <article>
+        <h1>Purpose of a Readme file</h1>
+        <p>A readme file is a document which contains essential information about a program.
+          It includes instructions, additional help and details regarding updates.</p>
+
+<h2>Why is it important to include a README file in my project?</h2>
+<p>Including a README file in your project provides users with vital information to get started. It enhances user experience by offering clear instructions on installation, usage, 
+  and troubleshooting. This transparency can also help attract contributors and users who are looking for well-documented projects.</p>
+<p>
+<h2>What should I include in my README file?</h2>
+<p>A comprehensive README file should include an introduction to the project, installation instructions, usage examples, contribution guidelines, and licensing information. It may
+   also feature sections on troubleshooting, frequently asked questions, and a changelog to track updates and fixes.</p>
+<p>
+        </p>
+        <a href="C:\Users\praka\Module-Onboarding\Wireframe\webpage.html">Close/Back</a>
+      </article>
+    </main>
+  </body>
+</html>
diff --git a/Wireframe/Readmorewireframe.html b/Wireframe/Readmorewireframe.html
@@ -0,0 +1,30 @@
+<!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>
+    <main>
+      <article>
+        <h1>Purpose of Wireframe</h1>
+        <p>
+A purpose of a wireframe to align stakeholders on the project's vision, facilitate early 
+          feedback, and prevent costly, time-consuming revisions during the development phase.</p>
+
+
+<h2>Key Purposes</h2>
+<ul>
+<li>Structure & Layout: Defines where elements like headers, text, images, and buttons will go.</li>
+<li>Functionality: Shows interactive elements (forms, links) and how users navigate through the product.</li>
+<li>User Experience (UX): Maps out the user journey and content hierarchy to ensure intuitive use.</li>
+<li>Collaboration: Provides a shared visual reference for designers, developers, and clients to discuss and approve the core design.</li>
+<li>Early Feedback: Enables quick testing and iteration on core structure before investing in visual design, saving resources.</li> </ul>
+        </p>
+        <a href="C:\Users\praka\Module-Onboarding\Wireframe\webpage.html">Close/Back</a>
+      </article>
+    </main>
+  </body>
+</html>
diff --git a/Wireframe/index.html b/Wireframe/index.html
@@ -10,7 +10,7 @@
     <header>
       <h1>Wireframe</h1>
       <p>
-        This is the default, provided code and no changes have been made yet.
+        This is the default temperory file, provided code and no changes have been made yet.
       </p>
     </header>
     <main>

diff --git a/Wireframe/style.css b/Wireframe/style.css
@@ -38,7 +38,7 @@ a {
 }
 img,
 svg {
-  width: 100%;
+  /* width: 100%; */
   object-fit: cover;
 }
 /* ====== Site Layout ====== 
@@ -53,6 +53,8 @@ footer {
   position: fixed;
   bottom: 0;
   text-align: center;
+  width: 100%;
+  background-color: #f1cece;
 }
 /* ====== Articles Grid Layout ====
 Setting the rules for how articles are placed in the main element.
@@ -86,4 +88,24 @@ article {
   > img {
     grid-column: span 3;
   }
+  .Wireframe {
+    float: left;
+    width: 50%;
+    padding: 15px;
+  }
+}
+
+.side-by-side {
+  display: flex;
+  flex-direction: row;
 }
+
+.article {
+  width: 50%;
+}
+
+.center-header {
+  display: flex;
+  width: 100%;
+  justify-content: center;
+}
diff --git a/Wireframe/webpage.html b/Wireframe/webpage.html
@@ -0,0 +1,70 @@
+<!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>
+    <div class="center-header">
+      <h1>WIREFRAME</h1>
+    </div>
+    <p>
+      This is the webpage for understanding :
+    <ul>
+      <li>Purpose of Readme file</li>
+      <li>Purpose of Wireframe</li>
+      <li>Branch in Git</li>
+    </ul>
+    </p>
+  </header>
+
+  <main>
+    <article>
+      <img src="C:\Users\praka\Module-Onboarding\Wireframe\ReadmeImage.jpg" alt="Instruction Book\" height="300"
+        width="300" />
+      <h2>Purpose of Readme file</h2>
+      <p>
+        A readme file is a document which contains essential information about a program.
+        It includes instructions, additional help and details regarding updates.
+      </p>
+      <a href="C:\Users\praka\Module-Onboarding\Wireframe\ReadmoreReadme.html">Read more</a>
+    </article>
+  </main>
+  <main class="side-by-side">
+
+    <article class="article">
+      <img src="C:\Users\praka\Module-Onboarding\Wireframe\wireframe.png" alt="Wireframe image" height="350"
+        width="600" />
+      <h2>Purpose of Wireframe</h2>
+      <p>A purpose of a wireframe to align stakeholders on the project's vision, facilitate early
+        feedback, and prevent costly, time-consuming revisions during the development phase.
+      </p>
+      <a href="C:\Users\praka\Module-Onboarding\Wireframe\Readmorewireframe.html">Read more</a>
+    </article>
+
+    <article class="article">
+      <img src="C:\Users\praka\Module-Onboarding\Wireframe\BranchinGit.png" alt="Branch Image" height="350"
+        width="600" />
+      <h2>Branch in Git</h2>
+      <p>
+        In Git, a branch is like a separate workspace where you can make changes and try new
+        ideas without affecting the main project.
+      </p>
+      <a href="C:\Users\praka\Module-Onboarding\Wireframe\ReadmoreGitBranch.html">Read more</a>
+    </article>
+  </main>
+
+
+  <footer>
+    <p>
+    Prakash Dcosta - ITP Jan 2026
+    </p>
+  </footer>
+</body>
+
+</html>
diff --git a/Wireframe/wireframe.png b/Wireframe/wireframe.png