obaidazeino/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

solution

1. header- most important information
2. h1- most important piece of content
3. time datetime- marks text as a time or date
4. p- a paragraph
5. videoposter="..." autoplay loop muted controls- for embedding movies into a website
6. h2- subheader
7. p- a paragraph.
8. data value="480" for numerical pieces of information
9. ??
10. time datetime="p4d" marks text as a time or date
11. a href="..." for making hyperlinks
12. h2- subheader
13. ul- unordered list
14. li- list item
15. h2- subheader
16. dl- description list
17. dt- title of description
18. dd- description defintion
19. h2- subheader
20. blockquote- large stand alone quote
21. p- paragraph
22. footer- least important information
23. cite- citation from another source
24. h2- subheader
25. address- for addresses, duh

@abhaysharma