refactor: use an <article> element for for package readme

[knowler]

As discussed in #503 (comment) and #503 (comment), @rshigg and I noticed that a package’s readme would be better wrapped with an <article> element as it’s a standalone document. It’s alright that it’s a descendant of another <article> element (which wraps the page’s main contents).

Worth noting that an <article> element and its corresponding article ARIA role is not a navigational landmark, so this change will only impact users when they are traversing through the page.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
npmx.dev	Ready	Preview, Comment	Jan 31, 2026 5:56pm

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
npmx-lunaria	Ignored		Jan 31, 2026 5:56pm
docs.npmx.dev	Skipped		Jan 31, 2026 5:56pm

[rshigg]

Any reason to withhold removing the aside and ancestor article? I think this is a good opportunity to get that all sorted at once

[knowler]

I’m having second thoughts. I’m thinking this <div> that contains the README contents should be the <article> element, since our “README” heading isn’t a part of that document.

[knowler]

If we do that, then I’ll probably remove the top-level <article> for sure since they’ll probably have the same name which might be confusing.

[knowler]

b671b9a I made the change here. I’m still considering removing the top-level <article> and <aside> elements. Taking sometime to think on it.

[knowler]

@rshigg So, I think I’m done here and these are the changes:

• Instead of replacing the <section> with the README heading with an <article> element, I’ve used it to wrap the readme contents itself, which were wrapped in a <div>. This is because our heading is not a part of that document.
• I considered removing main > article element because it’d likely have a similar name to the README one, but I’ve left it because it really doesn’t have a whole lot of impact. The article ARIA role is really only exposed in macOS VoiceOver which has very low usage in comparison to other screen readers. So, you could say this whole PR was negligible, but we are using more semantic HTML now, so that’s at least a plus.
• I did remove the <aside> element used for the (presentational) sidebar.