Your code snippet:
<ul id="company" style="display: block;">
<div class="about_logo_area">
<div class="pic_categry_info_img2 full_img">
<img src="images/new/flutura_about_logo.jpg">
</div>
</div>
<div class="about_logo_txt_area">
<p><strong>Flutura</strong> is a specialized organization focusing on Big Data analytics solutions, located in <strong>Palo Alto</strong> (with a development center in Bangalore). The company's mission is to enhance operational outcomes by leveraging machine data for financial gain. By extracting meaningful signals from various data sources, <strong>Flutura</strong> aims to make significant economic impacts. The name "Flutura" symbolizes transformation and growth, drawing inspiration from the metamorphosis of a caterpillar into a butterfly. Trust and Transformation are core values that guide our actions every day.
<strong>Flutura</strong> has been recognized as one of the top 20 promising Big Data startups globally by renowned technology publication CIO Review. Additionally, the company has been featured in Gigaom reports on Big Data and M2M in the energy sector. <strong>Flutura</strong> also emerged as the winner at TechSparks among 800 innovative startups.</p>
<p><strong>Flutura</strong> is backed by leading Silicon Valley venture capital firm The Hive, known for investing in Big Data companies worldwide.</p>
</div>
</ul>
The div
element cannot be a direct child of a ul
. Please ensure your HTML structure follows the correct guidelines set by W3C by validating your code using their online tool. You can refer to the article on W3C about the ul
element:
4.5.6 The ul element
Categories
Flow content.
Contexts in which this element can be used:
Where flow content is expected.
Content model:
Zero or more li elements.
Content attributes:
Global attributes
DOM interface:
interface HTMLUListElement : HTMLElement {};
According to the specifications, only the li
element should be nested inside a ul
.
For XHTML 1.0 Strict, you can have div
, p
, etc. within an li
. However, if you are using HTML5, please adhere to the recommended structure for better compatibility and validation.