Levels of HTML, CSS, and Javascript: Part 1. HTML
Your attention is invited to a fairly large excerpt from the article "Levels of HTML knowledge," written by Roger Johansen on May 30, 2006.
Note translator : Initially, I published this post in the form of humorous excerpts from three articles written by three different authors and titled in a similar way: “HTML Levels”, “CSS Levels” and “Javascript Levels”. Which, of course, was a rather stupid idea. Awareness of the mistake made came in 5 minutes and two minuses to fasting and karma. Correct. Translation of "Levels of CSS" wait for tomorrow.
')
People at this level have never encountered HTML, except by mistake, for example, when they accidentally opened an HTML version of an email in text mode. These people do not work in the web industry, and never will, therefore they have neither the reason nor the desire to rise above the zero level.
Typical saying:
These people have been using the Internet for a long time and guess what is happening behind the scenes of the website they are currently viewing. If you try to publish anything on the network, they are helpless without any WYSIWYG editor. This could be Photoshop, Dreamweaver, Frontpage, or an editor embedded in the CMS, which they were told to use.
People who maintain the content of a website are often at this level of skill, and some even claim that there is no need to strive to go up a step. Many visual-oriented designers are firmly stuck on this level of their own accord, often defending their choice with the following: “No one in the print world edits PostScript code manually, so why should the network be different?” Unfortunately, many project managers also rarely climb above the first level.
At this level there are people who know enough about HTML to change, add or remove from the document a couple of tags (at this level, everything is called tags) that they know. But they never have a particularly strong desire to dig into HTML.
Second-level developers also consist of programmers who prefer the security of Visual Studio or any other IDE they use. They think that HTML is too easy for them, and that their development environment is advanced enough to sort things out by itself. Many second-level programmers are the target audience of CMS developers.
Many old school web developers who have been working in the industry since the late 90s can be found at this level. Up until the end of the last century, these people wrote HTML manually, so they know all about nested tables and single-pixel GIFs. Since then, WYSIWYG editors (such as GoLive and Dreamweaver) have improved to such an extent that third-level developers see no reason to know more about HTML. Now, most of their work related to HTML is done in the design mode of their editor, so they would prefer to spend their time studying a particular application, rather than delving into what is happening behind its scenes.
At this level, people are beginning to consciously use doctype-s. At the first stage, this is almost always a transitional doctype, more often XHTML 1.0 Transitional. All the same, XHTML is a later specification than HTML, so it's probably better, right? People at this level are also big fans of XHTML 1.1, naively believing that the older version implies some improvements.
After hearing from someone that tables cannot be used for markup, many fourth-level programmers use divs to recreate table-like structure types. So, the former tag-chefs become divomans who, day and night, produce tons of presentational markup with simple class names (red, blue, bigRedText, etc.) and inline CSS (style attribute).
Most web developers who have reached the fourth level are ready to continue their education. They understand that the methods that are promoted by the authors of blogs and books about web standards have an advantage. But they still did not understand why these methods are better.
Most developers working in accordance with the canons of web standards can be found here. These people, as a rule, first think about structure and semantics, and only then about representation. At this level, strict doctypes are commonly used to encourage separation of semantic and presentational markup. Whether it will be HTML version 4.01 or XHTML version 1.0 is not so important for many, although some fifth-level developers question the use of XHTML. At the fifth level, people tend to breed endless discussions about the nuances of markup. They can kill a few hours to come up with a name for the class or reorganize HTML and CSS files.
If you reach this level, I think you already have some reason to be proud. For most people, there is no compelling reason to climb higher.
These people are the wise men of our industry. They spend a lot of time on things that will only be useful in the future, not right now. The average developer will not be able to use the results of a significant part of their work for at least another five years.
At the sixth level, you want more than just to earn a living by creating websites. Instead, you can devote much effort to writing future specifications or interpreting browsers that already exist for developers.
Read the sequel about CSS in the next section .
Note translator : Initially, I published this post in the form of humorous excerpts from three articles written by three different authors and titled in a similar way: “HTML Levels”, “CSS Levels” and “Javascript Levels”. Which, of course, was a rather stupid idea. Awareness of the mistake made came in 5 minutes and two minuses to fasting and karma. Correct. Translation of "Levels of CSS" wait for tomorrow.
')
Level 0
Hee-te-me-chago?
People at this level have never encountered HTML, except by mistake, for example, when they accidentally opened an HTML version of an email in text mode. These people do not work in the web industry, and never will, therefore they have neither the reason nor the desire to rise above the zero level.
Typical saying:
Level 1
Html? These are such things to make the text zhirny or italic?
These people have been using the Internet for a long time and guess what is happening behind the scenes of the website they are currently viewing. If you try to publish anything on the network, they are helpless without any WYSIWYG editor. This could be Photoshop, Dreamweaver, Frontpage, or an editor embedded in the CMS, which they were told to use.
People who maintain the content of a website are often at this level of skill, and some even claim that there is no need to strive to go up a step. Many visual-oriented designers are firmly stuck on this level of their own accord, often defending their choice with the following: “No one in the print world edits PostScript code manually, so why should the network be different?” Unfortunately, many project managers also rarely climb above the first level.
Level 2
The pages I make in Macromedia Dreamweaver work fine in Internet Explorer. Why should I even look at this HTML?
At this level there are people who know enough about HTML to change, add or remove from the document a couple of tags (at this level, everything is called tags) that they know. But they never have a particularly strong desire to dig into HTML.
Second-level developers also consist of programmers who prefer the security of Visual Studio or any other IDE they use. They think that HTML is too easy for them, and that their development environment is advanced enough to sort things out by itself. Many second-level programmers are the target audience of CMS developers.
Level 3
Yes Yes. I heard about these new tags: ul, li and all that. But I get along well with my favorite table, img, br.
Many old school web developers who have been working in the industry since the late 90s can be found at this level. Up until the end of the last century, these people wrote HTML manually, so they know all about nested tables and single-pixel GIFs. Since then, WYSIWYG editors (such as GoLive and Dreamweaver) have improved to such an extent that third-level developers see no reason to know more about HTML. Now, most of their work related to HTML is done in the design mode of their editor, so they would prefer to spend their time studying a particular application, rather than delving into what is happening behind its scenes.
Level 4
Listen, how can you make a table with data only div'ami and span'ami, not using the table ?!
At this level, people are beginning to consciously use doctype-s. At the first stage, this is almost always a transitional doctype, more often XHTML 1.0 Transitional. All the same, XHTML is a later specification than HTML, so it's probably better, right? People at this level are also big fans of XHTML 1.1, naively believing that the older version implies some improvements.
After hearing from someone that tables cannot be used for markup, many fourth-level programmers use divs to recreate table-like structure types. So, the former tag-chefs become divomans who, day and night, produce tons of presentational markup with simple class names (red, blue, bigRedText, etc.) and inline CSS (style attribute).
Most web developers who have reached the fourth level are ready to continue their education. They understand that the methods that are promoted by the authors of blogs and books about web standards have an advantage. But they still did not understand why these methods are better.
Level 5
I wonder what type of list will be used semantically more correctly in this passage of the document?
Most developers working in accordance with the canons of web standards can be found here. These people, as a rule, first think about structure and semantics, and only then about representation. At this level, strict doctypes are commonly used to encourage separation of semantic and presentational markup. Whether it will be HTML version 4.01 or XHTML version 1.0 is not so important for many, although some fifth-level developers question the use of XHTML. At the fifth level, people tend to breed endless discussions about the nuances of markup. They can kill a few hours to come up with a name for the class or reorganize HTML and CSS files.
If you reach this level, I think you already have some reason to be proud. For most people, there is no compelling reason to climb higher.
Level 6
I consider the HTML 4.01 and XHTML 2.0 specifications to be semantically limited. Therefore, I am currently working on my own markup language.
These people are the wise men of our industry. They spend a lot of time on things that will only be useful in the future, not right now. The average developer will not be able to use the results of a significant part of their work for at least another five years.
At the sixth level, you want more than just to earn a living by creating websites. Instead, you can devote much effort to writing future specifications or interpreting browsers that already exist for developers.
Read the sequel about CSS in the next section .
Source: https://habr.com/ru/post/31475/
All Articles