microsoft/frontend-bootcamp
1
0
Fork 0
mirror of https://github.com/microsoft/frontend-bootcamp.git synced 2026-01-26 14:56:42 +08:00
Code Issues Packages Projects Releases Wiki Activity

Day 1 updates

Browse Source
This commit is contained in:
Elizabeth Craig
2019-02-27 17:46:56 -08:00
parent 5e5717240c
commit 5aed397e01
14 changed files with 144 additions and 142 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
step1-02/demo/README.md
View File

@@ -8,7 +8,7 @@ Every website, application, form or component starts with markup. The HTML will
## Demo
In this exercise we will scaffold out some HTML for our Todo app, then add some basic styling to it.
In this exercise we will scaffold out some HTML for our todo app, then add some basic styling to it.
### Page scaffold
@@ -20,14 +20,14 @@ In this exercise we will scaffold out some HTML for our Todo app, then add some
</html>
```
1. The DOCTYPE tells the browser that this file is written in modern HTML.
2. The HTML tag wraps the entire page, and is the page root. Nothing is placed outside of those tags. Attributes can be set on HTML.
3. Head will contain all of the page's meta data, in this case a link to our CSS file.
4. Body is where all of the visible content should be placed.
1. The [`DOCTYPE`](https://developer.mozilla.org/en-US/docs/Glossary/Doctype) tells the browser that this file is written in modern HTML.
2. The `html` tag wraps the entire page and is the page root. Nothing is placed outside of this tag.
3. `head` will contain all of the page's metadata, in this case a link to our CSS file.
4. `body` is where all of the visible content should be placed.
### Content Sectioning
As we saw in the previous demo, HTML elements can be used to describe different content sections of the applications. Let's add `header`, `main` and `footer`, as well as populate the header with an `h1`, addTodo div, and `nav` for our filters.
As we saw in the previous demo, HTML elements can be used to describe different content sections of the applications. Let's add `header`, `main` and `footer`, as well as populate the header with an `h1`, addTodo `div`, and `nav` for our filters.
```html
<body>
@@ -41,11 +41,11 @@ As we saw in the previous demo, HTML elements can be used to describe different
</body>
```
> Note that a `form` element would have been more semantic than a `div`, but we aren't using this form to POST to a server, so for this example a div is easier to use.
> Note that a `form` element would have been more semantically correct than a `div`, but we aren't using this form to POST to a server, so for this example a div is easier to use.
### Updating the header
The header of our page is where most of the action is going to happen. First, lets give our app a name, adding 'TODO' to our `h1`. Then we can add an input and button to our `addTodo` div.
The header of our page is where most of the action will happen. First, let's give our app a name, adding "TODO" to our `h1`. Then we can add an input and button to our `addTodo` div.
```html
<input class="textfield" placeholder="add todo" /> <button class="submit">Add</button>
@@ -53,7 +53,7 @@ The header of our page is where most of the action is going to happen. First, le
#### Navigation
The navigation for this application is quite simple. We want users to be able to switch between three filtered states. Since we need to track which state is currently selected, we'll add that as a class on the first item.
The navigation for this application is quite simple. We want users to be able to switch between three filtered states. Since we need to track which state is currently selected, we'll add a `selected` class to the first item.
```html
<nav class="filter">
@@ -65,7 +65,7 @@ The navigation for this application is quite simple. We want users to be able to
### Adding styles
Now that we've got the top of our application scaffolded, we can add some styles in the head.
Now that we've got the top of our application scaffolded, we can add some styles in the `head`.
```html
<head>
@@ -77,7 +77,7 @@ Now that we've got the top of our application scaffolded, we can add some styles
It looks like the selected button isn't getting any special styles. Let's dig in and see why that is.
Open up the browser inspector and target our 'all' button. You'll notice that the blue style is present on the list, but it is being overridden by the `border: none` above it. This is a situation where specificity is winning out over the cascade.
Open up the browser inspector and target our "all" button. You'll notice that the blue style is present on the list, but it is being overridden by the `border: none` above it. This is a situation where specificity is winning out over the cascade.
> **Cascade** states that if two selectors are equal, the lowest one on the page wins