Revise content and structure in index.html

khaliun-dev · web-flow · commit 0dd24d5c7e6a · 2026-01-21T21:31:43.000Z
Added three articles, with links. Also a footnote with a link to my github profile.
diff --git a/Wireframe/index.html b/Wireframe/index.html
@@ -8,25 +8,46 @@
   </head>
   <body>
     <header>
-      <h1>Wireframe</h1>
+      <h1>Understanding the developmental cycle of a product</h1>
       <p>
-        This is the default, provided code and no changes have been made yet.
+        A simple website made to explain how README file + WIREFRAME + GIT branching complement each other in developmental workflow for a digital product.
       </p>
     </header>
     <main>
       <article>
-        <img src="placeholder.svg" alt="" />
-        <h2>Title</h2>
+        <img src="placeholder.svg" alt="Image for wireframe article" />
+        <h2>The purpose of a WIREFRAME</h2>
         <p>
-          Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam,
-          voluptates. Quisquam, voluptates.
+          From a product developmental perspective wireframing is essentially a blueprint, an imagie file sent from a client, laying out the structure of a webpage for example, whether it be content placement, naviagation, basic interactions. Then from that skeletal blueprint developers take over and build the product itself.   
         </p>
-        <a href="">Read more</a>
+        <a href="https://en.wikipedia.org/wiki/Website_wireframe">Read more</a>
       </article>
+    
+     <article>
+        <img src="placeholder.svg" alt="Image for README article" />
+        <h2>Purpose of a README file</h2>
+        <p>
+          Now that you have your website layout, first thing you have to read is the README file. In there you will usually find information about the project, guidelines, requirements, licenses etc. The file acts as an evolving filing overview of the product.
+        </p>
+        <a href="https://en.wikipedia.org/wiki/README">Read more</a>
+      </article>
+    
+     <article>
+        <img src="placeholder.svg" alt="Image for GIT branch article" />
+        <h2>Purpose of a branch in GIT</h2>
+        <p>
+          And finally we have branching. As in any collaborative projects, especially if the team is spanning multiple locations, safety - security - support becomes very important. That's where GIT and GITHUB come in. Branching allows you to copy parts of the main code, to work on it independently without accidentally corrupting the main code, and to collaborate effectively on any changes made with your team. Once copy branch has been approved it gets merged into the main code.    
+        </p>
+        <a href="https://en.wikipedia.org/wiki/Branching_(version_control)">Read more</a>
+      </article>
+      
+      
+      
+      
     </main>
     <footer>
       <p>
-        This is the default, provided code and no changes have been made yet.
+        If you liked my website contact me directly on <a href="https://github.com/khaliun-dev">khaliun-dev</a>
       </p>
     </footer>
   </body>
