<commit_before><!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
<title>Blog Template Page</title>
</head>
<body>
<header>
<h1>
Blog Header
</h1>
  <nav>
    <ul>
    <li><a href="#">Home</a></li>
    <li><a href="#">About</a></li>
    <li><a href="#">Portfolio</a></li>
    </ul>
  </nav>
</header>
<section>
  <p>
  Random text goes here
  </p>
</section>
<section>
 <p>
 Blog text goes here
 </p>
</section>
<section>
    <p>
    Blog text goes here
    </p>
</section>
<br>
</body>
</html>

<!--
How was it to wireframe and create an HTML page with a pair?

When we came together and split up the work, who will do the wireframe and who will do the translation from wireframe to html syntax.  We breeze through it pretty fast.

Did you find wireframing to be helpful to your development process?

Yes, I found it extremely useful to create a wireframe first then create something from it and how where things are going to be located.

What did you and your pair decide made a good wireframe?

We split the work load, we put our ideas together and know what we wanted in a wireframe.  Since we split the work load, as long as it has my ideas and what I want it to have.  It would look un-natural because of the styling isn't on the page yet.  So therefor when the styling comes in to place.  It could be the same but have a totally different look and feel to it but the basic idea would be the same.

What new semantic elements did you learn about (if any)?

I learned a new semantic called "nav".  With nav is generally place on top of the screen for the naviagtion of the page.
<commit_msg>added link<commit_after><!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
<title>Blog Template Page</title>
</head>
<body>
<header>
<h1>
Blog Header
</h1>
  <nav>
    <ul>
    <li><a href="#">Home</a></li>
    <li><a href="#">About</a></li>
    <li><a href="#">Portfolio</a></li>
    </ul>
  </nav>
</header>
<section>
  <p>
  Random text goes here
  </p>
</section>
<section>
 <p>
 Blog text goes here
 </p>
</section>
<section>
    <p>
    Blog text goes here
    </p>
</section>
<br>
<img src="../imgs/wireframe-blogs.png"
</body>
</html>

<!--
How was it to wireframe and create an HTML page with a pair?

When we came together and split up the work, who will do the wireframe and who will do the translation from wireframe to html syntax.  We breeze through it pretty fast.

Did you find wireframing to be helpful to your development process?

Yes, I found it extremely useful to create a wireframe first then create something from it and how where things are going to be located.

What did you and your pair decide made a good wireframe?

We split the work load, we put our ideas together and know what we wanted in a wireframe.  Since we split the work load, as long as it has my ideas and what I want it to have.  It would look un-natural because of the styling isn't on the page yet.  So therefor when the styling comes in to place.  It could be the same but have a totally different look and feel to it but the basic idea would be the same.

What new semantic elements did you learn about (if any)?

I learned a new semantic called "nav".  With nav is generally place on top of the screen for the naviagtion of the page.

{'fraction_non_alphanumeric': 0.0983910891089109, 'fraction_numerical': 0.0018564356435643563, 'mean_word_length': 3.4902777777777776, 'pattern_counts': {'":': 0, '<': 92, '<?xml version=': 0, '>': 89, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5795446', 'n_tokens_mistral': 1004, 'n_tokens_neox': 974, 'n_words': 525}