added angular

docs/sdks/getting-started.md → docs/sdks/getting-started.mdx

@@ -4,6 +4,13 @@ sidebar_label: SDK Overview
 slug: /sdks/getting-started
 ---
 
+import SDKAndFrameworks from '../../src/components/getting-started/SDKAndFrameworks';
+import Styles from '../../src/components/getting-started/Styles';
+
+<Styles/>
+
+
+
 Statsig provides a comprehensive set of SDKs to integrate experimentation, feature flagging, and logging into your applications. With support for over **30 platforms**, Statsig’s SDKs enable you to control feature rollouts and experiments seamlessly, whether you're building for **web**, **mobile**, or **server-side** environments.
 
 ---
@@ -38,37 +45,7 @@ Additionally, for frameworks like **Next.js** that bridge client and server-side
 
 ---
 
-## Client-Side SDKs
-
-Our client-side SDKs are designed for front-end applications, enabling instant event logging, feature gating, and user assignments. Whether you're building for mobile, web, or other client platforms, Statsig offers SDKs tailored for your needs:
-
-- [JavaScript](/client/javascript-sdk)
-- [React](/client/javascript-sdk/react)
-- [React Native](/client/javascript-sdk/react-native)
-- [Expo](/client/javascript-sdk/expo)
-- [iOS](/client/iosClientSDK)
-- [Android](/client/androidClientSDK)
-- [.NET](/client/dotnetSDK)
-- [Unity](/client/unitySDK)
-- [Roku](/client/rokuSDK)
-- [C++](/client/cpp-client-sdk)
-- [Dart/Flutter](/client/dartSDK)
-
----
-
-## Server-Side SDKs
-
-Server-side SDKs allow you to manage experiments and feature flags from your backend, providing more control and reliability. They’re especially useful for server-driven features, background processes, and system events:
-
-- [Node.js](/server/nodejsServerSDK)
-- [Java](/server/javaSdk)
-- [Python](/server/pythonSDK)
-- [Go](/server/golangSDK)
-- [Ruby](/server/rubySDK)
-- [.NET](/server/dotnetSDK)
-- [PHP](/server/phpSDK)
-- [C++](/server/cppSDK)
-- [Rust](/server/rustSDK)
+<SDKAndFrameworks />
 
 ---
 

docs/understanding-the-platform.md

@@ -52,7 +52,7 @@ Still unsure! Read this blog post for further information: [Statsig Cloud vs War
 ## Next steps
 Once you've decided whether Statsig Cloud or Statsig Warehouse Native fits your organization’s needs, choose the appropriate *getting started* guide for your first use case:
 
-- [Getting Started with Statsig Cloud](/sdks/getting-started.md)
+- [Getting Started with Statsig Cloud](/sdks/getting-started)
 - [Getting Started with Statsig Warehouse Native](/statsig-warehouse-native/guides/quick-start)
 
 :::info

src/components/getting-started/SDKAndFrameworks.jsx

@@ -9,6 +9,7 @@ const sdkGroups = [
       { name: 'React', img: '/img/sdk/sdk_react.png', link: '/client/javascript-sdk/react' },
       { name: 'React Native', img: '/img/sdk/sdk_rn.png', link: '/client/javascript-sdk/react-native' },
       { name: 'Next.js', img: '/img/sdk/sdk_nextjs.svg', link: '/client/javascript-sdk/next-js' },
+      { name: 'Angular', img: '/img/sdk/sdk_angular.png', link: '/client/javascript-sdk/Angular' },
       { name: 'Swift', img: '/img/sdk/sdk_swift.png', link: '/client/iosClientSDK' },
       { name: 'Android', img: '/img/sdk/sdk_android.png', link: '/client/androidClientSDK' },
       { name: '.NET Client', img: '/img/sdk/sdk_dotnet.png', link: '/client/dotnetSDK' },