Afrikaans
Akan
Albanian
Amharic
Arabic
Armenian
Azerbaijani
Basque
Belarusian
Bemba
Bengali
Bihari
Bosnian
Breton
Bulgarian
Cambodian
Catalan
Cebuano
Cherokee
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Ewe
Faroese
Filipino
Finnish
French
Frisian
Ga
Galician
Georgian
German
Greek
Guarani
Gujarati
Haitian Creole
Hausa
Hawaiian
Hebrew
Hindi
Hmong
Hungarian
Icelandic
Igbo
Indonesian
Interlingua
Irish
Italian
Japanese
Javanese
Kannada
Kazakh
Kinyarwanda
Kirundi
Kongo
Korean
Krio (Sierra Leone)
Kurdish
Kurdish (Soranรฎ)
Kyrgyz
Laothian
Latin
Latvian
Lingala
Lithuanian
Lozi
Luganda
Luo
Luxembourgish
Macedonian
Malagasy
Malay
Malayalam
Maltese
Maori
Marathi
Mauritian Creole
Moldavian
Mongolian
Myanmar (Burmese)
Montenegrin
Nepali
Nigerian Pidgin
Northern Sotho
Norwegian
Norwegian (Nynorsk)
Occitan
Oriya
Oromo
Pashto
Persian
Polish
Portuguese (Brazil)
Portuguese (Portugal)
Punjabi
Quechua
Romanian
Romansh
Runyakitara
Russian
Samoan
Scots Gaelic
Serbian
Serbo-Croatian
Sesotho
Setswana
Seychellois Creole
Shona
Sindhi
Sinhalese
Slovak
Slovenian
Somali
Spanish
Spanish (Latin American)
Sundanese
Swahili
Swedish
Tajik
Tamil
Tatar
Telugu
Thai
Tigrinya
Tonga
Tshiluba
Tumbuka
Turkish
Turkmen
Twi
Uighur
Ukrainian
Urdu
Uzbek
Welsh
Wolof
Xhosa
Yiddish
Yoruba
Zulu
1
And welcome back.
2
In the previous video we went over the basic rules that all HTML files must follow.
3
And I kind of glossed over this '!DOCTYPE html' tag, and I did that on purpose because I want
4
you to develop a another developer fundamental concept.
5
And that is the fact that most of the time, as developers there's so much information out there that
6
there's no way that you can keep all of that in your head.
7
And as developers we must get really really good at problem solving.
8
So for the doctype let's say if I was working and somebody gives me this file and I say OK I've got
9
this that's good but I'm not sure what 'doctype' is.
10
Well again we wanna get really good at Googling here, and I know it sounds silly, but trust me, as a developer
11
you're going to be Googling a lot and going to get really really good at looking for answers and understanding
12
meanings behind code.
13
So, if I go into 'doctype html' and we Google that, one of the first things that we get is the W3 School
14
and this is a resource that I highly, highly recommend. They'll actually explain what the doctype is, and
15
even show you a demo of what it does.
16
You can read into this and get more familiar with it, but the general rule and the concept behind 'doctype'
17
is that 'doctype' says to the browser, 'Hey just a heads up this file is going to use HTML5.'
18
And we'll get into what HTML5, is but right now, HTML has evolved from back in the day when Tim
19
Berners-Lee invented it, to where it is now. And it has developed and evolved so that it has a few more
20
tags,
21
it has a few more features, and this is the way for us to say, 'Hey, browser we're going to be using HTML5.
22
So please make sure that you load the website properly.' And we'll get into what those new tags are and
23
some of the new syntaxes.
24
But again most likely in your day to day job you're going to be writing this at the top because we're
25
writing in HTML5, if that ever changes and something new comes along,
26
we might change this, but 'doctype' that's what it is.
27
But the key concept here is that I really want you to start Googling, at any time you see in my videos,
28
something that you don't fully understand or you want to dig a little bit deeper.
29
You really want to grow those roots of your foundation so that you really understand how the landscape
30
works.
31
OK.
32
So I just wanted to get that concept across that as a developer, you really want to understand
33
how things work and what they mean, and you'll come across in your day to day
34
many things that it's very easy to just, on the surface copy and paste,
35
or just look at an example and do it without fully understanding what it does.
36
But the developers that get really really good salaries, really good jobs, and are considered 'senior developers'
37
are the ones that fully understand all the meaning behind the things that they do.
38
We're going to be taking that throughout the course and making sure that we develop those fundamentals.
39
But any time, like I said, you have any questions or you don't understand something fully,
40
I do encourage you to Google and get the answers because there's a ton of free resources out there for
41
you to get fully, fully comfortable with the topic.
42
I'll see you in the next one.
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.