Fix broken external links (#1379)

* Remove deleted starter references

* Update contact information in blogs

.github/CODEOWNERS

@@ -2,4 +2,4 @@
 
 /content/docs/tina-cloud/**/* @tinacms/commercial-maintainers
 
-/content/blog/**/* james.perkins@forestry.io
+/content/blog/**/*

content/blog/2021-a-year-in-review.md

@@ -32,9 +32,9 @@ April was the launch of the cloud product. Scott Gallant (CEO) made the announce
 
 May is when we went "all in" on using Next.js, the biggest appeals to us were:
 
-*   Dynamic imports
-*   Flexible data fetching
-*   Next.js was becoming the leader in the Jamstack and had a great community.
+- Dynamic imports
+- Flexible data fetching
+- Next.js was becoming the leader in the Jamstack and had a great community.
 
 Working with a single framework helped us iterate quickly and focus on the right problems versus worrying about edge cases and nuances with each framework we supported.
 
@@ -52,7 +52,7 @@ After talking to the team about the vision of Tina, I was all in, I didn't want
 
 June 2nd, 2021 we announced to the community that Tina Cloud was in public alpha, and we encouraged anyone who wanted to see the future of content editing and management to give it a shot.
 
-![Tina Alpha Tweet](https://res.cloudinary.com/forestry-demo/image/upload/v1640092818/blog-media/year-in-review/alpha.png "")
+![Tina Alpha Tweet](https://res.cloudinary.com/forestry-demo/image/upload/v1640092818/blog-media/year-in-review/alpha.png)
 
 You all took us up on our offer, users spiked, commits were made, and feedback started to come in. We felt the beginnings of a community that wanted and cared about Tina. Your feedback went directly to the team and into brainstorming product meetings.
 
@@ -70,17 +70,17 @@ We wanted to make it as easy as possible to add Cloudinary support for your site
 
 In August we made the biggest announcement since I started at Tina. We placed the product in beta. I remember the buzz around the "office" as we got closer and closer to the announcement. There was a lot of hard work that went into our beta release, so the team were excited to see what the world though of these changes. We had no idea how we were going to fit it all in a blog post, the announcement wasn't just about changing the words alpha to beta we also had:
 
-*   Better documentation
-*   A new CLI
-*   Better guides
-*   Better starters
-*   Caching improvements
-*   Creating @tinacms/toolkit
-*   Vercel integration
-*   Dashboard overhaul
-*   Changes to content modeling
+- Better documentation
+- A new CLI
+- Better guides
+- Better starters
+- Caching improvements
+- Creating @tinacms/toolkit
+- Vercel integration
+- Dashboard overhaul
+- Changes to content modeling
 
-![Beta Tweet](https://res.cloudinary.com/forestry-demo/image/upload/v1640092818/blog-media/year-in-review/beta.png "")
+![Beta Tweet](https://res.cloudinary.com/forestry-demo/image/upload/v1640092818/blog-media/year-in-review/beta.png)
 
 We also hired Kelly to help with our Cloud offering and Logan to help with our open-source product. Logan had already been working as an intern but he was an integral part of the team and we wanted him to work at Tina after he graduated.
 
@@ -140,4 +140,4 @@ At the beginning of the year, Tina was an experimental open-source project that
 
 In our next post, we're going to describe where this is all going and our plan for Tina in 2022. The whole team is truly excited to enter the next phase of our project and hope you will check it out and give us honest feedback. We want to hear about your projects that use Tina and anything we can do to make it easier, faster or better.
 
-To keep up to date with Tina goings-on make sure to follow [@tina\_cms](https://twitter.com/tina\_cms) and [@james\_r\_perkins](https://twitter.com/james\_r\_perkins) on Twitter. Want to chat with the team? Join the [Discord](https://discord.gg/njvZZYHj2Q)
+To keep up to date with Tina goings-on make sure to follow [@tina_cms](https://twitter.com/tina_cms) on Twitter. Want to chat with the team? Join the [Discord](https://discord.gg/njvZZYHj2Q)

content/blog/announcement-tina-cloud-is-officially-in-alpha.md

@@ -59,6 +59,6 @@ We are still deciding out what we believe will be fair pricing for people who de
 
 The whole team is truly excited to enter a public Alpha phase and hope you will check it out and give us honest feedback. We wanna hear about your projects, let us know how Tina Cloud can help your team make progress.
 
-To keep up to date with Tina goings-on make sure to follow [@tina_cms](https://twitter.com/tina_cms) and [@james_r_perkins](https://twitter.com/james_r_perkins) on Twitter.
+To keep up to date with Tina goings-on make sure to follow [@tina_cms](https://twitter.com/tina_cms) on Twitter.
 
 Stay tuned for further improvements, features, community-built projects and more!

content/blog/mdx-powered-docs.md

@@ -13,13 +13,11 @@ When we released our [MDX Support](/docs/mdx/), we wanted to create a real-world
 
 Creating a documentation starter required some investigation. We wanted a starting point that would allow us to add all the features we believe are important to documentation, such as an easy way to add videos without using iframes or callouts. So we decided that Smooth Doc would be the perfect starting point.
 
-
 ## Smooth Doc
 
 [Smooth Doc](https://smooth-doc.com/) was created by [Greg Bergé](https://twitter.com/neoziro) who also created xstyled components and spends a lot of time creating products. He needed a great documentation site that he could reuse over and over again. The original Smooth Doc is built on Gatsby and uses MDX under the hood to power the entire site, another open-source creator turned Smooth Doc into a Next site.
 
-Smooth Doc has a lot of features, but we removed some,  such as carbon ads, so that we could deliver a streamlined product for our starter.
-
+Smooth Doc has a lot of features, but we removed some, such as carbon ads, so that we could deliver a streamlined product for our starter.
 
 ## MDX
 
@@ -47,7 +45,6 @@ We are big fans of markdown and have just introduced the ability to support MDX.
 
 Each one of these components is easily edited by content teams with no development experience. We also give developers the ability to create their own components for their content teams, such as a newsletter signup.
 
-
 ## Tina
 
 The MDX-powered Tina delivers a world-class experience for both developers and content teams. We allow you to create new documentation with ease by unlocking a contextual editing experience versus a traditional CMS.
@@ -78,4 +75,4 @@ One benefit of using Tina is that you can create new pages without leaving your
 
 We hope you enjoy the documentation starter and it unlocks your team’s productivity. If you have any questions or issues please make sure to join the [Discord](https://discord.gg/njvZZYHj2Q) or use our [GitHub Discussions](https://github.com/tinacms/tinacms/discussions).
 
-To keep up to date with Tina’s goings-on make sure to follow [@tina_cms](https://twitter.com/tina_cms) and [@james_r_perkins](https://twitter.com/james_r_perkins) on Twitter.
+To keep up to date with Tina’s goings-on make sure to follow [@tina_cms](https://twitter.com/tina_cms) on Twitter.

content/blog/simple-markdown-blog-nextjs.md

@@ -18,15 +18,15 @@ Next.js is a React "metaframework" (a framework built on a framework) for develo
 
 ---
 
-If you'd like to skip ahead and reference final versions of the starter, feel free to checkout the [finished implementation](https://github.com/perkinsjr/brevifolia-next-2022).
+If you'd like to skip ahead and reference final versions of the starter, feel free to checkout the [finished implementation](https://github.com/tinalabs/brevifolia-next-2022).
 
 ## Clone the starter
 
-Let’s get started. I have provided a [bare bones starter](https://github.com/perkinsjr/nextjs-starter-boilerplate) to use as a starting point for this tutorial. You can clone the project or check it out on [github](https://github.com/perkinsjr/nextjs-starter-boilerplate) for reference.
+Let’s get started. I have provided a [bare bones starter](https://github.com/tinalabs/nextjs-starter-boilerplate) to use as a starting point for this tutorial. You can clone the project or check it out on [github](https://github.com/tinalabs/nextjs-starter-boilerplate) for reference.
 
 ```javascript
 // clone the repo from your terminal
-$ git clone https://github.com/perkinsjr/nextjs-starter-boilerplate my-nextjs-blog
+$ git clone https://github.com/tinalabs/nextjs-starter-boilerplate my-nextjs-blog
 
 // install the dependencies
 $ cd my-nextjs-blog
@@ -317,13 +317,13 @@ const Index = props => {
 export default Index
 ```
 
-Then you are free to loop through the blogs and render the list within your `BlogList` component as you need. Feel free to check out the [BlogList component](https://github.com/perkinsjr/brevifolia-next-2022/blob/master/components/BlogList.js) in my starter to see how that data could be handled.
+Then you are free to loop through the blogs and render the list within your `BlogList` component as you need. Feel free to check out the [BlogList component](https://github.com/tinalabs/brevifolia-next-2022/blob/master/components/BlogList.js) in my starter to see how that data could be handled.
 
 ## Next Steps
 
-> Checkout the [final repo](https://github.com/perkinsjr/brevifolia-next-2022)!
+> Checkout the [final repo](https://github.com/tinalabs/brevifolia-next-2022)!
 
-After setting up your blog or portfolio site, you’ll most likely need a content management system to make editing and updating your posts or data easier. Stay tuned for my next blog on setting up this starter with TinaCMS. In the meantime, you can check out our [documentation ](/docs), or [fork the finished Next+Tina blog](https://github.com/perkinsjr/tina-simple-markdown) to start playing with TinaCMS right away.
+After setting up your blog or portfolio site, you’ll most likely need a content management system to make editing and updating your posts or data easier. Stay tuned for my next blog on setting up this starter with TinaCMS. In the meantime, you can check out our [documentation ](/docs), or [try out a starter](https://tina.io/docs/introduction/using-starter/) to start playing with TinaCMS right away.
 
 ## Where can you keep up to date with Tina?
 

content/blog/tina-is-in-beta.md

@@ -127,6 +127,6 @@ If you used the alpha of Tina you might want to read this article the team put t
 
 The whole team is truly excited to enter the beta phase and hope you will check it out and give us honest feedback. We want to hear about your projects or, let us know how Tina Cloud can help your team make progress.
 
-To keep up to date with Tina goings-on make sure to follow [@tina_cms](https://twitter.com/tina_cms) and [@james_r_perkins](https://twitter.com/james_r_perkins) on Twitter. Want to chat with the team? Join the [Discord](https://discord.gg/njvZZYHj2Q)
+To keep up to date with Tina goings-on make sure to follow [@tina_cms](https://twitter.com/tina_cms) on Twitter. Want to chat with the team? Join the [Discord](https://discord.gg/njvZZYHj2Q)
 
 Stay tuned for further improvements, features, community-built projects and more!

content/blog/using-tinacms-with-nextjs.md

@@ -26,15 +26,15 @@ The best way to get a feel for how Tina works is to use it. We hope that by the
 
 This tutorial will show you how to install and **configure Tina for editing content on a simple markdown-based blog** that was created in last week’s post. If you want to dig into how the base blog was made, read [Part I](/blog/simple-markdown-blog-nextjs/) of this series.
 
-> Jump ahead to see the [final repo here](https://github.com/perkinsjr/tina-simple-markdown). Or check out the [Tina documentation](/docs/setup-overview/) here
+> Jump ahead and check out the [Tina documentation](/docs/setup-overview/) here
 
 ### Set up Locally 🏡
 
 Feel free to follow along and fit these guidelines to your own site or blog, or you can use the starter we created in the previous tutorial. In your terminal, navigate to where you would like this blog to live, then run:
 
 ```bash
 # clone the repo
-$ git clone https://github.com/perkinsjr/brevifolia-next-2022 next-tina-blog
+$ git clone https://github.com/tinalabs/brevifolia-next-2022 next-tina-blog
 
 # navigate to the directory
 $ cd next-tina-blog
@@ -587,7 +587,7 @@ Your TinaCMS should now look like this:
 
 #### Testing
 
-Go ahead and launch your blog and you should be able to see a new markdown editor that allows you to pass in data. Well done! With some config and calling a few hooks, you can now edit all our blog posts with Tina. Checkout the [final repo](https://github.com/perkinsjr/tina-simple-markdown), you might consider doing the following
+Go ahead and launch your blog and you should be able to see a new markdown editor that allows you to pass in data. Well done! With some config and calling a few hooks, you can now edit all our blog posts with Tina.
 
 ## Where can you keep up to date with Tina?