revamp snowflake docs (#7)

* finish intro page

* remove hugo semantics

* get capabilities done

* finish integrations

* get ui docs done

* finish tutorials

* fix everything in getting started docs

* fix last remaining pieces

* few more things done

* add snowflake sql functions

* more changes

Author: HarshCasper

astro.config.mjs

@@ -287,7 +287,7 @@ export default defineConfig({
           collapsed: true,
           items: [
             {
-              label: 'Welcome',
+              label: 'Introduction',
               slug: 'snowflake',
             },
             {
@@ -324,10 +324,6 @@ export default defineConfig({
               label: 'SQL Functions',
               slug: 'snowflake/sql-functions',
             },
-            {
-              label: 'Feature Coverage',
-              slug: 'snowflake/coverage-features',
-            },
             {
               label: 'Changelog',
               slug: 'snowflake/changelog',

public/images/snowflake/credit_df_cat.png

@@ -6,16 +6,13 @@ nav:
 label: 
 ---
 
-
-
-
 LocalStack exposes various configuration options to control its behaviour.
 
 These options can be passed to LocalStack as environment variables like so:
 
-{{< command >}}
-$ DEBUG=1 localstack start
-{{< / command >}}
+```bash
+DEBUG=1 localstack start
+```
 
 ## Core
 
@@ -39,7 +36,7 @@ These options are applicable when using the CLI to start LocalStack.
 | Variable | Example Values | Description |
 | - | - | - |
 | `LOCALSTACK_VOLUME_DIR` | `~/.cache/localstack/volume` (on Linux) | The location on the host of the LocalStack volume directory mount. |
-| `CONFIG_PROFILE` | | The configuration profile to load. See [Profiles]({{< ref "#profiles" >}}) |
+| `CONFIG_PROFILE` | | The configuration profile to load. See [Profiles](#profiles) |
 | `CONFIG_DIR` | `~/.localstack` | The path where LocalStack can find configuration profiles and other CLI-specific configuration |
 
 ## Docker
@@ -72,42 +69,41 @@ A configuration profile is a set of environment variables stored in a `*.env` fi
 
 Here is an example of what configuration profiles might look like:
 
-{{< command >}}
+```bash
 $ tree ~/.localstack
 /home/username/.localstack
 ├── default.env
 ├── dev.env
 └── pro.env
-{{< / command >}}
+```
 
 Here is an example of what a specific environment profile looks like
 
-{{< command >}}
+```bash
 $ cat ~/.localstack/pro-debug.env
 LOCALSTACK_AUTH_TOKEN=XXXXX
 SF_LOG=trace
 SF_S3_ENDPOINT=s3.localhost.localstack.cloud:4566
-{{< / command >}}
+```
 
 You can load a profile by either setting the environment variable `CONFIG_PROFILE=<profile>` or the `--profile=<profile>` CLI flag when using the CLI.
 Let's take an example to load the `dev.env` profile file if it exists:
 
-{{< command >}}
-$ IMAGE_NAME=localstack/snowflake localstack --profile=dev start
-{{< / command >}}
+```bash
+IMAGE_NAME=localstack/snowflake localstack --profile=dev start
+```
 
 If no profile is specified, the `default.env` profile will be loaded.
 If explicitly specified, any environment variables will overwrite the configurations defined in the profile.
 
 To display the config environment variables, you can use the following command:
 
-{{< command >}}
-$ localstack --profile=dev config show
-{{< / command >}}
+```bash
+localstack --profile=dev config show
+```
 
-{{< alert title="Note" >}}
+:::note
 The `CONFIG_PROFILE` is a CLI feature and cannot be used directly with a docker-compose setup.
 You can look at [alternative means of setting environment variables](https://docs.docker.com/compose/environment-variables/set-environment-variables/) for your Docker Compose setups.
 For Docker setups, we recommend passing the environment variables directly to the `docker run` command.
-{{< /alert >}}
-
+:::

public/images/snowflake/credit_df_hist.png

@@ -3,8 +3,8 @@ title: Initialization Hooks
 description: Writing SQL scripts to initialize your Snowflake emulator
 ---
 
+import { Tabs, TabItem } from '@astrojs/starlight/components';
 
- 
 ## Introduction
 
 LocalStack for Snowflake supports automatically executing `*.sf.sql` files via [Init Hooks](https://docs.localstack.cloud/references/init-hooks/) when mounted into the Docker container. A script can be added to one of these stages in the lifecycle:
@@ -28,8 +28,9 @@ SHOW DATABASES;
 
 Mount the script into `/etc/localstack/init/ready.d/` using Docker Compose or the `localstack` CLI:
 
-{{< tabpane >}}
-{{< tab header="docker-compose.yml" lang="yml" >}}
+<Tabs>
+<TabItem label="docker-compose.yml">
+```yaml
 version: "3.8"
 
 services:
@@ -47,13 +48,17 @@ services:
       - "/path/to/test.sf.sql:/etc/localstack/init/ready.d/test.sf.sql"  # ready hook
       - "${LOCALSTACK_VOLUME_DIR:-./volume}:/var/lib/localstack"
       - "/var/run/docker.sock:/var/run/docker.sock"
-{{< /tab >}}
-{{< tab header="CLI" lang="bash" >}}
+```
+</TabItem>
+<TabItem label="CLI">
+```bash
 # DOCKER_FLAGS are additional parameters to the `docker run` command of localstack start
-
-DOCKER_FLAGS='-v /path/to/test.sf.sql:/etc/localstack/init/ready.d/test.sf.sql' DEBUG=1 localstack start
-{{< /tab >}}
-{{< /tabpane >}}
+DOCKER_FLAGS='-v /path/to/test.sf.sql:/etc/localstack/init/ready.d/test.sf.sql' \
+DEBUG=1 \
+localstack start
+```
+</TabItem>
+</Tabs>
 
 Start the Snowflake emulator, and the following logs will appear:
 

public/images/snowflake/dbeaver-new-connection.png

@@ -3,7 +3,7 @@ title: State Management
 description: Get started with State Management in LocalStack for Snowflake
 ---
 
-
+import { Tabs, TabItem } from '@astrojs/starlight/components'; 
 
 ## Introduction
 
@@ -22,34 +22,43 @@ LocalStack’s Persistence mechanism enables the saving and restoration of the e
 
 To start snapshot-based persistence, launch LocalStack with the configuration option `PERSISTENCE=1`. This setting instructs LocalStack to save all local Snowflake resources and their respective application states into the LocalStack Volume Directory. Upon restarting LocalStack, you'll be able to resume your activities exactly where you left off.
 
-{{< tabpane >}}
-{{< tab header="LocalStack CLI" lang="bash" >}}
-LOCALSTACK_AUTH_TOKEN=... PERSISTENCE=1 IMAGE_NAME=localstack/snowflake localstack start
-{{< /tab >}}
-{{< tab header="Docker Compose" lang="yaml" >}}
+<Tabs>
+<TabItem label="LocalStack CLI">
+```bash
+LOCALSTACK_AUTH_TOKEN=... \
+PERSISTENCE=1 \
+IMAGE_NAME=localstack/snowflake \
+localstack start
+```
+</TabItem>
+<TabItem label="Docker Compose">
+```yaml
     ...
     image: localstack/snowflake
     environment:
       - LOCALSTACK_AUTH_TOKEN=${LOCALSTACK_AUTH_TOKEN:?}
       - PERSISTENCE=1
     volumes:
       - "${LOCALSTACK_VOLUME_DIR:-./volume}:/var/lib/localstack"
-{{< /tab >}}
-{{< tab header="Docker" lang="bash" >}}
+```
+</TabItem>
+<TabItem label="Docker">
+```bash
 docker run \
   -e LOCALSTACK_AUTH_TOKEN=${LOCALSTACK_AUTH_TOKEN:?} \
   -e PERSISTENCE=1 \
   -v ./volume:/var/lib/localstack \
   -p 4566:4566 \
   localstack/snowflake
-{{< /tab >}}
-{{< /tabpane >}}
+```
+</TabItem>
+</Tabs>
 
-{{< alert title="Note">}}
+:::note
 Snapshots may not be compatible across different versions of LocalStack.
 It is possible that snapshots from older versions can be restored, but there are no guarantees as to whether LocalStack will start into a consistent state.
 We are actively working on a solution for this problem.
-{{< /alert >}}
+:::
 
 ## Export/Import State
 
@@ -59,18 +68,18 @@ The Export/Import State feature enables you to export the state of your LocalSta
 
 To export the state, you can run the following command:
 
-{{< command >}}
-$ localstack state export '<file-name>'
-{{< /command >}}
+```bash
+localstack state export '<file-name>'
+```
 
 You can use the `<file-name>` argument to specify a file path to export the state to. If you do not specify a file path, the state will be exported to the current working directory into a file named `ls-state-export`.
 
 ### Import the State
 
 To import the state, you can run the following command:
 
-{{< command >}}
-$ localstack state import '<file-name>'
-{{< /command >}}
+```bash
+localstack state import '<file-name>'
+```
 
 The `<file-name>` argument is required and specifies the file path to import the state from. The file should be generated from a previous export.