convert all old CodeWithTabs to new Tabs

Author: davemooreuws

docs/apis.mdx

@@ -710,9 +710,11 @@ func main() {
 
 By default APIs deployed by Nitric will be assigned a domain by the target cloud provider. If you would like to deploy APIs with predefined custom domains you can specify the custom domains for each API in your project's stack files. For these domains to be successfully configured you will need to meet the prerequisites defined for each cloud provider below.
 
-<CodeWithTabs>
+<Tabs syncKey="providers">
 
-```yaml !!tabs AWS file:nitric.prod.yaml
+<TabItem label="AWS">
+
+```yaml file:nitric.prod.yaml
 provider: nitric/[email protected]
 region: ap-southeast-2
 
@@ -725,23 +727,35 @@ apis:
       - test.example.com
 ```
 
-```yaml !!tabs Azure file:nitric.prod.yaml
+</TabItem>
+
+<TabItem label="Azure">
+
+```yaml file:nitric.prod.yaml
 # currently unsupported - request support here: https://github.com/nitrictech/nitric/issues
 ```
 
-```yaml !!tabs Google Cloud file:nitric.prod.yaml
+</TabItem>
+
+<TabItem label="Google Cloud">
+
+```yaml file:nitric.prod.yaml
 # currently unsupported - request support here: https://github.com/nitrictech/nitric/issues
 ```
 
-</CodeWithTabs>
+</TabItem>
+
+</Tabs>
 
 ## Custom Descriptions
 
 By default, APIs will not be deployed with a description. You can add a description using the following configuration in your stack file.
 
-<CodeWithTabs>
+<Tabs syncKey="providers">
 
-```yaml !!tabs AWS file:nitric.prod.yaml
+<TabItem label="AWS">
+
+```yaml file:nitric.prod.yaml
 provider: nitric/[email protected]
 region: ap-southeast-2
 
@@ -753,7 +767,11 @@ apis:
     description: An AWS API
 ```
 
-```yaml !!tabs Azure file:nitric.prod.yaml
+</TabItem>
+
+<TabItem label="Azure">
+
+```yaml file:nitric.prod.yaml
 provider: nitric/[email protected]
 region: Australia East
 org: example-org
@@ -766,7 +784,11 @@ apis:
     description: An Azure API
 ```
 
-```yaml !!tabs Google Cloud file:nitric.prod.yaml
+</TabItem>
+
+<TabItem label="Google Cloud">
+
+```yaml file:nitric.prod.yaml
 provider: nitric/[email protected]
 region: australia-southeast1
 
@@ -778,7 +800,9 @@ apis:
     description: A GCP API
 ```
 
-</CodeWithTabs>
+</TabItem>
+
+</Tabs>
 
 ### AWS Custom Domain Prerequisites
 

docs/get-started/foundations/infrastructure/index.mdx

@@ -24,9 +24,11 @@ Sometimes it's easier to explain IfC by exploring the benefits.
 
 Nitric significantly reduces or removes cloud-specific code. For example, accessing a file in a cloud storage bucket with Nitric is just a few lines of code, while the equivalent code using cloud provider SDKs is much more verbose and error prone:
 
-<CodeWithTabs>
+<Tabs>
 
-```javascript !!tabs Nitric SDK
+<TabItem label="Nitric SDK">
+
+```javascript
 import { bucket } from '@nitric/sdk'
 
 const profiles = bucket('profiles').allow('read')
@@ -36,7 +38,11 @@ export const getProfilePic = async (filename) => {
 }
 ```
 
-```javascript !!tabs AWS SDK
+</TabItem>
+
+<TabItem label="AWS SDK">
+
+```javascript
 import { GetObjectCommand, S3Client } from '@aws-sdk/client-s3'
 
 const client = new S3Client({})
@@ -57,7 +63,9 @@ export const getProfilePic = async (filename) => {
 }
 ```
 
-</CodeWithTabs>
+</TabItem>
+
+</Tabs>
 
 ---
 
@@ -79,25 +87,41 @@ export const publishMessage = async (message) => {
 
 We can change the underlying messaging service through a simple configuration change, without modifying the application code.
 
-<CodeWithTabs>
+<Tabs>
+
+<TabItem label="AWS">
 
-```yaml !!tabs AWS file:nitric.prod.yaml
+```yaml file:nitric.prod.yaml
 provider: nitric/[email protected]
 ```
 
-```yaml !!tabs Azure file:nitric.prod.yaml
+</TabItem>
+
+<TabItem label="Azure">
+
+```yaml file:nitric.prod.yaml
 provider: nitric/[email protected]
 ```
 
-```yaml !!tabs Google Cloud file:nitric.prod.yaml
+</TabItem>
+
+<TabItem label="Google Cloud">
+
+```yaml file:nitric.prod.yaml
 provider: nitric/[email protected]
 ```
 
-```yaml !!tabs Anything Else file:nitric.prod.yaml
+</TabItem>
+
+<TabItem label="Anything Else">
+
+```yaml file:nitric.prod.yaml
 provider: your_namespace/[email protected]
 ```
 
-</CodeWithTabs>
+</TabItem>
+
+</Tabs>
 
 <Note>
   The runtime code for cloud services like SNS still exists, it's just isolated

docs/get-started/foundations/projects/index.mdx

@@ -24,9 +24,11 @@ We recommend starting with a template, using the `nitric new` CLI command. These
 
 Here are some examples of basic Nitric project structures:
 
-<CodeWithTabs>
+<Tabs>
 
-```text !!tabs Go
+<TabItem label="Go">
+
+```text Go
 my-project/
 ├── nitric.yaml
 ├── nitric.aws.yaml
@@ -37,7 +39,11 @@ my-project/
         └── main.go
 ```
 
-```text !!tabs JavaScript
+</TabItem>
+
+<TabItem label="JavaScript">
+
+```text JavaScript
 my-project/
 ├── nitric.yaml
 ├── nitric.aws.yaml
@@ -46,7 +52,11 @@ my-project/
     └── service2.js
 ```
 
-```text !!tabs Python
+</TabItem>
+
+<TabItem label="Python">
+
+```text Python
 my-project/
 ├── nitric.yaml
 ├── nitric.aws.yaml
@@ -55,7 +65,9 @@ my-project/
     └── service2.py
 ```
 
-</CodeWithTabs>
+</TabItem>
+
+</Tabs>
 
 This flexibility allows you to build apps as a single monolithic service, multiple microservices, or something else entirely.