Skip to content

Commit f7fdc12

Browse files
authored
Created index.html
This is the markdown-to-html file with semantic html practice.
1 parent fb73c3d commit f7fdc12

File tree

1 file changed

+47
-0
lines changed

1 file changed

+47
-0
lines changed

lesson_01/chelseaogbonnia/index.html

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
<!DOCTYPE html>
2+
<html lang="en">
3+
<head>
4+
<meta charset="UTF-8">
5+
<meta name="viewport" content="width=device-width, initial-scale=1.0">
6+
<link rel="stylesheet" type="text/css" href="style.css">
7+
<title>Read Me HTML</title>
8+
</head>
9+
<body>
10+
<main>
11+
<h1 id="personal-readme">Personal README</h1>
12+
<section>
13+
<h2 id="introduction">Introduction</h2>
14+
<article>
15+
<div>
16+
<p>Hi there! I’m currently on my journey to becoming a full-stack software engineer. I enjoy solving problems and learning new technologies as I go. This README gives you a little insight into how I work best, what motivates me, and how I approach learning and collaboration.</p>
17+
</div>
18+
</article>
19+
</section>
20+
<section>
21+
<h2 id="how-i-learn-best">How I Learn Best</h2>
22+
<div>
23+
<ul>
24+
<li>Independent Learning: I prefer figuring things out on my own, and I enjoy working through challenges independently before reaching out for help. This allows me to build resilience and a deeper understanding of the material.</li>
25+
<li>Visual Learning: I grasp concepts more quickly when I can visualize them. Charts, diagrams, and presentations help me organize information in a way that sticks. I find that seeing a process step-by-step or looking at a flowchart helps solidify abstract concepts.</li>
26+
<li>Planning Ahead: I like having access to the curriculum early so I can break down topics and structure my learning schedule. When I can map out what’s ahead, I feel more in control and can manage my time better.</li>
27+
<li>Mastering Subjects: I work on a subject until I feel confident enough to explain it to someone else. Teaching is one of the ways I confirm my own understanding. If I can make something simple enough for others to understand, I know I’ve truly mastered it.</li>
28+
<li>Note-Taking: I’m not the type to take long-winded notes. Instead, my notes are an organized summary of my thoughts. They serve as a reference point for later, but I tend to work through most concepts in my head first before writing anything down.</li>
29+
</ul>
30+
</div>
31+
</section>
32+
<section>
33+
<h2 id="what-i-value-in-collaboration">What I Value in Collaboration</h2>
34+
<ul>
35+
<li>Clear Communication: I appreciate clear, concise communication, especially in code reviews or when getting feedback. I respond well to messages that are to the point, with direct and actionable suggestions.</li>
36+
<li>Respect for Work Styles: I understand that everyone has their own preferred way of working, and I appreciate when team environments respect those differences. For me, that means giving me space to work independently but also being available for collaboration when needed.</li>
37+
<li>Knowledge Sharing: I believe that a team works best when everyone shares what they’ve learned. I enjoy exchanging tips, resources, or strategies that can help others grow. When the team is open to learning from each other, everyone benefits.</li>
38+
</ul>
39+
</section>
40+
<section>
41+
<h2 id="fun-fact">Fun Fact</h2>
42+
<p>I often like to challenge myself with side projects. Whether it&#39;s exploring a new API or building a small application for fun, these projects give me a chance to experiment with new technologies and sharpen my skills.</p>
43+
<p><img src="https://github.com/user-attachments/assets/75cce26f-8244-4aa9-ac0a-39783d4e4473" alt="Python API Example"></p>
44+
</section>
45+
</main>
46+
</body>
47+
</html>

0 commit comments

Comments
 (0)