refactor(blog-plugin): blog archive reverse ordering of posts

[slorber]

Motivation

Chronological ordering is confusing.

v3 is the best time to do this change.

I'm considering it as an UX improvement, not a breaking change.

Test Plan

preview

Test links

https://deploy-preview-9438--docusaurus-2.netlify.app/blog/archive

Related issues/PRs

johnnyreilly/blog.johnnyreilly.com#327

#5428

[slorber]

cc @johnnyreilly, was also wondering if the items inside a year should also be in reverse order?

[netlify]

✅ [V2]

Name	Link
🔨 Latest commit	126b8ed
🔍 Latest deploy log	https://app.netlify.com/sites/docusaurus-2/deploys/65367404833a8f0008a31df2
😎 Deploy Preview	https://deploy-preview-9438--docusaurus-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions]

⚡️ Lighthouse report for the deploy preview of this PR

URL	Performance	Accessibility	Best Practices	SEO	PWA	Report
/	🟠 63	🟢 97	🟢 92	🟢 100	🟠 89	Report
/docs/installation/	🟠 78	🟢 98	🟢 92	🟢 100	🟠 89	Report
/docs/category/getting-started/	🟠 83	🟢 100	🟢 92	🟢 90	🟠 89	Report
/blog/	🟠 80	🟢 100	🟢 92	🟢 90	🟠 89	Report
/blog/preparing-your-site-for-docusaurus-v3/	🟠 77	🟢 97	🟢 92	🟢 100	🟠 89	Report
/blog/tags/release/	🟠 80	🟢 100	🟢 92	🟠 80	🟠 89	Report
/blog/tags/	🟢 91	🟢 100	🟢 92	🟢 90	🟠 89	Report

[github-actions]

Size Change: 0 B

Total Size: 1.13 MB

ℹ️ View Unchanged

Filename	Size
website/.docusaurus/globalData.json	117 kB
website/build/assets/css/styles.********.css	113 kB
website/build/assets/js/main.********.js	862 kB
website/build/index.html	41.4 kB

_{compressed-size-action}

[johnnyreilly]

I actually moved away from the in-built docusaurus archive that was based on my blog post https://johnnyreilly.com/blog-archive-for-docusaurus because the ordering seemed strange to me. My handrolled approach looks like this:

It looks like the changes you're suggesting align with what I'm doing and so (unsurprisingly) I think this is a good idea!

Interestingly, I was advised it is better for SEO also. The idea being that you typically want newer blog posts to get more noticed. And the higher up the screen, the more significant a link is regarded.

---

Unrelated to the change you're making here, is there a way to control the URL of the archive functionality? I think it's hardcoded to [BLOG_ROOT]/archive at present. It would be nice if that URL was configurable so people can pick the URL they think is most appropriate.

[Josh-Cena]

@johnnyreilly: https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-content-blog#archiveBasePath

[slorber]

ok so let's merge this as is for now 👍