create/skeletons: Wrap section and home lists with section tags

[imomaliev]

Read more #14044

[CLAassistant]

All committers have signed the CLA.

[jmooring]

Neither article nor section are semantically correct in this context. See:

• https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/article
• https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/section

Use a div element instead.

[imomaliev]

@jmooring Hi, thanks for the reply!

Neither article nor section are semantically correct in this context.
Use a div element instead.

I might be misunderstanding something, so can you please help me understand this better? Why are article and section not correct in this context?

MDN docs for article state

A given document can have multiple articles in it; for example, on a blog that shows the text of each article one after another as the reader scrolls, each post would be contained in an <article> element, possibly with one or more <section>s within.

and for section

If the contents of the element represent a standalone, atomic unit of content that makes sense syndicated as a standalone piece (e.g., a blog post or blog comment, or a newspaper article), the <article> element would be a better choice.

The home.html and section.html are clearly used for listing articles with "summary" of their text. In my understanding this exactly the case outlined in docs and should be a better fit than div.

[jmooring]

Using an article element is incorrect because a summary is not a self-contained composition.

Go ahead and use section as long as you wrap both the heading and the summary.

[imomaliev]

Using an article element is incorrect because a summary is not a self-contained composition.
Go ahead and use section as long as you wrap both the heading and the summary.

But I am not wrapping .Summary by itself, I am wrapping it together with h2 for .Page.Title. I think the title was incorrect and this is why there is some missunderstaning.

I've updated title to Use article tag to wrap pages in collection rendering when using .Summary to avoid issues with tag leakage. Can you please review the code and tell me if I should it change it to section or div?

[jmooring]

Go ahead and use section as long as you wrap both the heading and the summary.

Or to put it another way, don't use an article element.

[imomaliev]

Replaced article with section in code and updated the title

[jmooring]

Final step... please review the commit message guidelines. It should be something like:

create/skeletons: Wrap section and home lists with section tags

[imomaliev]

@jmooring I'm so sorry, missed that part when reading CONTRIBUTING.md yesterday. Thanks for your patience)

[jmooring]

No problem, looks good, thank you for your contribution.

[imomaliev]

Wanted to leave this research for the context, not for continuing the discussion

---

After re-reading the spec and multiple articles 1, 2,3

The article element represents a complete, or self-contained, composition in a document, page, application, or site and that is, in principle, independently distributable or reusable, e.g. in syndication. This could be a forum post, a magazine or newspaper article, a blog entry, a user-submitted comment, an interactive widget or gadget, or any other independent item of content.

When used specifically with content to be redistributed in syndication, the article element is similar in purpose to the entry element in Atom. [ATOM]

A section forms part of something else. An article is its own thing. But how does one know which is which? Mostly the real answer is "it depends on author intent".

I still think article tag usage here could be considered semantically correct (when wrapping together with heading). If we are talking in the context of syndication, title + summary in collections pages like home.html and section.html may be considered self-contained composition or "independent item of content." Because one could argue that it is possible to distribute only article's intro (title + summary) as separate content. As well as in the context of using screen readers, this may be preferable to section because we are listing "repeating content units".

[jmooring]

I have approved this PR as-is. I think we're done here.

[imomaliev]

I have approved this PR as-is. I think we're done here

Yes, of course. As I've stated in the previous comment, I only intended to add some information after additional research, not to continue with the discussion. You are the "author" in the context of my previous comment, so your intent is what matters))