Skip to content

Commit d175bc8

Browse files
FarancisGHFarancisGH
committed
Made changes to Wireframe/index.html and index.html
1 parent 9f18fff commit d175bc8

2 files changed

Lines changed: 36 additions & 96 deletions

File tree

‎Wireframe/index.html‎

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -95,9 +95,6 @@ <h2>Branches</h2>
9595
</article>
9696

9797
</main>
98-
99-
</body>
100-
98+
</body>
10199
</html>
102100

103-
<!DOCTYPE html>

‎index.html‎

Lines changed: 35 additions & 92 deletions
Original file line numberDiff line numberDiff line change
@@ -1,103 +1,46 @@
11
<!DOCTYPE html>
2-
3-
<html>
4-
52
<html lang="en">
6-
73
<head>
8-
94
<meta charset="UTF-8" />
10-
115
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
12-
13-
<title>Wireframe</title>
14-
15-
<link rel="stylesheet" href="style.css" />
16-
6+
<title>Coursework</title>
7+
<style>
8+
:root {
9+
--paper: oklch(7 0 0);
10+
--ink: color-mix(in oklab, var(--color) 5%, black);
11+
--font: 100%/1.5 system-ui;
12+
--space: clamp(6px, 6px + 2vw, 15px);
13+
--line: 1px solid;
14+
}
15+
body {
16+
background: var(--paper);
17+
color: var(--ink);
18+
font: var(--font);
19+
max-width: 1280px;
20+
margin: 0 auto;
21+
}
22+
</style>
1723
</head>
18-
1924
<body>
20-
25+
<header><h1>🧐 CYF Coursework Disposable Branch Previews</h1></header>
2126
<main>
22-
23-
<header>
24-
25-
<strong><h1>ReadMe, Wireframe and Branches.</h1></strong>
26-
27-
<p>
28-
29-
Below we will be discussing on what the purpose of a Readme file is, the purpose of a wireframe and what a branch is and what a branch in git is. But first, lets look at this image.
30-
31-
</p>
32-
33-
</header>
34-
35-
<section class="section1">
36-
37-
<img src="https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcQJS8HBwSIm--Dd_YOAfCSDnQUexFj_Qa8W_A&s" alt="Image"/>
38-
39-
<article >
40-
41-
<h2>ReadMe</h2>
42-
43-
<p>
44-
45-
A ReadMe file is a document that provides essential information about a project, software, or repository. It serves as a guide for users and developers, offering details such as installation instructions, usage guidelines, features, and licensing information. The primary purpose of a ReadMe file is to help users understand what the project is about, how to use it effectively, and how to contribute if applicable. It often includes sections like an overview, prerequisites, installation steps, usage examples, and contact information for support.
46-
47-
</p>
48-
49-
<a href="https://www.geeksforgeeks.org/git/what-is-readme-md-file/" id="section1link">Click to learn more.</a>
50-
51-
</article>
52-
53-
</section>
54-
55-
<section class="sectionGroup">
56-
57-
<section class="section2">
58-
59-
<article>
60-
61-
<img src="https://cdn.sanity.io/images/599r6htc/regionalized/4c8605ad998d69b03a6eefb850cce5e23a0a96dc-2880x1440.png?w=2880&h=1440&q=75&fit=max&auto=format" alt="Image of a wireframe"/>
62-
63-
<h2>Wireframe</h2>
64-
27+
<ol>
28+
<li>
29+
<h2><a href="/Wireframe">Project 1: Wireframe</a></h2>
6530
<p>
66-
67-
A wireframe is a visual representation or blueprint of a website, application, or user interface. It outlines the basic structure, layout, and functionality of a design without focusing on detailed aesthetics. Wireframes are typically created in the early stages of the design process to help designers, developers, and stakeholders visualize the overall structure and flow of a project. They often include placeholders for content, navigation elements, and interactive features, allowing for easy communication and collaboration among team members before moving on to more detailed design and development phases.
68-
31+
Mentors:
32+
<a href="Wireframe/readme.md">open the assignment in a tab</a>
6933
</p>
70-
71-
<a href="https://www.figma.com/resource-library/what-is-wireframing/" id="section2link">Click to learn more.</a>
72-
73-
</article>
74-
75-
</section>
76-
77-
<section class="section3">
78-
79-
<article>
80-
81-
<img src="https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/d/0d19837bbaf82a71ab35b2a62c5f8776af8e900a.png" alt="Image of git branches"/>
82-
83-
<h2>Branches</h2>
84-
85-
<p>
86-
87-
In version control systems like Git, a branch is a separate line of development that allows multiple developers to work on different features or fixes simultaneously without affecting the main codebase. Branches enable teams to isolate changes, experiment with new ideas, and collaborate more effectively. When a feature or fix is complete, the changes made in the branch can be merged back into the main branch (often called "main" or "master"). This process helps maintain a clean and stable codebase while allowing for parallel development efforts.
88-
89-
</p>
90-
91-
<a href="https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell" id="section3link">Click to learn more.</a>
92-
93-
</section>
94-
95-
</article>
96-
34+
</li>
35+
<li>
36+
<h2><a href="/Form-Controls">Project 2: Form Controls</a></h2>
37+
<p>
38+
Mentors:
39+
<a href="Form-Controls/readme.md">open the assignment in a tab</a>
40+
</p>
41+
</li>
42+
</ol>
9743
</main>
98-
99-
</body>
100-
101-
</html>
102-
103-
<!DOCTYPE html>
44+
<footer><a href="HOW_TO_REVIEW.md">HOW TO REVIEW MD</a></footer>
45+
</body>
46+
</html>

0 commit comments

Comments
 (0)