Skip to content

Manchester | ITP-Jan 2026| Ofonime Edak | Sprint1 | Feature/wireframe #965

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Ofonimeedak wants to merge 4 commits into
base: main
Choose a base branch
from
+190 −0
Open

Manchester | ITP-Jan 2026| Ofonime Edak | Sprint1 | Feature/wireframe #965

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
fdeecfb
all about readMe.md file
Ofonimeedak Jan 17, 2026
69c28cd
wireframe and branching
Ofonimeedak Jan 17, 2026
d47ec1b
add external style sheet
Ofonimeedak Jan 17, 2026
cf64130
style classes
Ofonimeedak Jan 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
108 changes: 108 additions & 0 deletions Wireframe/readMe.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,108 @@
<!doctype html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>Sprint1 Version Control</title>
<link rel="stylesheet" href="readme.css">
</head>
<body>
<head>
<h1>README FILE</h1>
<p class="description">What is the Purpose of a ReadMe</p>
</head>

<section class="readme">
<h2>Introduction</h2>
<p>
According to wikipedia, a A README file contains descriptive information
about the content of a directory in which the file is located. The scope
of the information generally includes the files of the directory, and
may include descendant directories, or even the full directory tree. The
name is intended to draw a user's attention to important and
orientational information about the directory content
</p>

<h2>The Purpose of ReadMe</h2>
<p>
A README file's purpose is to serve as the entry point and overview for
a software project, providing essential information like what the
project does, why it's useful, and how to install, use, or contribute to
it, helping users and new developers quickly understand and get started
with the code. It acts as a project's homepage, reducing friction and
guiding collaboration by centralizing documentation, installation steps,
contribution guidelines, and license details in one easily accessible
file, usually in the project's root directory.
</p>
<summary>
<p>
Without a proper read me, collaborators especially on open source
project find it difficult to understand and contribute to the project
in general
</p>
</summary>
</section>
<section class="wireframe">
<article>
<h2>What is the Purpose of Wireframes</h2>
<p>
Wireframes are skeleton of the web. This skeleton is a two-dimensional
depiction of a page’s interface that shows the spacing of elements on
the page, how content is prioritized, what functionalities are
available, and how users will interact with the site. They also play a
vital role in connecting information architecture to the visual
aspects of the design by showing pathways between the various pages.
Wireframes are intentionally void of color, graphics and stylized
fonts.
</p>
<summary>
Wireframing is a quick and effective way to identify usability issues
early on in your design process
</summary>
</article>
</section>

<section class="branch">

<article>

<h2> What is Branch in Git </h2>

<p> A Git branch is a separate workspace used to make changes without affecting the main project. Once the work is complete,
the changes can be merged back into the main or master branch.
Branches make it easy to:
<ul>
<li> Manage different tasks or features independently </li>
<li>Test changes without affecting live code</li>
<li> Collaborate with others efficiently</li>
</ul>
</p>
</article>
<summary>
Without branching developers will not have the flexibility of making changes and contributing to the main branch after a pull request
</summary>
</section>

<h3>Additional resources and links</h3>

<footer>

<p>
For more resources on README please follow the
<a
href="https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes"
>link</a
>
</p>
<p>
Click
<a
href="https://protoio.medium.com/why-wireframes-are-important-in-the-design-process-de4e773e611"
>here</a> to read more on wireframes
</p>

<p><a href="https://www.geeksforgeeks.org/git/introduction-to-git-branch/"> Branching in git</a></p>

</footer>
</body>
</html>
82 changes: 82 additions & 0 deletions Wireframe/readme.css
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,82 @@
*{

padding: 0px;
margin:0px ;
box-sizing: border-box;
}
body{
background-color: rgb(210, 30, 114);
}
h1{color: black;
margin:10px ;
padding: 5px;




}
.description{color: rgb(127, 255, 238);
margin:10px ;
padding: 5px;




}
h2{color: black;


}
.readme{
color: rgb(127, 255, 238);
color: rgb(127, 255, 238);
font-weight: 100;
margin: 10px;
padding: 5px;
}

.wireframe{
margin: 10px;
padding: 5px;
color: rgb(127, 255, 238);
font-weight: 100;
}
.branch{
margin: 10px;
padding: 5px;
color: rgb(127, 255, 238);
font-weight: 100;
}

ul{
padding: 20px;
}


h3{
text-align: center;
margin: 0 10px;
padding: 10px;
}
footer{
bottom: 0;
position:relative;
text-align: center;
gap: 15px;
margin: 5px;
padding: 10px;
width: 100vw;
height: inherit;
align-content: center;
}











Loading