This is the very first exercise in the course. It is expected that it will provide a brief overview of what will be covered in the course, not teach you the entire course in one exercise. It takes time to learn anything, HTML included. Navigate through the course as it was intended to be followed and you’ll have a decent understanding and ability to write HTML by the end of it.
Where do you see this? This isn’t on the exercise.
You’ll learn these in later lessons. You need to understand what HTML does, its syntax, and more basic components of the language before you delve into more complicated topics.
It’s not unhelpful at all. You need to first understand why you’re using HTML, its capabilities, and its applications. Without knowing an object’s purpose, it’d be like learning to use a computer without knowing what a computer is used for.
Progress through the course exercise by exercise, module by module (press the “Next” button). Without an understanding of the basics, how can you understand complexities?
We are given that there are three static document types being imported into a single namespace. That’s the memory where all the magic happens. The HTML formulates the DOM, the CSS populates it with style properties, and the JS lays in wait to spring forth with user triggered behaviors, apart from those that went into the page load.
If we find that last statement confusing, then we need to step back. If needs be, right to the very beginning and start over with a fresh view.
The browser. That’s what we’re composing for. Every device is equipped with one. What’s more the technology has evolved to omit the browser and merely use its scripting engine in apps, along with its HTML and CSS APIs for the UX.