kylesousae / content-to-code

Given a chunk of content, determine the groups & HTML tags—without writing any code.

summary	time	deliverables
Given a chunk of content, determine the groups & HTML tags—without writing any code.	1 hour	A GitHub Issue

Content to code

Overview

• Fork & clone this repository.
• Using the two PDFs, determine the most semantically appropriate HTML tag for each numbered content
• There are two PDFs: content-to-code.pdf — Just the plain content, by itself content-to-code-numbered.pdf — A messier version showing each numbered tag
• Submit your HTML tag choices with explanations.

---

Hand in

On GitHub’s website, on your forked repository, create an Issue labeled “Solution”—and tag your teacher.

Inside the content of the Issue write out your tag choices & explanations. Here’s an example:

1. h1 — The most important content
2. abbr — Defines a shortened word
3. p — Some none specific text content
   ⋮

The above is just an example—not the answers.

Don’t forget to tag your teacher!

content-to-code's Issues

Solutions

1. link href- css link tag
2. h1- most important part of the page.
3. datetime- month, days, year.
   4.main- primary content on the page.
4. video poster- embedding a movie into the website.
5. h2- subheading for h1.
6. p- generic paragraph of text.
7. dl- description list.
8. dt- length of time.
9. dd- 4days.
10. id- link on the same page.
11. h3- content subheading.
12. ol- ordered list.
13. li- single list item.
14. h4- content subheading.
15. ul- unordered list.
16. i- defines a game title.
17. dfn- definition of the game title.
18. h5- content subheading.
19. p- a generic paragraph.
20. q- small quote.
21. p- generic paragraph.
22. cite- the persons name.
23. h6- content subheading.
24. address- contact information.

@hellachella