So code literacy. This is again, we're not learning how to write code, but we are learning how to read code. So all browsers come with a function called Inspect Element, which we'll dig into in another segment, which allow me to click on any object in the interface and see the associated markup underneath it. Just a general overview, just to get everybody on the same page, you're gonna be looking at HTML and you're gonna be looking at CSS. And they have some specific rules. Again, you don't have to be a maestro in it but you need to understand the mechanics of how it's put together. HTML tags, the good news is HTML was written for anybody to use. Like if you look at programming languages, capital p programming languages, it hurts, it hurts my head. I don't understand. But HTML, it's like a series of nested dolls. It's just here's a container that contains this container, that contains that container. Every container has a start and stop. And what I love about the designers of HTML is I...
understand that metaphor. My head is at the top of my body and my feet are down below. Oh dude, thanks for keeping it like (clicking) crystal, crystal clear for me. Can't mix that up. Although some people will put the header down. But the idea is that at the element level, it's written in such a way, and more and more with HTML five, you have more and more of these elements that are written in such a way that are more semantic, describing how they relate to each other. So again, just to be clear. Starter tag, closing tag, content in between. That's about as much as you need to know about HTML to start, alright? We're gonna add classes to these things. CSS classes work like this: I'm gonna have a name, this is gonna be maybe a component name. This is some of that name space, this would be slacked, right? It's gonna have a property, we'll say that's color. It's gonna have a value. You're, as a designer in the beginning, all you do is you live in value land. This is as you're learning. The developers, you're gonna work with a developer to sort of get the nomenclature around the classes together. But all your editing are gonna be these sort of value blocks and this is what that looks like. Again, CSS Guidelines is a great resource as far as learning CSS statements, how it's put together. And he gives this breakdown. So this is my class name, baz. Here are the properties associated with that class name, so anywhere I put baz on an HTML element, it'll be displayed as a block, background color green, and color red. Again, I was telling Andy I love how they use green and red here. Which are statements you can use in a browser. You're gonna have to get used to seeing hex colors, which I'm sure most of you are familiar with on some level. And again, CSS Guidelines, we'll walk you through a lot of that. The reason we're doing all this stuff is so that we can be just a little bit more informed when we have a conversation and we create a ticket in one of these project management tools. I can no longer tell a developer, I need to change the sidebar from purple to blue, please. (laughing) I need, I feel you need to update the background color of .aside-secondary, which is the class name of that object, to .primary-blue, which is the class name for that color. So and if you can, also give them associated hex colors so you know you're talking about the same thing. Again, we'll take a look at how we get all these values from the browser. So again, things to remember, the days of design and dash are over. We're in a long term relationship, we're goin' steady, with our developers. We can utilize collaborate documents like chat, hack session, white-boarding to stay connected. We're gonna establish a common language of parts that will make for iterative parallel efforts. And then as designers, it's our responsibility to read some code.