[Bug] story vs authored-post vs raw article component labelling and structural mismatches

[possumbilities]

Description

In a plurality the nature of "stories" or "authored-posts" is non consistent, appearing in various areas in various ways that are not well structured or defined. For example the use of a div vs section vs article.

body.home-index > main > article.authored-posts
body.blog-index > main > article.authored-posts, directly after the main > header
body.blog-index > main > article.authored-posts, directly after the first main > article.authored-posts
body.archive-page > main > div.authored-posts, directly after the main > aside
body.person-page > main > section.authored-posts, directly after the main > header
body.blog-post > main > article.related-posts > article.authored-posts, as the last child of body > main/span>

Expectation

The singular is often referred to as story, but the plural is authored-post this needs resolution. It should be either authored-post and authored-posts OR story and stories OR both handled as differing components (thought that is less likely and less ideal based on current usecases)

In a singular sense they are targeted and marked up as .story, and a classless article element. This needs to be corrected with the appropriately chosen class where possible.

In the plural the parenting wrapper should be using consistently the same element, OR have documented rules for why a change is needed in certain contexts.

Resolution

• I would be interested in resolving this bug.