A conflict about section

[AuroraTea]

main content: <main>, with various content subsections represented by <article>, <section>, and <div> elements.

In the MDN Document_and_website_structure

<section> is similar to <article>, but it is more for grouping together a single part of the page that constitutes one single piece of functionality (e.g., a mini map, or a set of article headlines and summaries), or a theme. It's considered best practice to begin each section with a heading; also note that you can break <article>s up into different <section>s, or <section>s up into different <article>s, depending on the context.

In the MDN Document_and_website_structure

Sectioning content, a subset of flow content, creates a section in the current outline defining the scope of <header> elements, <footer> elements, and heading content.

Elements belonging to this category are <article>, <aside>, <nav>, and <section>.

In the MDN Content_categories.

If you are only using the element as a styling wrapper, use a div instead.

In the MDN section.

However, there are many places that do not follow this specification, such as Element Plus container. No criticism of the component library is intended here, it's just that this is how it's used in MDN grid-template as well.

<section id="page">
  <header>Header</header>
  <nav>Navigation</nav>
  <main>Main area</main>
  <footer>Footer</footer>
</section>

Apparently, there is a contradiction in terms in MDN. It should be standardized in the same document, though it's not necessary to make this distinction in modern front-end work.