refactor(website): organise blog posts by year with new flattenFolder…

…s option

website/blog/2022-01-24-docusaurus-2021-recap/index.mdx → website/blog/2022/2022-01-24-docusaurus-2021-recap/index.mdx

@@ -7,7 +7,7 @@ image: ./img/thumbnail.png
 
 Docusaurus has made great progress in 2021! We've seen a lot of traction and just crossed **30k stars on GitHub**!
 
-We've **reached full feature parity** with v1 after [the release of internationalization](../2021-03-09-releasing-docusaurus-i18n.mdx), [announced our **first beta**](../2021-05-12-announcing-docusaurus-two-beta/index.mdx), and welcomed **significantly more users** this year.
+We've **reached full feature parity** with v1 after [the release of internationalization](/blog/2021/2021-03-09-releasing-docusaurus-i18n.mdx), [announced our **first beta**](/blog/2021/2021-05-12-announcing-docusaurus-two-beta/index.mdx), and welcomed **significantly more users** this year.
 
 The **official v2 release** is just around the corner! Follow the [roadmap issue](https://github.com/facebook/docusaurus/issues/6113) for any latest news.
 
@@ -17,7 +17,7 @@ The **official v2 release** is just around the corner! Follow the [roadmap issue
 
 ## Highlights
 
-Let's begin by going over a few highlights this year. Remember the [todo-list](../2021-05-12-announcing-docusaurus-two-beta/index.mdx#whats-next) from half a year ago? Time to take it out again and see how far we've come!
+Let's begin by going over a few highlights this year. Remember the [todo-list](/blog/2021/2021-05-12-announcing-docusaurus-two-beta/index.mdx#whats-next) from half a year ago? Time to take it out again and see how far we've come!
 
 - **Internationalization**: officially released four months after its initial landing in late 2020. Seen great success in [many projects](/showcase?tags=i18n)
 - **Autogenerated sidebars**: no need to maintain a big `sidebars.js` anymore
@@ -118,7 +118,7 @@ We'd like to express our gratitude to [all the contributors in 2021](https://git
 
 - The core team: [Alexey Pyltsyn](https://github.com/lex111), [Sébastien Lorber](https://github.com/slorber), [Joshua Chen](https://github.com/Josh-Cena), and [Yangshun Tay](https://github.com/yangshun) for moderating the community, publicizing Docusaurus, triaging issues, and implementing new features
 - [Joel Marcey](https://github.com/JoelMarcey) for creating Docusaurus and supporting its development all along
-- The Algolia team for helping Docusaurus users [migrate to the new DocSearch](../2021-11-21-algolia-docsearch-migration/index.mdx) and answering search-related questions
+- The Algolia team for helping Docusaurus users [migrate to the new DocSearch](/blog/2021/2021-11-21-algolia-docsearch-migration/index.mdx) and answering search-related questions
 - All the active community members for making valuable code contributions, improving our documentation, and answering questions on Discord
 
 So long, 2021, and let's greet a great 2022!

website/blog/2022-08-01-announcing-docusaurus-2.0/index.mdx → website/blog/2022/2022-08-01-announcing-docusaurus-2.0/index.mdx

@@ -95,7 +95,7 @@ Docusaurus was created at **Facebook Open Source** in **2017** (now [Meta Open S
 
 At that time, our solution was to **copy/paste a Jekyll template** over and over again. This naturally became **hard to maintain**, so we created a tool to **solve our own pain** once for all.
 
-**[Docusaurus v1 was born](../2017-12-14-introducing-docusaurus.mdx)!**
+**[Docusaurus v1 was born](/blog/2017-12-14-introducing-docusaurus.mdx)!**
 
 ![Birth of Slash](/img/slash-birth.png)
 
@@ -129,7 +129,7 @@ Notice that the sample sites above use different colors, but still look quite th
 - We kept **everything good from v1**: docs, blog, pages, versioning, i18n...
 - We implemented **several new features**
 
-More details in the [Docusaurus 2 project announcement](../2018-09-11-Towards-Docusaurus-2.mdx) and [v1 to v2 migration guide](https://docusaurus.io/docs/migration)
+More details in the [Docusaurus 2 project announcement](/blog/2018/2018-09-11-Towards-Docusaurus-2.mdx) and [v1 to v2 migration guide](https://docusaurus.io/docs/migration)
 
 ## Who uses Docusaurus 2.0?
 
@@ -420,7 +420,7 @@ We'd like to express our gratitude to [all our contributors](https://github.com/
 - [Joel Marcey](https://github.com/JoelMarcey) for creating Docusaurus 1.0 and supporting the Docusaurus 2.0 project at Meta Open Source
 - [Paul O’Shannessy](https://github.com/zpao) for supporting the development of all the next versions of Docusaurus at Meta Open Source
 - [Eric Nakagawa](https://github.com/ericnakagawa) for creating our cutest mascot Slash
-- [Endilie Yacop Sucipto](https://github.com/endiliey) for his significant [initial work on Docusaurus v2](../2020-01-07-tribute-to-endi.mdx)
+- [Endilie Yacop Sucipto](https://github.com/endiliey) for his significant [initial work on Docusaurus v2](/blog/2020/2020-01-07-tribute-to-endi.mdx)
 - [Clément Vannicatte](https://github.com/shortcuts), [Kevin Granger](https://github.com/Shipow) and the whole Algolia team for their support
 - All the community members for making valuable code contributions, improving our documentation, and answering questions on [Discord](https://discordapp.com/invite/docusaurus)
 

website/docs/migration/v3.mdx

@@ -149,7 +149,7 @@ To obtain a compilation behavior similar to what Docusaurus v2 uses, please turn
 - Use `remark-gfm`
 - Use `remark-directive`
 
-![Screenshot of the MDX playground's options panel, with only the "Use `MDX`", "Use `remark-gfm`", and "Use `remark-directive`" options checked](@site/blog/2023-09-29-preparing-your-site-for-docusaurus-v3/img/mdx2-playground-options.png)
+![Screenshot of the MDX playground's options panel, with only the "Use `MDX`", "Use `remark-gfm`", and "Use `remark-directive`" options checked](@site/blog/2023/2023-09-29-preparing-your-site-for-docusaurus-v3/img/mdx2-playground-options.png)
 
 </details>
 
@@ -171,7 +171,7 @@ npx docusaurus-mdx-checker
 
 For each compilation issue, the CLI will log the file path and a line number to look at.
 
-![Screenshot of the terminal showing an example MDX checker CLI output, with a few error messages](@site/blog/2023-09-29-preparing-your-site-for-docusaurus-v3/img/mdx-checker-output.png)
+![Screenshot of the terminal showing an example MDX checker CLI output, with a few error messages](@site/blog/2023/2023-09-29-preparing-your-site-for-docusaurus-v3/img/mdx-checker-output.png)
 
 :::tip
 

website/docusaurus.config.ts

@@ -445,6 +445,7 @@ export default async function createConfigAsync() {
             path: 'blog',
             showLastUpdateAuthor: true,
             showLastUpdateTime: true,
+            flattenFolders: true,
             editUrl: ({locale, blogDirPath, blogPath}) => {
               if (locale !== defaultLocale) {
                 return `https://crowdin.com/project/docusaurus-v2/${locale}`;

website/versioned_docs/version-3.0.1/migration/v3.mdx

@@ -149,7 +149,7 @@ To obtain a compilation behavior similar to what Docusaurus v2 uses, please turn
 - Use `remark-gfm`
 - Use `remark-directive`
 
-![Screenshot of the MDX playground's options panel, with only the "Use `MDX`", "Use `remark-gfm`", and "Use `remark-directive`" options checked](@site/blog/2023-09-29-preparing-your-site-for-docusaurus-v3/img/mdx2-playground-options.png)
+![Screenshot of the MDX playground's options panel, with only the "Use `MDX`", "Use `remark-gfm`", and "Use `remark-directive`" options checked](@site/blog/2023/2023-09-29-preparing-your-site-for-docusaurus-v3/img/mdx2-playground-options.png)
 
 </details>
 
@@ -171,7 +171,7 @@ npx docusaurus-mdx-checker
 
 For each compilation issue, the CLI will log the file path and a line number to look at.
 
-![Screenshot of the terminal showing an example MDX checker CLI output, with a few error messages](@site/blog/2023-09-29-preparing-your-site-for-docusaurus-v3/img/mdx-checker-output.png)
+![Screenshot of the terminal showing an example MDX checker CLI output, with a few error messages](@site/blog/2023/2023-09-29-preparing-your-site-for-docusaurus-v3/img/mdx-checker-output.png)
 
 :::tip
 

website/versioned_docs/version-3.1.1/migration/v3.mdx

@@ -149,7 +149,7 @@ To obtain a compilation behavior similar to what Docusaurus v2 uses, please turn
 - Use `remark-gfm`
 - Use `remark-directive`
 
-![Screenshot of the MDX playground's options panel, with only the "Use `MDX`", "Use `remark-gfm`", and "Use `remark-directive`" options checked](@site/blog/2023-09-29-preparing-your-site-for-docusaurus-v3/img/mdx2-playground-options.png)
+![Screenshot of the MDX playground's options panel, with only the "Use `MDX`", "Use `remark-gfm`", and "Use `remark-directive`" options checked](@site/blog/2023/2023-09-29-preparing-your-site-for-docusaurus-v3/img/mdx2-playground-options.png)
 
 </details>
 
@@ -171,7 +171,7 @@ npx docusaurus-mdx-checker
 
 For each compilation issue, the CLI will log the file path and a line number to look at.
 
-![Screenshot of the terminal showing an example MDX checker CLI output, with a few error messages](@site/blog/2023-09-29-preparing-your-site-for-docusaurus-v3/img/mdx-checker-output.png)
+![Screenshot of the terminal showing an example MDX checker CLI output, with a few error messages](@site/blog/2023/2023-09-29-preparing-your-site-for-docusaurus-v3/img/mdx-checker-output.png)
 
 :::tip