{"id":53,"date":"2024-09-30T16:51:48","date_gmt":"2024-10-01T00:51:48","guid":{"rendered":"https:\/\/dulce.matmcc.org\/creative-journal\/?p=53"},"modified":"2024-12-11T18:25:16","modified_gmt":"2024-12-12T02:25:16","slug":"dusting-off-html-css","status":"publish","type":"post","link":"https:\/\/dulce.matmcc.org\/creative-journal\/dusting-off-html-css\/","title":{"rendered":"Dusting Off HTML & CSS"},"content":{"rendered":"\n
\n

This is the link to download the documents with all the code I used for this page and in class:<\/p>\n\n\n\n

8-27<\/a>Download<\/a><\/div>\n<\/div>\n\n\n\n
\n\n\n\n
\n

Rem vs Ems<\/h2>\n\n\n\n

Ems used to be the norm in web development, but frankly, when rems joined the party, people started to use them because they made more sense and also made the math a lot <\/em>easier. <\/p>\n\n\n\n

Ems have a complicated existence. They get their name from the letter ‘M’ because the size of an ‘M’ in width is the largest in the alphabet. So, using an em is like using 100% of the font size. To do this, Ems target their parent element. <\/p>\n\n\n\n

By contrast, Rems target the root element hence their name ‘root ems.’<\/p>\n\n\n\n

\n

Example<\/h3>\n\n\n\n

Take a look at the code below:<\/p>\n\n\n\n

\n
\n
<main>\n  <section <\/mark>class<\/mark>=<\/mark>\"em\"<\/mark>>\n    <article <\/mark>class<\/mark>=<\/mark>\"em\"<\/mark>>\n      <p><\/mark>Lorem ipsum\n      dolor sit amet<\/mark><\/p>\n    <\/article>\n  <\/section>\n          \n  <section <\/mark>class<\/mark>=<\/mark>\"rem\"<\/mark>>\n    <article <\/mark>class<\/mark>=<\/mark>\"rem\"<\/mark>>\n      <p><\/mark>Lorem ipsum\n      dolor sit amet<\/mark><\/p>\n    <\/article>\n  <\/section>\n<\/main><\/mark><\/code><\/pre>\n<\/div>\n\n\n\n
\n
main <\/mark>{<\/mark>\n    <\/mark>font-size<\/mark>:<\/mark> <\/mark>10px<\/mark>;<\/mark>\n<\/mark>}<\/mark>\n\nsection.em <\/mark>{<\/mark>\n    <\/mark>font-size<\/mark>:<\/mark> <\/mark>2em<\/mark>;<\/mark>\n<\/mark>}<\/mark>\n\narticle.em <\/mark>{\n<\/mark>    <\/mark>font-size<\/mark>:<\/mark> <\/mark>2em<\/mark>;<\/mark>\n<\/mark>}<\/mark>\n\n\n\n\n<\/code><\/pre>\n<\/div>\n<\/div>\n\n\n\n
As a result of this code, the <article><\/mark><\/code> will result in a font size of 40px. This is because ems look to their parent element for the size. If section is set to 2em, then it looks to it’s parent, <main><\/mark><\/code><\/code><\/code> whose font size is 10px. Two of those is 20px. <article><\/mark><\/code><\/code> is also set to 2rem so the browser looks to it’s parent, <section><\/mark><\/code><\/code> <section><\/mark><\/code><\/code>‘s font size is 20px so two of those would make it 40px. <\/p>\n\n\n\n
\n
\n
:root <\/mark>{<\/mark>\n    <\/mark>font-size<\/mark>:<\/mark> <\/mark>10px<\/mark>;<\/mark>\n<\/mark>}<\/mark>\n\nsection.rem <\/mark>{<\/mark>\n    <\/mark>font-size<\/mark>:<\/mark> <\/mark>2rem<\/mark>;<\/mark>\n<\/mark>}<\/mark>\n\narticle.rem <\/mark>{\n<\/mark>    <\/mark>font-size<\/mark>:<\/mark> <\/mark>2rem<\/mark>;<\/mark>\n<\/mark>}<\/mark>\n\n<\/code><\/pre>\n<\/div>\n\n\n\n
\n
However, replacing the above CSS with this code, would result in the text being 20px. When the font size of <section><\/mark><\/code><\/code> is set to 2rem, it looks to the root whose font size is 10px, making it 20px. <article><\/mark><\/code><\/code>‘s font size is also set to 2rem which makes it look to the root as well. Despite it’s parent being set to 2rem, it makes no difference. On a related note, :root<\/mark><\/code><\/code><\/code> refers to the root of the document or the <html><\/mark><\/code><\/code> element which is represented by the html selector in CSS. It’s a pseudo-class so it has a higher specificity. <\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\n
\n
Block vs Inline Elements<\/h2>\n\n\n\n
Block elements span the entire width of the viewport which makes elements that come after it appear under it because there is no space next to them. Examples of these elements are headers, paragraphs, and lists<\/p>\n\n\n\n
Inline elements do not take the entire width of the viewport. They only take up the space they need to based on their content. These can appear inside block elements. Some examples are span, a, and em. <\/p>\n<\/div>\n\n\n\n
\n\n\n\n
\n
Semantic Tags<\/h2>\n\n\n\n
Semantic elements are elements that give the browser some meaning as to what content will be going inside it. They don’t use up space on the screen and are for the developer to organize their code and content in a much easier manner both for them and anyone they want to share their code with. Semantic elements also make it easier to target a large block of code to style and then find it later because there aren’t a million divs. Before semantic elements, divs and spans were overwhelmingly used and classes and ids were used to differentiate them, but that quickly became extremely confusing. These are the most common semantic tags:<\/p>\n\n\n\n
<header><\/mark><\/code><\/code><\/code> – A header is like an introduction to the website. It appears at the top and is usually the first element in the body. It can contain hero images, the message of the brand, or a logo. <\/p>\n\n\n\n
<nav><\/mark><\/code><\/code><\/code> – In here goes any type of navigation. Most of the time, unordered lists and list items are found inside this tag. Navigation also appears at the top of the webpage. There are many types of navigation such as global navigation which is always present or navigation that maybe specific to a certain page. These can be differentiated with classes or ids, but navigation always goes inside a nav tag. <\/p>\n\n\n\n
<main><\/mark><\/code><\/code><\/code> – Main contains all the main content of the document. This can be made up of multiple sections and articles. <\/p>\n\n\n\n
<section><\/mark><\/code><\/code><\/code> – A section typically contains a heading inside it and it defines a section of the document. Each section contains a different topic like how each paragraph in an essay contains a new idea.<\/p>\n\n\n\n
<article><\/mark><\/code><\/code><\/code> – Articles are like sections of a section. They can go alone, but can also be nested within a section. They are used to differentiate subtopics of the same topic.<\/p>\n\n\n\n
<aside><\/mark><\/code><\/code><\/code> – An aside is used for content that is related to the website, but separate from the content inside <main>. Usually, this content appears on the side of the screen. <\/p>\n\n\n\n
<footer><\/mark><\/code><\/code><\/code> – This goes at the bottom of a webpage. It typically has contact information, links to other resources, and copyright information.<\/p>\n\n\n\n
Here are some more semantic tags<\/a>.<\/p>\n<\/div>\n\n\n\n
\n\n\n\n
\n
Viewport Units<\/h2>\n\n\n\n
There are four viewport units: vh, vw, vmin, vmax. They are units of measurement used in CSS based on the viewport size. These units are responsive since they change with the size of the viewport. This is a helpful website<\/a> to understand these units.<\/p>\n\n\n\n
Vh stands for viewport height. 1vh is 1% of the viewport while 100vh is 100% of the viewport.<\/p>\n\n\n\n
Vw stands for viewport width. 1vw is 1% of the viewport while 100vw is 100% of the viewport. <\/p>\n\n\n\n
Vmin stands for viewport minimum. This is based off of the smallest dimension of the viewport. 1vmin would be 1% of the width if it was smaller than the length. <\/p>\n\n\n\n
Vmax stands for viewport maximum. This is based off of the largest dimension of the viewport. 100vmax would be 100% of the length if it was larger than the width.<\/p>\n<\/div>\n\n\n\n
\n\n\n\n
\n
Emmet<\/h2>\n\n\n\n
Emmet is a toolkit that makes it easier to write HTML and CSS. This is the link to the emmet cheat sheet<\/a>.<\/p>\n\n\n\n
The following are shortcuts that I believe are the most helpful as well as the ones I use\/have used the most: <\/p>\n\n\n\n
\n
Typing In Multiple Spots<\/h3>\n\n\n\n
Holding down Command while clicking multiple places in the code allows for the user to type the same thing in multiple spots. This is useful for adding things like classes or ids to multiple elements or indenting multiple elements. Press command again in the same spots to remove the effect. <\/p>\n<\/div>\n\n\n\n
\n
Creating Long Blocks of Code With One Line<\/h3>\n\n\n\n
This line, nav#global>ul>li*5>a[href=#]<\/mark><\/code>, creates the code below:<\/p>\n\n\n\n
\n
\n
<nav <\/mark>id<\/mark>=<\/mark>\"global\"<\/mark>>\n  <ul>\n    <li><a <\/mark>href<\/mark>=<\/mark>\"#\"<\/mark>><\/a><\/li>\n    <li><a <\/mark>href<\/mark>=<\/mark>\"#\"<\/mark>><\/a><\/li>\n    <li><a <\/mark>href<\/mark>=<\/mark>\"#\"<\/mark>><\/a><\/li><\/mark>\n    <li><a <\/mark>href<\/mark>=<\/mark>\"#\"<\/mark>><\/a><\/li>\n    <li><a <\/mark>href<\/mark>=<\/mark>\"#\"<\/mark>><\/a><\/li>\n  <\/ul>\n<\/nav><\/mark><\/code><\/pre>\n<\/div>\n\n\n\n
\n
Now, let’s break it apart. The #<\/mark><\/code><\/code><\/code> specifies an id. So nav#global<\/mark><\/code><\/code><\/code> is a nav tag with the id “global” Anything following a ><\/mark><\/code><\/code><\/code> is a child element and goes down a layer in the hierarchy. To go back up, you use ^<\/mark><\/code><\/code><\/code>. Inside our nav goes an unordered list and inside that are list items. *<\/mark><\/code><\/code><\/code> represents multiplication so li*5<\/mark><\/code><\/code><\/code> makes 5 list items. Inside each of those list items is an anchor. By default, when Emmet creates an anchor, the href attribute is already there, but there is nothing inside the quotation marks. To place a #<\/code><\/mark> inside the quotation marks (which in this context is used as a placeholder), use []<\/mark><\/code><\/code><\/code>. Inside them, specify the attribute and<\/p>\n<\/div>\n<\/div>\n\n\n\n
set them equal to something: [href=#]<\/mark><\/code><\/code><\/code>. Press tab and voila.<\/p>\n<\/div>\n\n\n\n
\n
Other Useful Short Cuts<\/h3>\n\n\n\n
\n
\n
Siblings

<\/p>\n\n\n\n
header>h2^img+p<\/mark><\/code><\/code><\/code>
<\/p>\n\n\n\n
<header>\n  <h2><\/h2>\n<\/header>\n<img <\/mark>src<\/mark>=<\/mark>\"\"<\/mark> alt<\/mark>=<\/mark>\"\"<\/mark>>\n<p><\/p><\/mark>\n\n\n\n\n\n\n<\/code><\/pre>\n<\/div>\n\n\n\n
\n
Text & Item Numbering <\/p>\n\n\n\n
ul>li*5{Item $}<\/mark><\/code><\/code><\/code>
<\/p>\n\n\n\n
<ul>\n  <li><\/mark>Item 1<\/mark><\/li>\n  <li><\/mark>Item 2<\/mark><\/li>\n  <li><\/mark>Item 3<\/mark><\/li>\n  <li><\/mark>Item 4<\/mark><\/li>\n  <li><\/mark>Item 5<\/mark><\/li>\n<\/ul><\/mark><\/code><\/pre>\n<\/div>\n\n\n\n
\n
Grouping
<\/p>\n\n\n\n
section>(header>h2+p)+p<\/mark><\/code><\/code><\/code>
<\/p>\n\n\n\n
<section>\n  <header>\n    <h2><\/h2>\n      <p><\/p>\n  <\/header>\n  <p><\/p>\n<\/section><\/mark>\n\n\n\n\n\n<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\n
\n
Developer Tools<\/h2>\n\n\n\n
To open the Developer Tools in Chrome: 3 dots in the corner > More Tools > Developer Tools <\/em>or use the shortcut command + control + I. <\/p>\n\n\n\n
In the developer tools, developers can click line by line on their html and see what styles are placed on it. Styles can be altered in real time temporarily in the Styles section on the right pane. However, if the page is refreshed, the styles are reset to how they are written on the style sheet.<\/p>\n\n\n\n
Furthermore, next to the Styles tab on the right pane is a pane called ‘Computed.’ Here, a developer can view how much space an element is taking up such as its border, margin, padding, and content. <\/p>\n\n\n\n
Next to that is ‘Layout,’ which is used when flexbox or grid is placed on elements. A developer can select elements that have display: grid<\/mark><\/code><\/code><\/code> <\/code>or display: flex<\/mark><\/code> <\/code><\/code><\/code>on them, and they’ll be highlighted in a color. Track sizes can be seen as well as numbers for use with grid. <\/p>\n\n\n\n
A button to the left of ‘Elements’ is called “Toggle Device Toolbar.” When that is pressed, the width and height of the viewport and can be altered by dragging it. This is especially useful for media queries. <\/p>\n\n\n\n
The developer tools can also be docked against different sides of the screen by clicking the 3 dots on the bottom right next to the ‘x.’ Docking them against the left or right sides allows for a developer to see the downward flow of their webpage as they build or style it in the beginning stages(like when they’re building the mobile version). It’s also easier to see all of the code at once without having to scroll. However, because of this, the amount of pixels in width is limited if the developer tools are docks on the sides, so when building tablet or computer version of the site, it may be easier to see how they’ll look if the developer tools are docked to the bottom.<\/p>\n<\/div>\n\n\n\n
\n\n\n\n
\n
Flexbox<\/h2>\n\n\n\n
Flex box is a one-dimensional responsive layout. There are flex containers and flex items. The flex container is the element that display: flex is placed upon. Flex is inherited so everything inside the flex container become flex items. <\/p>\n\n\n\n
\n
Flex Container<\/h3>\n\n\n\n
These are the properties that can be placed on the flex container: <\/p>\n\n\n\n
justify-content<\/mark><\/code><\/code><\/code><\/code> – aligns flex items horizontally within the flex container like aligning text. They can be aligned on either side of the viewport, in the center, with equal amounts of space between them, or equal amounts of space both around and between them. <\/p>\n\n\n\n
align-items<\/mark><\/code><\/code><\/code><\/code> – aligns flex items vertically within the flex container. They can be aligned on either side of the viewport, in the center, with equal amounts of space between them, or equal amounts of space both around and between them. <\/p>\n\n\n\n
flex-direction<\/mark><\/code><\/code><\/code><\/code> – controls the direction in which the flex items go. By default, it is set to ‘row,’ so the items appear beside each other. This can be changed to column in which they’ll be arrange from top to bottom or in the reverse, where they’ll  be arranged from bottom to top  (column-reverse) or right to left (row-reverse). <\/p>\n\n\n\n
flex-wrap<\/mark><\/code><\/code><\/code> – controls if the flex items will spill onto a new line or squish themselves in a singular one. By default, this property is set to nowrap, meaning they’ll squish themselves, but it can be changed to wrap and wrap-reverse where they’ll wrap, but backwards. This allows for better readability, especially on smaller screens. <\/p>\n\n\n\n
flex-flow<\/mark><\/code><\/code><\/code> – short hand for flex-direction and flex-wrap<\/p>\n\n\n\n
gap<\/mark><\/code><\/code><\/code> – controls how much space is between the flex items<\/p>\n\n\n\n
Flex Items<\/h3>\n\n\n\n
These are the properties that can be placed on the items:<\/p>\n\n\n\n
order<\/mark><\/code><\/code><\/code> – sets the order in which elements appear even if they are written differently in the html<\/p>\n\n\n\n
flex-grow<\/mark><\/code><\/code><\/code> – determines how much a flex item will grow or stretch compared to the rest of the items. By default, it’s set to 0. If it’s set to 2, then that item will grow twice as fast as the others. <\/p>\n\n\n\n
align-self<\/mark><\/code><\/code><\/code> – overrides align-items<\/mark><\/code><\/code><\/code> that is placed on the flex container<\/p>\n\n\n\n
flex-shrink<\/mark><\/code><\/code><\/code> – determines how much a flex item will shrink compared to the rest of the items. By default, it’s set to 1, meaning it’ll shrink the same amount as the other items. If it’s set to 0, it won’t shrink at all. <\/p>\n\n\n\n
flex-basis<\/mark><\/code><\/code><\/code> – sets the initial length of a flex item<\/p>\n\n\n\n
flex<\/mark><\/code><\/code><\/code> – shorthand for flex-grow<\/mark><\/code><\/code><\/code>, flex-shrink<\/mark><\/code><\/code><\/code>, and flex-basis<\/mark><\/code><\/code><\/code><\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\n
\n
Media Queries<\/h2>\n\n\n\n
Media queries add responsiveness to a website. They set conditions on the webpage to change things like layout, or font size when they are met. <\/p>\n\n\n\n
Note: Media queries weren’t working until I added this meta tag in the head element:<\/em> <\/p>\n\n\n\n
<meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\"><\/code><\/pre>\n\n\n\n
\n
\n
@media<\/mark> screen<\/mark> and<\/mark> (min-width<\/mark>:850px<\/mark>) {\n   section<\/mark> {\n        display<\/mark>: flex<\/mark>;\n        justify-content<\/mark>: center<\/mark>;\n        gap<\/mark>: 3rem<\/mark>;\n    }\n}<\/code><\/pre>\n<\/div>\n\n\n\n
\n
For example, here is a media query, that states that when the viewport is 850px in width, everything inside will take effect. <\/p>\n<\/div>\n<\/div>\n\n\n\n
\n
\n
This is at 411px in width. The text appears under the image because by default, they are block elements. <\/p>\n<\/div>\n\n\n\n
\n
\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n<\/div>\n<\/div>\n\n\n\n
Below is at 1109px. It is over 850px so the conditions have taken effect. The display of the sections have been switched to flex so now they appear side by side. <\/p>\n\n\n\n
\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n<\/div>\n\n\n\n
\n","protected":false},"excerpt":{"rendered":"
These are my notes on what was covered in class on 8\/27\/24 as well as some extra research. This includes notes and examples for rem vs ems, block vs inline elements, semantic tags, viewport units, emmet, flexbox, etc<\/p>\n","protected":false},"author":1,"featured_media":54,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9,4],"tags":[46,45,42,44,51,41,47,43,49,50],"class_list":["post-53","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-class-work","category-notes","tag-block","tag-code","tag-css","tag-em","tag-emmet","tag-html","tag-inline","tag-rem","tag-semantic-tags","tag-viewport"],"_links":{"self":[{"href":"https:\/\/dulce.matmcc.org\/creative-journal\/wp-json\/wp\/v2\/posts\/53","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dulce.matmcc.org\/creative-journal\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dulce.matmcc.org\/creative-journal\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dulce.matmcc.org\/creative-journal\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/dulce.matmcc.org\/creative-journal\/wp-json\/wp\/v2\/comments?post=53"}],"version-history":[{"count":11,"href":"https:\/\/dulce.matmcc.org\/creative-journal\/wp-json\/wp\/v2\/posts\/53\/revisions"}],"predecessor-version":[{"id":488,"href":"https:\/\/dulce.matmcc.org\/creative-journal\/wp-json\/wp\/v2\/posts\/53\/revisions\/488"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dulce.matmcc.org\/creative-journal\/wp-json\/wp\/v2\/media\/54"}],"wp:attachment":[{"href":"https:\/\/dulce.matmcc.org\/creative-journal\/wp-json\/wp\/v2\/media?parent=53"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dulce.matmcc.org\/creative-journal\/wp-json\/wp\/v2\/categories?post=53"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dulce.matmcc.org\/creative-journal\/wp-json\/wp\/v2\/tags?post=53"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}