Updated blog post on MkDocs 2.0

docs/blog/posts/mkdocs-2.0.md

@@ -89,6 +89,8 @@ Here's a summary of [the timeline of events]:
 
 The moment we learned about these plans, [we immediately started working] on what would eventually become [Zensical] – a new static site generator designed to be backward-compatible with MkDocs 1.x and a reliable long-term home for your existing documentation projects.
 
+For years, we were already trying to improve MkDocs from within. We authored [12 plugins], which gave us a deep understanding of the plugin API's limitations. We conducted quantitative and qualitative analyses of the ecosystem to identify where MkDocs was falling short and talked to dozens of organizations. We raised these issues and repeatedly got nowhere. When the new direction of MkDocs 2.0 became apparent, the thinking was already done.
+
 We considered forking MkDocs, but quickly realized it wasn't viable: every plugin in the ecosystem has a direct dependency on `mkdocs`, which means forking MkDocs would require forking every single one of its [300 plugins] – __like moving an entire city at once__.
 
 With forking being impractical, we had to start from scratch.
@@ -108,6 +110,7 @@ With forking being impractical, we had to start from scratch.
   [a team call on August 1]: https://github.com/mkdocs/mkdocs/discussions/3671#discussioncomment-10164237
   [we raised objections multiple times]: https://github.com/mkdocs/mkdocs/discussions/3671#discussioncomment-10215445
   [a reliable, backward-compatible home]: https://zensical.org/compatibility/
+  [12 plugins]: ../../plugins/index.md
 
 ## Where Zensical comes in