Intro

Author's conclusion on 31 August 2025 from google knowledge graph and the scientific content released by web platforms including web.dev and multaqaweb states that technological progress contributed to building many digital writing and interpreting applications to operate HTML language usage. These applications are classified into somewhat distinct types but all are the same in HTML standardized writing principles.

HTML is the mark up language named "HyperText Markup Language", presenting the main coding language used to build the principal structural frame of the web pages interface, organizing texts, images, videos, buttons, lists, etc.. This process occurs through the browser (or application) ability to read, understand and interpret html code into the desired content visible on the web page interface.

According to Miss Noor Khattab overview conclusion in September 2025 about an educational video for HTML by the side of yanfaa web platform, with the help of the information background of platforms like MDN Web Docs and web.dev on the 4th of August 2025; To write HTML code we can use a Text Editor or an Integrated Development Environment IDE e.g. Visual Studio Code (VS code) and find that HTML is written in the style of Tag; the principal style whether using vs code or other html text editor, or any interpreting application.

Principal ( general ) style of html is written <Tag/> or <Tag> content </Tag>, and if we are going to give HTML input resource on some page, the page content should be written between those literal tags as follows : <html> content </html> which is called Paired Tags syntax, while the elements on the page with no content are written as follows : <element/> which is called Self-Closing Tags syntax and is used generally in modern HTML.

Slide 1 discussion

According to Miss Nour Khattab conclusion from her practice engagement using VS code in the previous example, our using experience for Paired tags went through arranging main tags in a vertical way, pressing "Enter" on the keyboard every time we want to go to the newline coding. All tags and elements should be captured between <html> and </html> where elements are coded according to thier features by being put between their specifying tags like the the following

<head> <title> element </title> </head> is an example code for the element appears on the web page browser tab or search engine result.

<body> element </body> is an example code for any content appears on the web page itself, including titles, paragraphs, and etc..

Slide 3 discussion

A conclusion writing of Ahmed Mohamed on the 31st of May 2026, relied on his review of the educational HTML video published by Yanfa3 platform. If we saved the file showcased in slide 2 that describes the content written with the codeline <h1> intro </h1>, we notice that the web interface shows a heading "intro" appears in the superior part of the page. When we write the same codeline below the first one with only number 1 being changed to 2; <h2> intro </h2>, and save the file, we find the previous heading "intro" in the same statement and another smaller "intro" word located below it, both 2 'intro' are showcased on the web page interface in a vertical sequence, and if we want to showcase a third smaller "intro" word below the second one on the web page interface, we write the codeline <h3> intro </h3> below the second one and save the file, using the same mechanism every time we want to go smaller and smaller. After previous light, the text sheet showcased in slide 3 results in 6 'intro' arranged vertically in descending order from the largest above to the smallest below; as 6 is the maximum number of headings in our experience with VS code text editor.

Another consideration intended to be discussed later from the experience of size identification talking about how and which side or digital environment is properly programmed and responsible for analyzing, identifying, and distinguishing between textual sizes of a word like "intro" through number differentiations in the codeline <hn> intro </hn>, with n letter referring to the number written after h letter to identify the word size. The relation of writing and interpreting between vs code and the browser is a programmed specified featuring that goes under some standards like distinguishing between sizes accroding to descending order of numbers, either it's the vs code application side which is given the input (code), or it's the browser side which gives the showcased output (words), or them both are engaged in the process of size identification analysis.

Thinking critically, the one can interpret a complete article using the feature of the variable codeline <hn> intro </hn>, replacing the variable n letter with number 1 or 2 for the fonts of primary and secondary titles, and with 3 or 4 for the fonts of paragraphs and note. This is critically a secondary option for writing paragraphs while the primary option is discussed in the following of our course.

If we want to hide any of our content from the output page ( audience/user interface ) without being actually deleted; still save our work ( the written code ) at the vs code controlling or coding space, we call this process "making a comment for the code" and is done by selecting the codeline then pressing Ctrl + / shortcut, or we can do this by writing < + ! + `` + the codeline we want to hide, which will appear on the vs code space as following < ! - - <hn> any word </hn> - - >

One of the practical benefits of that previous feature appears in the programming working team ability to agree between each other on which content is showcased for the browser webpage visitors and which content is hidden from the visitors without being actually deleted from the vs code space, which enables delaying, organizing, or improving the content showcased for a better user experience.

Note that "+" symbols in this paragraph are used for expressing the process of adding letters after letters like "!" written after "<" from left to right so you don't actually write "+" in the codeline.

Paragraph Code

In the previous discussion, we found a critical way to write down a paragraph with the code of titles, now we are moving to learn how to write down paragraphs with their standard coding way which enables us to edit the paragraphs format, and which's nature is distinguished by browsers and our text editor from the title's standard coding way..

Paragraph tag is written <p>content</p>, in which "content" refers to the written paragraph showcased on the browser interface, for example — if we want to write down "I want to learn programming because it will help me in my career and my future" as a showcased paragraph on our webpage interface, our code in the text editor must be as follows — <p>I want to learn programming because it will help me in my career and my future</p>

Flow Online

Intro

Example 1 : Paired Tags syntax

Slide 1 discussion

Slide 2 discussion

Slide 3 discussion

Paragraph Code

Edition

Reference

Apply to be one of the research contributors