If you want to display a list or a list on a web page, there are 3 types of tags on the HTML, you can use any one as necessary.

Unordered List:

This is the most used professionally. <ul> </ ul> should be placed inside and <li> </ li> put one item inside the element. There will be no numbering in the list size. By default the default one goal is on the side of each item. Such as

<ul>
<li>Earth</li>
<li>Jupitar</li>
<li>Ventus</li>
<li>Marcs</li>
</ul>

Display:

  • Earth
  • Jupitar
  • Ventus
  • Marcs

If you wish, you can give other marks instead of rounds with CSS, and they will be discussed in CSS.

 

Ordered List:

Sometimes a list with a number may be needed by <li> <li> <li> inside the tag

<ol>
<li>iPad</li>
<li>iPhone</li>
<li>MacBook Air</li>
</ol>

Display

  1. iPad
  2. iPhone
  3. MacBook Air

How to start using the att element in the ol element start, it can be justified as if the top list is displayed from 10

<ol start="10">
<li>iPad</li>
<li>iPhone</li>
<li>MacBook Air</li>
</ol>

Display

  1. iPad
  2. iPhone
  3. MacBook Air

In li, the value of any item can be changed using an attribute named value such as

<ol>
<li value="5">iPad</li>
<li value="10">iPhone</li>
<li value="15">MacBook Air</li>
</ol>

Display

  1. iPad
  2. iPhone
  3. MacBook Air

It is not very useful to have another listing tag named Definition, it can be shown in a different way with this

<dl>
<dt>Preliminary analysis</dt>
<dd> in this step, you need to find out the organization's objectives and the nature and scope of the problem under study. Even if a problem refers only to a small segment of the organization itself then you need to find out what the objectives of the organization itself are. Then you need to see how the problem being studied fits in with them</dd>
<dt>Systems analysis, requirements definition</dt>
<dd>Defines project goals into defined functions and operation of the intended application. Analyzes end-user information needs</dd>
<dt>Systems design</dt>
<dd>Describes desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudocode and other documentation.</dd>
<dt>Development</dt>
<dd>The real code here</dd>
</dl>

Display

 

Preliminary analysis
in this step, you need to find out the organization’s objectives and the nature and scope of the problem under study. Even if a problem refers only to a small segment of the organization itself then you need to find out what the objectives of the organization itself are. Then you need to see how the problem being studied fits in with them
Systems analysis, requirements definition
Defines project goals into defined functions and operation of the intended application. Analyzes end-user information needs
Systems design
Describes desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudocode and other documentation.
Development
The real code here