TinaCMS content update

Co-authored-by: Landon Maxwell <[email protected]>

content/blog/deprecating-tina-git-server.mdx

@@ -1,10 +1,15 @@
 ---
+draft: false
+seo:
+  title: Deprecating Tina-Git-Server | TinaCMS Blog
+  description: >-
+    Learn about the deprecation of Tina-Git-Server in TinaCMS and what it means
+    for your projects, along with alternative solutions for content management
 title: Updated Next.js Docs + Deprecating tina-git-server
 date: '2019-12-06T07:00:00.000Z'
 author: DJ Walker
-draft: false
-next: content/blog/dynamic-plugin-system.mdx
 prev: content/blog/using-tinacms-with-nextjs.mdx
+next: content/blog/dynamic-plugin-system.mdx
 ---
 
 We've changed our recommended approach for using Tina's Git Backend with Next.js websites. Check out [Tina's Next.js documentation](/guides/nextjs/git/adding-backend) for details.
@@ -18,6 +23,6 @@ With Next.js, the lack of a plugin system requires developers to write a bit mor
 
 We previously settled on solution 1 in order to maximize compatibility with any existing Next.js sites; otherwise, anyone already using a custom server with Next.js and not using Express may have a harder time integrating the two together. This led to the creation of the `tina-git-server` command.
 
-The main issue with solution 1 is that, while middleware is a convenient way to "plug in" server code in the absence of a proper plugin system, these middleware "plugins" could only control _other plugins_. There is no way, in this system, to attach middleware that could exert any control over the website itself. We were originally OK with this limitation, but when strategizing about possible **access control** features, we decided this solution was inadequate.
+The main issue with solution 1 is that, while middleware is a convenient way to "plug in" server code in the absence of a proper plugin system, these middleware "plugins" could only control *other plugins*. There is no way, in this system, to attach middleware that could exert any control over the website itself. We were originally OK with this limitation, but when strategizing about possible **access control** features, we decided this solution was inadequate.
 
 Ultimately, solution 2 is both simpler and more robust. Although it requires more work on the end of the developer using Tina, this is often a side effect of software that properly [inverts control](https://kentcdodds.com/blog/inversion-of-control/).