Merge branch 'issue-0351' into adam/experiments

www/docs/src/content/docs/start-here/why-studioCMS.mdx

@@ -5,34 +5,25 @@ sidebar:
    order: 4
 ---
 
-We're so excited to introduce StudioCMS - a dedicated content management system (CMS) built on top of Astro's latest product: [Astro DB](https://docs.astro.build/en/guides/astro-db/). This project was developed by [Adam](https://github.com/Adammatthiesen), [Dreyfus](https://github.com/dreyfus92), and [Jumper](https://github.com/jdtjenkins), three passionate members of the Astro community.
+Astro is a content-focused framework. Features like content collections and the new content layer make it extremely easy to manage content of any size or form.
 
-## Why another CMS?
+However, it is also a solution that basically requires you to be a developer, or at least have a decent amount of knowledge about how Astro uses the files you
+put into your content directory. Also, the experience it provides is not something you can present to a client or any person just wanting an easy content 
+managing experience. You need a CMS for that.
 
-While Astro's content capabilities are powerful, we recognized a need for a more streamlined and user-friendly CMS solution within the Astro ecosystem. Many Astro users, especially those coming from more traditional CMS backgrounds, have expressed a desire for a dedicated CMS that can seamlessly integrate with Astro projects.
-
-StudioCMS was born out of this need, providing a content management platform that is tailor-made for Astro. By building on top of Astro Studio, we're able to offer a CMS experience that feels native to the Astro workflow, making it easier for both developers and content creators to collaborate on Astro-powered projects.
-
-## An Experimental Endeavor
-
-It's important to note that StudioCMS is an experimental project that heavily relies on the [@astrojs/db package](https://github.com/withastro/astro/tree/main/packages/db), which is currently in active development and not yet considered stable. As a result, you should expect a significant number of breaking changes as the project continues to evolve.
-
-We believe that by building on the cutting-edge features of Astro Db, we can create a powerful and innovative CMS solution. However, this also means that StudioCMS may not be suitable for mission-critical or production-ready projects at this stage. We encourage you to use caution and thoroughly test the CMS in your own projects before deploying it to a live environment.
+There's a lot of CMSs out there, with different flavors and features for your needs, but there is none that completely takes advantage of all of Astro's capabilities.
+That's why StudioCMS exists: a CMS that is completely focused on Astro and that can hook into every single one of its features to provide a highly improved DX.
 
 ## Key Features
 
-- **Part of Astrolicious:** Astrolicious leverages Astro's robust and efficient framework, providing a solid base for building and scaling applications.
-
-- **Secure libSQL Database:** All data is securely housed within your own libSQL database. Bring your own libSQL server through a provider such as [Turso](https://turso.tech/). Or self-host your own libSQL server.
-
-- **Realtime Markdown Editor:** StudioCMS has a real-time Markdown editor so you can create your content using powerful Markdown syntax and see changes reflected in real-time!
+- **@astrojs/db:** We use Astro DB, meaning that you can choose where and how your data is stored, be it Turso or a local file.
 
-- **Enhanced Markdown:** We've incorporated 'Marked' with support for extensions, enriching the markdown experience with greater flexibility and functionality.
+- **Shiki Syntax Highlighting:** Using shiki, we can make sure your code is both visually appealing and easy to read.
 
-- **Shiki Syntax Highlighting:** StudioCMS offers Shiki-powered syntax highlighting, ensuring your code is both visually appealing and easy to read. This is especially useful in non-Cloudflare environments due to bundle size considerations.
+- **Markdoc Integration:** In addition to `Marked`, you can use Markdoc to process your markdown however you need.
 
-- **Markdoc Integration:** In addition to 'Marked', StudioCMS provides an alternative with Markdoc, offering users a choice for their markdown processing needs.
+- **Built-in Authentication:** We support 5 different OAuth providers for which you can provide your own tokens to customize your auth however you need.
 
-- **Built-in Authentication:** StudioCMS features built-in authentication with support for multiple platforms, including Local and Github, enhancing security and user management (currently in development).
+- **WordPress Importer:** It's easy to switch to StudioCMS from any standard WordPress installation!
 
-- **Unpic Image Service:** StudioCMS includes a free and efficient image service, Unpic, which makes managing external URLs straightforward, with support for major CDNs.
+- **More to come in the future:** StudioCMS is under active development! We'll add more features over time to make your content experience even smoother!