Update archive.php

[jgclarke]

Revising the "primary" element to use a "div" vs. "section" to bring it into sync with index.php and single.php

[obenland]

The spec says:

The section element […] is a thematic grouping of content, typically with a heading.

This would not apply to index.php or single.php, it does apply to archive.php though.

Also see #104, #117, #150, #363, and possibly others.

[jgclarke]

Multiple points of feedback, in my opinion:

• The spec also states that "The section element is not a generic container element.", which it is being used for here.
• The spec also clearly shows examples wherein sections are intended to be used more often in groups, ie, it's less common to use 'section' in an isolated manner such as this. As supporting evidence, the spec states that "A general rule is that the section element is appropriate only if the element's contents would be listed explicitly in the document's outline."
• The importance of using the same elements (div vs. section) consistently across the same type of templates, when factored into the spec's point (noted above) about 'section' not being intended for generic containers suggests that 'div' should be used here instead.

More broadly, there seems to be a strict interpretation of the spec, when in fact the spec itself is often ambiguous. This ambiguity suggests we should interpret the spec within the context of the overall theme, with the theme's organization and consistency taking precedent when there are conflicts with unclear aspects of the spec.

[obenland]

The spec also states that "The section element is not a generic container element.", which it is being used for here.

If we had section titles in index or single, those divs would be sections too.

The spec also clearly shows examples wherein sections are intended to be used more often in groups, ie, it's less common to use 'section' in an isolated manner such as this. As supporting evidence, the spec states that "A general rule is that the section element is appropriate only if the element's contents would be listed explicitly in the document's outline."

I believe the section's contents would be listed in the document's outline.

The importance of using the same elements (div vs. section) consistently across the same type of templates, when factored into the spec's point (noted above) about 'section' not being intended for generic containers suggests that 'div' should be used here instead.

I think it is more important to use the right element for a given situation. Not necessarily the same ones. I still believe a section element in the context of archive pages is more fitting than a div, because in that context, it is not used as generic wrapper. It would be in index and single, which is why we don't use sections there.

[binaryliving]

After looking closely at the specs, and the code, it is being used as a generic container, although not as generic as a bootstrap container. The specs also prescribe "identification of themes..." such as h1, h2, etc.. as a child of the section. The loop inside the section (or multiple loops) as is would generate 1 to N various sized header elements (in theory). Rendering the intention of the section element useless.