diff --git a/.github/workflows/prettier.yml b/.github/workflows/prettier.yml
index aef4d8f166d..f1314528f5b 100644
--- a/.github/workflows/prettier.yml
+++ b/.github/workflows/prettier.yml
@@ -11,9 +11,16 @@ jobs:
     steps:
       - name: Check out repo
         uses: actions/checkout@v3
+      - name: Setup node
+        uses: actions/setup-node@v3
+        with:
+          node-version: 18
+          cache: 'npm'
+      - name: Download dependencies
+        run: npm ci
       - name: Run prettier
         run: |-
-          npx prettier -c 'apps/**/*.{js,jsx,ts,tsx,css,md,json}'
+          npx prettier -c 'apps/**/*.{js,jsx,ts,tsx,css,md,mdx,json}'
         # [Joshen] Temp disable the following due to an issue
         # https://github.com/EPMatt/reviewdog-action-prettier/issues/34
         # uses: EPMatt/reviewdog-action-prettier@v1
@@ -42,9 +49,16 @@ jobs:
     steps:
       - name: Check out repo
         uses: actions/checkout@v3
+      - name: Setup node
+        uses: actions/setup-node@v3
+        with:
+          node-version: 18
+          cache: 'npm'
+      - name: Download dependencies
+        run: npm ci
       - name: Run prettier
         run: |-
-          npx prettier -c 'i18n/**/*.{js,jsx,ts,tsx,css,md,json}'
+          npx prettier -c 'i18n/**/*.{js,jsx,ts,tsx,css,md,mdx,json}'
         # uses: EPMatt/reviewdog-action-prettier@v1
         # with:
         #   github_token: ${{ secrets.github_token }}
diff --git a/.prettierrc b/.prettierrc
index b9bda117c38..c60d3ab91ef 100644
--- a/.prettierrc
+++ b/.prettierrc
@@ -5,5 +5,7 @@
   "singleQuote": true,
   "printWidth": 100,
   "endOfLine": "lf",
-  "sqlKeywordCase": "lower"
+  "sqlKeywordCase": "lower",
+  "pluginSearchDirs": false,
+  "plugins": ["prettier-plugin-sql-cst"]
 }
diff --git a/README.md b/README.md
index 56fc08e0f7d..bf770cbaa39 100644
--- a/README.md
+++ b/README.md
@@ -149,8 +149,8 @@ Our approach for client libraries is modular. Each sub-library is a standalone i
   <tr>
     <td>Kotlin</td>
     <td><a href="https://github.com/supabase-community/supabase-kt" target="_blank" rel="noopener noreferrer">supabase-kt</a></td>
-    <td><a href="https://github.com/supabase-community/postgrest-kt" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
-    <td><a href="https://github.com/supabase-community/gotrue-kt" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Postgrest" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/GoTrue" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
     <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Realtime" target="_blank" rel="noopener noreferrer">realtime-kt</a></td>
     <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Storage" target="_blank" rel="noopener noreferrer">storage-kt</a></td>
     <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Functions" target="_blank" rel="noopener noreferrer">functions-kt</a></td>
diff --git a/apps/docs/components/MDX/social_provider_settings_supabase.mdx b/apps/docs/components/MDX/social_provider_settings_supabase.mdx
index 1cc3771e6f3..38e0d9e5bfe 100644
--- a/apps/docs/components/MDX/social_provider_settings_supabase.mdx
+++ b/apps/docs/components/MDX/social_provider_settings_supabase.mdx
@@ -3,4 +3,4 @@
 - Click on [`Providers`](https://app.supabase.com/project/_/auth/providers) under the Configuration section
 - Click on **{props.provider}** from the accordion list to expand and turn **{props.provider} Enabled** to ON
 - Enter your **{props.provider} Client ID** and **{props.provider} Client Secret** saved in the previous step
-- Click `Save`
\ No newline at end of file
+- Click `Save`
diff --git a/apps/docs/components/Navigation/NavigationMenu/HomeMenuIconPicker.tsx b/apps/docs/components/Navigation/NavigationMenu/HomeMenuIconPicker.tsx
index 07ad9d7f9c0..a2b9fa52511 100644
--- a/apps/docs/components/Navigation/NavigationMenu/HomeMenuIconPicker.tsx
+++ b/apps/docs/components/Navigation/NavigationMenu/HomeMenuIconPicker.tsx
@@ -20,6 +20,7 @@ import {
   IconMenuStorage,
   IconMenuSwift,
   IconMenuStatus,
+  IconMenuKotlin,
 } from './HomeMenuIcons'
 
 function getMenuIcon(menuKey: string, width: number = 16, height: number = 16) {
@@ -58,6 +59,8 @@ function getMenuIcon(menuKey: string, width: number = 16, height: number = 16) {
       return <IconMenuCsharp width={width} height={height} />
     case 'reference-swift':
       return <IconMenuSwift width={width} height={height} />
+    case 'reference-kotlin':
+      return <IconMenuKotlin width={width} height={height} />
     case 'reference-api':
       return <IconMenuApi width={width} height={height} />
     case 'reference-cli':
diff --git a/apps/docs/components/Navigation/NavigationMenu/HomeMenuIcons.tsx b/apps/docs/components/Navigation/NavigationMenu/HomeMenuIcons.tsx
index 73a39c75f59..b9df4569256 100644
--- a/apps/docs/components/Navigation/NavigationMenu/HomeMenuIcons.tsx
+++ b/apps/docs/components/Navigation/NavigationMenu/HomeMenuIcons.tsx
@@ -382,6 +382,25 @@ export function IconMenuSwift({ width = 16, height = 16 }: HomeMenuIcon) {
   )
 }
 
+export function IconMenuKotlin({ width = 16, height = 16 }: HomeMenuIcon) {
+  return (
+    <svg
+      xmlns="http://www.w3.org/2000/svg"
+      viewBox="0 0 16 16"
+      width={width}
+      height={height}
+      fill="none"
+    >
+      <path
+        fillRule="evenodd"
+        clipRule="evenodd"
+        d="M14 14H2V2H14L8 8L14 14Z"
+        fill="currentColor"
+      />
+    </svg>
+  )
+}
+
 export function IconMenuStatus({ width = 16, height = 16 }: HomeMenuIcon) {
   return (
     <svg
diff --git a/apps/docs/components/Navigation/NavigationMenu/NavigationMenu.constants.ts b/apps/docs/components/Navigation/NavigationMenu/NavigationMenu.constants.ts
index 65906a620b3..840c07ac2a0 100644
--- a/apps/docs/components/Navigation/NavigationMenu/NavigationMenu.constants.ts
+++ b/apps/docs/components/Navigation/NavigationMenu/NavigationMenu.constants.ts
@@ -117,6 +117,13 @@ export const HOMEPAGE_MENU_ITEMS: HomepageMenuItems = [
       level: 'reference_swift',
       community: true,
     },
+    {
+      label: 'Kotlin',
+      icon: 'reference-kotlin',
+      href: '/reference/kotlin/introduction',
+      level: 'reference_kotlin',
+      community: true,
+    },
     {
       label: 'Tools reference',
     },
@@ -167,6 +174,12 @@ export const REFERENCES: References = {
     versions: ['v0'],
     icon: '/docs/img/libraries/swift-icon.svg',
   },
+  kotlin: {
+    name: 'Kotlin',
+    library: 'supabase-kt',
+    versions: ['v0'],
+    icon: '/docs/img/libraries/kotlin-icon.svg',
+  },
   cli: {
     name: 'CLI',
     library: undefined,
@@ -284,6 +297,10 @@ export const cli = {
   items: [
     { name: 'Overview', url: '/guides/cli' },
     { name: 'Managing Environments', url: '/guides/cli/managing-environments' },
+    {
+      name: 'Using environment variables in config.toml',
+      url: '/guides/cli/using-environment-variables-in-config',
+    },
   ],
 }
 
@@ -845,6 +862,10 @@ export const supabase_cli = {
   items: [
     { name: 'Overview', url: '/guides/cli' },
     { name: 'Managing Environments', url: '/guides/cli/managing-environments' },
+    {
+      name: 'Using environment variables in config.toml',
+      url: '/guides/cli/using-environment-variables-in-config',
+    },
     {
       name: 'Reference',
       url: undefined,
@@ -923,6 +944,10 @@ export const platform = {
           name: 'HTTP and Project Issues',
           url: '/guides/platform/troubleshooting',
         },
+        {
+          name: 'High CPU Usage',
+          url: '/guides/platform/exhaust-cpu',
+        },
       ],
     },
   ],
@@ -1128,6 +1153,13 @@ export const reference = {
           items: [],
           icon: '/img/icons/menu/reference-swift',
         },
+        {
+          name: 'supabase-kt',
+          url: '/reference/kotlin/start',
+          level: 'reference_kotlin',
+          items: [],
+          icon: '/img/icons/menu/reference-kotlin',
+        },
         // {
         //   name: 'supabase-python',
         //   url: '/reference/python/start',
@@ -1204,6 +1236,13 @@ export const reference_swift_v0 = {
   parent: '/reference',
 }
 
+export const reference_kotlin_v0 = {
+  icon: 'reference-kotlin',
+  title: 'kotlin',
+  url: 'guides/reference/kotlin',
+  parent: '/reference',
+}
+
 export const reference_cli = {
   icon: 'reference-cli',
   title: 'Supabase CLI',
@@ -1325,6 +1364,13 @@ export const references = [
         icon: '/docs/img/icons/swift-icon.svg',
         url: '/reference/swift/start',
       },
+      {
+        label: 'supabase-kt',
+        versions: ['v0'],
+        description: 'something about the reference',
+        icon: '/docs/img/icons/kotlin-icon.svg',
+        url: '/reference/kotlin/start',
+      },
     ],
   },
   {
diff --git a/apps/docs/components/Navigation/NavigationMenu/NavigationMenu.tsx b/apps/docs/components/Navigation/NavigationMenu/NavigationMenu.tsx
index de73c85aea9..2c5ad1a6734 100644
--- a/apps/docs/components/Navigation/NavigationMenu/NavigationMenu.tsx
+++ b/apps/docs/components/Navigation/NavigationMenu/NavigationMenu.tsx
@@ -143,6 +143,13 @@ const menus: Menu[] = [
     specFile: 'supabase_swift_v0.yml',
     type: 'reference',
   },
+  {
+    id: 'reference_kotlin_v0',
+    path: '/reference/kotlin',
+    commonSectionsFile: 'common-client-libs-sections.json',
+    specFile: 'supabase_kt_v0.yml',
+    type: 'reference',
+  },
   {
     id: 'reference_cli',
     path: '/reference/cli',
diff --git a/apps/docs/components/Navigation/NavigationMenu/TopNavBar.tsx b/apps/docs/components/Navigation/NavigationMenu/TopNavBar.tsx
index 3ade00aad45..15dd0f831d1 100644
--- a/apps/docs/components/Navigation/NavigationMenu/TopNavBar.tsx
+++ b/apps/docs/components/Navigation/NavigationMenu/TopNavBar.tsx
@@ -56,7 +56,7 @@ const TopNavBar: FC = () => {
   }
 
   return (
-    <nav className="h-[60px] border-b px-4 backdrop-blur backdrop-filter bg-white-1200 dark:bg-blackA-300">
+    <nav className="h-[60px] border-b px-4 backdrop-blur backdrop-filter bg-white-1200 bg-scale-200/90">
       <div className="max-w-[1400px] grid grid-cols-12 mx-auto gap-4 px-5 h-full">
         <div className="col-span-3 flex items-center">
           <button className="mr-4 block stroke-2 lg:hidden" onClick={toggleMobileMenu}>
diff --git a/apps/docs/components/Navigation/NavigationMenu/TopNavBarRef.tsx b/apps/docs/components/Navigation/NavigationMenu/TopNavBarRef.tsx
index 6a56ee7d544..826dda8003d 100644
--- a/apps/docs/components/Navigation/NavigationMenu/TopNavBarRef.tsx
+++ b/apps/docs/components/Navigation/NavigationMenu/TopNavBarRef.tsx
@@ -56,7 +56,7 @@ const TopNavBarRef: FC = () => {
   }
 
   return (
-    <nav className="h-[60px] border-b backdrop-blur backdrop-filter bg-white-1200 dark:bg-blackA-300">
+    <nav className="h-[60px] border-b backdrop-blur backdrop-filter bg-white-1200 dark:bg-scale-200/90">
       <div className="px-5 max-w-7xl mx-auto flex gap-3 justify-between items-center h-full">
         <div className={['lg:hidden'].join(' ')}>
           <Link href="/">
diff --git a/apps/docs/components/index.tsx b/apps/docs/components/index.tsx
index 468ea91e3c1..831b1fa4027 100644
--- a/apps/docs/components/index.tsx
+++ b/apps/docs/components/index.tsx
@@ -48,6 +48,7 @@ import {
   IconMenuPython,
   IconMenuCsharp,
   IconMenuSwift,
+  IconMenuKotlin,
   IconMenuApi,
   IconMenuCli,
 } from './Navigation/NavigationMenu/HomeMenuIcons'
@@ -110,6 +111,7 @@ const components = {
   IconMenuFlutter,
   IconMenuPython,
   IconMenuCsharp,
+  IconMenuKotlin,
   IconMenuSwift,
   IconMenuApi,
   IconMenuCli,
diff --git a/apps/docs/components/reference/RefFunctionSection.tsx b/apps/docs/components/reference/RefFunctionSection.tsx
index ddb35ba930b..739ad2c139e 100644
--- a/apps/docs/components/reference/RefFunctionSection.tsx
+++ b/apps/docs/components/reference/RefFunctionSection.tsx
@@ -123,6 +123,8 @@ const RefFunctionSection: React.FC<IRefFunctionSection> = (props) => {
                         ? 'dart'
                         : example?.code?.startsWith('```c#')
                         ? 'csharp'
+                        : example?.code?.startsWith('```kotlin')
+                        ? 'kotlin'
                         : 'js'
                       //                     `
                       // import { createClient } from '@supabase/supabase-js'
@@ -156,7 +158,8 @@ const RefFunctionSection: React.FC<IRefFunctionSection> = (props) => {
                                   .replace('js', '')
                                   .replace('ts', '')
                                   .replace('dart', '')
-                                  .replace('c#', ''))}
+                                  .replace('c#', '')
+                                  .replace('kotlin', ''))}
                           </CodeBlock>
 
                           {((tables && tables.length > 0) || sql) && (
diff --git a/apps/docs/data/nonGeneratedReferencePages.ts b/apps/docs/data/nonGeneratedReferencePages.ts
index 35ae2e4f540..e2d578ce2de 100644
--- a/apps/docs/data/nonGeneratedReferencePages.ts
+++ b/apps/docs/data/nonGeneratedReferencePages.ts
@@ -16,6 +16,8 @@ const nonGeneratedReferencePages = [
   'docs/reference/csharp',
   'docs/reference/csharp/installing',
   'docs/reference/csharp/initializing',
+  'docs/reference/kotlin/installing',
+  'docs/reference/kotlin/initializing',
   'docs/reference/api',
   'docs/reference/api/release-notes',
   'docs/reference/cli',
diff --git a/apps/docs/docs/ref/javascript/v1/upgrade-guide.mdx b/apps/docs/docs/ref/javascript/v1/upgrade-guide.mdx
index 01e843bbd42..d13e0311cae 100644
--- a/apps/docs/docs/ref/javascript/v1/upgrade-guide.mdx
+++ b/apps/docs/docs/ref/javascript/v1/upgrade-guide.mdx
@@ -89,7 +89,6 @@ The signIn() method has been deprecated in favor of more explicit method signatu
   defaultActiveId="1.0x"
 >
 <TabPanel id="1.0x" label="Before">
-{/* prettier-ignore */}
 ```ts
 const { user, error } = await supabase
   .auth
@@ -98,7 +97,6 @@ const { user, error } = await supabase
 
 </TabPanel>
 <TabPanel id="2.0x" label="After">
-{/* prettier-ignore */}
 ```ts
 const {
   data: { user },
@@ -128,7 +126,6 @@ const {
   defaultActiveId="1.0x"
 >
 <TabPanel id="1.0x" label="Before">
-{/* prettier-ignore */}
 ```ts
 const { error } = await supabase
   .auth
@@ -137,7 +134,6 @@ const { error } = await supabase
 
 </TabPanel>
 <TabPanel id="2.0x" label="After">
-{/* prettier-ignore */}
 ```ts
 const { error } = await supabase
   .auth
@@ -165,7 +161,6 @@ const { error } = await supabase
   defaultActiveId="1.0x"
 >
 <TabPanel id="1.0x" label="Before">
-{/* prettier-ignore */}
 ```ts
 const { error } = await supabase
   .auth
@@ -174,7 +169,6 @@ const { error } = await supabase
 
 </TabPanel>
 <TabPanel id="2.0x" label="After">
-{/* prettier-ignore */}
 ```ts
 const { error } = await supabase
   .auth
@@ -201,7 +195,6 @@ const { error } = await supabase
   defaultActiveId="1.0x"
 >
 <TabPanel id="1.0x" label="Before">
-{/* prettier-ignore */}
 ```ts
 const { error } = await supabase
   .auth
@@ -210,7 +203,6 @@ const { error } = await supabase
 
 </TabPanel>
 <TabPanel id="2.0x" label="After">
-{/* prettier-ignore */}
 ```ts
 const { error } = await supabase
   .auth
@@ -238,7 +230,6 @@ const { error } = await supabase
   defaultActiveId="1.0x"
 >
 <TabPanel id="1.0x" label="Before">
-{/* prettier-ignore */}
 ```ts
 const { error } = await supabase
   .auth
@@ -248,16 +239,15 @@ const { error } = await supabase
 
 </TabPanel>
 <TabPanel id="2.0x" label="After">
-{/* prettier-ignore */}
 ```ts
 const { data, error } = await supabase
   .auth
   .signInWithOtp({ phone })
-
+  
 // After receiving a SMS with a OTP.
 const { data, error } = await supabase
-.auth
-.verifyOtp({ phone, token })
+  .auth
+  .verifyOtp({ phone, token })
 ```
 
 </TabPanel>
@@ -281,7 +271,6 @@ const { data, error } = await supabase
   defaultActiveId="1.0x"
 >
 <TabPanel id="1.0x" label="Before">
-{/* prettier-ignore */}
 ```ts
 const { data, error } = await supabase
   .auth
@@ -291,7 +280,6 @@ const { data, error } = await supabase
 
 </TabPanel>
 <TabPanel id="2.0x" label="After">
-{/* prettier-ignore */}
 ```ts
 const { data, error } = await supabase
   .auth
@@ -390,7 +378,6 @@ const { user } = session
   defaultActiveId="1.0x"
 >
 <TabPanel id="1.0x" label="Before">
-{/* prettier-ignore */}
 ```ts
 const { user, error } = await supabase
   .auth
@@ -435,7 +422,6 @@ const { user, error } = supabase.auth.setAuth(access_token)
 
 </TabPanel>
 <TabPanel id="2.0x" label="After">
-{/* prettier-ignore */}
 ```ts
 const supabase = createClient(
   SUPABASE_URL,
@@ -486,7 +472,6 @@ Previously, these methods return inserted/updated/deleted rows by default (which
   defaultActiveId="1.0x"
 >
 <TabPanel id="1.0x" label="Before">
-{/* prettier-ignore */}
 ```ts
 const { data, error } = await supabase
   .from('my_table')
@@ -495,7 +480,6 @@ const { data, error } = await supabase
 
 </TabPanel>
 <TabPanel id="2.0x" label="After">
-{/* prettier-ignore */}
 ```ts
 const { data, error } = await supabase
   .from('my_table')
@@ -524,7 +508,6 @@ const { data, error } = await supabase
   defaultActiveId="1.0x"
 >
 <TabPanel id="1.0x" label="Before">
-{/* prettier-ignore */}
 ```ts
 const { data, error } = await supabase
   .from('my_table')
@@ -534,7 +517,6 @@ const { data, error } = await supabase
 
 </TabPanel>
 <TabPanel id="2.0x" label="After">
-{/* prettier-ignore */}
 ```ts
 const { data, error } = await supabase
   .from('my_table')
@@ -564,7 +546,6 @@ const { data, error } = await supabase
   defaultActiveId="1.0x"
 >
 <TabPanel id="1.0x" label="Before">
-{/* prettier-ignore */}
 ```ts
 const { data, error } = await supabase
   .from('my_table')
@@ -573,7 +554,6 @@ const { data, error } = await supabase
 
 </TabPanel>
 <TabPanel id="2.0x" label="After">
-{/* prettier-ignore */}
 ```ts
 const { data, error } = await supabase
   .from('my_table')
@@ -602,7 +582,6 @@ const { data, error } = await supabase
   defaultActiveId="1.0x"
 >
 <TabPanel id="1.0x" label="Before">
-{/* prettier-ignore */}
 ```ts
 const { data, error } = await supabase
   .from('my_table')
@@ -612,7 +591,6 @@ const { data, error } = await supabase
 
 </TabPanel>
 <TabPanel id="2.0x" label="After">
-{/* prettier-ignore */}
 ```ts
 const { data, error } = await supabase
   .from('my_table')
diff --git a/apps/docs/docs/ref/kotlin/installing.mdx b/apps/docs/docs/ref/kotlin/installing.mdx
new file mode 100644
index 00000000000..8d341ad0f63
--- /dev/null
+++ b/apps/docs/docs/ref/kotlin/installing.mdx
@@ -0,0 +1,268 @@
+---
+id: installing
+title: 'Installing & Initialization'
+slug: installing
+custom_edit_url: https://github.com/supabase/supabase/edit/master/web/spec/supabase.yml
+---
+
+### Add one or more modules to your project
+
+<RefSubLayout.EducationRow>
+    <RefSubLayout.Examples>
+        <div style={{ display: 'flex', flexDirection: 'row', alignItems: 'center' }}>
+            <a href="https://github.com/supabase-community/supabase-kt/releases" style={{ marginRight: '8px' }}>
+                <img src="https://img.shields.io/github/release/supabase-community/supabase-kt?label=stable" alt="latest stable supabase-kt version"/>
+            </a>
+            <a href="https://github.com/supabase-community/supabase-kt/releases">
+                <img src="https://img.shields.io/maven-central/v/io.github.jan-tennert.supabase/supabase-kt?label=experimental" alt="latest supabase-kt version"/>
+            </a>
+        </div>
+        Add dependency to your build file:
+        <Tabs
+            size="small"
+            type="underlined"
+            defaultActiveId="kotlin">
+            <TabPanel id="kotlin" label="build.gradle.kts">
+
+                ```kotlin
+                implementation("io.github.jan-tennert.supabase:[module]:VERSION")
+                ```
+
+            </TabPanel>
+            <TabPanel id="groovy" label="build.gradle">
+
+                ```groovy
+                implementation 'io.github.jan-tennert.supabase:[module]:VERSION'
+                ```
+
+            </TabPanel>
+            <TabPanel id="xml" label="pom.xml">
+
+                ```xml
+                <dependency>
+                    <groupId>io.github.jan-tennert.supabase</groupId>
+                    <artifactId>[module]</artifactId>
+                    <version>VERSION</version>
+                </dependency>
+                ```
+
+            </TabPanel>
+        </Tabs>
+
+        The available modules are: **gotrue-kt**, **realtime-kt**, **storage-kt**, **functions-kt**, **postgrest-kt** and **apollo-graphql**
+
+        When using multiple modules, you can also use the BOM dependency to ensure that all modules use the same version:
+
+        <Tabs
+            size="small"
+            type="underlined"
+            defaultActiveId="kotlin">
+            <TabPanel id="kotlin" label="build.gradle.kts">
+
+                ```kotlin
+                implementation(platform("io.github.jan-tennert.supabase:bom:VERSION"))
+                implementation("io.github.jan-tennert.supabase:postgrest-kt")
+                implementation("io.github.jan-tennert.supabase:realtime-kt")
+                ```
+
+            </TabPanel>
+            <TabPanel id="groovy" label="build.gradle">
+
+                ```groovy
+                implementation platform("io.github.jan-tennert.supabase:bom:VERSION")
+                implementation 'io.github.jan-tennert.supabase:postgrest-kt'
+                implementation 'io.github.jan-tennert.supabase:realtime-kt'
+                ```
+
+            </TabPanel>
+            <TabPanel id="xml" label="pom.xml">
+
+                ```xml
+                <dependency>
+                    <groupId>io.github.jan-tennert.supabase</groupId>
+                    <artifactId>bom</artifactId>
+                    <version>VERSION</version>
+                    <type>pom</type>
+                    <scope>import</scope>
+                </dependency>
+                <dependency>
+                    <groupId>io.github.jan-tennert.supabase</groupId>
+                    <artifactId>postgrest-kt</artifactId>
+                </dependency>
+                <dependency>
+                    <groupId>io.github.jan-tennert.supabase</groupId>
+                    <artifactId>realtime-kt</artifactId>
+                </dependency>
+                ```
+
+            </TabPanel>
+        </Tabs>
+
+    </RefSubLayout.Examples>
+
+</RefSubLayout.EducationRow>
+
+### Add Ktor Client Engine to each of your Kotlin targets (required)
+
+<RefSubLayout.EducationRow>
+    <RefSubLayout.Examples>
+
+        You can find a list of engines [here](https://ktor.io/docs/http-client-engines.html)
+
+        <Tabs
+            size="small"
+            type="underlined"
+            defaultActiveId="kotlin">
+            <TabPanel id="kotlin" label="build.gradle.kts">
+
+                ```kotlin
+                implementation("io.ktor:ktor-client-[engine]:KTOR_VERSION")
+                ```
+
+            </TabPanel>
+            <TabPanel id="groovy" label="build.gradle">
+
+                ```groovy
+                implementation 'io.ktor:ktor-client-[engine]:KTOR_VERSION'
+                ```
+
+            </TabPanel>
+            <TabPanel id="xml" label="pom.xml">
+
+                ```xml
+                <dependency>
+                    <groupId>io.ktor</groupId>
+                    <artifactId>ktor-client-[engine]</artifactId>
+                    <version>KTOR_VERSION</version>
+                </dependency>
+                ```
+
+            </TabPanel>
+        </Tabs>
+
+        Multiplatform example:
+
+        <Tabs
+            size="small"
+            type="underlined"
+            defaultActiveId="kotlin">
+            <TabPanel id="kotlin" label="build.gradle.kts">
+
+                ```kotlin
+                val commonMain by getting {
+                    dependencies {
+                        //supabase modules
+                    }
+                }
+                val jvmMain by getting {
+                    dependencies {
+                        implementation("io.ktor:ktor-client-cio:KTOR_VERSION")
+                    }
+                }
+                val androidMain by getting {
+                    dependsOn(jvmMain)
+                }
+                val jsMain by getting {
+                    dependencies {
+                        implementation("io.ktor:ktor-client-js:KTOR_VERSION")
+                    }
+                }
+                val iosMain by getting {
+                    dependencies {
+                        implementation("io.ktor:ktor-client-darwin:KTOR_VERSION")
+                    }
+                }
+                ```
+
+            </TabPanel>
+        </Tabs>
+
+    </RefSubLayout.Examples>
+
+</RefSubLayout.EducationRow>
+
+### Add KotlinX Serialization (required for PostgREST and Realtime serialization)
+
+<RefSubLayout.EducationRow>
+    <RefSubLayout.Examples>
+
+        Add the serialization plugin
+
+        <Tabs
+            size="small"
+            type="underlined"
+            defaultActiveId="kotlin">
+            <TabPanel id="kotlin" label="build.gradle.kts">
+
+                ```kotlin
+                plugins {
+                    kotlin("plugin.serialization") version "KOTLIN_VERSION"
+                }
+                ```
+
+            </TabPanel>
+            <TabPanel id="groovy" label="build.gradle">
+
+                ```groovy
+                plugins {
+                    id 'org.jetbrains.kotlin.plugin.serialization' version 'KOTLIN_VERSION'
+                }
+                ```
+
+            </TabPanel>
+            <TabPanel id="xml" label="pom.xml">
+
+                ```xml
+                <build>
+                    <plugins>
+                        <plugin>
+                            <groupId>org.jetbrains.kotlin</groupId>
+                            <artifactId>kotlin-maven-plugin</artifactId>
+                            <version>${kotlin.version}</version>
+                            <executions>
+                                <execution>
+                                    <id>compile</id>
+                                    <phase>compile</phase>
+                                    <goals>
+                                        <goal>compile</goal>
+                                    </goals>
+                                </execution>
+                            </executions>
+                            <configuration>
+                                <compilerPlugins>
+                                    <plugin>kotlinx-serialization</plugin>
+                                </compilerPlugins>
+                            </configuration>
+                            <dependencies>
+                                <dependency>
+                                    <groupId>org.jetbrains.kotlin</groupId>
+                                    <artifactId>kotlin-maven-serialization</artifactId>
+                                    <version>${kotlin.version}</version>
+                                </dependency>
+                            </dependencies>
+                        </plugin>
+                    </plugins>
+                </build>
+                ```
+
+            </TabPanel>
+        </Tabs>
+
+        Now you can create serializable classes in your project:
+        ```kotlin
+        @Serializable
+        data class Message(
+            val id: Int,
+            val content: String,
+            @SerialName("author_id")
+            val authorId: String
+        )
+        ```
+        And use them in your Supabase queries:
+        ```kotlin
+        val messages = client.postgrest["messages"].select().decodeList<Message>()
+        ```
+
+    </RefSubLayout.Examples>
+
+</RefSubLayout.EducationRow>
diff --git a/apps/docs/docs/ref/kotlin/introduction.mdx b/apps/docs/docs/ref/kotlin/introduction.mdx
new file mode 100644
index 00000000000..36be6dd7a89
--- /dev/null
+++ b/apps/docs/docs/ref/kotlin/introduction.mdx
@@ -0,0 +1,33 @@
+---
+id: introduction
+title: Introduction
+hideTitle: true
+---
+
+<div className="flex items-start gap-6 not-prose" id="introduction">
+  <IconMenuKotlin width={35} height={35} />
+  <div className="flex flex-col gap-2">
+    <h1 className="text-3xl text-scale-1200 m-0">Kotlin Client Library</h1>
+    <h2 className="text-base font-mono text-scale-1100">@supabase-community/supabase-kt</h2>
+  </div>
+</div>
+
+<div className="max-w-xl">
+
+This reference documents every object and method available in Supabase's Kotlin Multiplatform library, [supabase-kt](https://github.com/supabase-community/supabase-kt). You can use supabase-kt to interact with your Postgres database, listen to database changes, invoke Deno Edge Functions, build login and user management functionality, and manage large files.
+
+Supported Kotlin targets:
+
+- JVM
+- Android
+- iOS (Experimental)
+- JS (Browser)
+
+</div>
+
+<div className="max-w-xl bg-slate-300 px-4 py-2 rounded-md">
+  <p>The Kotlin client library is created and maintained by the Supabase community, and is not an official library. Please be tolerant of areas where the library is still being developed, and — as with all the libraries — feel free to contribute wherever you find issues.</p>
+
+<p>Huge thanks to official maintainer, [jan-tennert](https://github.com/jan-tennert).</p>
+
+</div>
diff --git a/apps/docs/docs/ref/self-hosting-auth/introduction.mdx b/apps/docs/docs/ref/self-hosting-auth/introduction.mdx
index d33aee3de4f..0fe820ce9b3 100644
--- a/apps/docs/docs/ref/self-hosting-auth/introduction.mdx
+++ b/apps/docs/docs/ref/self-hosting-auth/introduction.mdx
@@ -14,9 +14,9 @@ hideTitle: true
 <RefSubLayout.EducationRow>
   <RefSubLayout.Details>
 
-  The Supabase Auth Server (GoTrue) is a JSON Web Token (JWT)-based API for managing users and issuing access tokens.
+    The Supabase Auth Server (GoTrue) is a JSON Web Token (JWT)-based API for managing users and issuing access tokens.
 
-  GoTrue is an open-source API written in Golang, that acts as a self-standing API service for handling user registration and authentication for JAM projects. It's based on OAuth2 and JWT and handles user signup, authentication, and custom user data.
+    GoTrue is an open-source API written in Golang, that acts as a self-standing API service for handling user registration and authentication for JAM projects. It's based on OAuth2 and JWT and handles user signup, authentication, and custom user data.
 
   </RefSubLayout.Details>
 
diff --git a/apps/docs/docs/ref/self-hosting-storage/introduction.mdx b/apps/docs/docs/ref/self-hosting-storage/introduction.mdx
index 40fd27d4ce8..150820d09b2 100644
--- a/apps/docs/docs/ref/self-hosting-storage/introduction.mdx
+++ b/apps/docs/docs/ref/self-hosting-storage/introduction.mdx
@@ -14,12 +14,12 @@ hideTitle: true
 <RefSubLayout.EducationRow>
   <RefSubLayout.Details>
 
-  An S3 compatible object storage service that integrates with Postgres.
+    An S3 compatible object storage service that integrates with Postgres.
 
-  - Uses Postgres as it's datastore for storing metadata
-  - Authorization rules are written as Postgres Row Level Security policies
-  - Integrates with S3 as the storage backend (with more in the pipeline!)
-  - Extremely lightweight and performant
+    - Uses Postgres as it's datastore for storing metadata
+    - Authorization rules are written as Postgres Row Level Security policies
+    - Integrates with S3 as the storage backend (with more in the pipeline!)
+    - Extremely lightweight and performant
 
   </RefSubLayout.Details>
 
diff --git a/apps/docs/docs/ref/swift/introduction.mdx b/apps/docs/docs/ref/swift/introduction.mdx
index 475ae7f8a03..0d08cbed84f 100644
--- a/apps/docs/docs/ref/swift/introduction.mdx
+++ b/apps/docs/docs/ref/swift/introduction.mdx
@@ -13,9 +13,9 @@ hideTitle: true
 </div>
 
 <div className="max-w-xl">
-This reference documents every object and method available in Supabase's Swift library, [supabase-swift](https://github.com/supabase-community/supabase-swift). You can use supabase-swift to interact with your Postgres database, listen to database changes, invoke Deno Edge Functions, build login and user management functionality, and manage large files.
+This reference documents every object and method available in Supabase's Swift library, [supabase-swift](https://github.com/supabase-community/supabase-swift). You can use supabase-swift to interact with your Postgres database, listen to database changes, invoke Deno Edge Functions, build login and user management functionality, and manage large files.
 
-We also provide a [supabase](https://pub.dev/packages/supabase) package for non-Swift projects.
+We also provide a [supabase](https://pub.dev/packages/supabase) package for non-Swift projects.
 
 </div>
 
diff --git a/apps/docs/docs/reference/dart/initializing.mdx b/apps/docs/docs/reference/dart/initializing.mdx
index 7d914d71efd..ba76c217cce 100644
--- a/apps/docs/docs/reference/dart/initializing.mdx
+++ b/apps/docs/docs/reference/dart/initializing.mdx
@@ -4,9 +4,6 @@ title: 'Initializing'
 slug: initializing
 ---
 
-import Tabs from '@theme/Tabs'
-import TabItem from '@theme/TabItem'
-
 ## Flutter
 
 For `supabase-flutter`, you will be using the static `initialize()` method on `Supabase` class.
@@ -30,8 +27,9 @@ final supabase = Supabase.instance.client;
 
 ### Call `initialize()` with custom headers
 
-You can pass `headers` to initialize your Supabase client with customer headers. 
+You can pass `headers` to initialize your Supabase client with customer headers.
 Here is an example of passing a custom auth header to Supabase client.
+
 ```dart title=main.dart
 Future<void> main() async {
   await Supabase.initialize(
diff --git a/apps/docs/docs/reference/dart/installing.mdx b/apps/docs/docs/reference/dart/installing.mdx
index 49822681a67..5565c145a91 100644
--- a/apps/docs/docs/reference/dart/installing.mdx
+++ b/apps/docs/docs/reference/dart/installing.mdx
@@ -4,9 +4,6 @@ title: 'Installing'
 slug: installing
 ---
 
-import Tabs from '@theme/Tabs'
-import TabItem from '@theme/TabItem'
-
 ## Flutter
 
 For Flutter project, you can use [supabase_flutter](https://pub.dev/packages/supabase_flutter) package.
diff --git a/apps/docs/docs/reference/javascript/v1/generating-types.mdx b/apps/docs/docs/reference/javascript/v1/generating-types.mdx
index a46fd7ba70d..8878f4c1911 100644
--- a/apps/docs/docs/reference/javascript/v1/generating-types.mdx
+++ b/apps/docs/docs/reference/javascript/v1/generating-types.mdx
@@ -5,9 +5,6 @@ slug: generating-types
 custom_edit_url: https://github.com/supabase/supabase/edit/master/spec/supabase_js_v1.yml
 ---
 
-import Tabs from '@theme/Tabs'
-import TabItem from '@theme/TabItem'
-
 Supabase will soon release native type generators that dump your database types for various languages. For now, we support TypeScript [through third-party tools](/docs/guides/database/api/generating-types).
 
 ## Usage with TypeScript
diff --git a/apps/docs/docs/reference/javascript/v1/initializing.mdx b/apps/docs/docs/reference/javascript/v1/initializing.mdx
index 7ea5f5cf164..5672bd80f57 100644
--- a/apps/docs/docs/reference/javascript/v1/initializing.mdx
+++ b/apps/docs/docs/reference/javascript/v1/initializing.mdx
@@ -5,9 +5,6 @@ slug: initializing
 custom_edit_url: https://github.com/supabase/supabase/edit/master/spec/supabase_js_v1.yml
 ---
 
-import Tabs from '@theme/Tabs'
-import TabItem from '@theme/TabItem'
-
 You can initialize a new Supabase client using the `createClient()` method.
 
 The Supabase client is your entrypoint to the rest of the Supabase functionality
@@ -117,7 +114,7 @@ const supabase = createClient('https://xyzcompany.supabase.co', 'public-anon-key
 ```
 
 By default the API server points to the `public` schema. You can enable other database schemas within the Dashboard.
-Go to `Settings > API > Schema` and add the schema which you want to expose to the API. You also need to grant `USAGE` on your new schema with the grants you desire, such as `SELECT, INSERT, UPDATE, DELETE`. 
+Go to `Settings > API > Schema` and add the schema which you want to expose to the API. You also need to grant `USAGE` on your new schema with the grants you desire, such as `SELECT, INSERT, UPDATE, DELETE`.
 
 Note: each client connection can only access a single schema, so the code above can access the `other_schema` schema but cannot access the `public` schema.
 
diff --git a/apps/docs/docs/reference/javascript/v1/installing.mdx b/apps/docs/docs/reference/javascript/v1/installing.mdx
index 4441c7253d7..e6e3abb6151 100644
--- a/apps/docs/docs/reference/javascript/v1/installing.mdx
+++ b/apps/docs/docs/reference/javascript/v1/installing.mdx
@@ -5,9 +5,6 @@ slug: installing
 custom_edit_url: https://github.com/supabase/supabase/edit/master/spec/supabase_js_v1.yml
 ---
 
-import Tabs from '@theme/Tabs'
-import TabItem from '@theme/TabItem'
-
 All JavaScript libraries are built directly by the Supabase team.
 
 Other languages are built by the community and supported by Supabase.
diff --git a/apps/docs/docs/reference/postgres/changing-timezones.mdx b/apps/docs/docs/reference/postgres/changing-timezones.mdx
index d05e32afc8b..e836b1bf252 100644
--- a/apps/docs/docs/reference/postgres/changing-timezones.mdx
+++ b/apps/docs/docs/reference/postgres/changing-timezones.mdx
@@ -1,16 +1,12 @@
 ---
 id: changing-timezones
-title: "Changing Timezones"
+title: 'Changing Timezones'
 slug: changing-timezones
 custom_edit_url: https://github.com/supabase/supabase/edit/master/web/spec/postgres.yml
 ---
 
-import Tabs from '@theme/Tabs';
-import TabsPanel from '@theme/TabsPanel';
-
 Data types.
 
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -19,38 +15,22 @@ Data types.
 <TabsPanel id="sql" label="sql">
 
 ```sql
-alter database postgres 
+alter database postgres
 set timezone to 'America/New_York';
 ```
 
-
 </TabsPanel>
 
 </Tabs>
 
-
-
-
-
 ## Notes
 
 - View a full list of timezones on [Wikipedia](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
 
-
-
-
-
-
-
-
-
-
 ## Examples
 
 ### Change timezone
 
-
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -59,11 +39,10 @@ set timezone to 'America/New_York';
 <TabsPanel id="sql" label="sql">
 
 ```sql
-alter database postgres 
+alter database postgres
 set timezone to 'America/New_York';
 ```
 
-
 </TabsPanel>
 
 </Tabs>
@@ -77,7 +56,6 @@ Get a full list of timezones supported by your database. This will return the fo
 - `utc_offset`: Offset from UTC (positive means east of Greenwich)
 - `is_dst`: True if currently observing daylight savings
 
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -87,11 +65,10 @@ Get a full list of timezones supported by your database. This will return the fo
 
 ```sql
 select name, abbrev, utc_offset, is_dst
-from pg_timezone_names() 
+from pg_timezone_names()
 order by name;
 ```
 
-
 </TabsPanel>
 
 </Tabs>
@@ -108,12 +85,11 @@ Use `ilike` (case insensitive search) to find specific timezones.
 <TabsPanel id="sql" label="sql">
 
 ```sql
-select * 
-from pg_timezone_names() 
+select *
+from pg_timezone_names()
 where name ilike '%york%';
 ```
 
-
 </TabsPanel>
 
-</Tabs>
\ No newline at end of file
+</Tabs>
diff --git a/apps/docs/docs/reference/postgres/columns.mdx b/apps/docs/docs/reference/postgres/columns.mdx
index 0ccaa830381..8ec74a21db2 100644
--- a/apps/docs/docs/reference/postgres/columns.mdx
+++ b/apps/docs/docs/reference/postgres/columns.mdx
@@ -1,16 +1,12 @@
 ---
 id: columns
-title: "Columns"
+title: 'Columns'
 slug: columns
 custom_edit_url: https://github.com/supabase/supabase/edit/master/web/spec/postgres.yml
 ---
 
-import Tabs from '@theme/Tabs';
-import TabsPanel from '@theme/TabsPanel';
-
 Creating columns.
 
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -26,33 +22,14 @@ create table table_name (
 );
 ```
 
-
 </TabsPanel>
 
 </Tabs>
 
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
 ## Examples
 
 ### During table creation
 
-
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -68,15 +45,12 @@ create table table_name (
 );
 ```
 
-
 </TabsPanel>
 
 </Tabs>
 
 ### Create column
 
-
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -89,7 +63,6 @@ alter table new_table
 add new_column text;
 ```
 
-
 </TabsPanel>
 
-</Tabs>
\ No newline at end of file
+</Tabs>
diff --git a/apps/docs/docs/reference/postgres/connection-strings.mdx b/apps/docs/docs/reference/postgres/connection-strings.mdx
index 12e4f919c9c..4d7a60ae516 100644
--- a/apps/docs/docs/reference/postgres/connection-strings.mdx
+++ b/apps/docs/docs/reference/postgres/connection-strings.mdx
@@ -1,16 +1,12 @@
 ---
 id: connection-strings
-title: "Connection Strings"
+title: 'Connection Strings'
 slug: connection-strings
 custom_edit_url: https://github.com/supabase/supabase/edit/master/web/spec/postgres.yml
 ---
 
-import Tabs from '@theme/Tabs';
-import TabsPanel from '@theme/TabsPanel';
-
 There are various ways to connect to your database, depending on the configuration of your Postgres instance and the tool which you are connecting with.
 
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -20,42 +16,27 @@ There are various ways to connect to your database, depending on the configurati
 
 ```bash
 postgres://postgres:postgres@localhost:5432/postgres
-# or 
+# or
 postgresql://postgres:postgres@localhost:5432/postgres
 ```
 
-
 </TabsPanel>
 
 </Tabs>
 
-
-
-
-
 ## Notes
 
 - [Official Documentation](https://www.postgresql.org/docs/current/libpq-connect.html).
 - Avoid using special characters usernames and passwords. If you use special characters in a connection URL, you'll need to URL encode any special characters.
 
-
-
-
-
-
-
-
-
-
 ## Examples
 
 ### Basic connection string
 
-If you're using a default setup, your postgres connection string will likely be in the format: 
+If you're using a default setup, your postgres connection string will likely be in the format:
 
 `postgres://{user}:{password}@{host}:{port}/{database_name}`
 
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -65,11 +46,10 @@ If you're using a default setup, your postgres connection string will likely be
 
 ```bash
 postgres://postgres:postgres@localhost:5432/postgres
-# or 
+# or
 postgresql://postgres:postgres@localhost:5432/postgres
 ```
 
-
 </TabsPanel>
 
 </Tabs>
@@ -89,7 +69,6 @@ See full [documentation](http://jdbc.postgresql.org/documentation/head/connect.h
 jdbc:postgresql://{host}:{port}/{database_name}
 ```
 
-
 </TabsPanel>
 
 </Tabs>
@@ -109,7 +88,6 @@ See full [documentation](http://npgsql.projects.postgresql.org/docs/manual/UserM
 Server=host;Port=5432;User Id=username;Password=secret;Database=database_name;
 ```
 
-
 </TabsPanel>
 
 </Tabs>
@@ -129,7 +107,6 @@ See full [documentation](http://php.net/manual/en/book.pgsql.php).
 host=hostname port=5432 dbname=databasename user=username password=secret
 ```
 
-
 </TabsPanel>
 
-</Tabs>
\ No newline at end of file
+</Tabs>
diff --git a/apps/docs/docs/reference/postgres/database-passwords.mdx b/apps/docs/docs/reference/postgres/database-passwords.mdx
index 9f58234b1a1..4cc8ec9fa8e 100644
--- a/apps/docs/docs/reference/postgres/database-passwords.mdx
+++ b/apps/docs/docs/reference/postgres/database-passwords.mdx
@@ -1,40 +1,16 @@
 ---
 id: database-passwords
-title: "Database Passwords"
+title: 'Database Passwords'
 slug: database-passwords
 custom_edit_url: https://github.com/supabase/supabase/edit/master/web/spec/postgres.yml
 ---
 
-import Tabs from '@theme/Tabs';
-import TabsPanel from '@theme/TabsPanel';
-
 Manage the passwords of your database users using any super user.
 
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
 ## Examples
 
 ### Password reset
 
-
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -43,11 +19,10 @@ Manage the passwords of your database users using any super user.
 <TabsPanel id="sql" label="sql">
 
 ```sql
-alter user postgres 
+alter user postgres
 with password 'new_password';
 ```
 
-
 </TabsPanel>
 
-</Tabs>
\ No newline at end of file
+</Tabs>
diff --git a/apps/docs/docs/reference/postgres/database-users.mdx b/apps/docs/docs/reference/postgres/database-users.mdx
index 8ccca2ce94a..d13e8621679 100644
--- a/apps/docs/docs/reference/postgres/database-users.mdx
+++ b/apps/docs/docs/reference/postgres/database-users.mdx
@@ -1,40 +1,16 @@
 ---
 id: database-users
-title: "Database Users"
+title: 'Database Users'
 slug: database-users
 custom_edit_url: https://github.com/supabase/supabase/edit/master/web/spec/postgres.yml
 ---
 
-import Tabs from '@theme/Tabs';
-import TabsPanel from '@theme/TabsPanel';
-
 Users and Roles are almost interchangeable.
 
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
 ## Examples
 
 ### Create New User
 
-
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -47,7 +23,6 @@ create user new_user
 with password 'hello';
 ```
 
-
 </TabsPanel>
 
-</Tabs>
\ No newline at end of file
+</Tabs>
diff --git a/apps/docs/docs/reference/postgres/index.mdx b/apps/docs/docs/reference/postgres/index.mdx
index b6641472785..5d4e2e7a731 100644
--- a/apps/docs/docs/reference/postgres/index.mdx
+++ b/apps/docs/docs/reference/postgres/index.mdx
@@ -1,15 +1,11 @@
 ---
 id: index
-title: "Getting started"
+title: 'Getting started'
 slug: getting-started
 custom_edit_url: https://github.com/supabase/supabase/edit/master/web/spec/postgres.yml
 ---
 
-import Tabs from '@theme/Tabs';
-import TabsPanel from '@theme/TabsPanel';
-
-
-PostgreSQL, also known as Postgres, is a free and open-source relational 
-database management system emphasizing extensibility and SQL compliance. 
-It was originally named POSTGRES, referring to its origins as a successor 
-to the Ingres database developed at the University of California, Berkeley.
\ No newline at end of file
+PostgreSQL, also known as Postgres, is a free and open-source relational
+database management system emphasizing extensibility and SQL compliance.
+It was originally named POSTGRES, referring to its origins as a successor
+to the Ingres database developed at the University of California, Berkeley.
diff --git a/apps/docs/docs/reference/postgres/publications.mdx b/apps/docs/docs/reference/postgres/publications.mdx
index 87559a38e34..aabcc783c99 100644
--- a/apps/docs/docs/reference/postgres/publications.mdx
+++ b/apps/docs/docs/reference/postgres/publications.mdx
@@ -1,42 +1,19 @@
 ---
 id: publications
-title: "Publications"
+title: 'Publications'
 slug: publications
 custom_edit_url: https://github.com/supabase/supabase/edit/master/web/spec/postgres.yml
 ---
 
-import Tabs from '@theme/Tabs';
-import TabsPanel from '@theme/TabsPanel';
-
-Publications are a way of grouping changes generated from a table or a group of tables. 
+Publications are a way of grouping changes generated from a table or a group of tables.
 These changes can then be sent to other systems (usually another Postgres database).
 
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
 ## Examples
 
 ### Create a Publication
 
 This publication will contain all changes to all tables.
 
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -45,19 +22,16 @@ This publication will contain all changes to all tables.
 <TabsPanel id="sql" label="sql">
 
 ```sql
-create publication publication_name 
+create publication publication_name
 for all tables;
 ```
 
-
 </TabsPanel>
 
 </Tabs>
 
 ### Create a Publication which listens to individual tables
 
-
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -66,19 +40,16 @@ for all tables;
 <TabsPanel id="sql" label="sql">
 
 ```sql
-create publication publication_name 
+create publication publication_name
 for table table_one, table_two;
 ```
 
-
 </TabsPanel>
 
 </Tabs>
 
 ### Add tables to an existing publication
 
-
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -87,19 +58,16 @@ for table table_one, table_two;
 <TabsPanel id="sql" label="sql">
 
 ```sql
-alter publication publication_name 
+alter publication publication_name
 add table table_name;
 ```
 
-
 </TabsPanel>
 
 </Tabs>
 
 ### Listens to inserts only
 
-
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -108,20 +76,17 @@ add table table_name;
 <TabsPanel id="sql" label="sql">
 
 ```sql
-create publication publication_name 
+create publication publication_name
 for all tables
 with (publish = 'insert');
 ```
 
-
 </TabsPanel>
 
 </Tabs>
 
 ### Listens to updates only
 
-
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -130,20 +95,17 @@ with (publish = 'insert');
 <TabsPanel id="sql" label="sql">
 
 ```sql
-create publication publication_name 
+create publication publication_name
 for all tables
 with (publish = 'update');
 ```
 
-
 </TabsPanel>
 
 </Tabs>
 
 ### Listens to deletions only
 
-
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -152,20 +114,17 @@ with (publish = 'update');
 <TabsPanel id="sql" label="sql">
 
 ```sql
-create publication publication_name 
+create publication publication_name
 for all tables
 with (publish = 'delete');
 ```
 
-
 </TabsPanel>
 
 </Tabs>
 
 ### Remove a Publication
 
-
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -177,7 +136,6 @@ with (publish = 'delete');
 drop publication if exists publication_name;
 ```
 
-
 </TabsPanel>
 
 </Tabs>
@@ -186,7 +144,6 @@ drop publication if exists publication_name;
 
 If you are planning to re-create a publication, it's best to do it in a transaction to ensure the operation succeeds.
 
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -195,16 +152,15 @@ If you are planning to re-create a publication, it's best to do it in a transact
 <TabsPanel id="sql" label="sql">
 
 ```sql
-begin; 
+begin;
   -- remove the realtime publication
-  drop publication if exists publication_name; 
+  drop publication if exists publication_name;
 
   -- re-create the publication but don't enable it for any tables
-  create publication publication_name;  
+  create publication publication_name;
 commit;
 ```
 
-
 </TabsPanel>
 
-</Tabs>
\ No newline at end of file
+</Tabs>
diff --git a/apps/docs/docs/reference/postgres/schemas.mdx b/apps/docs/docs/reference/postgres/schemas.mdx
index ad4fbf6d9ef..7b77f396b41 100644
--- a/apps/docs/docs/reference/postgres/schemas.mdx
+++ b/apps/docs/docs/reference/postgres/schemas.mdx
@@ -1,19 +1,15 @@
 ---
 id: schemas
-title: "Schemas"
+title: 'Schemas'
 slug: schemas
 custom_edit_url: https://github.com/supabase/supabase/edit/master/web/spec/postgres.yml
 ---
 
-import Tabs from '@theme/Tabs';
-import TabsPanel from '@theme/TabsPanel';
+Schemas are like "folders". They help to keep your database organized.
 
-Schemas are like "folders". They help to keep your database organized. 
-
-Schemas are particularly useful for security. You can set different permissions on each schema. 
+Schemas are particularly useful for security. You can set different permissions on each schema.
 For example, you might want to use a `public` schema for user-facing data, and an `auth` schema for all logins and secured data.
 
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -25,36 +21,20 @@ For example, you might want to use a `public` schema for user-facing data, and a
 create schema schema_name;
 ```
 
-
 </TabsPanel>
 
 </Tabs>
 
-
-
-
-
 ## Notes
 
 - Schemas contain [tables](/docs/reference/postgres/tables), columns, triggers, functions, etc.
 - Postgres comes with a `public` schema set up by default.
 - It is best practice to use lowercase and underscores when naming schemas. For example: `schema_name`, not `Schema Name`.
 
-
-
-
-
-
-
-
-
-
 ## Examples
 
 ### Creating a schema
 
-
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -66,15 +46,12 @@ create schema schema_name;
 create schema schema_name;
 ```
 
-
 </TabsPanel>
 
 </Tabs>
 
 ### Removing a schema
 
-
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -86,7 +63,6 @@ create schema schema_name;
 drop schema if exists schema_name;
 ```
 
-
 </TabsPanel>
 
 </Tabs>
@@ -96,7 +72,6 @@ drop schema if exists schema_name;
 Although it's not recommended, you can use uppercase and spaces when naming your schema by wrapping the name with double-quotes.
 As a result, you will always need to use double-quotes when referencing your schema.
 
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -108,7 +83,6 @@ As a result, you will always need to use double-quotes when referencing your sch
 create schema "Schema Name";
 ```
 
-
 </TabsPanel>
 
-</Tabs>
\ No newline at end of file
+</Tabs>
diff --git a/apps/docs/docs/reference/postgres/tables.mdx b/apps/docs/docs/reference/postgres/tables.mdx
index 05df802a961..ad95ca5fda1 100644
--- a/apps/docs/docs/reference/postgres/tables.mdx
+++ b/apps/docs/docs/reference/postgres/tables.mdx
@@ -1,19 +1,15 @@
 ---
 id: tables
-title: "Tables"
+title: 'Tables'
 slug: tables
 custom_edit_url: https://github.com/supabase/supabase/edit/master/web/spec/postgres.yml
 ---
 
-import Tabs from '@theme/Tabs';
-import TabsPanel from '@theme/TabsPanel';
-
 Tables are similar to excel spreadsheets. They contain columns & rows of data. There are a few key differences from a spreadsheet however:
 
 - Every column is a strict type of data. When you set up a column, you must define what "data type" it is.
 - Tables can be joined together through relationships. For example you can have a "users" table, which is joined to a "teams" table.
 
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -28,7 +24,7 @@ create table table_name (
   name text
 );
 
-# with schema 
+# with schema
 create table schema_name.table_name (
   id integer primary key,
   data jsonb,
@@ -36,36 +32,20 @@ create table schema_name.table_name (
 );
 ```
 
-
 </TabsPanel>
 
 </Tabs>
 
-
-
-
-
 ## Notes
 
-- Tables contain columns, rows, triggers, comments, 
+- Tables contain columns, rows, triggers, comments,
 - It is best practice to use lowercase and underscores when naming tables. For example: `table_name`, not `Table Name`.
 - Tables belong to [schemas](/docs/reference/postgres/schemas). If you don't explicitly pass the schema, Postgres will assume that you want to create the table in the `public` schema.
 
-
-
-
-
-
-
-
-
-
 ## Examples
 
 ### Create table
 
-
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -80,7 +60,7 @@ create table table_name (
   name text
 );
 
-# with schema 
+# with schema
 create table schema_name.table_name (
   id integer primary key,
   data jsonb,
@@ -88,15 +68,12 @@ create table schema_name.table_name (
 );
 ```
 
-
 </TabsPanel>
 
 </Tabs>
 
 ### Primary keys using multiple columns
 
-
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -113,15 +90,12 @@ create table table_name (
 );
 ```
 
-
 </TabsPanel>
 
 </Tabs>
 
 ### Multiple foreign keys to the same table
 
-
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -135,15 +109,12 @@ alter table table_name
   add constraint constraint_name_2 foreign key (column_2) references foreign_table(id);
 ```
 
-
 </TabsPanel>
 
 </Tabs>
 
 ### Delete a table
 
-
-
 <Tabs
   defaultActiveId="sql"
   groupId="reference/postgres"
@@ -155,7 +126,6 @@ alter table table_name
 delete table if exists table_name;
 ```
 
-
 </TabsPanel>
 
-</Tabs>
\ No newline at end of file
+</Tabs>
diff --git a/apps/docs/internals/files/reference-lib.mjs b/apps/docs/internals/files/reference-lib.mjs
index 8c410770fca..71c6c3bc368 100644
--- a/apps/docs/internals/files/reference-lib.mjs
+++ b/apps/docs/internals/files/reference-lib.mjs
@@ -12,6 +12,7 @@ const clientLibFiles = [
   { fileName: 'supabase_py_v2', label: 'python', version: 'v2', versionSlug: false },
   { fileName: 'supabase_csharp_v0', label: 'csharp', version: 'v0', versionSlug: false },
   { fileName: 'supabase_swift_v0', label: 'swift', version: 'v0', versionSlug: false },
+  { fileName: 'supabase_kt_v0', label: 'kotlin', version: 'v0', versionSlug: false },
 ]
 
 export function generateReferencePages() {
diff --git a/apps/docs/layouts/DefaultLayout.tsx b/apps/docs/layouts/DefaultLayout.tsx
index f1c5de485b0..bc1afe6fc95 100644
--- a/apps/docs/layouts/DefaultLayout.tsx
+++ b/apps/docs/layouts/DefaultLayout.tsx
@@ -12,6 +12,7 @@ interface Props {
     description?: string
     hide_table_of_contents?: boolean
     video?: string
+    tocVideo?: string
     canonical?: string
   }
   children: any
diff --git a/apps/docs/layouts/SiteLayout.tsx b/apps/docs/layouts/SiteLayout.tsx
index bada86f1d6c..ff35c1af441 100644
--- a/apps/docs/layouts/SiteLayout.tsx
+++ b/apps/docs/layouts/SiteLayout.tsx
@@ -94,6 +94,10 @@ const levelsData = {
     icon: '/docs/img/icons/menu/reference-swift',
     name: 'Swift Reference v1.0',
   },
+  reference_kotlin_v0: {
+    icon: '/docs/img/icons/menu/reference-kotlin',
+    name: 'Kotlin Reference v0.0',
+  },
   reference_cli: {
     icon: '/docs/img/icons/menu/reference-cli',
     name: 'CLI Reference',
@@ -197,7 +201,7 @@ const MobileMenuBackdrop = memo(function MobileMenuBackdrop() {
         'left-0',
         'right-0',
         'z-10',
-        'backdrop-blur-sm backdrop-filter bg-white-1200 dark:bg-blackA-600',
+        'backdrop-blur-sm backdrop-filter bg-white-1200 dark:bg-scale-200/90',
         mobileMenuOpen ? 'absolute h-full w-full top-0 left-0' : 'hidden h-0',
         // always hide on desktop
         'lg:hidden',
@@ -272,7 +276,7 @@ const NavContainer = memo(function NavContainer() {
           'relative',
           'w-auto',
           'border-r overflow-auto h-screen',
-          'backdrop-blur backdrop-filter bg-white-1200 dark:bg-blackA-300',
+          'backdrop-blur backdrop-filter bg-white-1200 dark:bg-scale-200',
           'flex flex-col',
         ].join(' ')}
       >
@@ -328,7 +332,7 @@ const SiteLayout = ({ children }: PropsWithChildren<{}>) => {
               className={[
                 'sticky transition-all top-0',
                 'z-10',
-                'backdrop-blur backdrop-filter bg-white-1200 dark:bg-blackA-300',
+                'backdrop-blur backdrop-filter bg-white-1200 dark:bg-scale-200',
               ].join(' ')}
             >
               <div className={['lg:hidden', 'px-5 ', 'border-b z-10'].join(' ')}>
diff --git a/apps/docs/layouts/guides/index.tsx b/apps/docs/layouts/guides/index.tsx
index c4ccfad09f3..4c54d701bfe 100644
--- a/apps/docs/layouts/guides/index.tsx
+++ b/apps/docs/layouts/guides/index.tsx
@@ -5,6 +5,7 @@ import Link from 'next/link'
 import { useRouter } from 'next/router'
 import { FC, useEffect, useRef, useState } from 'react'
 import { IconExternalLink } from 'ui'
+import ExpandableVideo from 'ui/src/components/ExpandableVideo/ExpandableVideo'
 import components from '~/components'
 import { highlightSelectedTocItem } from '~/components/CustomHTMLElements/CustomHTMLElements.utils'
 import FooterHelpCallout, { FooterHelpCalloutType } from '~/components/FooterHelpCallout'
@@ -21,6 +22,7 @@ interface Props {
     subtitle?: string
     footerHelpType?: FooterHelpCalloutType
     video?: string
+    tocVideo?: string
     canonical?: string
   }
   children: any
@@ -36,7 +38,6 @@ const Layout: FC<Props> = (props) => {
   const [tocList, setTocList] = useState([])
 
   const { asPath } = useRouter()
-
   const router = useRouter()
 
   const EDIT_BUTTON_EXCLUDE_LIST = ['/404']
@@ -64,6 +65,7 @@ const Layout: FC<Props> = (props) => {
   }, [])
 
   const hasTableOfContents = tocList.length > 0
+  const tocVideoPreview = `http://img.youtube.com/vi/${props.meta.tocVideo}/0.jpg`
 
   // page type, ie, Auth, Database, Storage etc
   const ogPageType = asPath.split('/')[2]
diff --git a/apps/docs/layouts/tutorials/TutorialLayout.tsx b/apps/docs/layouts/tutorials/TutorialLayout.tsx
index ba3ffe68f6e..47557e96b1b 100644
--- a/apps/docs/layouts/tutorials/TutorialLayout.tsx
+++ b/apps/docs/layouts/tutorials/TutorialLayout.tsx
@@ -6,7 +6,13 @@ import SideBar from '~/components/Navigation/SideBar'
 import TableOfContents from '~/components/TableOfContents'
 
 interface Props {
-  meta: { title: string; description?: string; hide_table_of_contents?: boolean; video?: string }
+  meta: {
+    title: string
+    description?: string
+    hide_table_of_contents?: boolean
+    video?: string
+    tocVideo?: string
+  }
   children: any
   toc?: any
   menuItems: any
diff --git a/apps/docs/lib/mdx/handleRefStaticPaths.tsx b/apps/docs/lib/mdx/handleRefStaticPaths.tsx
index ae7aeb1e3b4..f458f4f3e8b 100644
--- a/apps/docs/lib/mdx/handleRefStaticPaths.tsx
+++ b/apps/docs/lib/mdx/handleRefStaticPaths.tsx
@@ -1,14 +1,11 @@
 import { ICommonSection } from '~/components/reference/Reference.types'
 
-async function handleRefGetStaticPaths(sections: ICommonSection[], libraryPath: string) {
+async function handleRefGetStaticPaths(sections: ICommonSection[]) {
   return {
     paths: sections.map((section) => {
       return {
         params: {
-          slug: libraryPath
-            .split('/')
-            .filter((dir) => !!dir)
-            .concat(section.slug),
+          slug: [section.slug],
         },
       }
     }),
diff --git a/apps/docs/next.config.mjs b/apps/docs/next.config.mjs
index 5f38a0d35c6..47fe88b4ffa 100644
--- a/apps/docs/next.config.mjs
+++ b/apps/docs/next.config.mjs
@@ -60,6 +60,7 @@ const nextConfig = {
       'user-images.githubusercontent.com',
       'raw.githubusercontent.com',
       'weweb-changelog.ghost.io',
+      'img.youtube.com',
     ],
   },
   experimental: {
diff --git a/apps/docs/pages/guides/api.mdx b/apps/docs/pages/guides/api.mdx
index 3b518ced47b..390dcadd33d 100644
--- a/apps/docs/pages/guides/api.mdx
+++ b/apps/docs/pages/guides/api.mdx
@@ -32,6 +32,7 @@ Supabase provides a RESTful API using [PostgREST](https://postgrest.org/). This
 It provides everything you need from a CRUD API at the URL `https://<project_ref>.supabase.co/rest/v1/`.
 
 The REST interface is automatically reflected from your database's schema and supports:
+
 - Basic CRUD operations (Create/Read/Update/Delete)
 - Arbitrarily deep relationships among tables/views, functions that return table types can also nest related tables/views.
 - Works with Postgres Views, Materialized Views and Foreign Tables
@@ -42,6 +43,7 @@ The REST interface is automatically reflected from your database's schema and su
 The REST API resolves all requests to a single SQL statement leading to fast response times and high throughput.
 
 Reference:
+
 - [Docs](https://postgrest.org/)
 - [Source Code](https://github.com/PostgREST/postgrest)
 
@@ -52,6 +54,7 @@ You can introspect and query the GraphQL API of an existing Supabase project wit
 or navigate there manually at `API Docs > GraphQL > GraphiQL`.
 
 The GraphQL interface is automatically reflected from your database's schema and supports:
+
 - Basic CRUD operations (Create/Read/Update/Delete)
 - Support for Tables, Views, Materialized Views, and Foreign Tables
 - Arbitrarily deep relationships among tables/views
@@ -61,6 +64,7 @@ The GraphQL interface is automatically reflected from your database's schema and
 The GraphQL API resolves all requests in a single round-trip leading to fast response times and high throughput.
 
 Reference:
+
 - [Docs](https://supabase.github.io/pg_graphql/)
 - [Source Code](https://github.com/supabase/pg_graphql)
 
diff --git a/apps/docs/pages/guides/api/joins-and-nesting.mdx b/apps/docs/pages/guides/api/joins-and-nesting.mdx
index 205e1ceece0..1ee2d396193 100644
--- a/apps/docs/pages/guides/api/joins-and-nesting.mdx
+++ b/apps/docs/pages/guides/api/joins-and-nesting.mdx
@@ -40,24 +40,25 @@ Let's use an example database that stores `countries` and `cities`:
 <TabPanel id="SQL" label="SQL">
 
 ```sql
-create table
-  countries ("id" serial primary key, "name" text);
+create table countries (
+  "id" serial primary key,
+  "name" text
+);
 
-insert into
-  countries (id, name)
+insert into countries
+  (id, name)
 values
   (1, 'United Kingdom'),
   (2, 'United States');
 
-create table
-  cities (
-    "id" serial primary key,
-    "name" text,
-    "country_id" int references "countries"
-  );
+create table cities (
+  "id" serial primary key,
+  "name" text,
+  "country_id" int references "countries"
+);
 
-insert into
-  cities (name, country_id)
+insert into cities
+  (name, country_id)
 values
   ('London', 1),
   ('Manchester', 1),
@@ -130,18 +131,21 @@ GET https://[REF].supabase.co/rest/v1/countries?select=id,name,cities(id,name)
 The Serverless APIs will detect many-to-many joins. For example, if you have a database which stored teams of users (where each user could belong to many teams):
 
 ```sql
-create table
-  users ("id" serial primary key, "name" text);
+create table users (
+  "id" serial primary key,
+  "name" text
+);
 
-create table
-  teams ("id" serial primary key, "team_name" text);
+create table teams (
+  "id" serial primary key,
+  "team_name" text
+);
 
-create table
-  members (
-    "user_id" int references users,
-    "team_id" int references teams,
-    primary key(user_id, team_id)
-  );
+create table members (
+  "user_id" int references users,
+  "team_id" int references teams,
+  primary key (user_id, team_id)
+);
 ```
 
 In these cases you don't need to explicitly define the joining table (members). If we wanted to fetch all the teams and the members in each team:
diff --git a/apps/docs/pages/guides/api/securing-your-api.mdx b/apps/docs/pages/guides/api/securing-your-api.mdx
index 70fa2ef38ae..5887a6a33b8 100644
--- a/apps/docs/pages/guides/api/securing-your-api.mdx
+++ b/apps/docs/pages/guides/api/securing-your-api.mdx
@@ -49,10 +49,8 @@ To confirm that safeupdate is enabled for API queries, run the following query:
 select
   usename,
   useconfig
-from
-  pg_shadow
-where
-  usename = 'authenticator';
+from pg_shadow
+where usename = 'authenticator';
 ```
 
 The expected value for `useconfig` should be:
diff --git a/apps/docs/pages/guides/auth/auth-captcha.mdx b/apps/docs/pages/guides/auth/auth-captcha.mdx
index 6aaee2f4388..b2546a5c7b6 100644
--- a/apps/docs/pages/guides/auth/auth-captcha.mdx
+++ b/apps/docs/pages/guides/auth/auth-captcha.mdx
@@ -7,7 +7,7 @@ export const meta = {
   video: 'https://www.youtube.com/v/em1cpOAXknM',
 }
 
-Supabase provides you with the option of adding captcha to your sign-in, sign-up, and password reset forms. This keeps your website safe from bots and malicious scripts. Supabase authentication has support for [hCaptcha](https://www.hcaptcha.com/).
+Supabase provides you with the option of adding captcha to your sign-in, sign-up, and password reset forms. This keeps your website safe from bots and malicious scripts. Supabase authentication has support for [hCaptcha](https://www.hcaptcha.com/) and [Cloudflare Turnstile](https://www.cloudflare.com/products/turnstile/).
 
 <div className="video-container">
   <iframe
@@ -18,8 +18,15 @@ Supabase provides you with the option of adding captcha to your sign-in, sign-up
   ></iframe>
 </div>
 
-## Sign up for hCaptcha
+## Sign up for Captcha
 
+<Tabs
+  scrollable
+  size="small"
+  type="underlined"
+  defaultActiveId="hcaptcha-1"
+>
+<TabPanel id="hcaptcha-1" label="HCaptcha">
 Go to the [hCaptcha](https://www.hcaptcha.com/) website and sign up for an account. On the welcome page, copy the **Sitekey** and **Secret key**.
 
 If you have already signed up and didn't copy this information from the welcome page, you can get the **Secret key** from the settings page.
@@ -34,17 +41,34 @@ In the Settings page, look for the **Sitekey** section and copy the key.
 
 ![sitekey_settings.png](/docs/img/guides/auth-captcha/sitekey_settings.png)
 
-## Enable hCaptcha protection for your Supabase project
+</TabPanel>
 
-Navigate to the **[Authentication](https://app.supabase.com/project/_/settings/auth)** page in the Supabase Dashboard and find the **Enable hCaptcha protection** toggle under the **Security and Protection** section.
+<TabPanel id="turnstile-1" label="Turnstile">
+ Go to the [Cloudflare website](https://dash.cloudflare.com/login) and sign up for an account. On the welcome page, head to the Turnstile section and add a new site. Create a site and take note of the **Sitekey** and **Secret Key** as shown below
+      ![cloudflare_settings.png](/docs/img/guides/auth-captcha/cloudflare_settings.png)
+</TabPanel>
+</Tabs>
+
+## Enable Captcha protection for your Supabase project
+
+Navigate to the **[Authentication](https://app.supabase.com/project/_/settings/auth)** page in the Supabase Dashboard and find the **Enable Captcha protection** toggle under the **Security and Protection** section.
 
 ![supabase_auth_general_settings.png](/docs/img/guides/auth-captcha/supabase_auth_general_settings.png)
 
-Enter your hCaptcha **Secret key** and click **Save**.
+Enter your Captcha **Secret key** and click **Save**.
 
-## Add the hCaptcha frontend component
+## Add the Captcha frontend component
 
-The frontend requires some changes to provide the captcha on-screen for the user. This example uses React and the hCaptcha React component, but hCaptcha can be used with any JavaScript framework.
+The frontend requires some changes to provide the captcha on-screen for the user. This example uses React and the corresponding Captcha React component, but both Captcha providers can be used with any JavaScript framework.
+
+<Tabs
+  scrollable
+  size="small"
+  type="underlined"
+  defaultActiveId="hcaptcha-2"
+>
+
+<TabPanel id="hcaptcha-2" label="HCaptcha">
 
 Install `@hcaptcha/react-hcaptcha` in your project as a dependency.
 
@@ -58,7 +82,7 @@ Now import the `HCaptcha` component from the `@hcaptcha/react-hcaptcha` library.
 import HCaptcha from '@hcaptcha/react-hcaptcha'
 ```
 
-Let’s create a empty state to store our `captchaToken`
+Let's create a empty state to store our `captchaToken`
 
 ```jsx
 const [captchaToken, setCaptchaToken] = useState()
@@ -75,7 +99,7 @@ We will pass it the sitekey we copied from the hCaptcha website as a property al
 ```jsx
 <HCaptcha
   sitekey="your-sitekey"
-  onVerify={(token) => { setCaptchaToken(token) }
+  onVerify={(token) => { setCaptchaToken(token) }
 />
 ```
 
@@ -117,6 +141,60 @@ captcha.current.resetCaptcha()
 
 In order to test that this works locally we will need to use something like [ngrok](https://ngrok.com/) or add an entry to your hosts file. You can read more about this in the [hCaptcha docs](https://docs.hcaptcha.com/#local-development).
 
+</TabPanel>
+
+<TabPanel id="turnstile-2" label="Turnstile">
+
+      The frontend requires some changes to provide the captcha on-screen for the user. This example uses React and the Turnstile React component, but Turnstile can be used with any JavaScript framework.
+
+Install @marsidev/react-turnstile in your project as a dependency.
+
+```bash
+npm install @marsidev/react-turnstile
+```
+
+Now import the Turnstile component from the @marsidev/react-turnstile library.
+
+```jsx
+import { Turnstile } from '@marsidev/react-turnstile'
+```
+
+Let's create an empty state to store our `captchaToken`
+
+```jsx
+const [captchaToken, setCaptchaToken] = useState()
+```
+
+Now lets add the Cloudflare Turnstile component to the JSX section of our code
+
+```html
+<Turnstile />
+```
+
+We will pass it the sitekey we copied from the Cloudflare website as a property along with a `onVerify` property which takes a callback function. This callback function will have a token as one of its properties. Let's set the token in the state using `setCaptchaToken`
+
+```jsx
+<Turnstile
+  sitekey="your-sitekey"
+  onVerify={(token) => { setCaptchaToken(token) }
+/>
+```
+
+We can now use the captchaToken we receive in our Supabase `signUp` function.
+
+```jsx
+await supabase.auth.signUp({
+  email,
+  password,
+  options: { captchaToken },
+})
+```
+
+To test locally, you will need to add localhost to the domain whitelist as per the [Cloudflare docs](https://developers.cloudflare.com/turnstile/reference/testing/)
+
+      </TabPanel>
+      </Tabs>
+
 Run the application and you should now be provided with a captcha challenge.
 
 export const Page = ({ children }) => <Layout meta={meta} children={children} />
diff --git a/apps/docs/pages/guides/auth/auth-helpers/auth-ui.mdx b/apps/docs/pages/guides/auth/auth-helpers/auth-ui.mdx
index c5607129ce3..53cc8a37d90 100644
--- a/apps/docs/pages/guides/auth/auth-helpers/auth-ui.mdx
+++ b/apps/docs/pages/guides/auth/auth-helpers/auth-ui.mdx
@@ -94,7 +94,7 @@ The Auth component is currently shipped with the following views:
 - Update password
 - Forgotten password
 
-We are planning on adding more views in the future.  Follow along on that [repo](https://github.com/supabase/auth-ui).
+We are planning on adding more views in the future. Follow along on that [repo](https://github.com/supabase/auth-ui).
 
 ## Customization
 
@@ -202,10 +202,7 @@ See the list of [tokens within a theme](https://github.com/supabase/auth-ui/blob
 import { createClient } from '@supabase/supabase-js'
 import { Auth } from '@supabase/auth-ui-react'
 
-const supabase = createClient(
-  '<INSERT PROJECT URL>',
-  '<INSERT PROJECT ANON API KEY>'
-)
+const supabase = createClient('<INSERT PROJECT URL>', '<INSERT PROJECT ANON API KEY>')
 
 const customTheme = {
   default: {
@@ -239,7 +236,7 @@ const App = () => (
   <Auth
     supabaseClient={supabase}
     theme="default" // can also be "dark" or "evenDarker"
-    appearance={{ theme: customTheme}}
+    appearance={{ theme: customTheme }}
   />
 )
 ```
diff --git a/apps/docs/pages/guides/auth/auth-helpers/nextjs-server-components.mdx b/apps/docs/pages/guides/auth/auth-helpers/nextjs-server-components.mdx
index 5cad755ec61..230eae8d42f 100644
--- a/apps/docs/pages/guides/auth/auth-helpers/nextjs-server-components.mdx
+++ b/apps/docs/pages/guides/auth/auth-helpers/nextjs-server-components.mdx
@@ -138,7 +138,7 @@ import { useRouter } from 'next/navigation'
 
 const Context = createContext(undefined)
 
-export default function SupabaseProvider({ children }) {
+export default function SupabaseProvider({ children, session }) {
   const [supabase] = useState(() => createBrowserSupabaseClient())
   const router = useRouter()
 
@@ -155,7 +155,7 @@ export default function SupabaseProvider({ children }) {
   }, [router, supabase])
 
   return (
-    <Context.Provider value={{ supabase }}>
+    <Context.Provider value={{ supabase, session }}>
       <>{children}</>
     </Context.Provider>
   )
@@ -188,13 +188,22 @@ import { useRouter } from 'next/navigation'
 import type { SupabaseClient } from '@supabase/auth-helpers-nextjs'
 import type { Database } from '@/lib/database.types'
 
+type MaybeSession = Session | null
+
 type SupabaseContext = {
   supabase: SupabaseClient<Database>
+  session: MaybeSession
 }
 
 const Context = createContext<SupabaseContext | undefined>(undefined)
 
-export default function SupabaseProvider({ children }: { children: React.ReactNode }) {
+export default function SupabaseProvider({
+  children,
+  session,
+}: {
+  children: React.ReactNode
+  session: MaybeSession
+}) {
   const [supabase] = useState(() => createBrowserSupabaseClient())
   const router = useRouter()
 
@@ -211,7 +220,7 @@ export default function SupabaseProvider({ children }: { children: React.ReactNo
   }, [router, supabase])
 
   return (
-    <Context.Provider value={{ supabase }}>
+    <Context.Provider value={{ supabase, session }}>
       <>{children}</>
     </Context.Provider>
   )
@@ -256,7 +265,10 @@ export default function RootLayout({ children }) {
   return (
     <html lang="en">
       <body>
-        <SupabaseProvider>{children}</SupabaseProvider>
+        <SupabaseProvider session={session}>
+          <SupabaseListener serverAccessToken={session?.access_token} />
+          {children}
+        </SupabaseProvider>
       </body>
     </html>
   )
@@ -282,7 +294,10 @@ export default function RootLayout({ children }: { children: React.ReactNode })
   return (
     <html lang="en">
       <body>
-        <SupabaseProvider>{children}</SupabaseProvider>
+        <SupabaseProvider session={session}>
+          <SupabaseListener serverAccessToken={session?.access_token} />
+          {children}
+        </SupabaseProvider>
       </body>
     </html>
   )
diff --git a/apps/docs/pages/guides/auth/auth-helpers/remix.mdx b/apps/docs/pages/guides/auth/auth-helpers/remix.mdx
index 621c2d473f8..7ff90a03904 100644
--- a/apps/docs/pages/guides/auth/auth-helpers/remix.mdx
+++ b/apps/docs/pages/guides/auth/auth-helpers/remix.mdx
@@ -424,9 +424,7 @@ And then use the revalidator, inside the `onAuthStateChange` hook.
 const { env, session } = useLoaderData()
 const { revalidate } = useRevalidator()
 
-const [supabase] = useState(() =>
-  createBrowserClient(env.SUPABASE_URL, env.SUPABASE_ANON_KEY)
-)
+const [supabase] = useState(() => createBrowserClient(env.SUPABASE_URL, env.SUPABASE_ANON_KEY))
 
 const serverAccessToken = session?.access_token
 
@@ -464,7 +462,7 @@ useEffect(() => {
   const {
     data: { subscription },
   } = supabase.auth.onAuthStateChange((event, session) => {
-    if (event !== "INITIAL_SESSION" && session?.access_token !== serverAccessToken) {
+    if (event !== 'INITIAL_SESSION' && session?.access_token !== serverAccessToken) {
       // server and client are out of sync.
       revalidate()
     }
diff --git a/apps/docs/pages/guides/auth/auth-helpers/sveltekit.mdx b/apps/docs/pages/guides/auth/auth-helpers/sveltekit.mdx
index 424ed29ee0a..6696b99b73e 100644
--- a/apps/docs/pages/guides/auth/auth-helpers/sveltekit.mdx
+++ b/apps/docs/pages/guides/auth/auth-helpers/sveltekit.mdx
@@ -35,19 +35,16 @@ Create a server supabase client in a handle hook:
 
 ```ts title=src/hooks.server.ts
 // src/hooks.server.ts
-import {
-  PUBLIC_SUPABASE_URL,
-  PUBLIC_SUPABASE_ANON_KEY
-} from '$env/static/public';
-import { createSupabaseServerClient } from '@supabase/auth-helpers-sveltekit';
-import type { Handle } from '@sveltejs/kit';
+import { PUBLIC_SUPABASE_URL, PUBLIC_SUPABASE_ANON_KEY } from '$env/static/public'
+import { createSupabaseServerClient } from '@supabase/auth-helpers-sveltekit'
+import type { Handle } from '@sveltejs/kit'
 
 export const handle: Handle = async ({ event, resolve }) => {
   event.locals.supabase = createSupabaseServerClient({
     supabaseUrl: PUBLIC_SUPABASE_URL,
     supabaseKey: PUBLIC_SUPABASE_ANON_KEY,
-    event
-  });
+    event,
+  })
 
   /**
    * a little helper that is written for convenience so that instead
@@ -56,10 +53,10 @@ export const handle: Handle = async ({ event, resolve }) => {
    */
   event.locals.getSession = async () => {
     const {
-      data: { session }
-    } = await event.locals.supabase.auth.getSession();
-    return session;
-  };
+      data: { session },
+    } = await event.locals.supabase.auth.getSession()
+    return session
+  }
 
   return resolve(event, {
     /**
@@ -68,10 +65,10 @@ export const handle: Handle = async ({ event, resolve }) => {
      * https://github.com/sveltejs/kit/issues/8061
      */
     filterSerializedResponseHeaders(name) {
-      return name === 'content-range';
-    }
-  });
-};
+      return name === 'content-range'
+    },
+  })
+}
 ```
 
 > Note that we are specifying filterSerializedResponseHeaders here. We need to tell SvelteKit that supabase needs the content-range header.
@@ -82,13 +79,13 @@ In order to make the session available to the UI (pages, layouts) we need to pas
 
 ```ts title=src/routes/+layout.server.ts
 // src/routes/+layout.server.ts
-import type { LayoutServerLoad } from './$types';
+import type { LayoutServerLoad } from './$types'
 
 export const load: LayoutServerLoad = async ({ locals: { getSession } }) => {
   return {
-    session: await getSession()
-  };
-};
+    session: await getSession(),
+  }
+}
 ```
 
 ### Shared Load functions and pages
@@ -97,30 +94,27 @@ To be able to use Supabase in shared load functions and inside pages you need to
 
 ```ts
 // src/routes/+layout.ts
-import {
-  PUBLIC_SUPABASE_ANON_KEY,
-  PUBLIC_SUPABASE_URL
-} from '$env/static/public';
-import { createSupabaseLoadClient } from '@supabase/auth-helpers-sveltekit';
-import type { LayoutLoad } from './$types';
-import type { Database } from '../DatabaseDefinitions';
+import { PUBLIC_SUPABASE_ANON_KEY, PUBLIC_SUPABASE_URL } from '$env/static/public'
+import { createSupabaseLoadClient } from '@supabase/auth-helpers-sveltekit'
+import type { LayoutLoad } from './$types'
+import type { Database } from '../DatabaseDefinitions'
 
 export const load: LayoutLoad = async ({ fetch, data, depends }) => {
-  depends('supabase:auth');
+  depends('supabase:auth')
 
   const supabase = createSupabaseLoadClient<Database>({
     supabaseUrl: PUBLIC_SUPABASE_URL,
     supabaseKey: PUBLIC_SUPABASE_ANON_KEY,
     event: { fetch },
-    serverSession: data.session
-  });
+    serverSession: data.session,
+  })
 
   const {
-    data: { session }
-  } = await supabase.auth.getSession();
+    data: { session },
+  } = await supabase.auth.getSession()
 
-  return { supabase, session };
-};
+  return { supabase, session }
+}
 ```
 
 Access the client inside pages by `$page.data.supabase` or `data.supabase` when using `export let data: PageData`.
@@ -169,17 +163,17 @@ In order to get the most out of TypeScript and it's intellisense, you should imp
 ```ts
 // src/app.d.ts
 
-import { SupabaseClient, Session } from '@supabase/supabase-js';
-import { Database } from './DatabaseDefinitions';
+import { SupabaseClient, Session } from '@supabase/supabase-js'
+import { Database } from './DatabaseDefinitions'
 
 declare global {
   namespace App {
     interface Locals {
-      supabase: SupabaseClient<Database>;
-      getSession(): Promise<Session | null>;
+      supabase: SupabaseClient<Database>
+      getSession(): Promise<Session | null>
     }
     interface PageData {
-      session: Session | null;
+      session: Session | null
     }
     // interface Error {}
     // interface Platform {}
@@ -193,24 +187,24 @@ For [row level security](https://supabase.com/docs/guides/auth/row-level-securit
 
 ```html
 <script lang="ts">
-  import type { PageData } from './$types';
+  import type { PageData } from './$types'
 
-  export let data: PageData;
+  export let data: PageData
 
-  let loadedData = [];
+  let loadedData = []
   async function loadData() {
-    const { data: result } = await data.supabase.from('test').select('*').limit(20);
-    loadedData = result;
+    const { data: result } = await data.supabase.from('test').select('*').limit(20)
+    loadedData = result
   }
 
   $: if (data.session) {
-    loadData();
+    loadData()
   }
 </script>
 
 {#if data.session}
-  <p>client-side data fetching with RLS</p>
-  <pre>{JSON.stringify(loadedData, null, 2)}</pre>
+<p>client-side data fetching with RLS</p>
+<pre>{JSON.stringify(loadedData, null, 2)}</pre>
 {/if}
 ```
 
@@ -219,10 +213,10 @@ For [row level security](https://supabase.com/docs/guides/auth/row-level-securit
 ```html
 <!-- src/routes/profile/+page.svelte -->
 <script lang="ts">
-  import type { PageData } from './$types';
+  import type { PageData } from './$types'
 
-  export let data: PageData;
-  $: ({ user, tableData } = data);
+  export let data: PageData
+  $: ({ user, tableData } = data)
 </script>
 
 <div>Protected content for {user.email}</div>
@@ -232,21 +226,21 @@ For [row level security](https://supabase.com/docs/guides/auth/row-level-securit
 
 ```ts
 // src/routes/profile/+page.ts
-import type { PageLoad } from './$types';
-import { redirect } from '@sveltejs/kit';
+import type { PageLoad } from './$types'
+import { redirect } from '@sveltejs/kit'
 
 export const load: PageLoad = async ({ parent }) => {
-  const { supabase, session } = await parent();
+  const { supabase, session } = await parent()
   if (!session) {
-    throw redirect(303, '/');
+    throw redirect(303, '/')
   }
-  const { data: tableData } = await supabase.from('test').select('*');
+  const { data: tableData } = await supabase.from('test').select('*')
 
   return {
     user: session.user,
-    tableData
-  };
-};
+    tableData,
+  }
+}
 ```
 
 ## Protecting API routes
@@ -255,21 +249,19 @@ Wrap an API Route to check that the user has a valid session. If they're not log
 
 ```ts
 // src/routes/api/protected-route/+server.ts
-import type { RequestHandler } from './$types';
-import { json, error } from '@sveltejs/kit';
+import type { RequestHandler } from './$types'
+import { json, error } from '@sveltejs/kit'
 
-export const GET: RequestHandler = async ({
-  locals: { supabase, getSession }
-}) => {
-  const session = await getSession();
+export const GET: RequestHandler = async ({ locals: { supabase, getSession } }) => {
+  const session = await getSession()
   if (!session) {
     // the user is not signed in
-    throw error(401, { message: 'Unauthorized' });
+    throw error(401, { message: 'Unauthorized' })
   }
-  const { data } = await supabase.from('test').select('*');
+  const { data } = await supabase.from('test').select('*')
 
-  return json({ data });
-};
+  return json({ data })
+}
 ```
 
 If you visit `/api/protected-route` without a valid session cookie, you will get a 401 response.
@@ -280,35 +272,35 @@ Wrap an Action to check that the user has a valid session. If they're not logged
 
 ```ts
 // src/routes/posts/+page.server.ts
-import type { Actions } from './$types';
-import { error, fail } from '@sveltejs/kit';
+import type { Actions } from './$types'
+import { error, fail } from '@sveltejs/kit'
 
 export const actions: Actions = {
   createPost: async ({ request, locals: { supabase, getSession } }) => {
-    const session = await getSession();
+    const session = await getSession()
 
     if (!session) {
       // the user is not signed in
-      throw error(401, { message: 'Unauthorized' });
+      throw error(401, { message: 'Unauthorized' })
     }
     // we are save, let the user create the post
-    const formData = await request.formData();
-    const content = formData.get('content');
+    const formData = await request.formData()
+    const content = formData.get('content')
 
     const { error: createPostError, data: newPost } = await supabase
       .from('posts')
-      .insert({ content });
+      .insert({ content })
 
     if (createPostError) {
       return fail(500, {
-        supabaseErrorMessage: createPostError.message
-      });
+        supabaseErrorMessage: createPostError.message,
+      })
     }
     return {
-      newPost
-    };
-  }
-};
+      newPost,
+    }
+  },
+}
 ```
 
 If you try to submit a form with the action `?/createPost` without a valid session cookie, you will get a 401 error response.
@@ -316,47 +308,47 @@ If you try to submit a form with the action `?/createPost` without a valid sessi
 ## Saving and deleting the session
 
 ```ts
-import type { Actions } from './$types';
-import { fail, redirect } from '@sveltejs/kit';
-import { AuthApiError } from '@supabase/supabase-js';
+import type { Actions } from './$types'
+import { fail, redirect } from '@sveltejs/kit'
+import { AuthApiError } from '@supabase/supabase-js'
 
 export const actions: Actions = {
   signin: async ({ request, locals: { supabase } }) => {
-    const formData = await request.formData();
+    const formData = await request.formData()
 
-    const email = formData.get('email') as string;
-    const password = formData.get('password') as string;
+    const email = formData.get('email') as string
+    const password = formData.get('password') as string
 
     const { error } = await supabase.auth.signInWithPassword({
       email,
-      password
-    });
+      password,
+    })
 
     if (error) {
       if (error instanceof AuthApiError && error.status === 400) {
         return fail(400, {
           error: 'Invalid credentials.',
           values: {
-            email
-          }
-        });
+            email,
+          },
+        })
       }
       return fail(500, {
         error: 'Server error. Try again later.',
         values: {
-          email
-        }
-      });
+          email,
+        },
+      })
     }
 
-    throw redirect(303, '/dashboard');
+    throw redirect(303, '/dashboard')
   },
 
   signout: async ({ locals: { supabase } }) => {
-    await supabase.auth.signOut();
-    throw redirect(303, '/');
-  }
-};
+    await supabase.auth.signOut()
+    throw redirect(303, '/')
+  },
+}
 ```
 
 ## Protecting multiple routes
@@ -366,33 +358,30 @@ protect multiple routes at once.
 
 ```ts
 // src/hooks.server.ts
-import type { RequestHandler } from './$types';
-import { redirect, error } from '@sveltejs/kit';
+import type { RequestHandler } from './$types'
+import { redirect, error } from '@sveltejs/kit'
 
 export const handle: Handle = async ({ event, resolve }) => {
   // protect requests to all routes that start with /protected-routes
   if (event.url.pathname.startsWith('/protected-routes')) {
-    const session = await event.locals.getSession();
+    const session = await event.locals.getSession()
     if (!session) {
       // the user is not signed in
-      throw redirect(303, '/');
+      throw redirect(303, '/')
     }
   }
 
   // protect POST requests to all routes that start with /protected-posts
-  if (
-    event.url.pathname.startsWith('/protected-posts') &&
-    event.request.method === 'POST'
-  ) {
-    const session = await event.locals.getSession();
+  if (event.url.pathname.startsWith('/protected-posts') && event.request.method === 'POST') {
+    const session = await event.locals.getSession()
     if (!session) {
       // the user is not signed in
-      throw error(303, '/');
+      throw error(303, '/')
     }
   }
 
-  return resolve(event);
-};
+  return resolve(event)
+}
 ```
 
 ## Migrate from 0.8.x to 0.9 [#migration]
@@ -425,19 +414,16 @@ export const supabaseClient = createClient(env.PUBLIC_SUPABASE_URL, env.PUBLIC_S
 
 ```js title=src/hooks.server.ts
 // src/hooks.server.ts
-import {
-  PUBLIC_SUPABASE_URL,
-  PUBLIC_SUPABASE_ANON_KEY
-} from '$env/static/public';
-import { createSupabaseServerClient } from '@supabase/auth-helpers-sveltekit';
-import type { Handle } from '@sveltejs/kit';
+import { PUBLIC_SUPABASE_URL, PUBLIC_SUPABASE_ANON_KEY } from '$env/static/public'
+import { createSupabaseServerClient } from '@supabase/auth-helpers-sveltekit'
+import type { Handle } from '@sveltejs/kit'
 
 export const handle: Handle = async ({ event, resolve }) => {
   event.locals.supabase = createSupabaseServerClient({
     supabaseUrl: PUBLIC_SUPABASE_URL,
     supabaseKey: PUBLIC_SUPABASE_ANON_KEY,
-    event
-  });
+    event,
+  })
 
   /**
    * a little helper that is written for convenience so that instead
@@ -446,10 +432,10 @@ export const handle: Handle = async ({ event, resolve }) => {
    */
   event.locals.getSession = async () => {
     const {
-      data: { session }
-    } = await event.locals.supabase.auth.getSession();
-    return session;
-  };
+      data: { session },
+    } = await event.locals.supabase.auth.getSession()
+    return session
+  }
 
   return resolve(event, {
     /**
@@ -458,10 +444,10 @@ export const handle: Handle = async ({ event, resolve }) => {
      * https://github.com/sveltejs/kit/issues/8061
      */
     filterSerializedResponseHeaders(name) {
-      return name === 'content-range';
-    }
-  });
-};
+      return name === 'content-range'
+    },
+  })
+}
 ```
 
 </TabPanel>
@@ -469,7 +455,7 @@ export const handle: Handle = async ({ event, resolve }) => {
 
 ### Initialize the client [#migration-initialize-client]
 
-In order to use the Supabase library in your client code you will need to setup a shared load function inside the root `+layout.ts` and create a `+layout.svelte` to handle our event listening for Auth events. 
+In order to use the Supabase library in your client code you will need to setup a shared load function inside the root `+layout.ts` and create a `+layout.svelte` to handle our event listening for Auth events.
 
 <Tabs
   scrollable
@@ -507,31 +493,28 @@ In order to use the Supabase library in your client code you will need to setup
 
 ```ts title=src/routes/+layout.ts
 // src/routes/+layout.ts
-import { invalidate } from '$app/navigation';
-import {
-  PUBLIC_SUPABASE_ANON_KEY,
-  PUBLIC_SUPABASE_URL
-} from '$env/static/public';
-import { createSupabaseLoadClient } from '@supabase/auth-helpers-sveltekit';
-import type { LayoutLoad } from './$types';
-import type { Database } from '../DatabaseDefinitions';
+import { invalidate } from '$app/navigation'
+import { PUBLIC_SUPABASE_ANON_KEY, PUBLIC_SUPABASE_URL } from '$env/static/public'
+import { createSupabaseLoadClient } from '@supabase/auth-helpers-sveltekit'
+import type { LayoutLoad } from './$types'
+import type { Database } from '../DatabaseDefinitions'
 
 export const load: LayoutLoad = async ({ fetch, data, depends }) => {
-  depends('supabase:auth');
+  depends('supabase:auth')
 
   const supabase = createSupabaseLoadClient<Database>({
     supabaseUrl: PUBLIC_SUPABASE_URL,
     supabaseKey: PUBLIC_SUPABASE_ANON_KEY,
     event: { fetch },
-    serverSession: data.session
-  });
+    serverSession: data.session,
+  })
 
   const {
-    data: { session }
-  } = await supabase.auth.getSession();
+    data: { session },
+  } = await supabase.auth.getSession()
 
-  return { supabase, session };
-};
+  return { supabase, session }
+}
 ```
 
 ```svelte title=src/routes/+layout.svelte
@@ -605,17 +588,17 @@ declare namespace App {
 
 ```ts title=src/app.d.ts
 // src/app.d.ts
-import { SupabaseClient, Session } from '@supabase/supabase-js';
-import { Database } from './DatabaseDefinitions';
+import { SupabaseClient, Session } from '@supabase/supabase-js'
+import { Database } from './DatabaseDefinitions'
 
 declare global {
   namespace App {
     interface Locals {
-      supabase: SupabaseClient<Database>;
-      getSession(): Promise<Session | null>;
+      supabase: SupabaseClient<Database>
+      getSession(): Promise<Session | null>
     }
     interface PageData {
-      session: Session | null;
+      session: Session | null
     }
     // interface Error {}
     // interface Platform {}
@@ -675,10 +658,10 @@ export const load: PageLoad = async (event) => {
 ```html title=src/routes/profile/+page.svelte
 <!-- src/routes/profile/+page.svelte -->
 <script lang="ts">
-  import type { PageData } from './$types';
+  import type { PageData } from './$types'
 
-  export let data: PageData;
-  $: ({ user, tableData } = data);
+  export let data: PageData
+  $: ({ user, tableData } = data)
 </script>
 
 <div>Protected content for {user.email}</div>
@@ -688,21 +671,21 @@ export const load: PageLoad = async (event) => {
 
 ```ts title=src/routes/profile/+page.ts
 // src/routes/profile/+page.ts
-import type { PageLoad } from './$types';
-import { redirect } from '@sveltejs/kit';
+import type { PageLoad } from './$types'
+import { redirect } from '@sveltejs/kit'
 
 export const load: PageLoad = async ({ parent }) => {
-  const { supabase, session } = await parent();
+  const { supabase, session } = await parent()
   if (!session) {
-    throw redirect(303, '/');
+    throw redirect(303, '/')
   }
-  const { data: tableData } = await supabase.from('test').select('*');
+  const { data: tableData } = await supabase.from('test').select('*')
 
   return {
     user: session.user,
-    tableData
-  };
-};
+    tableData,
+  }
+}
 ```
 
 </TabPanel>
@@ -740,27 +723,24 @@ export const GET: RequestHandler = async (event) => {
 
 ```ts title=src/routes/api/protected-route/+server.ts
 // src/routes/api/protected-route/+server.ts
-import type { RequestHandler } from './$types';
-import { json, error } from '@sveltejs/kit';
+import type { RequestHandler } from './$types'
+import { json, error } from '@sveltejs/kit'
 
-export const GET: RequestHandler = async ({
-  locals: { supabase, getSession }
-}) => {
-  const session = await getSession();
+export const GET: RequestHandler = async ({ locals: { supabase, getSession } }) => {
+  const session = await getSession()
   if (!session) {
     // the user is not signed in
-    throw error(401, { message: 'Unauthorized' });
+    throw error(401, { message: 'Unauthorized' })
   }
-  const { data } = await supabase.from('test').select('*');
+  const { data } = await supabase.from('test').select('*')
 
-  return json({ data });
-};
+  return json({ data })
+}
 ```
 
 </TabPanel>
 </Tabs>
 
-
 ## Migrate from 0.7.x to 0.8 [#migration-0-8]
 
 ### Set up the Supabase client [#migration-set-up-supabase-client-0-8]
diff --git a/apps/docs/pages/guides/auth/quickstarts/react.mdx b/apps/docs/pages/guides/auth/quickstarts/react.mdx
index 3ce980031f3..d173003dc1b 100644
--- a/apps/docs/pages/guides/auth/quickstarts/react.mdx
+++ b/apps/docs/pages/guides/auth/quickstarts/react.mdx
@@ -98,7 +98,7 @@ export const meta = {
             } = supabase.auth.onAuthStateChange((_event, session) => {
               setSession(session)
             })
-            
+
             return () => subscription.unsubscribe()
           }, [])
 
diff --git a/apps/docs/pages/guides/auth/social-login/auth-github.mdx b/apps/docs/pages/guides/auth/social-login/auth-github.mdx
index 5a3e76eed1d..31c5cf47b2a 100644
--- a/apps/docs/pages/guides/auth/social-login/auth-github.mdx
+++ b/apps/docs/pages/guides/auth/social-login/auth-github.mdx
@@ -36,7 +36,7 @@ Go to the [GitHub Developer Settings](https://github.com/settings/developers) pa
 
 <SocialProviderSetup provider="GitHub" />
 
-## Register a new OAuth application on Github. 
+## Register a new OAuth application on Github.
 
 - Navigate to `Settings`/`Developer settings`/`OAuth Apps`
 - Click `Register a new application`. If you've created an app before, click `New OAuth App` here.
diff --git a/apps/docs/pages/guides/auth/sso/auth-sso-saml.mdx b/apps/docs/pages/guides/auth/sso/auth-sso-saml.mdx
index 1923b2ed243..1e922686c78 100644
--- a/apps/docs/pages/guides/auth/sso/auth-sso-saml.mdx
+++ b/apps/docs/pages/guides/auth/sso/auth-sso-saml.mdx
@@ -105,17 +105,16 @@ A common use case with SSO is to use the UUID of the identity provider as the id
 For example, let's say you have a table like:
 
 ```sql
-CREATE TABLE
-  organization_settings (
-    -- the organization's unique ID
-    id UUID NOT NULL PRIMARY KEY,
-    -- the organization's SSO identity provider
-    sso_provider_id UUID UNIQUE,
-    -- name of the organization
-    name TEXT,
-    -- billing plan (paid, free, enterprise)
-    billing_plan TEXT
-  );
+create table organization_settings (
+  -- the organization's unique ID
+  id uuid not null primary key,
+  -- the organization's SSO identity provider
+  sso_provider_id uuid unique,
+  -- name of the organization
+  name text,
+  -- billing plan (paid, free, enterprise)
+  billing_plan text
+);
 ```
 
 You can use the information present in the user's JWT to scope down which rows from this table the user can see, without doing any additional user management:
diff --git a/apps/docs/pages/guides/cli/using-environment-variables-in-config.mdx b/apps/docs/pages/guides/cli/using-environment-variables-in-config.mdx
new file mode 100644
index 00000000000..c5a5e24524d
--- /dev/null
+++ b/apps/docs/pages/guides/cli/using-environment-variables-in-config.mdx
@@ -0,0 +1,35 @@
+import Layout from '~/layouts/DefaultGuideLayout'
+
+export const meta = {
+  id: 'using-environment-variables-in-config',
+  title: 'Using environment variables in config.toml',
+  description: 'How to use environment variables in config.toml with the Supabase CLI.',
+}
+
+The Supabase CLI is capable of utilizing environment variables stored in our project's root directory's `.env` file within the `config.toml` file.
+
+We can reference the environment variable by using the `env()` function.
+
+Inside of our `.env` file we add the environment variable as we normally would
+
+```env
+GITHUB_CLIENT_ID=""
+GITHUB_SECRET=""
+```
+
+And then reference them inside of our `config.toml`
+
+```toml
+[auth.external.github]
+enabled = true
+client_id = "env(GITHUB_CLIENT_ID)"
+secret = "env(GITHUB_SECRET)"
+# Overrides the default auth redirectUrl.
+redirect_uri = ""
+```
+
+These same environment variables will be referenced by the `supabase start` command from the Supabase CLI.
+
+export const Page = ({ children }) => <Layout meta={meta} children={children} />
+
+export default Page
diff --git a/apps/docs/pages/guides/database/extensions/pgsodium.mdx b/apps/docs/pages/guides/database/extensions/pgsodium.mdx
index 1ac0c84b371..8e5f92ff5fe 100644
--- a/apps/docs/pages/guides/database/extensions/pgsodium.mdx
+++ b/apps/docs/pages/guides/database/extensions/pgsodium.mdx
@@ -12,13 +12,13 @@ extension which provides SQL access to
 algorithms.
 
 libsodium is a modern, easy-to-use software library for encryption,
-decryption, signatures, password hashing, and more.  It is a portable,
+decryption, signatures, password hashing, and more. It is a portable,
 cross-compilable, installable, and packageable fork of the
 [NaCl](http://nacl.cr.yp.to/) library, with a compatible but extended
 API to improve usability even further.
 
 Its goal is to provide all of the core operations needed to build
-higher-level cryptographic tools.  Sodium is cross-platform and
+higher-level cryptographic tools. Sodium is cross-platform and
 cross-language. It runs on many compilers and operating systems,
 including Windows (with MinGW or Visual Studio, x86 and x86_64), iOS,
 and Android. JavaScript and WebAssembly versions are also available
@@ -33,12 +33,12 @@ pgsodium exposes the following libsodium APIs to SQL:
 
 - [Generating Random Data](https://github.com/michelp/pgsodium/#generating-random-data)
 - [Secret key cryptography](https://github.com/michelp/pgsodium/#secret-key-cryptography)
-   - [Authenticated encryption](https://github.com/michelp/pgsodium/#authenticated-encryption)
-   - [Authentication](https://github.com/michelp/pgsodium/#authentication)
+  - [Authenticated encryption](https://github.com/michelp/pgsodium/#authenticated-encryption)
+  - [Authentication](https://github.com/michelp/pgsodium/#authentication)
 - [Public key cryptography](https://github.com/michelp/pgsodium/#public-key-cryptography)
-   - [Authenticated encryption](https://github.com/michelp/pgsodium/#authenticated-encryption-1)
-   - [Public key signatures](https://github.com/michelp/pgsodium/#public-key-signatures)
-   - [Sealed boxes](https://github.com/michelp/pgsodium/#sealed-boxes)
+  - [Authenticated encryption](https://github.com/michelp/pgsodium/#authenticated-encryption-1)
+  - [Public key signatures](https://github.com/michelp/pgsodium/#public-key-signatures)
+  - [Sealed boxes](https://github.com/michelp/pgsodium/#sealed-boxes)
 - [Hashing](https://github.com/michelp/pgsodium/#hashing)
 - [Password hashing](https://github.com/michelp/pgsodium/#password-hashing)
 - [Key Derivation](https://github.com/michelp/pgsodium/#key-derivation)
diff --git a/apps/docs/pages/guides/database/postgres/indexes.mdx b/apps/docs/pages/guides/database/postgres/indexes.mdx
index 138143348de..60e7a3e2eeb 100644
--- a/apps/docs/pages/guides/database/postgres/indexes.mdx
+++ b/apps/docs/pages/guides/database/postgres/indexes.mdx
@@ -15,6 +15,7 @@ Even though indexes improve query performance, the Postgres query planner may no
 ## Create an index
 
 Let's take an example table:
+
 ```sql
 create table persons (
   id bigint generated by default as identity primary key,
@@ -25,6 +26,7 @@ create table persons (
   deceased boolean
 );
 ```
+
 <Admonition>
 
 All the queries in this guide can be run using the [SQL Editor](https://app.supabase.com/project/_/sql) in the Supabase Dashboard, or via `psql` if you're [connecting directly to the database](/docs/guides/database/connecting-to-postgres#direct-connections).
@@ -32,6 +34,7 @@ All the queries in this guide can be run using the [SQL Editor](https://app.supa
 </Admonition>
 
 We might want to frequently query users based on their age:
+
 ```sql
 select name from persons where age = 32;
 ```
@@ -39,19 +42,22 @@ select name from persons where age = 32;
 Without an index, Postgres will scan every row in the table to find equality matches on age.
 
 You can verify this by doing an explain on the query:
+
 ```sql
 explain select name from persons where age = 32;
 ```
 
 Outputs:
+
 ```
 Seq Scan on persons  (cost=0.00..22.75 rows=x width=y)
 Filter: (age = 32)
 ```
 
 To add a simple B-Tree index you can run:
+
 ```sql
-create index idx_persons_age on persons(age);
+create index idx_persons_age on persons (age);
 ```
 
 <Admonition type="caution">
@@ -73,7 +79,8 @@ You can see that in any large data set, traversing the index to locate a given v
 If you are frequently querying a subset of rows then it may be more efficient to build a partial index. In our example, perhaps we only want to match on `age` where `deceased is false`. We could build a partial index:
 
 ```sql
-create index idx_living_persons_age ON persons(age) where deceased is false;
+create index idx_living_persons_age on persons (age)
+where deceased is false;
 ```
 
 ## Ordering indexes
@@ -81,14 +88,13 @@ create index idx_living_persons_age ON persons(age) where deceased is false;
 By default B-Tree indexes are sorted in ascending order, but sometimes you may want to provide a different ordering. Perhaps our application has a page featuring the top 10 oldest people. Here we would want to sort in descending order, and include `NULL` values last. For this we can use:
 
 ```sql
-create index idx_persons_age_desc on persons(age desc nulls last);
+create index idx_persons_age_desc on persons (age desc nulls last);
 ```
 
 ## Reindexing
 
 After a while indexes can become stale and may need rebuilding. Postgres provides a `reindex` command for this, but due to Postgres locks being placed on the index during this process, you may want to make use of the `concurrent` keyword.
 
-
 ```sql
 reindex index concurrently idx_persons_age;
 ```
@@ -103,4 +109,4 @@ Take note that `reindex` can be used inside a transaction, but `reindex [index/t
 
 export const Page = ({ children }) => <Layout meta={meta} children={children} />
 
-export default Page
\ No newline at end of file
+export default Page
diff --git a/apps/docs/pages/guides/getting-started/tutorials/with-nextjs.mdx b/apps/docs/pages/guides/getting-started/tutorials/with-nextjs.mdx
index 980ca00eef6..0aaca423fc5 100644
--- a/apps/docs/pages/guides/getting-started/tutorials/with-nextjs.mdx
+++ b/apps/docs/pages/guides/getting-started/tutorials/with-nextjs.mdx
@@ -4,6 +4,7 @@ export const meta = {
   title: 'Build a User Management App with NextJS',
   description: 'Learn how to use Supabase in your Next App.',
   video: 'https://www.youtube.com/v/0Fs96oZ4se0',
+  tocVideo: '0Fs96oZ4se0',
 }
 
 <QuickstartIntro />
@@ -126,7 +127,7 @@ export default MyApp
 Wrap your `pages/_app.tsx` component with the `SessionContextProvider` component:
 
 ```jsx lines=2,8 title=pages/_app.tsx
-import '../styles/globals.css';
+import '../styles/globals.css'
 import { useState } from 'react'
 import { createBrowserSupabaseClient } from '@supabase/auth-helpers-nextjs'
 import { SessionContextProvider, Session } from '@supabase/auth-helpers-react'
diff --git a/apps/docs/pages/guides/getting-started/tutorials/with-solidjs.mdx b/apps/docs/pages/guides/getting-started/tutorials/with-solidjs.mdx
index c56047307f9..8c9188408cb 100644
--- a/apps/docs/pages/guides/getting-started/tutorials/with-solidjs.mdx
+++ b/apps/docs/pages/guides/getting-started/tutorials/with-solidjs.mdx
@@ -122,13 +122,13 @@ After a user is signed in we can allow them to edit their profile details and ma
 
 Let's create a new component for that called `Account.tsx`.
 
-```jsx title=src/Account.tsx
+```tsx title=src/Account.tsx
 import { AuthSession } from '@supabase/supabase-js'
 import { Component, createEffect, createSignal } from 'solid-js'
 import { supabase } from './supabaseClient'
 
 interface Props {
-  session: AuthSession;
+  session: AuthSession
 }
 
 const Account: Component<Props> = ({ session }) => {
diff --git a/apps/docs/pages/guides/getting-started/tutorials/with-sveltekit.mdx b/apps/docs/pages/guides/getting-started/tutorials/with-sveltekit.mdx
index 8eba8465d47..a43b94dddc9 100644
--- a/apps/docs/pages/guides/getting-started/tutorials/with-sveltekit.mdx
+++ b/apps/docs/pages/guides/getting-started/tutorials/with-sveltekit.mdx
@@ -63,29 +63,26 @@ Add the code below to your `src/hooks.server.ts` to initialize the client on the
 
 ```ts title=src/hooks.server.ts
 // src/hooks.server.ts
-import {
-  PUBLIC_SUPABASE_URL,
-  PUBLIC_SUPABASE_ANON_KEY
-} from '$env/static/public';
-import { createSupabaseServerClient } from '@supabase/auth-helpers-sveltekit';
-import type { Handle } from '@sveltejs/kit';
+import { PUBLIC_SUPABASE_URL, PUBLIC_SUPABASE_ANON_KEY } from '$env/static/public'
+import { createSupabaseServerClient } from '@supabase/auth-helpers-sveltekit'
+import type { Handle } from '@sveltejs/kit'
 
 export const handle: Handle = async ({ event, resolve }) => {
   event.locals.supabase = createSupabaseServerClient({
     supabaseUrl: PUBLIC_SUPABASE_URL,
     supabaseKey: PUBLIC_SUPABASE_ANON_KEY,
-    event
-  });
+    event,
+  })
 
   /**
    * A convenience helper so we can just call await getSession() instead const { data: { session } } = await supabase.auth.getSession()
    */
   event.locals.getSession = async () => {
     const {
-      data: { session }
-    } = await event.locals.supabase.auth.getSession();
-    return session;
-  };
+      data: { session },
+    } = await event.locals.supabase.auth.getSession()
+    return session
+  }
 
   return resolve(event, {
     /**
@@ -94,10 +91,10 @@ export const handle: Handle = async ({ event, resolve }) => {
      * https://github.com/sveltejs/kit/issues/8061
      */
     filterSerializedResponseHeaders(name) {
-      return name === 'content-range';
-    }
-  });
-};
+      return name === 'content-range'
+    },
+  })
+}
 ```
 
 If you are using TypeScript the compiler might complain about `event.locals.supabase` and `event.locals.getSession`, this can be fixed by updating your `src/app.d.ts` with the content below:
@@ -105,16 +102,16 @@ If you are using TypeScript the compiler might complain about `event.locals.supa
 ```ts title=src/app.d.ts
 // src/app.d.ts
 
-import { SupabaseClient, Session } from '@supabase/supabase-js';
+import { SupabaseClient, Session } from '@supabase/supabase-js'
 
 declare global {
   namespace App {
     interface Locals {
-      supabase: SupabaseClient;
-      getSession(): Promise<Session | null>;
+      supabase: SupabaseClient
+      getSession(): Promise<Session | null>
     }
     interface PageData {
-      session: Session | null;
+      session: Session | null
     }
     // interface Error {}
     // interface Platform {}
@@ -126,11 +123,13 @@ Create a new `src/routes/+layout.server.ts` file to handle the session on the se
 
 ```ts title=src/routes/+layout.server.ts
 // src/routes/+layout.server.ts
-export const load = async ({ locals: { getSession } }) => {
+import type { LayoutServerLoad } from './$types'
+
+export const load: LayoutServerLoad = async ({ locals: { getSession } }) => {
   return {
-    session: await getSession()
-  };
-};
+    session: await getSession(),
+  }
+}
 ```
 
 > Start your dev server (`npm run dev`) in order to generate the `./$types` files we are referencing in our project.
@@ -139,29 +138,27 @@ Create a new `src/routes/+layout.ts` file to handle the session and the supabase
 
 ```ts title=src/routes/+layout.ts
 // src/routes/+layout.ts
-import { invalidate } from '$app/navigation';
-import {
-  PUBLIC_SUPABASE_ANON_KEY,
-  PUBLIC_SUPABASE_URL
-} from '$env/static/public';
-import { createSupabaseLoadClient } from '@supabase/auth-helpers-sveltekit';
+import { invalidate } from '$app/navigation'
+import { PUBLIC_SUPABASE_ANON_KEY, PUBLIC_SUPABASE_URL } from '$env/static/public'
+import { createSupabaseLoadClient } from '@supabase/auth-helpers-sveltekit'
+import type { LayoutLoad } from './$types'
 
-export const load = async ({ fetch, data, depends }) => {
-  depends('supabase:auth');
+export const load: LayoutLoad = async ({ fetch, data, depends }) => {
+  depends('supabase:auth')
 
   const supabase = createSupabaseLoadClient({
     supabaseUrl: PUBLIC_SUPABASE_URL,
     supabaseKey: PUBLIC_SUPABASE_ANON_KEY,
     event: { fetch },
-    serverSession: data.session
-  });
+    serverSession: data.session,
+  })
 
   const {
-    data: { session }
-  } = await supabase.auth.getSession();
+    data: { session },
+  } = await supabase.auth.getSession()
 
-  return { supabase, session };
-};
+  return { supabase, session }
+}
 ```
 
 Update your `src/routes/+layout.svelte`:
@@ -239,24 +236,26 @@ Add the `Auth` component to your home page
 
 Create a `src/routes/+page.server.ts` file that will return our website url to be used in our `redirectTo` above.
 
-> This is necessary because the current Supabase auth flow uses implicit grant which returns the tokens as part of the url fragment (#).  
-The redirect to a non server protected page will make sure that the client captures the url fragment as we cannot read these on the server
-and send it over to the server. This all happens behind the scenes and isn't something you will need to do manually.
+> This is necessary because the current Supabase auth flow uses implicit grant which returns the tokens as part of the url fragment (#).
+
+> The redirect to a non server protected page will make sure that the client captures the url fragment as we cannot read these on the server
+> and send it over to the server. This all happens behind the scenes and isn't something you will need to do manually.
 
 ```ts
 // src/routes/+page.server.ts
-import { redirect } from '@sveltejs/kit';
+import { redirect } from '@sveltejs/kit'
+import type { PageServerLoad } from './$types'
 
-export const load = async ({ url, locals: { getSession } }) => {
-	const session = await getSession();
+export const load: PageServerLoad = async ({ url, locals: { getSession } }) => {
+  const session = await getSession()
 
-    // if the user is already logged in return them to the account page
-	if (session) {
-		throw redirect(303, '/account');
-	}
+  // if the user is already logged in return them to the account page
+  if (session) {
+    throw redirect(303, '/account')
+  }
 
-	return { url: url.origin };
-};
+  return { url: url.origin }
+}
 ```
 
 ### Loading page
@@ -378,67 +377,68 @@ Now create the associated `src/routes/account/+page.server.ts` file that will ha
 and handle all our form actions through the `actions` object.
 
 ```ts
-import { fail, redirect } from '@sveltejs/kit';
+import { fail, redirect } from '@sveltejs/kit'
+import type { Actions, PageServerLoad } from './$types'
 
-export const load = async ({ locals: { supabase, getSession } }) => {
-	const session = await getSession();
+export const load = (async ({ locals: { supabase, getSession } }) => {
+  const session = await getSession()
 
-	if (!session) {
-		throw redirect(303, '/');
-	}
+  if (!session) {
+    throw redirect(303, '/')
+  }
 
-	const { data: profile } = await supabase
-		.from('profiles')
-		.select(`username, full_name, website, avatar_url`)
-		.eq('id', session.user.id)
-		.single();
+  const { data: profile } = await supabase
+    .from('profiles')
+    .select(`username, full_name, website, avatar_url`)
+    .eq('id', session.user.id)
+    .single()
 
-	return { session, profile };
-};
+  return { session, profile }
+}) satisfies PageServerLoad
 
 export const actions = {
-	update: async ({ request, locals: { supabase, getSession } }) => {
-		const formData = await request.formData();
-		const fullName = formData.get('fullName') as string;
-		const username = formData.get('username') as string;
-		const website = formData.get('website') as string;
-		const avatarUrl = formData.get('avatarUrl') as string;
+  update: async ({ request, locals: { supabase, getSession } }) => {
+    const formData = await request.formData()
+    const fullName = formData.get('fullName') as string
+    const username = formData.get('username') as string
+    const website = formData.get('website') as string
+    const avatarUrl = formData.get('avatarUrl') as string
 
-		const session = await getSession();
+    const session = await getSession()
 
-		const { error } = await supabase.from('profiles').upsert({
-			id: session?.user.id,
-			full_name: fullName,
-			username,
-			website,
-			avatar_url: avatarUrl,
-			updated_at: new Date()
-		});
+    const { error } = await supabase.from('profiles').upsert({
+      id: session?.user.id,
+      full_name: fullName,
+      username,
+      website,
+      avatar_url: avatarUrl,
+      updated_at: new Date(),
+    })
 
-		if (error) {
-			return fail(500, {
-				fullName,
-				username,
-				website,
-				avatarUrl
-			});
-		}
+    if (error) {
+      return fail(500, {
+        fullName,
+        username,
+        website,
+        avatarUrl,
+      })
+    }
 
-		return {
-			fullName,
-			username,
-			website,
-			avatarUrl
-		};
-	},
-	signout: async ({ locals: { supabase, getSession } }) => {
-		const session = await getSession();
-		if (session) {
-			await supabase.auth.signOut();
-			throw redirect(303, '/');
-		}
-	}
-};
+    return {
+      fullName,
+      username,
+      website,
+      avatarUrl,
+    }
+  },
+  signout: async ({ locals: { supabase, getSession } }) => {
+    const session = await getSession()
+    if (session) {
+      await supabase.auth.signOut()
+      throw redirect(303, '/')
+    }
+  },
+} satisfies Actions
 ```
 
 ### Launch!
diff --git a/apps/docs/pages/guides/getting-started/tutorials/with-vue-3.mdx b/apps/docs/pages/guides/getting-started/tutorials/with-vue-3.mdx
index 98b8bcce015..0263b65ea7c 100644
--- a/apps/docs/pages/guides/getting-started/tutorials/with-vue-3.mdx
+++ b/apps/docs/pages/guides/getting-started/tutorials/with-vue-3.mdx
@@ -65,7 +65,7 @@ Optionally, update [src/style.css](https://raw.githubusercontent.com/supabase/su
 
 ### Set up a Login component
 
-Set up an `src/components/Auth.vue` component to manage logins and sign ups. We'll use Magic Links, so users can sign in with their email without using passwords. 
+Set up an `src/components/Auth.vue` component to manage logins and sign ups. We'll use Magic Links, so users can sign in with their email without using passwords.
 
 ```vue title=/src/components/Auth.vue
 <script setup>
diff --git a/apps/docs/pages/guides/platform/backups.mdx b/apps/docs/pages/guides/platform/backups.mdx
index 3f19a5f9090..1a0d53cf5d0 100644
--- a/apps/docs/pages/guides/platform/backups.mdx
+++ b/apps/docs/pages/guides/platform/backups.mdx
@@ -24,7 +24,9 @@ Daily Backups and PITR are mutually exclusive. If your project opts into using P
 All Pro and Enterprise tier Supabase projects are backed up automatically on a daily basis. In terms of Recovery Point Objective (RPO), Daily Backups would be suitable for projects willing to lose up to 24 hours worth of data if disaster hits at the most inopportune time. If a lower RPO is required, enabling Point-in-Time Recovery should be considered.
 
 <Admonition type="note">
-  For security purposes, passwords for custom roles are not stored in daily backups, and will not be found in downloadable files. As such, if you are restoring from a daily backup and are using custom roles, you will need to set their passwords once more following a completed restoration.
+  For security purposes, passwords for custom roles are not stored in daily backups, and will not be
+  found in downloadable files. As such, if you are restoring from a daily backup and are using
+  custom roles, you will need to set their passwords once more following a completed restoration.
 </Admonition>
 
 ### Backup Process [#daily-backups-process]
diff --git a/apps/docs/pages/guides/platform/exhaust-cpu.mdx b/apps/docs/pages/guides/platform/exhaust-cpu.mdx
new file mode 100644
index 00000000000..9a5f0484b26
--- /dev/null
+++ b/apps/docs/pages/guides/platform/exhaust-cpu.mdx
@@ -0,0 +1,49 @@
+import Layout from '~/layouts/DefaultGuideLayout'
+
+export const meta = {
+  id: 'exhaust-cpu',
+  title: 'High CPU Usage',
+  description:
+    'Learn what high CPU usage could mean for your Supabase instance and what could have caused it.',
+}
+
+Learn what high CPU usage could mean for your Supabase instance and what could have caused it.
+
+## The danger of high CPU usage
+
+Every Supabase project runs in its dedicated virtual machine. Your instance will have a different set of hardware provisioned depending on your [compute add-on](https://supabase.com/docs/guides/platform/compute-add-ons). Your hardware may not be suitable for the intended workload and may experience high CPU usage.
+
+High CPU usage could come with a range of issues:
+
+- slower queries
+- disruption of daily backup routines
+- in rare cases, your instance may become unresponsive
+
+Moreover, your instance might not be able to handle future traffic spikes if it already has a high CPU usage.
+
+## Monitor your CPU
+
+You can check your CPU usage directly on the Supabase Platform. For this go to database health in the reports section or [click here](https://app.supabase.com/project/_/reports/database) and select your project.
+
+![CPU usage reported on Supabase dashboard](/docs/img/guides/platform/exhaust-cpu-report.png)
+
+It is also possible to monitor your resources and set up alerts using Prometheus/Grafana. You can find a guide for this [here](https://supabase.com/docs/guides/platform/metrics).
+
+## Common reasons for high CPU usage
+
+Everything you do with your Supabase project requires compute. Hence, there can be many reasons for high CPU usage. Here are some common ones:
+
+- **Query performance:** Queries that take a long time to complete (>1 second) as well as excessive amounts of querying can put a strain on the CPU. Check our guide on [examining query performance](https://supabase.com/docs/guides/platform/performance#examining-query-performance).
+- **Missing indexes:** Your database might have to scan through a large amount of data to find the information it needs. Creating indexes helps your database find data faster. Learn more about indexes [here](https://supabase.com/docs/guides/database/postgres/indexes).
+- **Unsuitable compute:** The instance size of your Supabase project might not be suitable for your application as you might have more traffic or run resource-intensive operations.
+
+## Solving high CPU usage
+
+There are two ways to solve high CPU:
+
+1. **Optimize performance:** Get more out of your instance's resources by optimizing your usage. Have a look at our [performance tuning guide](https://supabase.com/docs/guides/platform/performance#examining-query-performance) and our [production readiness guide](https://supabase.com/docs/guides/platform/going-into-prod#performance).
+2. **Upgrade your compute:** You can get a Compute Add-on for your project. Follow [this link](https://app.supabase.com/project/_/settings/billing/update/pro) and select your project to see your upgrade options.
+
+export const Page = ({ children }) => <Layout meta={meta} children={children} />
+
+export default Page
diff --git a/apps/docs/pages/guides/platform/logs.mdx b/apps/docs/pages/guides/platform/logs.mdx
index ad73fc5315d..95880b26fc2 100644
--- a/apps/docs/pages/guides/platform/logs.mdx
+++ b/apps/docs/pages/guides/platform/logs.mdx
@@ -112,7 +112,7 @@ To _permanently_ set a logging configuration (beyond a single session), execute
 alter role postgres set pgaudit.log to 'function, write, ddl';
 ```
 
-For user-traffic flowing through the [HTTP APIs](../../guides/database/api#rest-api-overview) powered by PostgREST, set your configuration values for the roles `anon` and `authenticated`.  For traffic using the `service_role` key, set the configuration values for the role `service_role`.
+For user-traffic flowing through the [HTTP APIs](../../guides/database/api#rest-api-overview) powered by PostgREST, set your configuration values for the roles `anon` and `authenticated`. For traffic using the `service_role` key, set the configuration values for the role `service_role`.
 
 To reset system-wide settings, execute the following, then perform a fast reboot:
 
diff --git a/apps/docs/pages/guides/platform/migrating-and-upgrading-projects.mdx b/apps/docs/pages/guides/platform/migrating-and-upgrading-projects.mdx
index 2dfa8e6bc56..0bb0f3b310a 100644
--- a/apps/docs/pages/guides/platform/migrating-and-upgrading-projects.mdx
+++ b/apps/docs/pages/guides/platform/migrating-and-upgrading-projects.mdx
@@ -12,7 +12,10 @@ In some cases, access to new features require upgrading or migrating your Supaba
 
 ## Upgrade your project
 
-<Admonition type="note">This is only available for projects on the Free plan. For projects on the Pro plan, please contact support for assistance with upgrading.</Admonition>
+<Admonition type="note">
+  This is only available for projects on the Free plan. For projects on the Pro plan, please contact
+  support for assistance with upgrading.
+</Admonition>
 
 When you pause and restore a project, the restored database includes the latest features. This method _does_ include downtime, so be aware that your project will be inaccessible for a short period of time.
 
@@ -80,7 +83,7 @@ const NEW_PROJECT_SERVICE_KEY = 'new-project-service-key-yyy'
 ;(async () => {
   const oldSupabaseRestClient = createClient(OLD_PROJECT_URL, OLD_PROJECT_SERVICE_KEY, {
     db: {
-        schema: 'storage'
+      schema: 'storage',
     },
   })
   const oldSupabaseClient = createClient(OLD_PROJECT_URL, OLD_PROJECT_SERVICE_KEY)
diff --git a/apps/docs/pages/guides/platform/spend-cap.mdx b/apps/docs/pages/guides/platform/spend-cap.mdx
index f23702e6c98..772392a8e60 100644
--- a/apps/docs/pages/guides/platform/spend-cap.mdx
+++ b/apps/docs/pages/guides/platform/spend-cap.mdx
@@ -45,8 +45,8 @@ Your project will continue to operate after using all the free quota allowance f
 This additional usage will be charged based on the line item's cost per unit outlined on the [pricing page](/pricing).
 
 <Admonition type="note">
-  When your Spend Cap is **off**, we recommend monitoring your consumption and costs using the [Usage
-  section of your project](https://app.supabase.com/project/_/settings/billing/usage) in the
+  When your Spend Cap is **off**, we recommend monitoring your consumption and costs using the
+  [Usage section of your project](https://app.supabase.com/project/_/settings/billing/usage) in the
   dashboard.
 </Admonition>
 
diff --git a/apps/docs/pages/guides/realtime/extensions/broadcast.mdx b/apps/docs/pages/guides/realtime/extensions/broadcast.mdx
index df1536ae283..6c9de742fd0 100644
--- a/apps/docs/pages/guides/realtime/extensions/broadcast.mdx
+++ b/apps/docs/pages/guides/realtime/extensions/broadcast.mdx
@@ -25,8 +25,7 @@ const supabase = createClient(process.env.SUPABASE_URL, process.env.SUPABASE_KEY
 
 const channel = supabase.channel('test')
 
-channel.on('broadcast', { event: 'supa' }, (payload) => console.log(payload))
-  .subscribe()
+channel.on('broadcast', { event: 'supa' }, (payload) => console.log(payload)).subscribe()
 ```
 
 ## Send Messages
@@ -69,7 +68,8 @@ const channel = supabase.channel('test', {
   },
 })
 
-channel.on('broadcast', { event: 'supa' }, (payload) => console.log(payload))
+channel
+  .on('broadcast', { event: 'supa' }, (payload) => console.log(payload))
   .subscribe((status) => {
     if (status === 'SUBSCRIBED') {
       channel.send({
diff --git a/apps/docs/pages/guides/realtime/extensions/postgres-changes.mdx b/apps/docs/pages/guides/realtime/extensions/postgres-changes.mdx
index aa93a0482cf..5cf3d01d1e8 100644
--- a/apps/docs/pages/guides/realtime/extensions/postgres-changes.mdx
+++ b/apps/docs/pages/guides/realtime/extensions/postgres-changes.mdx
@@ -139,9 +139,7 @@ const channel = supabase
   .subscribe()
 ```
 
-<Admonition type="note">
-  This filter uses Postgres' `=`.
-</Admonition>
+<Admonition type="note">This filter uses Postgres' `=`.</Admonition>
 
 ### neq
 
@@ -165,9 +163,7 @@ const channel = supabase
   .subscribe()
 ```
 
-<Admonition type="note">
-  This filter uses Postgres' `!=`.
-</Admonition>
+<Admonition type="note">This filter uses Postgres' `!=`.</Admonition>
 
 ### lt
 
@@ -244,7 +240,8 @@ const channel = supabase
 ```
 
 <Admonition type="note">
-  This filter uses Postgres' `>` so it works for non-numeric types but make sure to check the expected behavior of the compared data's type.
+  This filter uses Postgres' `>` so it works for non-numeric types but make sure to check the
+  expected behavior of the compared data's type.
 </Admonition>
 
 ### gte
@@ -270,7 +267,8 @@ const channel = supabase
 ```
 
 <Admonition type="note">
-  This filter uses Postgres' `>=` so it works for non-numeric types but make sure to check the expected behavior of the compared data's type.
+  This filter uses Postgres' `>=` so it works for non-numeric types but make sure to check the
+  expected behavior of the compared data's type.
 </Admonition>
 
 ### in
diff --git a/apps/docs/pages/guides/realtime/protocol.mdx b/apps/docs/pages/guides/realtime/protocol.mdx
index 488d2975612..3198403f3cb 100644
--- a/apps/docs/pages/guides/realtime/protocol.mdx
+++ b/apps/docs/pages/guides/realtime/protocol.mdx
@@ -39,7 +39,8 @@ In the initial message, the client sends a message specifying the features they
 ```
 
 <Admonition type="note">
-The `in` filter has the format `COLUMN_NAME=in.(value1,value2,value3)`. However, other filters use the format `COLUMN_NAME=FILTER_NAME.value`.
+  The `in` filter has the format `COLUMN_NAME=in.(value1,value2,value3)`. However, other filters use
+  the format `COLUMN_NAME=FILTER_NAME.value`.
 </Admonition>
 
 In response, the server sends the Postgres configuration with a unique ID. With this ID, the client should route incoming changes to the appropriate callback.
diff --git a/apps/docs/pages/guides/resources/examples.mdx b/apps/docs/pages/guides/resources/examples.mdx
index 6155462bedd..a414b43b63e 100644
--- a/apps/docs/pages/guides/resources/examples.mdx
+++ b/apps/docs/pages/guides/resources/examples.mdx
@@ -88,7 +88,7 @@ Build a basic Todo List with Supabase and your favorite frontend framework:
 - Flutter (in development): [GitHub](https://github.com/supabase/supabase-flutter)
 - Python (in development): [GitHub](https://github.com/supabase/supabase-py)
 - C# (in development): [GitHub](https://github.com/supabase/supabase-csharp)
-- Kotlin (in development): [GitHub](https://github.com/supabase-community/postgrest-kt)
+- Kotlin (in development): [GitHub](https://github.com/supabase-community/supabase-kt)
 - `useSupabase`: Supabase React Hooks. [GitHub](https://github.com/gbibeaul/use-supabase)
 - `vue-supabase`: Supabase Vue wrapper. [GitHub](https://github.com/supabase/vue-supabase)
 - `vue-3-supabase`: Supabase Vue 3 wrapper. [GitHub](https://github.com/DidoMarchet/vue-3-supabase)
diff --git a/apps/docs/pages/guides/resources/glossary.mdx b/apps/docs/pages/guides/resources/glossary.mdx
index e2e3ffdede5..44f9c6a266f 100755
--- a/apps/docs/pages/guides/resources/glossary.mdx
+++ b/apps/docs/pages/guides/resources/glossary.mdx
@@ -118,7 +118,6 @@ Single-sign on allows enterprises to centrally manage accounts and access to app
 
 A time-based one-time password is a one-time password generated at regular time intervals from a secret, usually from an application in a mobile device (e.g., Google Authenticator, 1Password).
 
-
 export const Page = ({ children }) => <Layout meta={meta} children={children} />
 
 export default Page
diff --git a/apps/docs/pages/guides/resources/migrating-to-supabase/amazon-rds.mdx b/apps/docs/pages/guides/resources/migrating-to-supabase/amazon-rds.mdx
index 6eacca05a42..a4058763fd7 100644
--- a/apps/docs/pages/guides/resources/migrating-to-supabase/amazon-rds.mdx
+++ b/apps/docs/pages/guides/resources/migrating-to-supabase/amazon-rds.mdx
@@ -5,7 +5,7 @@ export const meta = {
   description: 'Migrate your Amazon RDS MySQL or MS SQL database to Supabase Postgres database.',
 }
 
-This guide aims to exhibit the process of transferring your Amazon RDS database from any of these engines Postgres, MySQL or MS SQL to Supabase's Postgres database. Although Amazon RDS is a favored managed database service provided by AWS, it may not suffice for all use cases. Supabase, on the other hand, provides an excellent free and open source option that encompasses all the necessary backend features to develop a product: a Postgres database, authentication, instant APIs, edge functions, real-time subscriptions, and storage. 
+This guide aims to exhibit the process of transferring your Amazon RDS database from any of these engines Postgres, MySQL or MS SQL to Supabase's Postgres database. Although Amazon RDS is a favored managed database service provided by AWS, it may not suffice for all use cases. Supabase, on the other hand, provides an excellent free and open source option that encompasses all the necessary backend features to develop a product: a Postgres database, authentication, instant APIs, edge functions, real-time subscriptions, and storage.
 
 Supabase's core is Postgres, enabling the use of row-level security and providing access to over 40 Postgres extensions. By migrating from Amazon RDS to Supabase, you can leverage Postgres to its fullest potential and acquire all the features you need to complete your project.
 
@@ -33,7 +33,7 @@ Supabase's core is Postgres, enabling the use of row-level security and providin
 ## Migrate the database
 
 The fastest way to migrate your database is with the Supabase migration tool on
- [Google Colab](https://colab.research.google.com/github/mansueli/Supa-Migrate/blob/main/Amazon_RDS_to_Supabase.ipynb). 
+[Google Colab](https://colab.research.google.com/github/mansueli/Supa-Migrate/blob/main/Amazon_RDS_to_Supabase.ipynb).
 
 Alternatively, you can use [pgloader](https://github.com/dimitri/pgloader), a flexible and powerful data migration tool that supports a wide range of source database engines, including MySQL and MS SQL, and migrates the data to a Postgres database. For databases using the Postgres engine, we recommend using the pg_dump and psql command line tools, which are included in a full PostgreSQL installation.
 
@@ -47,8 +47,8 @@ Alternatively, you can use [pgloader](https://github.com/dimitri/pgloader), a fl
 
 1. Select the Dabase Engine from the Source database in the dropdown
 1. Set the environment variables (`HOST`, `USER`, `SOURCE_DB`,`PASSWORD`, `SUPABASE_URL`, and `SUPABASE_PASSWORD`) in the Colab notebook.
-2. Run the first two steps in [the notebook](https://colab.research.google.com/github/mansueli/Supa-Migrate/blob/main/Amazon_RDS_to_Supabase.ipynb) in order. The first sets engine and installs the necessary files.
-3. Run the third step to start the migration. This will take a few minutes.
+1. Run the first two steps in [the notebook](https://colab.research.google.com/github/mansueli/Supa-Migrate/blob/main/Amazon_RDS_to_Supabase.ipynb) in order. The first sets engine and installs the necessary files.
+1. Run the third step to start the migration. This will take a few minutes.
 
 </TabPanel>
 <TabPanel id="MySQL" label="Migrate from MySQL with pgloader">
@@ -57,18 +57,19 @@ Alternatively, you can use [pgloader](https://github.com/dimitri/pgloader), a fl
     Create a configuration file (e.g., config.load).
 
 ```sql
-LOAD DATABASE
-    FROM mysql://USER:PASSWORD@HOST/SOURCE_DB
-    INTO postgres://postgres:password@db.xxxx.supabase.co:6543/postgres
-ALTER SCHEMA 'public' OWNER TO 'postgres';
+load database
+  from mysql://user:password@host/source_db
+  into postgres://postgres:password@db.xxxx.supabase.co:6543/postgres
+alter schema 'public' owner to 'postgres';
 set wal_buffers = '64MB', max_wal_senders = 0, statement_timeout = 0, work_mem to '2GB';
-````
+```
 
 ##Run the migration with pgloader
 
 ```bash
 pgloader config.load
 ```
+
 </TabPanel>
 <TabPanel id="MS SQL" label="Migrate from MSSQL">
 
@@ -81,13 +82,14 @@ LOAD DATABASE
     INTO postgres://postgres:password@db.xxxx.supabase.co:6543/postgres
 ALTER SCHEMA 'public' OWNER TO 'postgres';
 set wal_buffers = '64MB', max_wal_senders = 0, statement_timeout = 0, work_mem to '2GB';
-````
+```
 
 ##Run the migration with pgloader
 
 ```bash
 pgloader config.load
 ```
+
 </TabPanel>
 </Tabs>
 
diff --git a/apps/docs/pages/guides/storage/cdn.mdx b/apps/docs/pages/guides/storage/cdn.mdx
index f0b23340130..b32bd30ac66 100644
--- a/apps/docs/pages/guides/storage/cdn.mdx
+++ b/apps/docs/pages/guides/storage/cdn.mdx
@@ -42,7 +42,6 @@ Note that CDNs might still evict your object from their cache if it has not been
 
 The cache status of a particular request is sent in the `cf-cache-status` header. A cache status of `MISS` indicates that the CDN node did not have the object in its cache and had to ping the origin to get it. A cache status of `HIT` indicates that the object was sent directly from the CDN.
 
-
 ## Smart CDN Caching
 
 <Admonition type="note">
diff --git a/apps/docs/pages/guides/storage/image-transformations.mdx b/apps/docs/pages/guides/storage/image-transformations.mdx
index 49c4b370d5c..dd2893b958b 100644
--- a/apps/docs/pages/guides/storage/image-transformations.mdx
+++ b/apps/docs/pages/guides/storage/image-transformations.mdx
@@ -77,7 +77,7 @@ For instance, if you use Chrome when viewing a jpeg image and using transformati
 As a result, this will lower the bandwidth that you send to your users and your application will load much faster.
 
 <Admonition type="note">
-    We currently only support WebP. AVIF support will come in the near future
+  We currently only support WebP. AVIF support will come in the near future
 </Admonition>
 
 **Disabling automatic optimisation:**
@@ -87,11 +87,11 @@ this is also supported in the JavaScript SDK starting from v2.2.0
 
 ```ts
 await storage.from('bucket').download('image.jpeg', {
-      transform: {
-        width: 200,
-        height: 200,
-        format: 'origin',
-      },
+  transform: {
+    width: 200,
+    height: 200,
+    format: 'origin',
+  },
 })
 ```
 
@@ -105,7 +105,9 @@ To get started, create a `supabase-image-loader.js` file in your NextJS project
 const projectId = '' // your supabase project id
 
 export default function supabaseLoader({ src, width, quality }) {
-  return `https://${projectId}.supabase.co/storage/v1/render/image/public/${src}?width=${width}&quality=${quality || 75}`
+  return `https://${projectId}.supabase.co/storage/v1/render/image/public/${src}?width=${width}&quality=${
+    quality || 75
+  }`
 }
 ```
 
@@ -193,11 +195,11 @@ Under the hood we use the awesome [Imgproxy](https://imgproxy.net/)
 Simply deploy an imgproxy container with the following configuration:
 
 ```yaml
-  imgproxy:
-    image: darthsim/imgproxy
-    environment:
-      - IMGPROXY_ENABLE_WEBP_DETECTION=true
-      - IMGPROXY_JPEG_PROGRESSIVE=true
+imgproxy:
+  image: darthsim/imgproxy
+  environment:
+    - IMGPROXY_ENABLE_WEBP_DETECTION=true
+    - IMGPROXY_JPEG_PROGRESSIVE=true
 ```
 
 Note: make sure that this service can only be reachable within an internal network and not exposed to the public internet
diff --git a/apps/docs/pages/reference/api/[...slug].tsx b/apps/docs/pages/reference/api/[...slug].tsx
index ca4c7128256..1850b2bc2b9 100644
--- a/apps/docs/pages/reference/api/[...slug].tsx
+++ b/apps/docs/pages/reference/api/[...slug].tsx
@@ -20,5 +20,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/cli/[...slug].tsx b/apps/docs/pages/reference/cli/[...slug].tsx
index 1fe46fa04a9..77aeb32c110 100644
--- a/apps/docs/pages/reference/cli/[...slug].tsx
+++ b/apps/docs/pages/reference/cli/[...slug].tsx
@@ -19,5 +19,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/csharp/[...slug].tsx b/apps/docs/pages/reference/csharp/[...slug].tsx
index c3ba488e1b1..7663a67ca86 100644
--- a/apps/docs/pages/reference/csharp/[...slug].tsx
+++ b/apps/docs/pages/reference/csharp/[...slug].tsx
@@ -17,5 +17,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/csharp/crawlers/[...slug].tsx b/apps/docs/pages/reference/csharp/crawlers/[...slug].tsx
index fc03fefa015..4aa2010fc26 100644
--- a/apps/docs/pages/reference/csharp/crawlers/[...slug].tsx
+++ b/apps/docs/pages/reference/csharp/crawlers/[...slug].tsx
@@ -40,5 +40,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/csharp/v0/[...slug].tsx b/apps/docs/pages/reference/csharp/v0/[...slug].tsx
index f8a6e985d1e..c55c751c354 100644
--- a/apps/docs/pages/reference/csharp/v0/[...slug].tsx
+++ b/apps/docs/pages/reference/csharp/v0/[...slug].tsx
@@ -17,5 +17,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/csharp/v0/crawlers/[...slug].tsx b/apps/docs/pages/reference/csharp/v0/crawlers/[...slug].tsx
index 18ee28ca14f..3777e16ec70 100644
--- a/apps/docs/pages/reference/csharp/v0/crawlers/[...slug].tsx
+++ b/apps/docs/pages/reference/csharp/v0/crawlers/[...slug].tsx
@@ -39,5 +39,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/dart/[...slug].tsx b/apps/docs/pages/reference/dart/[...slug].tsx
index b452d04d84f..fb39f9d64cc 100644
--- a/apps/docs/pages/reference/dart/[...slug].tsx
+++ b/apps/docs/pages/reference/dart/[...slug].tsx
@@ -17,5 +17,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/dart/crawlers/[...slug].tsx b/apps/docs/pages/reference/dart/crawlers/[...slug].tsx
index 29a9f880840..21c5d52b18a 100644
--- a/apps/docs/pages/reference/dart/crawlers/[...slug].tsx
+++ b/apps/docs/pages/reference/dart/crawlers/[...slug].tsx
@@ -40,5 +40,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/dart/v0/[...slug].tsx b/apps/docs/pages/reference/dart/v0/[...slug].tsx
index b30b791db60..8cee39483e0 100644
--- a/apps/docs/pages/reference/dart/v0/[...slug].tsx
+++ b/apps/docs/pages/reference/dart/v0/[...slug].tsx
@@ -17,5 +17,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/dart/v0/crawlers/[...slug].tsx b/apps/docs/pages/reference/dart/v0/crawlers/[...slug].tsx
index 1c2949b24a7..f43ccb6a732 100644
--- a/apps/docs/pages/reference/dart/v0/crawlers/[...slug].tsx
+++ b/apps/docs/pages/reference/dart/v0/crawlers/[...slug].tsx
@@ -39,5 +39,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/javascript/[...slug].tsx b/apps/docs/pages/reference/javascript/[...slug].tsx
index 24b8a0011ed..f8cba67d8b9 100644
--- a/apps/docs/pages/reference/javascript/[...slug].tsx
+++ b/apps/docs/pages/reference/javascript/[...slug].tsx
@@ -1,4 +1,3 @@
-import { inspect } from 'util'
 import clientLibsCommonSections from '~/../../spec/common-client-libs-sections.json'
 import typeSpec from '~/../../spec/enrichments/tsdoc_v2/combined.json'
 import spec from '~/../../spec/supabase_js_v2.yml' assert { type: 'yml' }
@@ -27,5 +26,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/javascript/crawlers/[...slug].tsx b/apps/docs/pages/reference/javascript/crawlers/[...slug].tsx
index 658469669d1..15bc700d40f 100644
--- a/apps/docs/pages/reference/javascript/crawlers/[...slug].tsx
+++ b/apps/docs/pages/reference/javascript/crawlers/[...slug].tsx
@@ -40,5 +40,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/javascript/v1/[...slug].tsx b/apps/docs/pages/reference/javascript/v1/[...slug].tsx
index 364b3e667ac..95a578fc559 100644
--- a/apps/docs/pages/reference/javascript/v1/[...slug].tsx
+++ b/apps/docs/pages/reference/javascript/v1/[...slug].tsx
@@ -27,5 +27,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/javascript/v1/crawlers/[...slug].tsx b/apps/docs/pages/reference/javascript/v1/crawlers/[...slug].tsx
index d040ffa7ec5..37fb218f804 100644
--- a/apps/docs/pages/reference/javascript/v1/crawlers/[...slug].tsx
+++ b/apps/docs/pages/reference/javascript/v1/crawlers/[...slug].tsx
@@ -40,5 +40,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/kotlin/[...slug].tsx b/apps/docs/pages/reference/kotlin/[...slug].tsx
new file mode 100644
index 00000000000..dfce2170a7b
--- /dev/null
+++ b/apps/docs/pages/reference/kotlin/[...slug].tsx
@@ -0,0 +1,21 @@
+import clientLibsCommonSections from '~/../../spec/common-client-libs-sections.json'
+import spec from '~/../../spec/supabase_kt_v0.yml' assert { type: 'yml' }
+import RefSectionHandler from '~/components/reference/RefSectionHandler'
+import { flattenSections } from '~/lib/helpers'
+import handleRefGetStaticPaths from '~/lib/mdx/handleRefStaticPaths'
+import handleRefStaticProps from '~/lib/mdx/handleRefStaticProps'
+
+const sections = flattenSections(clientLibsCommonSections)
+const libraryPath = '/kotlin'
+
+export default function KotlinReference(props) {
+  return <RefSectionHandler sections={sections} spec={spec} pageProps={props} type="client-lib" />
+}
+
+export async function getStaticProps() {
+  return handleRefStaticProps(sections, libraryPath)
+}
+
+export async function getStaticPaths() {
+  return handleRefGetStaticPaths(sections)
+}
diff --git a/apps/docs/pages/reference/kotlin/crawlers/[...slug].tsx b/apps/docs/pages/reference/kotlin/crawlers/[...slug].tsx
new file mode 100644
index 00000000000..e6a69bf155f
--- /dev/null
+++ b/apps/docs/pages/reference/kotlin/crawlers/[...slug].tsx
@@ -0,0 +1,44 @@
+import clientLibsCommonSections from '~/../../spec/common-client-libs-sections.json'
+import typeSpec from '~/../../spec/enrichments/tsdoc_v2/combined.json'
+import spec from '~/../../spec/supabase_kt_v0.yml' assert { type: 'yml' }
+import RefSectionHandler from '~/components/reference/RefSectionHandler'
+import { flattenSections } from '~/lib/helpers'
+import handleRefGetStaticPaths from '~/lib/mdx/handleRefStaticPaths'
+import handleRefStaticProps from '~/lib/mdx/handleRefStaticProps'
+import { useRouter } from 'next/router'
+import RefSEO from '~/components/reference/RefSEO'
+
+const sections = flattenSections(clientLibsCommonSections)
+const libraryPath = '/kotlin'
+
+export default function KotlinReference(props) {
+  const router = useRouter()
+  const slug = router.query.slug[0]
+  const filteredSection = sections.filter((section) => section.id === slug)
+
+  const pageTitle = filteredSection[0]?.title
+    ? `${filteredSection[0]?.title} | Supabase`
+    : 'Supabase'
+
+  return (
+    <>
+      <RefSEO title={pageTitle} />
+
+      <RefSectionHandler
+        sections={filteredSection}
+        spec={spec}
+        typeSpec={typeSpec}
+        pageProps={props}
+        type="client-lib"
+      />
+    </>
+  )
+}
+
+export async function getStaticProps() {
+  return handleRefStaticProps(sections, libraryPath)
+}
+
+export async function getStaticPaths() {
+  return handleRefGetStaticPaths(sections)
+}
diff --git a/apps/docs/pages/reference/kotlin/v0/[...slug].tsx b/apps/docs/pages/reference/kotlin/v0/[...slug].tsx
new file mode 100644
index 00000000000..81ec54b2efe
--- /dev/null
+++ b/apps/docs/pages/reference/kotlin/v0/[...slug].tsx
@@ -0,0 +1,21 @@
+import clientLibsCommonSections from '~/../../spec/common-client-libs-sections.json'
+import spec from '~/../../spec/supabase_kt_v0.yml' assert { type: 'yml' }
+import RefSectionHandler from '~/components/reference/RefSectionHandler'
+import { flattenSections } from '~/lib/helpers'
+import handleRefGetStaticPaths from '~/lib/mdx/handleRefStaticPaths'
+import handleRefStaticProps from '~/lib/mdx/handleRefStaticProps'
+
+const sections = flattenSections(clientLibsCommonSections)
+const libraryPath = '/kotlin/v0'
+
+export default function KotlinReference(props) {
+  return <RefSectionHandler sections={sections} spec={spec} pageProps={props} type="client-lib" />
+}
+
+export async function getStaticProps() {
+  return handleRefStaticProps(sections, libraryPath)
+}
+
+export async function getStaticPaths() {
+  return handleRefGetStaticPaths(sections)
+}
diff --git a/apps/docs/pages/reference/kotlin/v0/crawlers/[...slug].tsx b/apps/docs/pages/reference/kotlin/v0/crawlers/[...slug].tsx
new file mode 100644
index 00000000000..0bb3a187cc3
--- /dev/null
+++ b/apps/docs/pages/reference/kotlin/v0/crawlers/[...slug].tsx
@@ -0,0 +1,43 @@
+import clientLibsCommonSections from '~/../../spec/common-client-libs-sections.json'
+import typeSpec from '~/../../spec/enrichments/tsdoc_v2/combined.json'
+import spec from '~/../../spec/supabase_kt_v0.yml' assert { type: 'yml' }
+import RefSectionHandler from '~/components/reference/RefSectionHandler'
+import { flattenSections } from '~/lib/helpers'
+import handleRefGetStaticPaths from '~/lib/mdx/handleRefStaticPaths'
+import handleRefStaticProps from '~/lib/mdx/handleRefStaticProps'
+import { useRouter } from 'next/router'
+import RefSEO from '~/components/reference/RefSEO'
+
+const sections = flattenSections(clientLibsCommonSections)
+const libraryPath = '/kotlin/v0'
+
+export default function KotlinReference(props) {
+  const router = useRouter()
+  const slug = router.query.slug[0]
+  const filteredSection = sections.filter((section) => section.id === slug)
+
+  const pageTitle = filteredSection[0]?.title
+    ? `${filteredSection[0]?.title} | Supabase`
+    : 'Supabase'
+  return (
+    <>
+      <RefSEO title={pageTitle} />
+
+      <RefSectionHandler
+        sections={filteredSection}
+        spec={spec}
+        typeSpec={typeSpec}
+        pageProps={props}
+        type="client-lib"
+      />
+    </>
+  )
+}
+
+export async function getStaticProps() {
+  return handleRefStaticProps(sections, libraryPath)
+}
+
+export async function getStaticPaths() {
+  return handleRefGetStaticPaths(sections)
+}
diff --git a/apps/docs/pages/reference/python/[...slug].tsx b/apps/docs/pages/reference/python/[...slug].tsx
index 3da995dd993..708880602dc 100644
--- a/apps/docs/pages/reference/python/[...slug].tsx
+++ b/apps/docs/pages/reference/python/[...slug].tsx
@@ -26,5 +26,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/python/crawlers/[...slug].tsx b/apps/docs/pages/reference/python/crawlers/[...slug].tsx
index ca70d55716f..9c1062483db 100644
--- a/apps/docs/pages/reference/python/crawlers/[...slug].tsx
+++ b/apps/docs/pages/reference/python/crawlers/[...slug].tsx
@@ -40,5 +40,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/self-hosting-analytics/[...slug].tsx b/apps/docs/pages/reference/self-hosting-analytics/[...slug].tsx
index 46827290444..cafb0359aac 100644
--- a/apps/docs/pages/reference/self-hosting-analytics/[...slug].tsx
+++ b/apps/docs/pages/reference/self-hosting-analytics/[...slug].tsx
@@ -21,5 +21,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/self-hosting-auth/[...slug].tsx b/apps/docs/pages/reference/self-hosting-auth/[...slug].tsx
index 27e8a909182..c2c58cd7dbe 100644
--- a/apps/docs/pages/reference/self-hosting-auth/[...slug].tsx
+++ b/apps/docs/pages/reference/self-hosting-auth/[...slug].tsx
@@ -21,5 +21,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/self-hosting-functions/[...slug].tsx b/apps/docs/pages/reference/self-hosting-functions/[...slug].tsx
index 5d01436b310..97e10d09a18 100644
--- a/apps/docs/pages/reference/self-hosting-functions/[...slug].tsx
+++ b/apps/docs/pages/reference/self-hosting-functions/[...slug].tsx
@@ -18,5 +18,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/self-hosting-realtime/[...slug].tsx b/apps/docs/pages/reference/self-hosting-realtime/[...slug].tsx
index c5039628929..fbfec623fd2 100644
--- a/apps/docs/pages/reference/self-hosting-realtime/[...slug].tsx
+++ b/apps/docs/pages/reference/self-hosting-realtime/[...slug].tsx
@@ -17,5 +17,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/self-hosting-storage/[...slug].tsx b/apps/docs/pages/reference/self-hosting-storage/[...slug].tsx
index 7e55171583e..6db23fa3a33 100644
--- a/apps/docs/pages/reference/self-hosting-storage/[...slug].tsx
+++ b/apps/docs/pages/reference/self-hosting-storage/[...slug].tsx
@@ -21,5 +21,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/swift/[...slug].tsx b/apps/docs/pages/reference/swift/[...slug].tsx
index 22cb67c6f98..c084744e8ab 100644
--- a/apps/docs/pages/reference/swift/[...slug].tsx
+++ b/apps/docs/pages/reference/swift/[...slug].tsx
@@ -17,5 +17,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/swift/crawlers/[...slug].tsx b/apps/docs/pages/reference/swift/crawlers/[...slug].tsx
index f88e25b8997..4c848be8b09 100644
--- a/apps/docs/pages/reference/swift/crawlers/[...slug].tsx
+++ b/apps/docs/pages/reference/swift/crawlers/[...slug].tsx
@@ -40,5 +40,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/swift/v0/[...slug].tsx b/apps/docs/pages/reference/swift/v0/[...slug].tsx
index cdf3662f63b..4abf2725ad9 100644
--- a/apps/docs/pages/reference/swift/v0/[...slug].tsx
+++ b/apps/docs/pages/reference/swift/v0/[...slug].tsx
@@ -17,5 +17,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/pages/reference/swift/v0/crawlers/[...slug].tsx b/apps/docs/pages/reference/swift/v0/crawlers/[...slug].tsx
index bf3bc4bc449..d2172b6e739 100644
--- a/apps/docs/pages/reference/swift/v0/crawlers/[...slug].tsx
+++ b/apps/docs/pages/reference/swift/v0/crawlers/[...slug].tsx
@@ -39,5 +39,5 @@ export async function getStaticProps() {
 }
 
 export async function getStaticPaths() {
-  return handleRefGetStaticPaths(sections, libraryPath)
+  return handleRefGetStaticPaths(sections)
 }
diff --git a/apps/docs/public/img/guides/auth-captcha/cloudflare_settings.png b/apps/docs/public/img/guides/auth-captcha/cloudflare_settings.png
new file mode 100644
index 00000000000..d3387436240
Binary files /dev/null and b/apps/docs/public/img/guides/auth-captcha/cloudflare_settings.png differ
diff --git a/apps/docs/public/img/guides/platform/exhaust-cpu-report.png b/apps/docs/public/img/guides/platform/exhaust-cpu-report.png
new file mode 100644
index 00000000000..8d62afb6de1
Binary files /dev/null and b/apps/docs/public/img/guides/platform/exhaust-cpu-report.png differ
diff --git a/apps/docs/public/img/icons/menu/reference-kotlin-light.svg b/apps/docs/public/img/icons/menu/reference-kotlin-light.svg
new file mode 100644
index 00000000000..fb441330f2a
--- /dev/null
+++ b/apps/docs/public/img/icons/menu/reference-kotlin-light.svg
@@ -0,0 +1,6 @@
+<svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
+	 viewBox="0 0 500 500" style="enable-background:new 0 0 500 500;" xml:space="preserve">
+<g id="Logotypes">
+	<polygon points="500,500 0,500 0,0 500,0 250,250 	"/>
+</g>
+</svg>
diff --git a/apps/docs/public/img/icons/menu/reference-kotlin.svg b/apps/docs/public/img/icons/menu/reference-kotlin.svg
new file mode 100644
index 00000000000..00c834f31a1
--- /dev/null
+++ b/apps/docs/public/img/icons/menu/reference-kotlin.svg
@@ -0,0 +1,9 @@
+<svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
+	 viewBox="0 0 500 500" style="enable-background:new 0 0 500 500;" xml:space="preserve">
+<style type="text/css">
+	.st0{fill:#FFFFFF;}
+</style>
+<g id="Logotypes">
+	<polygon class="st0" points="500,500 0,500 0,0 500,0 250,250 	"/>
+</g>
+</svg>
diff --git a/apps/docs/scripts/search/sources/index.ts b/apps/docs/scripts/search/sources/index.ts
index fff7bc00799..8b3fce5bbdb 100644
--- a/apps/docs/scripts/search/sources/index.ts
+++ b/apps/docs/scripts/search/sources/index.ts
@@ -68,6 +68,14 @@ export async function fetchSources() {
     '../../spec/common-client-libs-sections.json'
   )
 
+  const ktLibReferenceSource = new ClientLibReferenceSource(
+    'kt-lib',
+    '/reference/kotlin',
+    { title: 'Kotlin Reference' },
+    '../../spec/supabase_kt_v0.yml',
+    '../../spec/common-client-libs-sections.json'
+  )
+
   const cliReferenceSource = new CliReferenceSource(
     'cli',
     '/reference/cli',
@@ -96,6 +104,7 @@ export async function fetchSources() {
     pythonLibReferenceSource,
     cSharpLibReferenceSource,
     swiftLibReferenceSource,
+    ktLibReferenceSource,
     cliReferenceSource,
     ...githubDiscussionSources,
     ...guideSources,
diff --git a/apps/docs/styles/main.scss b/apps/docs/styles/main.scss
index 6f627fe2991..1c60d4f3100 100644
--- a/apps/docs/styles/main.scss
+++ b/apps/docs/styles/main.scss
@@ -64,7 +64,7 @@ article h1 {
 
 .table-of-contents-height {
   max-height: calc(100vh - 3.75rem - 2rem);
-  top: calc(3.75rem + 1rem);
+  top: calc(4rem + 60px); // padding height + navbar height
 }
 
 .width-full {
diff --git a/apps/www/_blog/2020-07-09-postgresql-templates.mdx b/apps/www/_blog/2020-07-09-postgresql-templates.mdx
index e0908248c7f..2a820e50eab 100644
--- a/apps/www/_blog/2020-07-09-postgresql-templates.mdx
+++ b/apps/www/_blog/2020-07-09-postgresql-templates.mdx
@@ -17,7 +17,7 @@ Whenever you create a new database in Postgres, you are actually [basing it off
 This database, `template1`, and another, called `template0`, are standard system databases that exist in every newly created database cluster. Don't believe me? Why not quickly [spin up a database](/docs/postgres/server/about) and see it for yourself with this query:
 
 ```sql
-SELECT * FROM pg_database;
+select * from pg_database;
 ```
 
 In this post, we'll explore these template databases and see how we can make full use of their potential. We'll even look into creating a template database of our own.
diff --git a/apps/www/_blog/2020-11-18-postgresql-views.mdx b/apps/www/_blog/2020-11-18-postgresql-views.mdx
index 8f20842d9c6..81bdf493a8f 100644
--- a/apps/www/_blog/2020-11-18-postgresql-views.mdx
+++ b/apps/www/_blog/2020-11-18-postgresql-views.mdx
@@ -54,13 +54,14 @@ Creating a view consisting of all the three tables will look like this:
 
 ```sql
 create view transcripts as
-    select
-        students.name,
-        students.type,
-        courses.title,
-        courses.code,
-        grades.result
-    from grades
+  select
+    students.name,
+    students.type,
+    courses.title,
+    courses.code,
+    grades.result
+  from
+    grades
     left join students on grades.student_id = students.id
     left join courses on grades.course_id = courses.id;
 ```
@@ -88,14 +89,15 @@ As a query becomes complex it becomes a hassle to call it. Especially when we ru
 
 ```sql
 select
-    students.name,
-    students.type,
-    courses.title,
-    courses.code,
-    grades.result
-from grades
-left join students on grades.student_id = students.id
-left join courses on grades.course_id = courses.id;
+  students.name,
+  students.type,
+  courses.title,
+  courses.code,
+  grades.result
+from
+  grades
+  left join students on grades.student_id = students.id
+  left join courses on grades.course_id = courses.id;
 ```
 
 We can run this instead:
@@ -112,14 +114,15 @@ Views ensure that the likelihood of mistakes decreases when repeatedly executing
 
 ```sql
 select
-    students.name,
-    students.type,
-    courses.title,
-    courses.code,
-    grades.result
-from grades
-    left join students on grades.student_id = students.id
-    left join courses on grades.course_id = courses.id
+  students.name,
+  students.type,
+  courses.title,
+  courses.code,
+  grades.result
+from
+  grades
+  left join students on grades.student_id = students.id
+  left join courses on grades.course_id = courses.id
 where courses.code != 'PG101';
 ```
 
@@ -143,13 +146,14 @@ Using our example above, a materialized view can be created like this:
 
 ```sql
 create materialized view transcripts as
-    select
-        students.name,
-        students.type,
-        courses.title,
-        courses.code,
-        grades.result
-    from grades
+  select
+    students.name,
+    students.type,
+    courses.title,
+    courses.code,
+    grades.result
+  from
+    grades
     left join students on grades.student_id = students.id
     left join courses on grades.course_id = courses.id;
 ```
diff --git a/apps/www/_blog/2021-02-27-cracking-postgres-interview.mdx b/apps/www/_blog/2021-02-27-cracking-postgres-interview.mdx
index 9e83a52bb99..dbdc69fc6ee 100644
--- a/apps/www/_blog/2021-02-27-cracking-postgres-interview.mdx
+++ b/apps/www/_blog/2021-02-27-cracking-postgres-interview.mdx
@@ -29,9 +29,10 @@ A review of [database normalization](https://ocw.mit.edu/courses/civil-and-envir
 
 Postgres has tons of useful types beyond the basics, knowing how to use them will show you can leverage the true power of Postgres. JSONB for example can be incredibly useful for storing non-structured data, which you can query using syntax like:
 
+{/* prettier-ignore */}
 ```sql
 -- grades = {'geography': 'A', 'history': 'B', 'postgres': 'A++'}
-SELECT * FROM students WHERE grades->>'geography' = 'A';
+select * from students where grades->>'geography' = 'A';
 ```
 
 ### Know about namespacing with SCHEMAs
@@ -47,8 +48,7 @@ The art of indexing in Postgres could fill an entire book. In some circumstances
 An index can be simple, for example, if your students table is most frequently queried on surname alone, you create an index:
 
 ```sql
-CREATE INDEX idx_students_surname
-ON students(surname);
+create index idx_students_surname on students (surname);
 ```
 
 The default index type used here is `btree` (you could have specified this as `USING btree`), but there are other types of indexes, such as `BRIN`, `GiST`, `GIN`, `hash`, and more. Readers wanting to go deeper may also want to explore [Partial](https://www.postgresql.org/docs/current/indexes-partial.html) or [Multicolumn](https://www.postgresql.org/docs/13/indexes-multicolumn.html) Indexes.
@@ -139,17 +139,18 @@ Whilst PL/pgSQL does have [loops](https://www.postgresql.org/docs/current/plpgsq
 
 Common table expressions are temporary or intermediate result sets. They can make your queries more readable and even enable recursion. The typical form is:
 
+{/* prettier-ignore */}
 ```sql
-WITH ten_strumpers AS (
-    SELECT id, first_name
-    FROM students
-    WHERE surname = 'Strumper'
-    ORDER BY first_name
-    LIMIT 10
+with ten_strumpers as (
+  select id, first_name
+  from students
+  where surname = 'Strumper'
+  order by first_name
+  limit 10
 )
-SELECT id
-FROM ten_strumpers
-WHERE first_name LIKE "S%";
+select id
+from ten_strumpers
+where first_name like "S%";
 ```
 
 If you can reason about most of the topics in this post then you'll be in a very strong position to impress with your answers to PostgreSQL interview questions. As with all programming topics however, the real learning starts when you put these things into practice. At Supabase we offer a very very fast (the fastest?) way to spin up a PostgreSQL database and start querying it, and our browser based SQL editor is getting more powerful every day.
diff --git a/apps/www/_blog/2021-03-05-postgres-as-a-cron-server.mdx b/apps/www/_blog/2021-03-05-postgres-as-a-cron-server.mdx
index c879a5ca8cb..307339e3a02 100644
--- a/apps/www/_blog/2021-03-05-postgres-as-a-cron-server.mdx
+++ b/apps/www/_blog/2021-03-05-postgres-as-a-cron-server.mdx
@@ -120,7 +120,7 @@ from
     'https://webhook.site/223c8a43-725b-4cbd-b1fe-d0da73353a6b', -- webhook URL
     '{"hello": "world"}', -- payload
     'application/json'
-  )
+  );
 ```
 
 #### Scheduling the job
@@ -176,6 +176,7 @@ select * from cron.job_run_details;
 
 To stop a running cron job, you can run:
 
+{/* prettier-ignore */}
 ```sql
 select cron.unschedule('webhook-every-minute'); -- pass the name of the cron job
 ```
diff --git a/apps/www/_blog/2021-03-30-supabase-storage.mdx b/apps/www/_blog/2021-03-30-supabase-storage.mdx
index bea3afbfb2d..ad9b96c392d 100644
--- a/apps/www/_blog/2021-03-30-supabase-storage.mdx
+++ b/apps/www/_blog/2021-03-30-supabase-storage.mdx
@@ -13,10 +13,9 @@ date: '03-30-2021'
 <div className="bg-gray-300 rounded-lg px-6 py-2 italic">
 
 🆕 Storage has undergone significant enhancements with two major releases since its initial launch. Here is what is new:
-	
-	- [Supabase Storage v2: Image resizing and Smart CDN](https://supabase.com/blog/storage-image-resizing-smart-cdn)
-	- [Supabase Storage v3: Resumable Uploads with support for 50GB files](https://supabase.com/blog/storage-v3-resumable-uploads)
 
+- [Supabase Storage v2: Image resizing and Smart CDN](https://supabase.com/blog/storage-image-resizing-smart-cdn)
+- [Supabase Storage v3: Resumable Uploads with support for 50GB files](https://supabase.com/blog/storage-v3-resumable-uploads)
 
 </div>
 
@@ -165,8 +164,8 @@ You may be itching to get started tinkering around with our new Supabase storage
 ## What's next
 
 - We currently support S3 and will be adding more storage backends. Vote for the storage backends you would like to see us implement [here](https://github.com/supabase/supabase/discussions/982).
-- We will integrate our storage service with a Content Delivery Network. With a CDN, objects are cached on a global network. This leads to faster access times for your users around the world. **SHIPPED: [Supabase Storage v2: Image resizing and Smart CDN](https://supabase.com/blog/storage-image-resizing-smart-cdn#smart-cdn)
-- We are working on transformations like resizing of images and automatic optimization of different media types. This makes it easy to embed Supabase objects directly in your websites and mobile applications without additional processing. **SHIPPED: [Supabase Storage v2: Image resizing and Smart CDN](https://supabase.com/blog/storage-image-resizing-smart-cdn#image-resizing)
+- We will integrate our storage service with a Content Delivery Network. With a CDN, objects are cached on a global network. This leads to faster access times for your users around the world. \*\*SHIPPED: [Supabase Storage v2: Image resizing and Smart CDN](https://supabase.com/blog/storage-image-resizing-smart-cdn#smart-cdn)
+- We are working on transformations like resizing of images and automatic optimization of different media types. This makes it easy to embed Supabase objects directly in your websites and mobile applications without additional processing. \*\*SHIPPED: [Supabase Storage v2: Image resizing and Smart CDN](https://supabase.com/blog/storage-image-resizing-smart-cdn#image-resizing)
 - A better editor to make authoring policies easier and less error prone.
 - Reach out to us if you would like to help out with adding storage support in one of the [community maintained client libraries](/docs/reference/javascript/installing).
 
diff --git a/apps/www/_blog/2021-11-28-whats-new-in-postgres-14.mdx b/apps/www/_blog/2021-11-28-whats-new-in-postgres-14.mdx
index 8f6b15351da..3aa4704e6eb 100644
--- a/apps/www/_blog/2021-11-28-whats-new-in-postgres-14.mdx
+++ b/apps/www/_blog/2021-11-28-whats-new-in-postgres-14.mdx
@@ -59,7 +59,7 @@ To store sensor reading metric data, create a table consisting of the sensor des
 create table sensor_range (
   reading_id serial primary key,
   metric_desc varchar(100),
-  metric_level  valid_levels,
+  metric_level valid_levels,
   metric_ts tsmultirange
 );
 ```
@@ -67,27 +67,23 @@ create table sensor_range (
 Now, insert some data into the table. Note that, the insert statement below provides two time ranges that are not contiguous.
 
 ```sql hideCopy
-insert into sensor_range (
-  metric_desc,
-  metric_level,
-  metric_ts
-)
-values (
-  'Temperature',
-  'high',
-  '{[2021-11-01 6:00, 2021-11-01 10:00],[2021-11-05 14:00, 2021-11-05 20:00]}'
-);
+insert into sensor_range
+  (metric_desc, metric_level, metric_ts)
+values
+  (
+    'Temperature',
+    'high',
+    '{[2021-11-01 6:00, 2021-11-01 10:00],[2021-11-05 14:00, 2021-11-05 20:00]}'
+  );
 
-insert into sensor_range (
-  metric_desc,
-  metric_level,
-  metric_ts
-)
-values (
-  'Temperature',
-  'low',
-  '{[2021-11-01 10:00, 2021-11-01 12:00],[2021-11-05 21:00, 2021-11-05 22:00]}'
-);
+insert into sensor_range
+  (metric_desc, metric_level, metric_ts)
+values
+  (
+    'Temperature',
+    'low',
+    '{[2021-11-01 10:00, 2021-11-01 12:00],[2021-11-05 21:00, 2021-11-05 22:00]}'
+  );
 ```
 
 Query the data in the table to see the inserted data rows
diff --git a/apps/www/_blog/2021-11-30-supabase-studio.mdx b/apps/www/_blog/2021-11-30-supabase-studio.mdx
index a51cf705d29..4b779b905c9 100644
--- a/apps/www/_blog/2021-11-30-supabase-studio.mdx
+++ b/apps/www/_blog/2021-11-30-supabase-studio.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Supabase Studio"
+title: 'Supabase Studio'
 description: "The same Dashboard that you're using on our Platform is now available for local development and Self-Hosting."
 author: paul_copplestone
 author_url: https://github.com/kiwicopple
@@ -15,26 +15,26 @@ date: '2021-11-30'
 toc_depth: 2
 ---
 
-Today we're releasing [Supabase Studio](https://github.com/supabase/supabase/tree/master/studio). 
-The same Dashboard that you're using on our Platform is now available for [Local Development](https://supabase.com/docs/guides/local-development) 
+Today we're releasing [Supabase Studio](https://github.com/supabase/supabase/tree/master/studio).
+The same Dashboard that you're using on our Platform is now available for [Local Development](https://supabase.com/docs/guides/local-development)
 and [Self-Hosting](https://supabase.com/docs/guides/hosting/overview).
 
 ## Background
 
 Let's get the obvious question out of the way - why wasn't it already open source?
 
-When Ant and I started Supabase the codebase was one large monorepo which contained everything from the dashboard to cloud infrastructure code to experimental code. 
+When Ant and I started Supabase the codebase was one large monorepo which contained everything from the dashboard to cloud infrastructure code to experimental code.
 This is our preferred development setup - we like to keep all code in one place so that we have a single source of truth and tightly coupled CI workflows.
 
 The original Dashboard really wasn't much except a couple of buttons which allowed our Alpha users to start and stop a Supabase project - back then only a PostgreSQL connection string.
 
-Then time went on, and we started gaining traction - a lot faster than expected. 
-The nice thing about building for developers is that they are very vocal about the features they want to see next. 
+Then time went on, and we started gaining traction - a lot faster than expected.
+The nice thing about building for developers is that they are very vocal about the features they want to see next.
 And so we kept shipping - a SQL editor, a Table view, User management, auto-generated Docs, and everything else you can find on the Dashboard today.
 
-We've been planning to make the Dashboard public for a long time now, starting with [Supabase UI](https://ui.supabase.com/), 
-[`supabase/grid`](https://github.com/supabase/grid), and a standalone [PR](https://github.com/supabase/supabase/pull/2281) for Supabase Studio. 
-But as feature requests kept rolling in it became a Sisyphean task to maintain separate code bases. 
+We've been planning to make the Dashboard public for a long time now, starting with [Supabase UI](https://ui.supabase.com/),
+[`supabase/grid`](https://github.com/supabase/grid), and a standalone [PR](https://github.com/supabase/supabase/pull/2281) for Supabase Studio.
+But as feature requests kept rolling in it became a Sisyphean task to maintain separate code bases.
 
 After the last Launch Week, we decided to prioritize the Studio.
 
@@ -46,22 +46,23 @@ We investigated a few different approaches used in the open source world. There
 - Keep two repos in sync using some mixture of git submodules or a tool like [copycat](https://github.com/atomix/copycat)
 - Use the same codebase, abstracting platform-specific code behind an API and feature flags.
 
-Our frontend [team](https://github.com/orgs/supabase/teams/frontend/members) experimented with the first two approaches where they plucked (injected, merged, and wrangled) code for our Platform. 
-Time-to-production become a lot slower, an unacceptable outcome at Supabase. 
+Our frontend [team](https://github.com/orgs/supabase/teams/frontend/members) experimented with the first two approaches where they plucked (injected, merged, and wrangled) code for our Platform.
+Time-to-production become a lot slower, an unacceptable outcome at Supabase.
 
-Eventually we decided to open source all the frontend code, a shared codebase for both the Platform and Self Hosting. 
+Eventually we decided to open source all the frontend code, a shared codebase for both the Platform and Self Hosting.
 
 <details>
-<summary>
-<a>Special shout out</a>
-</summary>
-Sentry do a fantastic job of <a href="https://develop.sentry.dev/sentry-vs-getsentry/">documenting their strategy</a> for managing a shared codebase and served as a great model for Supabase. 
+  <summary>
+    <a>Special shout out</a>
+  </summary>
+  Sentry do a fantastic job of <a href="https://develop.sentry.dev/sentry-vs-getsentry/">
+    documenting their strategy
+  </a> for managing a shared codebase and served as a great model for Supabase.
 </details>
-    
 
 ## Build in public
 
-For the past week, the dashboard you've been using on the Platform has been deployed from our [main repository](https://github.com/supabase/supabase/tree/master/studio). 
+For the past week, the dashboard you've been using on the Platform has been deployed from our [main repository](https://github.com/supabase/supabase/tree/master/studio).
 
 This fits one of our core philosophies at Supabase: do less. Less code to manage means less bugs. Fewer codebases means faster shipping.
 
@@ -69,7 +70,7 @@ This fits one of our core philosophies at Supabase: do less. Less code to manage
 
 It also fits the development philosophy of every other part of Supabase: building in public, "warts and all".
 
-This is a huge step forward for the community. Supabase users can now spot a bug, fix it in the open source repository, 
+This is a huge step forward for the community. Supabase users can now spot a bug, fix it in the open source repository,
 and have it shipped to both the Platform and Self-Hosted environments - all in a few hours.
 
 ## Technical details
@@ -82,16 +83,16 @@ Studio is a Javascript application with a few key pieces of technology:
 
 - [Next.js](https://nextjs.org/) - A frontend Javascript framework built with React.
 - [Tailwind](https://tailwindcss.com/) - A utility-first CSS framework.
-- [Supabase UI](https://ui.supabase.com/) - Our own component library. 
+- [Supabase UI](https://ui.supabase.com/) - Our own component library.
 - [MobX](https://www.mobxjs.com/) - A state management library.
 - A host of other [useful libraries](https://github.com/supabase/supabase/blob/master/studio/package.json), including [Radix UI](https://www.radix-ui.com), [Lottiefiles](https://lottiefiles.com/), [react-grid-layout](https://github.com/react-grid-layout/react-grid-layout), and [zxcvbn](https://github.com/dropbox/zxcvbn).
 
 ### What's included
 
-Studio is designed to work with existing deployments - either the local hosted, docker setup, or our CLI. 
-It is not intended for managing the deployment and administration of projects - that's out of scope. 
+Studio is designed to work with existing deployments - either the local hosted, docker setup, or our CLI.
+It is not intended for managing the deployment and administration of projects - that's out of scope.
 
-The features exposed on Studio for existing deployments are limited to those which manage your database: 
+The features exposed on Studio for existing deployments are limited to those which manage your database:
 
 - Table & SQL editors. (Saved queries are unavailable for now)
 - Database management: Policies, roles, extensions, replication.
@@ -108,4 +109,3 @@ Check out the full instructions in our [Studio Readme](https://github.com/supaba
 Our new open source Studio is also on Product Hunt right now. If you like what you see, please give it an upvote and a review.
 
 [![Open Source Table Editor](https://api.producthunt.com/widgets/embed-image/v1/featured.svg?post_id=321226&theme=light)](https://www.producthunt.com/posts/open-source-postgresql-studio?utm_source=badge-featured&utm_medium=badge&utm_souce=badge-open-source-postgresql-studio)
-
diff --git a/apps/www/_blog/2021-12-01-realtime-row-level-security-in-postgresql.mdx b/apps/www/_blog/2021-12-01-realtime-row-level-security-in-postgresql.mdx
index cf849781aa6..f1488ad5a82 100644
--- a/apps/www/_blog/2021-12-01-realtime-row-level-security-in-postgresql.mdx
+++ b/apps/www/_blog/2021-12-01-realtime-row-level-security-in-postgresql.mdx
@@ -67,6 +67,7 @@ create policy todo_select_policy
 
 which is equivalent to adding
 
+{/* prettier-ignore */}
 ```sql hideCopy
 select *
 from todos
@@ -116,7 +117,7 @@ To maximize throughput, the query used to evaluate if a row is visible to a subs
 For example:
 
 ```sql hideCopy
-select exists(select 1 from some_table where id = 806);
+select exists (select 1 from some_table where id = 806);
 ```
 
 When more than one subscriber exists, the query is wrapped in a [prepared statement](https://www.postgresql.org/docs/13/sql-prepare.html) to remove the cost of the PostgreSQL
diff --git a/apps/www/_blog/2021-12-03-pg-graphql.mdx b/apps/www/_blog/2021-12-03-pg-graphql.mdx
index d521cc842aa..db65659b2a6 100644
--- a/apps/www/_blog/2021-12-03-pg-graphql.mdx
+++ b/apps/www/_blog/2021-12-03-pg-graphql.mdx
@@ -18,9 +18,9 @@ toc_depth: 3
 <div className="bg-gray-300 rounded-lg px-6 py-2 italic">
 
 🆕 `pg_graphql` is now generally available and has undergone significant enhancements since this announcement. Here is what is new:
-	
-	- [pg_graphql v1.0](https://supabase.com/blog/pg-graphql-v1)
-	- [New Features in pg_graphql v1.2](https://supabase.com/blog/whats-new-in-pg-graphql-v1-2)
+
+- [pg_graphql v1.0](https://supabase.com/blog/pg-graphql-v1)
+- [New Features in pg_graphql v1.2](https://supabase.com/blog/whats-new-in-pg-graphql-v1-2)
 
 </div>
 
@@ -36,7 +36,6 @@ Today we're open sourcing [`pg_graphql`](https://github.com/supabase/pg_graphql)
 
 Interested? You're [3 commands away](https://supabase.github.io/pg_graphql/quickstart/) from a live [GraphiQL](https://graphql-dotnet.github.io/docs/getting-started/graphiql/) demo.
 
-
 ## Motivation
 
 The Supabase stack is centered around PostgreSQL as the single source of truth. All data, configuration, and security are housed in the database so any GraphQL solution needed to be equivalently SQL-centric.
@@ -85,11 +84,11 @@ As a limited example of how the reflection engine works, here's how it converts
 
 ```sql hideCopy
 # schema.sql
-create table account(
-    id serial primary key,
-    email varchar(255) not null,
-    created_at timestamp not null,
-    updated_at timestamp not null
+create table account (
+  id serial primary key,
+  email varchar(255) not null,
+  created_at timestamp not null,
+  updated_at timestamp not null
 );
 ```
 
@@ -179,6 +178,7 @@ We're opting to expose the function over HTTP through PostgREST but you could al
 
 When it comes to APIs, performance counts. Here are some figures from [Apache Bench](https://www.tutorialspoint.com/apache_bench/apache_bench_quick_guide.htm) showing 2,205 requests/second on a 4 core machine with 16 GB of memory.
 
+{/* prettier-ignore */}
 ```markdown hideCopy
 Concurrency Level:      8
 Time taken for tests:   3.628 seconds
diff --git a/apps/www/_blog/2022-03-08-postgres-audit.mdx b/apps/www/_blog/2022-03-08-postgres-audit.mdx
index 41a2faa411b..cb8e99643fc 100644
--- a/apps/www/_blog/2022-03-08-postgres-audit.mdx
+++ b/apps/www/_blog/2022-03-08-postgres-audit.mdx
@@ -31,9 +31,9 @@ To demonstrate what we're working towards, the following example shows what we'l
 
 ```sql
 -- create a table
-create table public.members(
-    id int primary key,
-    name text not null
+create table public.members (
+  id int primary key,
+  name text not null
 );
 
 -- Enable auditing on the new table
@@ -44,10 +44,15 @@ Produce some records to audit
 
 ```sql
 -- create a new record
-insert into public.members(id, name) values (1, 'foo');
+insert into public.members
+  (id, name)
+values
+  (1, 'foo');
 
 -- edit the record
-update public.members set name = 'bar' where id = 1;
+update public.members
+set name = 'bar'
+where id = 1;
 
 -- delete the record
 delete from public.members;
@@ -56,7 +61,7 @@ delete from public.members;
 Review the audit log
 
 ```sql
-select * from audit.record_history
+select * from audit.record_history;
 ```
 
 ```markdown
@@ -227,14 +232,12 @@ Finally, we index the `record_id` and `old_record_id` columns that contain these
 
 ```sql
 -- index record_id for fast searching
-create index record_version_record_id
-    on audit.record_version(record_id)
-    where record_id is not null;
+create index record_version_record_id on audit.record_version (record_id)
+where record_id is not null;
 
 -- index old_record_id for fast searching
-create index record_version_old_record_id
-	on audit.record_version(record_id)
-  where old_record_id is not null;
+create index record_version_old_record_id on audit.record_version (record_id)
+where old_record_id is not null;
 ```
 
 ### Enrollment
diff --git a/apps/www/_blog/2022-03-29-graphql-now-available.mdx b/apps/www/_blog/2022-03-29-graphql-now-available.mdx
index ddf55bd01e6..a4c438c1bba 100644
--- a/apps/www/_blog/2022-03-29-graphql-now-available.mdx
+++ b/apps/www/_blog/2022-03-29-graphql-now-available.mdx
@@ -15,8 +15,8 @@ toc_depth: 3
 
 🆕 `pg_graphql` has undergone significant enhancements since this announcement. Here is what is new:
 
-	- [pg_graphql v1.0](https://supabase.com/blog/pg-graphql-v1)
-	- [New Features in pg_graphql v1.2](https://supabase.com/blog/whats-new-in-pg-graphql-v1-2)
+- [pg_graphql v1.0](https://supabase.com/blog/pg-graphql-v1)
+- [New Features in pg_graphql v1.2](https://supabase.com/blog/whats-new-in-pg-graphql-v1-2)
 
 </div>
 
@@ -67,11 +67,11 @@ GraphQL types and fields are reflected from the SQL schema:
 For example:
 
 ```sql
-create table "Account"(
-    "id" serial primary key,
-    "email" varchar(255) not null,
-    "createdAt" timestamp not null,
-    "updatedAt" timestamp not null
+create table "Account" (
+  "id" serial primary key,
+  "email" varchar(255) not null,
+  "createdAt" timestamp not null,
+  "updatedAt" timestamp not null
 );
 ```
 
@@ -152,12 +152,11 @@ For example, when selecting all comments for a blog post:
 
 ```sql
 select
-	blog_posts.title,
-	comments.body as comment_body
+  blog_posts.title,
+  comments.body as comment_body
 from
-	blog_posts
-join
-	comments on blog_posts.id = comments.blog_post_id
+  blog_posts
+  join comments on blog_posts.id = comments.blog_post_id;
 ```
 
 a SQL response would duplicate all data from the `blog_posts` table (title).
@@ -330,7 +329,6 @@ Didn't see the feature you're interested in? [Let us know](https://github.com/su
 
 ## More pg_graphql
 
-- [Introducing pg_graphql: A GraphQL extension for PostgreSQL](https://supabase.com/blog/pg-graphql) 
+- [Introducing pg_graphql: A GraphQL extension for PostgreSQL](https://supabase.com/blog/pg-graphql)
 - [pg_graphql v1.0](https://supabase.com/blog/pg-graphql-v1)
 - [pg_graphql v1.2](https://supabase.com/blog/whats-new-in-pg-graphql-v1-2)
-
diff --git a/apps/www/_blog/2022-04-01-supabase-realtime-with-multiplayer-features.mdx b/apps/www/_blog/2022-04-01-supabase-realtime-with-multiplayer-features.mdx
index f03ab864253..c45078e6ca7 100644
--- a/apps/www/_blog/2022-04-01-supabase-realtime-with-multiplayer-features.mdx
+++ b/apps/www/_blog/2022-04-01-supabase-realtime-with-multiplayer-features.mdx
@@ -39,7 +39,6 @@ The next and third major version, announced today on new Supabase Realtime Day,
 Presence is great for showing when your users are online. When a user connects or disconnects (even accidentally!), the server automatically detects this and let's everyone else know.
 Presence is powered by [CRDTs](https://crdt.tech/) (Conflict-free Replicated Data Type) on a distributed cluster useful for storing synced data across nodes.
 
-
 ### Broadcast
 
 ![realtime-multiplayer-broadcast.png](/images/blog/launch-week-4/friday-realtime/realtime-multiplayer-broadcast.png)
@@ -50,7 +49,7 @@ In Realtime, connected users communicate with other subscribing & publishing to
 ### Extensions
 
 In this version of Realtime we're re-architecting the way that we listen to PostgreSQL databases by opening the WebSocket functionality for general use.
-Instead of only using WebSockets to broadcast database changes, we are now moving the PostgreSQL listener to an “extension” architecture. This opens up numerous new ways of extending the server. 
+Instead of only using WebSockets to broadcast database changes, we are now moving the PostgreSQL listener to an “extension” architecture. This opens up numerous new ways of extending the server.
 Here are just a few that we've heard:
 
 - Multiple Postgres: listen to multiple PostgreSQL databases at the same time.
diff --git a/apps/www/_blog/2022-06-15-loading-data-supabase-python.mdx b/apps/www/_blog/2022-06-15-loading-data-supabase-python.mdx
index b20f1dd5369..e85bfbaf7ed 100644
--- a/apps/www/_blog/2022-06-15-loading-data-supabase-python.mdx
+++ b/apps/www/_blog/2022-06-15-loading-data-supabase-python.mdx
@@ -14,13 +14,14 @@ toc_depth: 3
 
 Python is an excellent choice when it comes to data science. With a wide selection of libraries and built-in analytics tools, you can crunch data with ease, analyze even the most complex datasets, and visualize your results in beautiful charts and graphs.
 
-Supabase is backend-as-a-service built on top of PostgreSQL. It’s an excellent choice for building modern data-intensive apps and tooling.
+Supabase is backend-as-a-service built on top of PostgreSQL. It's an excellent choice for building modern data-intensive apps and tooling.
 
-Thanks to our incredible community, Supabase now has a powerful and open source [Python SDK](https://github.com/supabase-community/supabase-py).  With Supabase and Python, you can automate tasks such as CRUD operations with only a few lines of code. This guide will first create a simple schema in Supabase, then we’ll use the Supabase Python SDK to show how you can load sample data.
+Thanks to our incredible community, Supabase now has a powerful and open source [Python SDK](https://github.com/supabase-community/supabase-py). With Supabase and Python, you can automate tasks such as CRUD operations with only a few lines of code. This guide will first create a simple schema in Supabase, then we'll use the Supabase Python SDK to show how you can load sample data.
 
 ## Prerequisites
 
-Before we dive in, let’s look at some prerequisites you'll need:
+Before we dive in, let's look at some prerequisites you'll need:
+
 - Python version > 3.7
   - The SDK only supports version > 3.7. You can download a supported Python version from [here](https://www.python.org/downloads/).
 - Python virtual environment
@@ -28,8 +29,8 @@ Before we dive in, let’s look at some prerequisites you'll need:
 - Faker python package
   - We will be using the [faker-commerce](https://pypi.org/project/faker-commerce/) package from the Faker library in Python to generate realistic sample data.
 
-
 ## Loading data into Supabase using Python
+
 Supabase is built for developers, and you can [get started for free](https://app.supabase.com) using your existing Github account. Once your Supabase account is set up, you will access the Supabase dashboard. From here, go to All Project > New Project.
 
 ![screen shot of supabase dashboard](/images/blog/python-1/1.png)
@@ -42,7 +43,8 @@ Your project will spin up within 2 minutes.
 
 ## Creating tables in Supabase
 
-In this example, we’ll be creating 2 tables in Supabase:
+In this example, we'll be creating 2 tables in Supabase:
+
 - Vendor (fields are vendor_name, vendor_location, and total_employees)
 - Product (vendor_id as FK, product_name, price, and total orders)
 
@@ -54,7 +56,7 @@ Let us now begin creating the tables. Once you create a project, you will need t
 
 ![screen shot of supabase dashboard](/images/blog/python-1/4.png)
 
-Now, you can create a table according to the defined schema. 
+Now, you can create a table according to the defined schema.
 
 ![screen shot of supabase dashboard](/images/blog/python-1/5.png)
 Click on Save to create your vendor table. Similarly, create the product table.
@@ -98,7 +100,7 @@ So for our example we will set them up like this:
 
 ```bash
 export SUPABASE_URL=<<the value under config > URL>>
-export SUPABASE_KEY=<<the value present in Project API keys > anon public>> 
+export SUPABASE_KEY=<<the value present in Project API keys > anon public>>
 export SUPABASE_SECRET_KEY=<<the value present in Project API keys > service_role secret>>
 ```
 
@@ -160,8 +162,9 @@ main()
 ```
 
 To summarize what we have done using this code snippet:
+
 - We have inserted 10 random vendors to the table.
-- For each of the 10 vendors, we have inserted a number of different products 
+- For each of the 10 vendors, we have inserted a number of different products
 
 ## Reading the data stored in Supabase
 
@@ -170,16 +173,16 @@ Data can also be viewed directly from the Supabase dashboard. To do this, go to
 ![screen shot of supabase dashboard](/images/blog/python-1/11.png)
 
 ![screen shot of supabase dashboard](/images/blog/python-1/12.png)
-Note: In case  you cannot see any of the data, you should hit the Refresh button.
+Note: In case you cannot see any of the data, you should hit the Refresh button.
 
 ## Conclusion
+
 With Python, data loading into Supabase is easy. It just takes a few easy steps to get started with the Python SDK and Supabase. In the next part of this blog series, we will learn [how to visualize the data that we just loaded into Supabase using Metabase](/blog/visualizing-supabase-data-using-metabase). Stay tuned!
 
 If you have any questions please reach out via [Twitter](https://twitter.com/supabase) or join our [Discord](https://discord.supabase.com).
 
 ## More Python and Supabase resources
+
 - [supabase-py](https://github.com/supabase-community/supabase-py)
 - [Slack Consolidate: a slackbot built with Python and Supabase](/blog/slack-consolidate-slackbot-to-consolidate-messages)
 - [Supabase-py (Database) on Replit](https://replit.com/@Supabase/Supabase-py-Database?v=1)
-
-
diff --git a/apps/www/_blog/2022-06-29-visualizing-supabase-data-using-metabase.mdx b/apps/www/_blog/2022-06-29-visualizing-supabase-data-using-metabase.mdx
index c7a6a0d2b4a..3ab89c167f1 100644
--- a/apps/www/_blog/2022-06-29-visualizing-supabase-data-using-metabase.mdx
+++ b/apps/www/_blog/2022-06-29-visualizing-supabase-data-using-metabase.mdx
@@ -100,10 +100,11 @@ Next, under the database, select "SupabaseDB".
 We will be using the following SQL query:
 
 ```sql
-SELECT "Vendor".vendor_name, product_name, "Vendor".total_employees
-FROM "Product"
-LEFT JOIN "Vendor" on "Product".vendor_id = "Vendor".vendor_id
-WHERE "Vendor".total_employees
+select "Vendor".vendor_name, product_name, "Vendor".total_employees
+from
+  "Product"
+  left join "Vendor" on "Product".vendor_id = "Vendor".vendor_id
+where "Vendor".total_employees;
 ```
 
 This query should fetch us the vendor name and the product where the number of employees for a given vendor is less than 110.
diff --git a/apps/www/_blog/2022-06-30-flutter-tutorial-building-a-chat-app.mdx b/apps/www/_blog/2022-06-30-flutter-tutorial-building-a-chat-app.mdx
index 1510e6b4143..2ac7e4607f6 100644
--- a/apps/www/_blog/2022-06-30-flutter-tutorial-building-a-chat-app.mdx
+++ b/apps/www/_blog/2022-06-30-flutter-tutorial-building-a-chat-app.mdx
@@ -266,7 +266,7 @@ class MyApp extends StatelessWidget {
 
 When a user launches the app, we want to redirect those who have already signed in to the Chat page and those who have not signed in yet to the register page.
 In order to achieve this, we will create a splash page, which is just a page with a preloader at the middle from the user, but takes care of fetching auth state and redirects users accordingly behind the scenes.
-Within the `_redirect()` method, we are fetching the auth state and navigating the user accordingly. 
+Within the `_redirect()` method, we are fetching the auth state and navigating the user accordingly.
 
 ```dart title="lib/pages/splash_page.dart"
 import 'package:flutter/material.dart';
diff --git a/apps/www/_blog/2022-07-18-seen-by-in-postgresql.mdx b/apps/www/_blog/2022-07-18-seen-by-in-postgresql.mdx
index 32414a702a9..5d8c7e1efe3 100644
--- a/apps/www/_blog/2022-07-18-seen-by-in-postgresql.mdx
+++ b/apps/www/_blog/2022-07-18-seen-by-in-postgresql.mdx
@@ -443,17 +443,16 @@ A likely requirement from the original scenario that we've completely ignored is
 In SQL:
 
 ```sql hideCopy
-BEGIN;
+begin;
 
-CREATE TABLE posts_seen_by_users (
-  post_id bigint REFERENCES posts(id),
-  user_id bigint REFERENCES users(id),
-  seen_count bigint NOT NULL DEFAULT 0 CHECK (seen_count > 0),
-
-  PRIMARY KEY (post_id, user_id)
+create table posts_seen_by_users (
+  post_id bigint references posts (id),
+  user_id bigint references users (id),
+  seen_count bigint not null default 0 check (seen_count > 0),
+  primary key (post_id, user_id)
 );
 
-COMMIT;
+commit;
 ```
 
 #### Caveats
diff --git a/apps/www/_blog/2022-08-09-slack-consolidate-slackbot-to-consolidate-messages.mdx b/apps/www/_blog/2022-08-09-slack-consolidate-slackbot-to-consolidate-messages.mdx
index 7581b57e33a..62928371434 100644
--- a/apps/www/_blog/2022-08-09-slack-consolidate-slackbot-to-consolidate-messages.mdx
+++ b/apps/www/_blog/2022-08-09-slack-consolidate-slackbot-to-consolidate-messages.mdx
@@ -192,15 +192,26 @@ Go to [SQL Editor](https://app.supabase.com/project/_/sql) and run insert comman
 Inserting a public channel named #support-channel to be monitored:
 
 ```sql
-INSERT INTO slack_channels(channel,channel_id,p_level,dest_channel, dest_channel_id, private)
-VALUES ('support-channel','C0000ABC02DE','Support msgs', 'all_them_messages','C0000ABC02DF',0);
+insert into slack_channels
+  (channel, channel_id, p_level, dest_channel, dest_channel_id, private)
+values
+  ('support-channel', 'C0000ABC02DE', 'Support msgs', 'all_them_messages', 'C0000ABC02DF', 0);
 ```
 
 Inserting a **private** channel named #support-enterprise to be monitored:
 
 ```sql
-INSERT INTO slack_channels(channel,channel_id,p_level,dest_channel, dest_channel_id, private)
-VALUES ('support-enterprise','C0000ABC02DC','Enterprise Support msgs', 'all_them_messages','C0000ABC02DF',1);
+insert into slack_channels
+  (channel, channel_id, p_level, dest_channel, dest_channel_id, private)
+values
+  (
+    'support-enterprise',
+    'C0000ABC02DC',
+    'Enterprise Support msgs',
+    'all_them_messages',
+    'C0000ABC02DF',
+    1
+  );
 ```
 
 Notes:
diff --git a/apps/www/_blog/2022-08-16-supabase-js-v2.mdx b/apps/www/_blog/2022-08-16-supabase-js-v2.mdx
index 6708ecaaf54..c03dd3a37b3 100644
--- a/apps/www/_blog/2022-08-16-supabase-js-v2.mdx
+++ b/apps/www/_blog/2022-08-16-supabase-js-v2.mdx
@@ -14,7 +14,7 @@ video: https://www.youtube.com/v/iqZlPtl_b-I
 <div className="bg-gray-300 rounded-lg p-6 italic">
 <br /> ⚠️ UPDATED 20/10: supabase-js v2 is fully released 🥳<br />
 
-<a href="https://supabase.com/docs/reference/javascript">Check the updated docs</a> and <a href="https://supabase.com/docs/reference/javascript/v1/upgrade-guide">migration guide</a>.
+[Check the updated docs](https://supabase.com/docs/reference/javascript) and [migration guide](https://supabase.com/docs/reference/javascript/v1/upgrade-guide).
 
 </div>
 
diff --git a/apps/www/_blog/2022-08-19-postgrest-v10.mdx b/apps/www/_blog/2022-08-19-postgrest-v10.mdx
index 0f5a29ebd83..6625918bfeb 100644
--- a/apps/www/_blog/2022-08-19-postgrest-v10.mdx
+++ b/apps/www/_blog/2022-08-19-postgrest-v10.mdx
@@ -39,6 +39,7 @@ The `text` format is used by default, which gives you the same output you’d ge
 
 For `supabase-js`, you can get the execution plan using the `explain()` transform. This works for every `supabase-js` method, including `rpc()`. Here’s an example for `select()`.
 
+{/* prettier-ignore */}
 ```jsx
 const { data, error } = await supabase
   .from('projects')
@@ -118,28 +119,28 @@ To avoid unnecessary JSON arrays in a query result, one-to-one relationships are
 
 ```sql
 -- A unique constraint on a foreign key
-create table country(
-  id serial primary key
-, name text
+create table country (
+  id serial primary key,
+  name text
 );
 
-create table capital(
-  id serial primary key
-, name text
-, country_id int unique
-, foreign key (country_id) references country(id)
+create table capital (
+  id serial primary key,
+  name text,
+  country_id int unique,
+  foreign key (country_id) references country (id)
 );
 
 -- or a primary key on a foreign key
-create table country(
-  id serial primary key
-, name text
+create table country (
+  id serial primary key,
+  name text
 );
 
-create table capital(
-  id serial primary key
-, name text
-, foreign key (id) references country(id)
+create table capital (
+  id serial primary key,
+  name text,
+  foreign key (id) references country (id)
 );
 ```
 
@@ -254,20 +255,20 @@ Detecting join tables for many-to-many relationships has been working for many r
 -- the primary key must include the foreign key columns
 -- of the many-to-many ends
 
-create table books(
-  id int primary key
-, name text
+create table books (
+  id int primary key,
+  name text
 );
 
-create table books_authors(
-  book_id int references books(id)
-, author_id int references authors(id)
-, primary key(book_id, author_id) -- this is now necessary
+create table books_authors (
+  book_id int references books (id),
+  author_id int references authors (id),
+  primary key (book_id, author_id) -- this is now necessary
 );
 
-create table authors(
-  id int primary key
-, name text
+create table authors (
+  id int primary key,
+  name text
 );
 ```
 
diff --git a/apps/www/_blog/2022-08-19-supabase-vault.mdx b/apps/www/_blog/2022-08-19-supabase-vault.mdx
index 62b386bd1b9..4415e4823eb 100644
--- a/apps/www/_blog/2022-08-19-supabase-vault.mdx
+++ b/apps/www/_blog/2022-08-19-supabase-vault.mdx
@@ -147,11 +147,12 @@ Now you can encrypt table secrets with this new key by inserting its ID explicit
 ```sql
 insert into vault.secrets
   (secret, associated, key_id)
-values (
-  'apikey_XaYrurzcquqhEdBjzfTzfwAZqpd',
-  'This is some different associated data.',
-  'f9f176eb-7069-4743-9403-582c04354ffc'
-)
+values
+  (
+    'apikey_XaYrurzcquqhEdBjzfTzfwAZqpd',
+    'This is some different associated data.',
+    'f9f176eb-7069-4743-9403-582c04354ffc'
+  )
 returning *;
 ```
 
diff --git a/apps/www/_blog/2022-08-24-building-a-realtime-trello-board-with-supabase-and-angular.mdx b/apps/www/_blog/2022-08-24-building-a-realtime-trello-board-with-supabase-and-angular.mdx
index 92ccd3f4ee0..c63debb9185 100644
--- a/apps/www/_blog/2022-08-24-building-a-realtime-trello-board-with-supabase-and-angular.mdx
+++ b/apps/www/_blog/2022-08-24-building-a-realtime-trello-board-with-supabase-and-angular.mdx
@@ -34,8 +34,8 @@ Along our jurney we will:
     frameborder="0"
     allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
     allowfullscreen
-  ></iframe> 
-</div> 
+  ></iframe>
+</div>
 Watch the video version of the tutorial.
 
 Since there are quite some code snippets we need I've put together the [full source code on Github](https://github.com/saimon24/supabase-trello-angular) so you can easily run the project yourself!
diff --git a/apps/www/_blog/2022-08-25-launch-week-5-hackathon-winners.mdx b/apps/www/_blog/2022-08-25-launch-week-5-hackathon-winners.mdx
index 02d80cf3932..516e6ff9629 100644
--- a/apps/www/_blog/2022-08-25-launch-week-5-hackathon-winners.mdx
+++ b/apps/www/_blog/2022-08-25-launch-week-5-hackathon-winners.mdx
@@ -13,7 +13,7 @@ toc_depth: 2
 
 During [Launch Week 5](https://supabase.com/launch-week), we shipped a lot of features, which was exciting, but what is more exciting is reviewing all the awesome hackathon submissions you all created for [Launch Week 5 Hackathon!](https://supabase.com/blog/launch-week-5-hackathon)
 
-It is always tough to pick the winner, but this time around it was extra hard because of the amount of incredible projects: there were 46 submitted projects, making this our most popular hackathon yet. You will be able to view all of the submissions of this hackathon on [madewithsupabase.com](https://www.madewithsupabase.com/). 
+It is always tough to pick the winner, but this time around it was extra hard because of the amount of incredible projects: there were 46 submitted projects, making this our most popular hackathon yet. You will be able to view all of the submissions of this hackathon on [madewithsupabase.com](https://www.madewithsupabase.com/).
 
 And now, without further ado, congratulations to the winners of Supabase Launch Week 5 Hackathon!
 
@@ -23,7 +23,7 @@ And now, without further ado, congratulations to the winners of Supabase Launch
 
 [Supabase Cache Helpers](https://github.com/psteinroe/supabase-cache-helpers) - by [@psteinroe](https://twitter.com/psteinroe).
 
-Supabase Cache Helpers is a caching utility library that works by turning your Supabase query into cache keys and provides methods for retrieving and mutating data on your Supabase database. 
+Supabase Cache Helpers is a caching utility library that works by turning your Supabase query into cache keys and provides methods for retrieving and mutating data on your Supabase database.
 
 ![Supabase Cache Helpers](/images/blog/lw5-hackathon-winners/supabase-cache-helpers.png)
 
@@ -31,7 +31,7 @@ Supabase Cache Helpers is a caching utility library that works by turning your S
 
 [Super UI](https://github.com/pheralb/superui) - by [Pablo Hdez](https://twitter.com/pheralb_), [Nacho Aldama](https://twitter.com/srdrabx), [David Huertas](https://twitter.com/ikurotime) and [Juan Rojas](https://twitter.com/tmchein)
 
-Super UI is a React UI component library for React, but it also lets you customize and create your own components from your browser. 
+Super UI is a React UI component library for React, but it also lets you customize and create your own components from your browser.
 
 ![Super UI](/images/blog/lw5-hackathon-winners/super-ui.png)
 
@@ -59,7 +59,7 @@ Vesta is an open source Google Keep alternative that helps you to save notes and
 
 [Otentik Authenticator](https://github.com/riipandi/otentik-authenticator-desktop) - by [@riipandi](https://twitter.com/riipandi)
 
-Otentik is a security desktop app to manage your 2-step verification tokens when logging into your online services so that you can complete your login flow within your computer. 
+Otentik is a security desktop app to manage your 2-step verification tokens when logging into your online services so that you can complete your login flow within your computer.
 
 ![Otentik Authenticator](/images/blog/lw5-hackathon-winners/otentik.png)
 
@@ -67,7 +67,7 @@ Otentik is a security desktop app to manage your 2-step verification tokens when
 
 [Stripe Sync](https://github.com/lawrencecchen/stripe-sync) - by [@lawrencecchen](https://github.com/lawrencecchen)
 
-Stripe Sync allows you to automatically sync your stripe data into your Supabase database using Edge Functions. 
+Stripe Sync allows you to automatically sync your stripe data into your Supabase database using Edge Functions.
 
 ![Stripe Sync](/images/blog/lw5-hackathon-winners/stripe-sync.png)
 
@@ -85,7 +85,7 @@ Play a classic hot dog eating contest with your friends! That Hot Dog Game uses
 
 [Quizgrad (Quiz App)](https://github.com/mehulsatardekar/Quizgrad) - by [Mehul Satardekar](https://twitter.com/MehulSatardekar)
 
-Quizgrad is a fun quiz app where you can compete against other players on quizzes from different categories. 
+Quizgrad is a fun quiz app where you can compete against other players on quizzes from different categories.
 
 ![Quizgrad (Quiz App)](/images/blog/lw5-hackathon-winners/quiz-grad.png)
 
@@ -113,7 +113,7 @@ A productivity manager application where you can leave a note right from your de
 
 [RepoWatch](https://github.com/vvidday/repo-watch) - by [@vvidday](https://github.com/vvidday)
 
-With RepoWatch, you can view any updates on across all the repositories in the Supabase GitHub org in realtime. 
+With RepoWatch, you can view any updates on across all the repositories in the Supabase GitHub org in realtime.
 
 ![RepoWatch](/images/blog/lw5-hackathon-winners/repo-watch.png)
 
@@ -127,7 +127,7 @@ CoWoFi is an application that helps managers, executives and the general public
 
 ## The Prizes
 
-As promised in the [hackathon announcement article](https://supabase.com/blog/launch-week-5-hackathon), each members of the winners will receive a limited edition golden Supabase cap! 
+As promised in the [hackathon announcement article](https://supabase.com/blog/launch-week-5-hackathon), each members of the winners will receive a limited edition golden Supabase cap!
 
 ![Golden Supabase Cap](/images/blog/lw5-hackathon/cap.png)
 
diff --git a/apps/www/_blog/2022-09-07-supabase-beta-update-august-2022.mdx b/apps/www/_blog/2022-09-07-supabase-beta-update-august-2022.mdx
index 906334d0d20..31a6206daec 100644
--- a/apps/www/_blog/2022-09-07-supabase-beta-update-august-2022.mdx
+++ b/apps/www/_blog/2022-09-07-supabase-beta-update-august-2022.mdx
@@ -2,7 +2,7 @@
 title: Supabase Beta August 2022
 description: Launch Week Special. See everything we shipped, plus winners of the Hackathon and the extended Community Highlights
 author: ant_wilson
-image: 2022-august/monthly-update-august-2022.jpg 
+image: 2022-august/monthly-update-august-2022.jpg
 thumb: 2022-august/monthly-update-august-2022.jpg
 tags:
   - release-notes
@@ -18,7 +18,7 @@ This month the Beta Update is a Launch Week special. #SupaLaunchWeek 5 just happ
 
 The Supabase CLI is now in v1.0 (including the ability to generate TypeScript types 🎉). We also released the Management API Beta, a REST API that opens the door to a whole new suite of integrations (Zapier, Terraform, Pulumi, you name it). Full programmatic control of your projects and orgs is on the way.
 
-[Blog Post](https://supabase.com/blog/supabase-cli-v1-and-admin-api-beta) 
+[Blog Post](https://supabase.com/blog/supabase-cli-v1-and-admin-api-beta)
 
 [Video Announcement](https://www.youtube.com/watch?v=OpPOaJI_Z28)
 
@@ -26,7 +26,7 @@ The Supabase CLI is now in v1.0 (including the ability to generate TypeScript ty
 
 ![Day 2 - supabase-js v2 Release Candidate](/images/blog/2022-august/supabase_js.png)
 
-**[supabase-js v2](https://github.com/supabase/supabase-js)** focuses on "quality-of-life" improvements for developers and includes Type Support, new Auth Methods, async Auth overhaul, improvements for Edge Functions, and more. We couldn't have done this without our amazing Community, so thanks a lot to everyone who contributed. 
+**[supabase-js v2](https://github.com/supabase/supabase-js)** focuses on "quality-of-life" improvements for developers and includes Type Support, new Auth Methods, async Auth overhaul, improvements for Edge Functions, and more. We couldn't have done this without our amazing Community, so thanks a lot to everyone who contributed.
 
 Try it out by running `npm i @supabase/supabase-js@rc`
 
@@ -84,8 +84,8 @@ We had a huge amount of open source submissions 🤯. The selection process was
 
 The following changes to the Supabase Platform will take effect from September 11th at 7 pm PDT.
 
--   HTTP API requests to Supabase will automatically be redirected to HTTPS.
--   The API Key was passed to Supabase both in the `Authorization` header and in a separate `apiKey` header. This led to confusion among new users of Supabase who used the API directly. It is no longer required to send the anon key or service key via the `apiKey` header. If you are using Supabase via our client libraries, no change is required from your side.
+- HTTP API requests to Supabase will automatically be redirected to HTTPS.
+- The API Key was passed to Supabase both in the `Authorization` header and in a separate `apiKey` header. This led to confusion among new users of Supabase who used the API directly. It is no longer required to send the anon key or service key via the `apiKey` header. If you are using Supabase via our client libraries, no change is required from your side.
 
 ## Supabase Migration Guides
 
@@ -93,10 +93,10 @@ The following changes to the Supabase Platform will take effect from September 1
 
 Our guides and tools make it super easy to migrate your projects to Supabase:
 
--   [Firebase Auth Migration](https://supabase.com/docs/guides/migrations/firebase-auth)
--   [Firestore Data Migration](https://supabase.com/docs/guides/migrations/firestore-data)
--   [Firebase Storage Migration](https://supabase.com/docs/guides/migrations/firebase-storage)
--   [Migrate from Heroku to Supabase](https://supabase.com/docs/guides/migrations/heroku)
+- [Firebase Auth Migration](https://supabase.com/docs/guides/migrations/firebase-auth)
+- [Firestore Data Migration](https://supabase.com/docs/guides/migrations/firestore-data)
+- [Firebase Storage Migration](https://supabase.com/docs/guides/migrations/firebase-storage)
+- [Migrate from Heroku to Supabase](https://supabase.com/docs/guides/migrations/heroku)
 
 ## Webinar: How Netlify and Supabase Enables “Supa” DX
 
@@ -104,8 +104,7 @@ Our guides and tools make it super easy to migrate your projects to Supabase:
 
 Our friends from Netlify invited Ant to their new webinar series. He and Netlify's VP of Partnerships & Ecosystems, Steven Larsen, will show you how to:
 
-
-- Deploy Supabase’s open source backend together with Netlify
+- Deploy Supabase's open source backend together with Netlify
 - Build User Management without handing over user data to any third parties
 - Upload files and folders to the cloud without needing to tack on additional tools
 
@@ -115,20 +114,20 @@ Our friends from Netlify invited Ant to their new webinar series. He and Netlify
 
 ![Community](/images/blog/2022-june/community.jpg)
 
--   Inian shared our journey with Cloudflare. [Video](https://twitter.com/Cloudflare/status/1557728943901675520)
--   Supabase Tips: Introduction to Supabase Storage. [Video](https://www.youtube.com/watch?v=J9mTPY8rIXE) 
--   Zack DeRose playing around with Supabase and Nx. [Part 1](https://www.youtube.com/watch?v=OTh5GBBfr4E) | [Part 2](https://www.youtube.com/watch?v=_5gJi_xwpzk)
--   A new guide showing how to combine Supabase and Directus. [Guide](https://supabase.com/docs/guides/integrations/directus)
--   Supabase with Flutter course on raywenderlich. [Course](https://www.raywenderlich.com/33619647-supabase-with-flutter)
--   Build a full-stack app with Next.js and Supabase on the LogRocket blog. [Tutorial](https://blog.logrocket.com/build-full-stack-app-next-js-supabase/)
--   Supabase Crash Course by The Net Ninja. [Video Courses](https://www.youtube.com/watch?v=ydz7Dj5QHKY&list=PL4cUxeGkcC9hUb6sHthUEwG7r9VDPBMKO)
--   How to build a Grocery Application with Webflow CMS using DhiWise. [Tutorial](https://dev.to/saloni137/how-to-build-a-grocery-application-with-webflow-cms-using-dhiwise-1a72)
--   How To Create a Full Stack app with SolidJS, Supabase, and TailwindCSS [Video and Tutorial.](https://blog.chetanverma.com/how-to-create-a-full-stack-app-with-solidjs-supabase-and-tailwindcss)
--   The WalletConnect Cloud now supports Sign in with Ethereum. [Announcement](https://twitter.com/TheHarryET/status/1559861021845643265).
--   Building In Public: Cartta Tech Stack. [Article](https://dev.to/fvaldes33/building-in-public-cartta-tech-stack-5en0)
--   Supabase + Vue 3 in 12 minutes. [Video](https://www.youtube.com/watch?v=YN32uVqAXw8&feature=emb_title)
+- Inian shared our journey with Cloudflare. [Video](https://twitter.com/Cloudflare/status/1557728943901675520)
+- Supabase Tips: Introduction to Supabase Storage. [Video](https://www.youtube.com/watch?v=J9mTPY8rIXE)
+- Zack DeRose playing around with Supabase and Nx. [Part 1](https://www.youtube.com/watch?v=OTh5GBBfr4E) | [Part 2](https://www.youtube.com/watch?v=_5gJi_xwpzk)
+- A new guide showing how to combine Supabase and Directus. [Guide](https://supabase.com/docs/guides/integrations/directus)
+- Supabase with Flutter course on raywenderlich. [Course](https://www.raywenderlich.com/33619647-supabase-with-flutter)
+- Build a full-stack app with Next.js and Supabase on the LogRocket blog. [Tutorial](https://blog.logrocket.com/build-full-stack-app-next-js-supabase/)
+- Supabase Crash Course by The Net Ninja. [Video Courses](https://www.youtube.com/watch?v=ydz7Dj5QHKY&list=PL4cUxeGkcC9hUb6sHthUEwG7r9VDPBMKO)
+- How to build a Grocery Application with Webflow CMS using DhiWise. [Tutorial](https://dev.to/saloni137/how-to-build-a-grocery-application-with-webflow-cms-using-dhiwise-1a72)
+- How To Create a Full Stack app with SolidJS, Supabase, and TailwindCSS [Video and Tutorial.](https://blog.chetanverma.com/how-to-create-a-full-stack-app-with-solidjs-supabase-and-tailwindcss)
+- The WalletConnect Cloud now supports Sign in with Ethereum. [Announcement](https://twitter.com/TheHarryET/status/1559861021845643265).
+- Building In Public: Cartta Tech Stack. [Article](https://dev.to/fvaldes33/building-in-public-cartta-tech-stack-5en0)
+- Supabase + Vue 3 in 12 minutes. [Video](https://www.youtube.com/watch?v=YN32uVqAXw8&feature=emb_title)
 
-## We’re hiring
+## We're hiring
 
 Come join one of the fastest growing open source projects ever 🤗
 
diff --git a/apps/www/_blog/2022-09-08-choosing-a-postgres-primary-key.mdx b/apps/www/_blog/2022-09-08-choosing-a-postgres-primary-key.mdx
index 8cbba05512d..a18e387b403 100644
--- a/apps/www/_blog/2022-09-08-choosing-a-postgres-primary-key.mdx
+++ b/apps/www/_blog/2022-09-08-choosing-a-postgres-primary-key.mdx
@@ -13,9 +13,9 @@ toc_depth: 3
 
 Primary keys are important. They uniquely identify rows of data in tables, and make it easy to fetch data. The job of a database is to archive and recall data and you're going to have a hard time finding data without a good primary key or a good index.
 
-Sometimes it makes sense to use a [“natural key”](https://en.wikipedia.org/wiki/Natural_key) (like an `email` column in a `users` table) and sometimes it’s better to use a “[surrogate key”](https://en.wikipedia.org/wiki/Surrogate_key), a value made *for the purpose* of identifying a row (and has no other meaning).
+Sometimes it makes sense to use a [“natural key”](https://en.wikipedia.org/wiki/Natural_key) (like an `email` column in a `users` table) and sometimes it's better to use a “[surrogate key”](https://en.wikipedia.org/wiki/Surrogate_key), a value made _for the purpose_ of identifying a row (and has no other meaning).
 
-At first glance, the question of *which* primary key to use is easy! Just throw a `integer`/`serial` on there, right? Numeric IDs are cool, but what about random value IDs or [Universally Unique IDentifiers (UUIDs)](https://en.wikipedia.org/wiki/Uuid)?
+At first glance, the question of _which_ primary key to use is easy! Just throw a `integer`/`serial` on there, right? Numeric IDs are cool, but what about random value IDs or [Universally Unique IDentifiers (UUIDs)](https://en.wikipedia.org/wiki/Uuid)?
 
 Turns out the question of which identifier (and in this case, UUID) to use is complicated -- we're going to dive into some of the complexity and inherent trade-offs, and figure things out:
 
@@ -51,24 +51,24 @@ CREATE UNIQUE INDEX users_email_uniq ON users USING BTREE (email);
 
 This looks great, but what should `id` be on new rows? I don't know -- maybe the application can figure it out? If they store some value in memory? That doesn't seem right.
 
-Maybe we could figure out the next integer from what's in the table itself -- we just need to be able to "count" upwards. We *do* have all the `users` tables rows in there, so we should be able to do it:
+Maybe we could figure out the next integer from what's in the table itself -- we just need to be able to "count" upwards. We _do_ have all the `users` tables rows in there, so we should be able to do it:
 
 ```sql
-INSERT INTO users (id, email, name)
-SELECT COUNT(*) + 1, 'new@example.com', 'new_user' FROM users;
+insert into users
+  (id, email, name)
+select count(*) + 1, 'new@example.com', 'new_user' from users;
 ```
 
 After running that query, we can double check our results:
 
 ```sql
-SELECT * FROM users;
+select * from users;
 ```
 
-| id | email            | name     |
-|----|------------------|----------|
-| `1`  | `new@example.com`  | `new user` |
-| `2`  | `new2@example.com` | `new user` |
-
+| id  | email              | name       |
+| --- | ------------------ | ---------- |
+| `1` | `new@example.com`  | `new user` |
+| `2` | `new2@example.com` | `new user` |
 
 Using `COUNT(*)` in our query is not the most efficient (or even easiest) solution though, and hopefully it's clear why -- **counting a sequence of numbers for primary keys is a feature built in to Postgres**!
 
@@ -76,46 +76,45 @@ Using `COUNT(*)` in our query is not the most efficient (or even easiest) soluti
 
 ### `serial`/`bigserial`
 
-`serial` is essentially a convenient macro for using [Postgres sequences](https://www.postgresql.org/docs/current/sql-createsequence.html), a database-managed auto-incrementing stream of `integer`. 
+`serial` is essentially a convenient macro for using [Postgres sequences](https://www.postgresql.org/docs/current/sql-createsequence.html), a database-managed auto-incrementing stream of `integer`.
 
 Let's hear it from the docs:
 
 > The data types `smallserial`, `serial` and `bigserial` are not true types, but merely a notational convenience for creating unique identifier columns (similar to the `AUTO_INCREMENT` property supported by some other databases).
-> 
 
-Using a `serial` column to create the `users` table would look like this: 
+Using a `serial` column to create the `users` table would look like this:
 
 ```sql
-CREATE TABLE users (
-  id serial PRIMARY KEY,
-  email citext NOT NULL CHECK (LENGTH(email) < 255),
-  name text NOT NULL
+create table users (
+  id serial primary key,
+  email citext not null check (length(email) < 255),
+  name text not null
 );
 ```
 
 OK, now let's try inserting into it - we shouldn't have to specify `id`:
 
 ```sql
-INSERT INTO users_serial (email, name) 
-VALUES ('user@example.com', 'new user');
+insert into users_serial
+  (email, name)
+values
+  ('user@example.com', 'new user');
 ```
 
-```sql 
-SELECT * FROM users;
-```
-
-
-| id | email            | name     |
-|----|------------------|----------|
-| `1`  | `user@example.com` | `new user` |
-
-
 ```sql
-(1 row) 
+select * from users;
+```
+
+| id  | email              | name       |
+| --- | ------------------ | ---------- |
+| `1` | `user@example.com` | `new user` |
+
+```sql
+(1 row)
 INSERT 0 1
 ```
 
-It works, as you might expect - now the application doesn't have to *somehow magically know* the right ID to use when inserting.
+It works, as you might expect - now the application doesn't have to _somehow magically know_ the right ID to use when inserting.
 
 But what does `serial` actually do? Using a serial column is operationally similar to the following SQL:
 
@@ -127,7 +126,7 @@ CREATE TABLE tablename (
 ALTER SEQUENCE tablename_colname_seq OWNED BY tablename.colname;
 ```
 
-Back in application land, the `INSERT` statement returns, and provides the new `id` the database assigned our new row. Multiple application instances don't need to coordinate what ID to use -- they just *don't*, and find out from the database.
+Back in application land, the `INSERT` statement returns, and provides the new `id` the database assigned our new row. Multiple application instances don't need to coordinate what ID to use -- they just _don't_, and find out from the database.
 
 **We've taken a somewhat meandering path to get here, but this is the standard solution for most reasonable database schemas.**
 
@@ -135,7 +134,7 @@ Back in application land, the `INSERT` statement returns, and provides the new `
 
 There are few issues with sequences:
 
-- When writing automation that simply iterates through id values, note that `serial` columns  can have gaps, even if you never `DELETE` (e.x. if an `INSERT` was rolled back — sequences live *outside* transactions).
+- When writing automation that simply iterates through id values, note that `serial` columns can have gaps, even if you never `DELETE` (e.x. if an `INSERT` was rolled back — sequences live _outside_ transactions).
 - When used from outside code `serial` may leak some data or give attackers an edge (e.x., if `yoursite.com/users/50` works, how about `yoursite.com/users/51`?).
 - `serial` is PostgreSQL specific (i.e. not SQL standards compliant)
 
@@ -157,7 +156,7 @@ CREATE TABLE (
 )
 ```
 
-So how does *this* work? Postgres does the same thing under the covers -- it generates a `sequence`. As this syntax is standards compliant, it's generally recommended practice for DBAs going forward, for the sake of the realm.
+So how does _this_ work? Postgres does the same thing under the covers -- it generates a `sequence`. As this syntax is standards compliant, it's generally recommended practice for DBAs going forward, for the sake of the realm.
 
 **So `integer`s are great, but information leakage is still a problem. How do we fix that?** Well, make the numbers random, obviously.
 
@@ -166,8 +165,8 @@ So how does *this* work? Postgres does the same thing under the covers -- it gen
 Let's say the application using the DB has some [Python](https://python.org) code like the following:
 
 ```python
-from random import randrange 
-from models import User 
+from random import randrange
+from models import User
 MAX_RANDOM_USER_ID = 1_000_000_000
 def create_user():
     """
@@ -178,11 +177,11 @@ def create_user():
     db.save(user)
 ```
 
-That *looks* good, but there's a problem -- [random](https://docs.python.org/3/library/random.html) is a *pseudorandom* generator.
+That _looks_ good, but there's a problem -- [random](https://docs.python.org/3/library/random.html) is a _pseudorandom_ generator.
 
-[Pseudo-random](https://en.wikipedia.org/wiki/Pseudorandomness) numbers are *not* what we want for ensuring user IDs cannot be easily guessed/collide. It's possible to get the exact same sequence of values out of a pseudo-random number generator by using the same *seed value*.
+[Pseudo-random](https://en.wikipedia.org/wiki/Pseudorandomness) numbers are _not_ what we want for ensuring user IDs cannot be easily guessed/collide. It's possible to get the exact same sequence of values out of a pseudo-random number generator by using the same _seed value_.
 
-Sometimes you *want* pseudo-random behavior (let's say for testing or fuzzing), but it's generally not desired for production systems that might run from a duplicated identical application image, since they *could* have weak pseudo-random seed initialization.
+Sometimes you _want_ pseudo-random behavior (let's say for testing or fuzzing), but it's generally not desired for production systems that might run from a duplicated identical application image, since they _could_ have weak pseudo-random seed initialization.
 
 ### (Secure) Random Numeric IDs
 
@@ -203,9 +202,9 @@ def create_user():
 
 Now we have a secure random value coming in for our user IDs. But having values like `583247` and `8923916` get generated are cool and all, but there are a few problems:
 
-- These numbers are random *and* quite inscrutable
+- These numbers are random _and_ quite inscrutable
 - The keyspace is fairly small (maybe good for comments on a popular website, but not for IDs!)
-- People can still *technically* check them all (the guessing space is 1 to `MAX_RANDOM_USER_ID`!)
+- People can still _technically_ check them all (the guessing space is 1 to `MAX_RANDOM_USER_ID`!)
 
 We need something better.
 
@@ -215,7 +214,7 @@ Along comes UUIDs -- you're probably used to seeing them now, values like this U
 
 `468e8075-5815-4fe2-80d3-45a31827954b` .
 
-They're *very* random (almost always generated with secure random sources), and while they're even worse for remembering, they're near impossible to practically guess -- the search space is just too large!
+They're _very_ random (almost always generated with secure random sources), and while they're even worse for remembering, they're near impossible to practically guess -- the search space is just too large!
 
 More importantly, UUIDs introduce methodology to the madness -- different versions of UUID are derived different ways -- combined with other sources of randomness or known values.
 
@@ -223,12 +222,12 @@ There are a lot of [versions of UUID](https://en.wikipedia.org/wiki/Universally_
 
 ### UUIDv1
 
-[Version 1 UUIDs](https://en.wikipedia.org/wiki/Universally_unique_identifier#Version_1_(date-time_and_MAC_address)) have three two components:
+[Version 1 UUIDs](<https://en.wikipedia.org/wiki/Universally_unique_identifier#Version_1_(date-time_and_MAC_address)>) have three two components:
 
 - a 60 bit date-time (at nanosecond precision)
 - a 48 bit [MAC address](https://en.wikipedia.org/wiki/MAC_address)
 
-But where's the randomness? Well v1s assume that you *won't* generate a ton of values in the same nanosecond (and there are some extra bits reserved for differentiating even when you do), but another source is the MAC address. MAC addresses uniquely (usually) identify network cards -- which is a security risk -- and those bits can be made random.
+But where's the randomness? Well v1s assume that you _won't_ generate a ton of values in the same nanosecond (and there are some extra bits reserved for differentiating even when you do), but another source is the MAC address. MAC addresses uniquely (usually) identify network cards -- which is a security risk -- and those bits can be made random.
 
 Here's what a UUIDv1 looks like:
 
@@ -247,13 +246,13 @@ SELECT uuid_generate_v1mc();
           uuid_generate_v1mc
 --------------------------------------
  dd1bbf10-0b47-11ed-80de-db48f6faaf86
- 
+
 (1 row)
 ```
 
 ### UUIDv4
 
-Version 4 UUIDs use *all* the available bits for randomness -- *122 bits worth*!.
+Version 4 UUIDs use _all_ the available bits for randomness -- _122 bits worth_!.
 
 UUIDv4s look like this:
 
@@ -261,7 +260,7 @@ UUIDv4s look like this:
 ce0b897d-03a0-4f54-8c97-41d29a325a23
 ```
 
-These don't have a time component, but  they don't have in time they make up for in randomness -- it is *very* unlikely for them to collide, so they make for excellent Global Unique IDentifiers ("GUID"s).
+These don't have a time component, but they don't have in time they make up for in randomness -- it is _very_ unlikely for them to collide, so they make for excellent Global Unique IDentifiers ("GUID"s).
 
 We can generate them in Postgres like this (with `uuid-ossp`):
 
@@ -271,7 +270,7 @@ SELECT gen_random_uuid();
            uuid_generate_v4
 --------------------------------------
  6ca93dde-81d4-4ea0-bfe1-92ecb4d81ee4
- 
+
 (1 row)
 ```
 
@@ -283,12 +282,12 @@ This is a workable solution, but as you might expect, it's not that easy.
 
 ![thats-alot-of-uuids.png](/images/blog/primary-keys/uuids.png)
 
-UUIDv1 and v4 were a start, but weren't enough for *many* companies out there. There are a couple shortcomings that plague both v1 and v2:
+UUIDv1 and v4 were a start, but weren't enough for _many_ companies out there. There are a couple shortcomings that plague both v1 and v2:
 
 - UUIDs are twice the size of `bigint`/`bigserial`
-- UUIDv1s contain a time element but they're *not* lexicographically sortable (this means they `SORT` terribly, relative to `integer` or a `timestamp` column)
+- UUIDv1s contain a time element but they're _not_ lexicographically sortable (this means they `SORT` terribly, relative to `integer` or a `timestamp` column)
 - UUIDv1s are less random than UUIDv4, and can collide/overlap in close enough time intervals, at large scale
-- UUIDv4s index *terribly*, as they're essentially random values (obviously, they `SORT` terribly as well)
+- UUIDv4s index _terribly_, as they're essentially random values (obviously, they `SORT` terribly as well)
 
 Many of the world's biggest companies generated UUIDs at speeds that made all of these deficiencies a problem.
 
@@ -316,7 +315,7 @@ Here's a quick list (from that IETF document):
 That's... A lot of UUIDs. They're all slightly different, but the innovation was summed up by the IETF:
 
 > An inspection of these implementations details the following trends that help define this standard:
-> 
+>
 > - Timestamps MUST be k-sortable. That is, values within or close to the same timestamp are ordered properly by sorting algorithms.
 > - Timestamps SHOULD be big-endian with the most-significant bits of the time embedded as-is without reordering.
 > - Timestamps SHOULD utilize millisecond precision and Unix Epoch as timestamp source. Although, there is some variation to this among implementations depending on the application requirements.
@@ -324,7 +323,7 @@ That's... A lot of UUIDs. They're all slightly different, but the innovation was
 > - IDs MUST ensure proper embedded sequencing to facilitate sorting when multiple UUIDs are created during a given timestamp.
 > - IDs MUST NOT require unique network identifiers as part of achieving uniqueness.
 > - Distributed nodes MUST be able to create collision resistant Unique IDs without a consulting a centralized resource.
-> **The IETF went on to introduce three 3 new types of UUIDs** that have these properties these companies were looking for: UUIDv6, UUIDv7, and UUIDv8.
+>   **The IETF went on to introduce three 3 new types of UUIDs** that have these properties these companies were looking for: UUIDv6, UUIDv7, and UUIDv8.
 
 So what's the difference you ask?
 
@@ -332,19 +331,19 @@ So what's the difference you ask?
 - **UUIDv7** - 36 bits of big endian unix timestamp (seconds since epoch + leapseconds w/ optional sub-second precision) + variable randomness up to 62 bits
 - **UUIDv8** - variable size timestamp (32/48/60/64 bits) + variable size clock (8/12 bits) + variable randomness (54/62 bits)
 
-It's not quite easy to work out what this all *means* but let's boil it down:
+It's not quite easy to work out what this all _means_ but let's boil it down:
 
 - All of these UUIDs sort properly (the "high bits" of time are first, like putting the year before the month -- "2022/07")
-- UUIDv6 *requires* randomness
+- UUIDv6 _requires_ randomness
 - The data contained in the UUID can be variable (ex. UUIDv8), this means you can bytes that mean something else (ex. an encoding of the compute region you're running in)
 
 Alright, done hearing about UUIDs? Let's get to the fun part.
 
 ## Benchmarking ID generation with `uuid-ossp` and `pg_idkit`
 
-With the history lesson behind us, let’s benchmark these ID generation mechanisms against each other! For UUIDv1 and UUIDv4 we can use [uuid-ossp](https://www.postgresql.org/docs/current/uuid-ossp.html).
+With the history lesson behind us, let's benchmark these ID generation mechanisms against each other! For UUIDv1 and UUIDv4 we can use [uuid-ossp](https://www.postgresql.org/docs/current/uuid-ossp.html).
 
-Unfortunately, `uuid-ossp` isn't *quite* so advanced as to have many of these newer UUIDs we've been discussing, so we’ll pull in [pg_idkit](https://github.com/t3hmrman/pg_idkit) here.
+Unfortunately, `uuid-ossp` isn't _quite_ so advanced as to have many of these newer UUIDs we've been discussing, so we'll pull in [pg_idkit](https://github.com/t3hmrman/pg_idkit) here.
 
 [pg_idkit](https://github.com/t3hmrman/pg_idkit) is built with Rust, so it gives us access to the following ID generation crates:
 
@@ -362,7 +361,7 @@ Unfortunately, `uuid-ossp` isn't *quite* so advanced as to have many of these ne
 
 For each type of UUID, we can test the following:
 
-- **Generation speed:** **How fast can I generate IDs (let's say 1,000,000 of them)?
+- **Generation speed:** \*\*How fast can I generate IDs (let's say 1,000,000 of them)?
 - **Table & Index size:** How much larger do tables and associated indices get?
 
 <aside>
@@ -382,17 +381,18 @@ Generation speed is pretty easy to test, we can enable `\\timing` mode on `psql`
 SELECT COUNT(idkit_ksuid_generate()) FROM generate_series(1, 1000000);
 ```
 
-Running all of the ID generation mechanisms on a *single core* of my machine (which happens to be an [Oryx Pro](https://system76.com/laptops/oryx)), the lowest of 5 runs for each ID looks like this:
+Running all of the ID generation mechanisms on a _single core_ of my machine (which happens to be an [Oryx Pro](https://system76.com/laptops/oryx)), the lowest of 5 runs for each ID looks like this:
 
 ![Generation speed test](/images/blog/primary-keys/generation-speed-chart.jpg)
 
-To be fair, **generation speed shouldn’t be a deal breaker** as it’s unlikely to be the bottle neck for most applications. That said, it is nice to have some data on where each ID generation mechanism lands.
+To be fair, **generation speed shouldn't be a deal breaker** as it's unlikely to be the bottle neck for most applications. That said, it is nice to have some data on where each ID generation mechanism lands.
 
 <aside>
 ℹ️ Percona and CyberTec have some excellent posts on the topic:
 
 [https://www.percona.com/blog/2014/12/19/store-uuid-optimized-way/](https://www.percona.com/blog/2014/12/19/store-uuid-optimized-way/)
 [https://www.cybertec-postgresql.com/en/uuid-serial-or-identity-columns-for-postgresql-auto-generated-primary-keys/](https://www.cybertec-postgresql.com/en/uuid-serial-or-identity-columns-for-postgresql-auto-generated-primary-keys/)
+
 </aside>
 
 ### Table & Index size
@@ -400,44 +400,44 @@ To be fair, **generation speed shouldn’t be a deal breaker** as it’s unlikel
 We can check the size of our tables & related indices with this query (after running `VACUUM`):
 
 ```sql
-SELECT
-   relname  as table_name,
-   pg_size_pretty(pg_total_relation_size(relid)) As "Table Size",
-   pg_size_pretty(pg_indexes_size(relid)) as "Index Size",
-   pg_size_pretty(pg_relation_size(relid)) as "Total Size"
-   FROM pg_catalog.pg_statio_user_tables
-ORDER BY pg_total_relation_size(relid) DESC;
+select
+  relname as table_name,
+  pg_size_pretty(pg_total_relation_size(relid)) as "Table Size",
+  pg_size_pretty(pg_indexes_size(relid)) as "Index Size",
+  pg_size_pretty(pg_relation_size(relid)) as "Total Size"
+from pg_catalog.pg_statio_user_tables
+order by pg_total_relation_size(relid) desc;
 ```
 
 Here are the sizes in tabular form:
 
 ![Sizes in tabular form](/images/blog/primary-keys/table-and-index-size-chart.jpg)
 
-These numbers are *mostly* a reflection of the *length* of the default settings of `pg_idkit` but probably worth having in front of you anyway.
+These numbers are _mostly_ a reflection of the _length_ of the default settings of `pg_idkit` but probably worth having in front of you anyway.
 
 With this, we probably have enough information to make a decision (and a new library to generate our UUIDs with)!
 
 ## Which ID should you use?
 
-As usual, *it depends* -- you didn't think it'd be that easy, did you?
+As usual, _it depends_ -- you didn't think it'd be that easy, did you?
 
 All I can offer are some general rules of thumb that hopefully work for you:
 
-- `integer`s and `serial` have obvious benefits for simplicity, storage, and sortability. You *might* not want to expose them to the world though.
+- `integer`s and `serial` have obvious benefits for simplicity, storage, and sortability. You _might_ not want to expose them to the world though.
 - If you want the ultimate in collision avoidance UUIDv4 is OK
-- UUIDv1 *could* have been great, *but* it doesn't lexicographically sort.
-- The best time-based ID seems to be `xid`, with good performance *and* sort friendliness
+- UUIDv1 _could_ have been great, _but_ it doesn't lexicographically sort.
+- The best time-based ID seems to be `xid`, with good performance _and_ sort friendliness
 - If you want to be a little more standards-oriented, UUID v6/v7
 
 As usual, the best results will come from weighing all the options and finding what's best for your use-case, and doing appropriate testing on your data.
 
 ## Possible Improvements
 
-We’ve done some good exploration so far, but here are some ideas for interesting use cases for `pg_idkit` and measuring the impact of ID generation using it.
+We've done some good exploration so far, but here are some ideas for interesting use cases for `pg_idkit` and measuring the impact of ID generation using it.
 
 ### Usecase: Generating our `created_at` columns from our IDs
 
-One interesting feature would be using at least partially time-based UUIDs for `created_at` columns -- we could save space by *virtualizing* our `created_at` columns:
+One interesting feature would be using at least partially time-based UUIDs for `created_at` columns -- we could save space by _virtualizing_ our `created_at` columns:
 
 ```sql
 -- At table creation
@@ -448,12 +448,12 @@ CREATE TABLE users (
 );
 
 -- An example query for a specific KSUID that uses created_at
-SELECT *, idkit_ksuid_extract_timestamptz(id) 
+SELECT *, idkit_ksuid_extract_timestamptz(id)
 FROM users
 WHERE id = '0F755149A55730412B0AEC0E3B5B089C14B5B58D';
 ```
 
-Ideally we could use the `GENERATED ALWAYS AS ( ... )` syntax for [generated columns](https://www.postgresql.org/docs/current/ddl-generated-columns.html) while creating the table, but as the time of this post *Postgres does not yet support virtual generated columns (only stored ones)*.
+Ideally we could use the `GENERATED ALWAYS AS ( ... )` syntax for [generated columns](https://www.postgresql.org/docs/current/ddl-generated-columns.html) while creating the table, but as the time of this post _Postgres does not yet support virtual generated columns (only stored ones)_.
 
 ### Benchmarking: Measuring index fragmentation
 
@@ -469,7 +469,7 @@ Another great metric to measure might be performance of these indices on certain
 
 In most code bases, simple `WHERE` queries with `SORT`s abound, and one of the big benefits of UUIDv6, UUIDv7 and the other alternatives is lexicographic sorting, after all.
 
-Knowing *just how good* a certain ID generation method is at maintaining locality would be nice to know.
+Knowing _just how good_ a certain ID generation method is at maintaining locality would be nice to know.
 
 Creating and using a function like `idkit_uuidv1_extract_timestamptz` and using it in a [“functional index” (an index on an expression)](https://www.postgresql.org/docs/14/indexes-expressional.html) could resolve the sort unfriendliness of UUIDv1 as well!
 
@@ -488,4 +488,3 @@ Hopefully this article helps you head off some bikeshedding with your teammates
 - [What are PostgreSQL Templates?](https://supabase.com/blog/postgresql-templates)
 - [Realtime Postgres RLS on Supabase](https://supabase.com/blog/realtime-row-level-security-in-postgresql)
 - [Implementing "seen by" functionality with Postgres](https://supabase.com/blog/seen-by-in-postgresql)
-
diff --git a/apps/www/_blog/2022-10-03-postgres-wasm.mdx b/apps/www/_blog/2022-10-03-postgres-wasm.mdx
index 13121a74747..7ef850cab10 100644
--- a/apps/www/_blog/2022-10-03-postgres-wasm.mdx
+++ b/apps/www/_blog/2022-10-03-postgres-wasm.mdx
@@ -101,7 +101,7 @@ See [source code](https://github.com/snaplet/postgres-browser/tree/main/packages
 Next, we need to run the VM inside our browser. How? [WASM](https://en.wikipedia.org/wiki/WebAssembly).
 We use [v86](https://github.com/copy/v86) to run our VM inside the browser. Our demo application is very simple - plain HTML and some basic styling.
 
-See [source code](https://github.com/snaplet/postgres-wasm/tree/main/packages/runtime). 
+See [source code](https://github.com/snaplet/postgres-wasm/tree/main/packages/runtime).
 
 ### Network proxy
 
diff --git a/apps/www/_blog/2022-10-05-supabase-beta-update-september-2022.mdx b/apps/www/_blog/2022-10-05-supabase-beta-update-september-2022.mdx
index 2072a1f6e70..91bb0ede5a0 100644
--- a/apps/www/_blog/2022-10-05-supabase-beta-update-september-2022.mdx
+++ b/apps/www/_blog/2022-10-05-supabase-beta-update-september-2022.mdx
@@ -2,22 +2,23 @@
 title: Supabase Beta September 2022
 description: We were too focused on clearing out the backlog so we didn't ship anything new last month... or did we?!
 author: ant_wilson
-image: 2022-september/monthly-update-september-2022.jpg  
+image: 2022-september/monthly-update-september-2022.jpg
 thumb: 2022-september/monthly-update-september-2022.jpg
 tags:
   - release-notes
 date: '2022-10-05'
 toc_depth: 3
 ---
+
 For September we made a huge effort to focus on crushing our backlog and outstanding tickets amongst other things, here's the full list of updates for the month...
 
 ## Kaizen Week
 
-Post Launch Week we did three subsequent weeks of [Kaizen](https://en.wikipedia.org/wiki/Kaizen), a term we use internally to deliver constant and incremental improvement. Each week had a different focus:
+Post Launch Week we did three subsequent weeks of [Kaizen](https://en.wikipedia.org/wiki/Kaizen), a term we use internally to deliver constant and incremental improvement. Each week had a different focus:
 
--   Week 1: QA and testing
--   Week 2: Documentation
--   Week 3: Issue Backlog and Automation
+- Week 1: QA and testing
+- Week 2: Documentation
+- Week 3: Issue Backlog and Automation
 
 It's pretty rare for a company to stop feature development altogether, but luckily we're just a bunch of developers so we all know the pain of technical debt. After 5 Launch Weeks, working on testing and backlogs feels like a bit of a relief.
 
@@ -39,11 +40,11 @@ We launched the new Auth UI on Product Hunt! Auth UI is a pre-built React compon
 
 ![Postgres WASM with Snaplet and Supabase](/images/blog/2022-september/postgres-wasm.jpg)
 
-If you've ever wondered, "can I run Postgres inside a browser, using an embeddable Linux Virtual Machine?", wonder no longer. With our friends at [Snaplet](https://www.snaplet.dev/?utm_campaign=Beta%20update%20emails&utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz-8u0x9grbiydYqh56hC_8Dta4ZiTdWbW0eXWkVCnUEUGWWoVDFXCpWzJWImkLfM-lG-o2JX), we've released an open source Postgres WASM.
+If you've ever wondered, "can I run Postgres inside a browser, using an embeddable Linux Virtual Machine?", wonder no longer. With our friends at [Snaplet](https://www.snaplet.dev/?utm_campaign=Beta%20update%20emails&utm_source=hs_email&utm_medium=email&_hsenc=p2ANqtz-8u0x9grbiydYqh56hC_8Dta4ZiTdWbW0eXWkVCnUEUGWWoVDFXCpWzJWImkLfM-lG-o2JX), we've released an open source Postgres WASM.
 
 [Read the blog post](https://supabase.com/blog/postgres-wasm) <br/>
 [Comment on Hacker News](https://news.ycombinator.com/item?id=33067962) <br/>
-Visit the repo: [Snaplet](https://github.com/snaplet/postgres-wasm) | [Supabase](https://github.com/supabase-community/postgres-wasm)
+Visit the repo: [Snaplet](https://github.com/snaplet/postgres-wasm) | [Supabase](https://github.com/supabase-community/postgres-wasm)
 
 ## Security updates
 
@@ -54,40 +55,39 @@ We're making some changes to the way the Dashboard interacts with your database.
 ## Quick product updates
 
 - Edge functions free plan script size is bumped to 2 MB
-- [functions-go](https://github.com/supabase-community/functions-go) was just contributed to supabase-community by [Zain Khan](https://twitter.com/Za1n_K)
-- A new [guide](https://supabase.com/docs/guides/auth/auth-captcha) to add captcha to your sign-in, sign-up, and password reset forms
-- New Postgres Extension for monitoring your PostgreSQL database network traffic: [pg_netstat](https://github.com/supabase/pg_netstat)
-- Added [docs](https://supabase.com/docs/guides/storage-cdn) for how caching works in Supabase
+- [functions-go](https://github.com/supabase-community/functions-go) was just contributed to supabase-community by [Zain Khan](https://twitter.com/Za1n_K)
+- A new [guide](https://supabase.com/docs/guides/auth/auth-captcha) to add captcha to your sign-in, sign-up, and password reset forms
+- New Postgres Extension for monitoring your PostgreSQL database network traffic: [pg_netstat](https://github.com/supabase/pg_netstat)
+- Added [docs](https://supabase.com/docs/guides/storage-cdn) for how caching works in Supabase
 
 ## Migrate from Heroku to Supabase
 
 ![Migrate from Heroku to Supabase](/images/blog/2022-september/migrate-from-heroku-to-supabase.jpg)
 
-In case you missed it, Heroku is shutting down their free tier. We're big fans of Heroku and take a lot of inspiration from what they've built. Supabase is compatible with Heroku's PostgreSQL product (because we're just Postgres too), and if you have a free project running on Heroku we've created a [tool to help migrate](https://migrate.supabase.com/) to our free tier.
+In case you missed it, Heroku is shutting down their free tier. We're big fans of Heroku and take a lot of inspiration from what they've built. Supabase is compatible with Heroku's PostgreSQL product (because we're just Postgres too), and if you have a free project running on Heroku we've created a [tool to help migrate](https://migrate.supabase.com/) to our free tier.
 
 ## Made with Supabase
 
 ![Made with Supabase - Supabase Schema](/images/blog/2022-september/madewithsupabase.jpg)
 
-[Supabase Schema](https://supabase-schema.vercel.app/): An open source, free, login-less and secured Supabase Schema Visualizer. Simply plug in your URL and anon key and see a visual representation of your database schema! Built by the amazing [Zernonia](https://twitter.com/zernonia) using Vue 3, Viti, and WindiCSS.
+[Supabase Schema](https://supabase-schema.vercel.app/): An open source, free, login-less and secured Supabase Schema Visualizer. Simply plug in your URL and anon key and see a visual representation of your database schema! Built by the amazing [Zernonia](https://twitter.com/zernonia) using Vue 3, Viti, and WindiCSS.
 
 ## Extended Community Highlights
 
 ![Community](/images/blog/2022-june/community.jpg)
 
-- Building a viral application to visualize train routes. [Blog](https://vercel.com/blog/building-a-viral-application-to-visualize-train-routes)
+- Building a viral application to visualize train routes. [Blog](https://vercel.com/blog/building-a-viral-application-to-visualize-train-routes)
 - OTP Authentication with Supabase and Twilio in React. [Tutorial](https://refine.dev/blog/supabase-twilio-otp-authentication-in-react/)
-- Join Vercel and us for [Next.js Conf](https://nextjs.org/conf).
-- Building $1K - $10K MRR Micro SaaS around Supabase. [Blog](https://microsaasidea.substack.com/p/micro-saas-products-around-supabase)
-- Watch How Netlify and Supabase Enables "Supa" DX. [Webinar](https://www.netlify.com/resources/webinars/how-netlify-supabase-enables-supa-dx/)
-- Postgres database functions are your next favorite feature! [Blog](https://mirror.xyz/0x7D15080A13c8128dBAf90a2c2326058b5c1D5eac/MaiOq5m1xSa9QfMuiLYq4bJdA0owWoTpOZNlQv76_so)
-- Create a blog with Vue, Tailwindcss & Supabase. [Part 1](https://youtube.com/watch?v=0NB9lgFcOT4) and [Part 2](https://youtube.com/watch?v=UP2mHUpcv6g) 
+- Join Vercel and us for [Next.js Conf](https://nextjs.org/conf).
+- Building $1K - $10K MRR Micro SaaS around Supabase. [Blog](https://microsaasidea.substack.com/p/micro-saas-products-around-supabase)
+- Watch How Netlify and Supabase Enables "Supa" DX. [Webinar](https://www.netlify.com/resources/webinars/how-netlify-supabase-enables-supa-dx/)
+- Postgres database functions are your next favorite feature! [Blog](https://mirror.xyz/0x7D15080A13c8128dBAf90a2c2326058b5c1D5eac/MaiOq5m1xSa9QfMuiLYq4bJdA0owWoTpOZNlQv76_so)
+- Create a blog with Vue, Tailwindcss & Supabase. [Part 1](https://youtube.com/watch?v=0NB9lgFcOT4) and [Part 2](https://youtube.com/watch?v=UP2mHUpcv6g)
 - Flutter Supabase Authentication. [Tutorial](https://www.sandromaglione.com/techblog/flutter-supabase-authentication-complete-tutorial)
 - Vue 3 + Pinia + Supabase Auth (Email). [Tutorial](https://towardsdev.com/vue-3-pinia-supabase-auth-email-1228f5f8502e)
 - Power up your ClickUp skills with Supabase, Figma, and DhiWise in a day. [Tutorial](https://dev.to/saloni137/power-up-your-clickup-skills-with-supabase-figma-and-dhiwise-in-a-day-3pak)
 - Creating an Email Authentication using Supabase in React. [Tutorial](https://dev.to/surajondev/creating-an-email-authentication-using-supabase-in-react-5883)
 
-
 ## Meme Zone
 
 If you made it this far in the blog post you deserve a treat. [Follow us on Twitter](https://twitter.com/supabase) for more.
diff --git a/apps/www/_blog/2022-10-14-postgres-full-text-search-vs-the-rest.mdx b/apps/www/_blog/2022-10-14-postgres-full-text-search-vs-the-rest.mdx
index 1a587021735..42561f91266 100644
--- a/apps/www/_blog/2022-10-14-postgres-full-text-search-vs-the-rest.mdx
+++ b/apps/www/_blog/2022-10-14-postgres-full-text-search-vs-the-rest.mdx
@@ -78,13 +78,9 @@ With nothing but the raw data in your database, we can actually do some _basic_
 
 ```sql
 select
-	*
-from
-	movies
-where
-  title like '%Avengers%'
-	or
-	overview like '%Avengers%';
+  *
+from movies
+where title like '%Avengers%' or overview like '%Avengers%';
 ```
 
 The `LIKE` [operator](https://www.postgresql.org/docs/current/functions-matching.html#FUNCTIONS-LIKE) as used in the query above will match _only_ the term "Avengers", but it will match it in any part of a given row's `title` or `overview`.
diff --git a/apps/www/_blog/2022-11-22-flutter-authentication-and-authorization-with-rls.mdx b/apps/www/_blog/2022-11-22-flutter-authentication-and-authorization-with-rls.mdx
index 5731c0bd3e7..93ed654d530 100644
--- a/apps/www/_blog/2022-11-22-flutter-authentication-and-authorization-with-rls.mdx
+++ b/apps/www/_blog/2022-11-22-flutter-authentication-and-authorization-with-rls.mdx
@@ -17,21 +17,21 @@ This article is the second part of the Flutter tutorial series. During the serie
 In this article, I will show you how you can make a secure chat application by introducing authentication and authorization to the basic chat app that we created [previously](https://supabase.com/blog/flutter-tutorial-building-a-chat-app).
 
 We will use [Supabase](https://supabase.com/) to store the chat data and will use its [auth feature](https://supabase.com/auth) to provide a secure chat room feature.
-Supabase lets us build a secure database where we can control who can access what part of the database, so your users’ data is secured without worrying about the backend. 
+Supabase lets us build a secure database where we can control who can access what part of the database, so your users' data is secured without worrying about the backend.
 
 ## What we created in the previous article
 
-Before we jump in, let’s go over what we built in the [previous article](blog/flutter-tutorial-building-a-chat-app), because we will be building on top of it. If you have not gone through it, I recommend you to go check it out. 
+Before we jump in, let's go over what we built in the [previous article](blog/flutter-tutorial-building-a-chat-app), because we will be building on top of it. If you have not gone through it, I recommend you to go check it out.
 
-In the previous article, we created a basic real-time chat application. Users will register or sign in using an email address and password. Once they are signed in, they are taken to a chat page, where they can view and send messages to everyone in the app. There are no Chat rooms, and everyone’s messages were sent to the same chat room. 
+In the previous article, we created a basic real-time chat application. Users will register or sign in using an email address and password. Once they are signed in, they are taken to a chat page, where they can view and send messages to everyone in the app. There are no Chat rooms, and everyone's messages were sent to the same chat room.
 
-You can also find a complete code example [here](https://github.com/supabase-community/flutter-chat/tree/with_auth) to follow along. 
+You can also find a complete code example [here](https://github.com/supabase-community/flutter-chat/tree/with_auth) to follow along.
 
 ![Chat app without authorization](/images/blog/flutter-chat-auth/chat-app-screenshot.png)
 
 ## Overview of the final app
 
-The app will allow us to have 1 on 1 chat with other users in the app. To enable this, we will introduce a new rooms page. The rooms page serves two purposes here, one is to initiate a conversation with other users, and the other is to display existing chat rooms. At the top of the app, we see a list of other users’ icons. A user can tap the icon to start a 1 on 1 conversation. Below the icons, there is a list of rooms that the user is a part of. 
+The app will allow us to have 1 on 1 chat with other users in the app. To enable this, we will introduce a new rooms page. The rooms page serves two purposes here, one is to initiate a conversation with other users, and the other is to display existing chat rooms. At the top of the app, we see a list of other users' icons. A user can tap the icon to start a 1 on 1 conversation. Below the icons, there is a list of rooms that the user is a part of.
 
 ![Chat app without authorization](/images/blog/flutter-chat-auth/rooms-and-chat-page.png)
 
@@ -52,7 +52,7 @@ flutter_bloc: ^8.0.0
 
 Since the app has evolved, we also need to update our table schema. In order to store rooms data, we will add a rooms table. We will also modify the messages table to add a foreign key constraint to the rooms table so that we can tell which message belongs to which room.
 
-We will also introduce a `create_new_room` function, which is a [database function](https://supabase.com/docs/guides/database/functions) that handles chat room creation. It knows to create a new room if a chat room with the two users does not exist yet, or to just return the room ID if it already exists. 
+We will also introduce a `create_new_room` function, which is a [database function](https://supabase.com/docs/guides/database/functions) that handles chat room creation. It knows to create a new room if a chat room with the two users does not exist yet, or to just return the room ID if it already exists.
 
 ```sql
 -- *** Table definitions ***
@@ -89,7 +89,7 @@ create or replace function create_new_room(other_user_id uuid) returns uuid as $
         with rooms_with_profiles as (
             select room_id, array_agg(profile_id) as participants
             from room_participants
-            group by room_id               
+            group by room_id
         )
         select room_id
         into new_room_id
@@ -119,7 +119,7 @@ $$ language plpgsql security definer;
 
 ### Setup deep links
 
-Something we skipped in the previous article was sending confirmation emails to users when they signup. Since today is about security, let's properly send confirmation emails to people who signup. 
+Something we skipped in the previous article was sending confirmation emails to users when they signup. Since today is about security, let's properly send confirmation emails to people who signup.
 
 When we send confirmation emails, the users need to be brought back to the app somehow.
 Since supabase_flutter has a mechanism to detect and handle deep links, we will register a `io.supabase.chat://login` as our deep link for the app and bring the users back after confirming their email address.
@@ -184,9 +184,9 @@ And that is it for deep link configuration.
 
 ### Step1: Create rooms page
 
-The rooms page will load two types of data, recently added users and a list of rooms that the user belongs to. We will be using bloc to load these two types of data and display them on the rooms page. 
+The rooms page will load two types of data, recently added users and a list of rooms that the user belongs to. We will be using bloc to load these two types of data and display them on the rooms page.
 
-Let’s start out by creating states for the rooms page.
+Let's start out by creating states for the rooms page.
 The rooms page would have four different states, loading, loaded, empty, and error. We will display different UI on the rooms page depending on what state it is.
 Create a `lib/cubit/rooms/rooms_state.dart` file and paste the following code.
 You may see some errors, but we will take care of them in the next step.
@@ -223,8 +223,8 @@ class RoomsError extends RoomState {
 ```
 
 Now that we have the states defined, we will create rooms_cubit.
-A [cubit](https://bloclibrary.dev/#/coreconcepts?id=cubit) is a class within the flutter_bloc library where we will make requests to Supabase to get the data and transform them into states and emit them to the UI widgets. 
-Let's create a `lib/cubit/rooms/rooms_cubit.dart` file and complete the cubit. 
+A [cubit](https://bloclibrary.dev/#/coreconcepts?id=cubit) is a class within the flutter_bloc library where we will make requests to Supabase to get the data and transform them into states and emit them to the UI widgets.
+Let's create a `lib/cubit/rooms/rooms_cubit.dart` file and complete the cubit.
 
 ```dart title=lib/cubit/rooms/rooms_cubit.dart
 import 'dart:async';
@@ -369,9 +369,9 @@ class RoomCubit extends Cubit<RoomState> {
 }
 ```
 
-Now that we have the states and cubit to power our rooms page, it’s time to create the `RoomsPage`. 
+Now that we have the states and cubit to power our rooms page, it's time to create the `RoomsPage`.
 
-We have two list views, one horizontal list view to display other users, and one vertical list views with list tiles representing each room that the user is a part of. 
+We have two list views, one horizontal list view to display other users, and one vertical list views with list tiles representing each room that the user is a part of.
 We will create a `lib/pages/rooms_page.dart` file with the following content.
 
 ```dart title=lib/pages/rooms_page.dart
@@ -670,7 +670,7 @@ class ChatCubit extends Cubit<ChatState> {
 }
 ```
 
-Chat cubit is pretty simple. It sets a real-time listener to the database using the stream method and emits an empty state if there are no messages in the room, or emits a loaded state if there are messages. 
+Chat cubit is pretty simple. It sets a real-time listener to the database using the stream method and emits an empty state if there are no messages in the room, or emits a loaded state if there are messages.
 
 Because we are using cubit, we need to modify the MessagesPage widget as well.
 Open `lib/pages/chat_page.dart` and let's update it.
@@ -873,7 +873,7 @@ class _ChatBubble extends StatelessWidget {
 
 ### Step 3: Implementing Authentication in Flutter
 
-Because we have modified the setting of our Supabase to send a confirmation email, we need to make some modifications to the register page and login page as well. 
+Because we have modified the setting of our Supabase to send a confirmation email, we need to make some modifications to the register page and login page as well.
 
 The main change is how we handle navigation.
 Previously, we were able to navigate the user to `ChatPage` right after sign-in was complete.
@@ -1054,9 +1054,9 @@ class _RegisterPageState extends State<RegisterPage> {
 ```
 
 Login page becomes more simple.
-All it is doing is taking a user’s email and password and logging them in.
+All it is doing is taking a user's email and password and logging them in.
 It is not doing any navigation whatsoever.
-This is because `LoginPage` is navigated on top of `RegisterPage`, the auth state listener on `RegisterPage` is still active, and therefore can take care of the navigation. 
+This is because `LoginPage` is navigated on top of `RegisterPage`, the auth state listener on `RegisterPage` is still active, and therefore can take care of the navigation.
 
 ```dart title=lib/pages/login_page.dart
 import 'package:flutter/material.dart';
@@ -1202,7 +1202,7 @@ class SplashPageState extends State<SplashPage> {
 ```
 
 Finally we implement those `ProfilesCubit` that you saw here and there throughout the code.
-This cubit will act as in memory cache of all the profiles data so that the app does not have to go fetch the same profiles every single time it needs it. 
+This cubit will act as in memory cache of all the profiles data so that the app does not have to go fetch the same profiles every single time it needs it.
 Create `profiles_state.dart` and `profiles_cubit.dart` under `lib/cubits/` and add the following code.
 
 ```dart title=lib/cubits/profiles_state.dart
@@ -1301,7 +1301,7 @@ class MyApp extends StatelessWidget {
 
 ### Step 4: Authorization with Row Level Security (RLS)
 
-At this point, we seemingly have a complete app, except if we open the app right now, we will see every user’s room with all the messages that have ever been sent within the app by any user. This is because we have not set up Row Level Security yet. [Row Level Security](https://supabase.com/docs/guides/auth/row-level-security) is a mechanism in PostgreSQL that allows developers to define who can perform what operation on a row-by-row basis. There are two ways we can define Row Level Security policies in Supabase, with the GUI or through SQL, but we will set them using SQL today. Let’s run the following SQL to set the security policy.
+At this point, we seemingly have a complete app, except if we open the app right now, we will see every user's room with all the messages that have ever been sent within the app by any user. This is because we have not set up Row Level Security yet. [Row Level Security](https://supabase.com/docs/guides/auth/row-level-security) is a mechanism in PostgreSQL that allows developers to define who can perform what operation on a row-by-row basis. There are two ways we can define Row Level Security policies in Supabase, with the GUI or through SQL, but we will set them using SQL today. Let's run the following SQL to set the security policy.
 
 ```sql
 -- Returns true if the signed in user is a participant of the room
@@ -1340,9 +1340,9 @@ create policy "Users can insert messages on rooms they are in."
   on public.messages for insert with check (is_room_participant(room_id) and profile_id = auth.uid());
 ```
 
-Notice that we have created a handy `is_room_participant` function that will return whether a particular user is a participant or not in a specific room. 
+Notice that we have created a handy `is_room_participant` function that will return whether a particular user is a participant or not in a specific room.
 
-With the Row Level Security policies set up, our application is complete. We now have a real-time chat application with proper authentication and authorization in place. 
+With the Row Level Security policies set up, our application is complete. We now have a real-time chat application with proper authentication and authorization in place.
 
 ## Conclusions/ Future Improvements
 
diff --git a/apps/www/_blog/2022-11-24-sql-or-nosql-both-with-postgresql.mdx b/apps/www/_blog/2022-11-24-sql-or-nosql-both-with-postgresql.mdx
index 43356c9a3cd..a347a18997e 100644
--- a/apps/www/_blog/2022-11-24-sql-or-nosql-both-with-postgresql.mdx
+++ b/apps/www/_blog/2022-11-24-sql-or-nosql-both-with-postgresql.mdx
@@ -11,29 +11,30 @@ date: '2022-11-24'
 toc_depth: 3
 ---
 
-It's a tough decision for any developer starting a new project.  Should you store your data in a standard, time-tested SQL database, or go with one of the newer NoSQL document-based databases?  This seemingly simple decision can literally make or break your project down the line.  Choose correctly and structure your data well, and you may sail smoothly into production and watch your app take off.  Make the wrong choice and you could be headed for nightmares (and maybe even some major re-writes) before your app ever makes it out the door.
+It's a tough decision for any developer starting a new project. Should you store your data in a standard, time-tested SQL database, or go with one of the newer NoSQL document-based databases? This seemingly simple decision can literally make or break your project down the line. Choose correctly and structure your data well, and you may sail smoothly into production and watch your app take off. Make the wrong choice and you could be headed for nightmares (and maybe even some major re-writes) before your app ever makes it out the door.
 
 ## Simplicity vs Power
-There are tradeoffs with both SQL and NoSQL solutions.  Typically it's easier to get started with NoSQL data structures, especially when the data is complex or hierarchical.  You can just take a JSON data object from your front-end code and throw it in the database and be done with it.  But later when you need to access that data to answer some basic business questions, it's much more difficult.  A SQL solution makes it easier to gather data and draw conclusions down the line.  Let's look at an example:
+
+There are tradeoffs with both SQL and NoSQL solutions. Typically it's easier to get started with NoSQL data structures, especially when the data is complex or hierarchical. You can just take a JSON data object from your front-end code and throw it in the database and be done with it. But later when you need to access that data to answer some basic business questions, it's much more difficult. A SQL solution makes it easier to gather data and draw conclusions down the line. Let's look at an example:
 
 Each day I track the food I eat, along with the number of calories in each item:
 
-| Day    | Food Item | Calories | Meal |
-|--------|-----------|----------|------|
-| 01 Jan | Apple     | 72 | Breakfast |
-| 01 Jan | Oatmeal   | 146 | Breakfast |
-| 01 Jan | Sandwich  | 445 | Lunch |
-| 01 Jan | Chips     | 280 | Lunch |
-| 01 Jan | Cookie    | 108 | Lunch |
-| 01 Jan | Mixed Nuts | 175 | Snack |
-| 01 Jan | Pasta/Sauce | 380 | Dinner |
-| 01 Jan | Garlic Bread | 200 | Dinner |
-| 01 Jan | Broccoli | 32 | Dinner |
+| Day    | Food Item    | Calories | Meal      |
+| ------ | ------------ | -------- | --------- |
+| 01 Jan | Apple        | 72       | Breakfast |
+| 01 Jan | Oatmeal      | 146      | Breakfast |
+| 01 Jan | Sandwich     | 445      | Lunch     |
+| 01 Jan | Chips        | 280      | Lunch     |
+| 01 Jan | Cookie       | 108      | Lunch     |
+| 01 Jan | Mixed Nuts   | 175      | Snack     |
+| 01 Jan | Pasta/Sauce  | 380      | Dinner    |
+| 01 Jan | Garlic Bread | 200      | Dinner    |
+| 01 Jan | Broccoli     | 32       | Dinner    |
 
 I also track the number of cups of water I drink and when I drink them:
 
 | Day    | Time  | Cups |
-|--------|-------|------|
+| ------ | ----- | ---- |
 | Jan 01 | 08:15 | 1    |
 | Jan 01 | 09:31 | 1    |
 | Jan 01 | 10:42 | 2    |
@@ -45,94 +46,96 @@ I also track the number of cups of water I drink and when I drink them:
 
 And finally, I track my exercise:
 
-| Day    | Time  | Duration | Exercise |
-|--------|-------|----------|----------|
-| Jan 01 | 11:02 | 0.5 | Walking |
-| Jan 02 | 09:44 | 0.75 | Bicycling |
-| Jan 02 | 17:00 | 0.25 | Walking |
+| Day    | Time  | Duration | Exercise  |
+| ------ | ----- | -------- | --------- |
+| Jan 01 | 11:02 | 0.5      | Walking   |
+| Jan 02 | 09:44 | 0.75     | Bicycling |
+| Jan 02 | 17:00 | 0.25     | Walking   |
 
 For each day I also track my current weight along with any notes for the day:
 
-| Day    | Weight | Notes |
-|--------|--------|-------|
-| Jan 01 | 172.6  | This new diet is awesome! |
-| Jan 14 | 170.2  | Not sure all this is worth it. |
-| Jan 22 | 169.8  | Jogged past a McDonald's today. It was hard. |
+| Day    | Weight | Notes                                              |
+| ------ | ------ | -------------------------------------------------- |
+| Jan 01 | 172.6  | This new diet is awesome!                          |
+| Jan 14 | 170.2  | Not sure all this is worth it.                     |
+| Jan 22 | 169.8  | Jogged past a McDonald's today. It was hard.       |
 | Feb 01 | 168.0  | I feel better, but sure miss all that greasy food. |
 
 ## Gathering All That Data
 
-That's a lot of different data that needs to be gathered, stored, retrieved, and later analyzed.  It's organized simply and easily, but the number of records varies from day to day.  On any given day I may have zero or more entries for food, water, and exercise, and I may have zero or one entry for weight & notes.
+That's a lot of different data that needs to be gathered, stored, retrieved, and later analyzed. It's organized simply and easily, but the number of records varies from day to day. On any given day I may have zero or more entries for food, water, and exercise, and I may have zero or one entry for weight & notes.
 
-In my app, I gather all the data for a single day on one page, to make it easier for my users.  So, I get a JSON object for each day that looks like this:
+In my app, I gather all the data for a single day on one page, to make it easier for my users. So, I get a JSON object for each day that looks like this:
 
 ```json
-{ "date": "2022-01-01", 
-  "weight": 172.6, 
-  "notes": "This new diet is awesome!", 
+{
+  "date": "2022-01-01",
+  "weight": 172.6,
+  "notes": "This new diet is awesome!",
   "food": [
-      { "title": "Apple", "calories": 72, "meal": "Breakfast"},
-      { "title": "Oatmeal", "calories": 146, "meal": "Breakfast"},
-      { "title": "Sandwich", "calories": 445, "meal": "Lunch"},
-      { "title": "Chips", "calories": 280, "meal": "Lunch"},
-      { "title": "Cookie", "calories": 108, "meal": "Lunch"},
-      { "title": "Mixed Nuts", "calories": 175, "meal": "Snack"},
-      { "title": "Pasta/Sauce", "calories": 380, "meal": "Dinner"},
-      { "title": "Garlic Bread", "calories": 200, "meal": "Dinner"},
-      { "title": "Broccoli", "calories": 32, "meal": "Dinner"}
+    { "title": "Apple", "calories": 72, "meal": "Breakfast" },
+    { "title": "Oatmeal", "calories": 146, "meal": "Breakfast" },
+    { "title": "Sandwich", "calories": 445, "meal": "Lunch" },
+    { "title": "Chips", "calories": 280, "meal": "Lunch" },
+    { "title": "Cookie", "calories": 108, "meal": "Lunch" },
+    { "title": "Mixed Nuts", "calories": 175, "meal": "Snack" },
+    { "title": "Pasta/Sauce", "calories": 380, "meal": "Dinner" },
+    { "title": "Garlic Bread", "calories": 200, "meal": "Dinner" },
+    { "title": "Broccoli", "calories": 32, "meal": "Dinner" }
   ],
   "water": [
-      {"time": "08:15", "qty": 1},
-      {"time": "09:31", "qty": 1},
-      {"time": "10:42", "qty": 2},
-      {"time": "10:42", "qty": 2},
-      {"time": "12:07", "qty": 1},
-      {"time": "14:58", "qty": 1},
-      {"time": "17:15", "qty": 1},
-      {"time": "18:40", "qty": 1},
-      {"time": "19:05", "qty": 1}
+    { "time": "08:15", "qty": 1 },
+    { "time": "09:31", "qty": 1 },
+    { "time": "10:42", "qty": 2 },
+    { "time": "10:42", "qty": 2 },
+    { "time": "12:07", "qty": 1 },
+    { "time": "14:58", "qty": 1 },
+    { "time": "17:15", "qty": 1 },
+    { "time": "18:40", "qty": 1 },
+    { "time": "19:05", "qty": 1 }
   ],
-  "exercise": [
-      {"time": "11:02", "duration": 0.5, "type": "Walking"}
-   ]
+  "exercise": [{ "time": "11:02", "duration": 0.5, "type": "Walking" }]
 }
 ```
 
 ## Saving the Data
 
-Once we've gathered all the data for a day, we need to store it in our database.  In a NoSQL database, this can be a pretty easy process, as we can just create a record (document) for a specific user for a specific date and throw document into a collection and we're done.  With SQL, we have some structure we have to work within, and in this case it looks like 4 separate tables: food, water, exercise, and notes.  We'd want to do 4 separate inserts here, one for each table.  If we don't have data for a specific table (say no exercise was recorded today) then we can skip that table.
+Once we've gathered all the data for a day, we need to store it in our database. In a NoSQL database, this can be a pretty easy process, as we can just create a record (document) for a specific user for a specific date and throw document into a collection and we're done. With SQL, we have some structure we have to work within, and in this case it looks like 4 separate tables: food, water, exercise, and notes. We'd want to do 4 separate inserts here, one for each table. If we don't have data for a specific table (say no exercise was recorded today) then we can skip that table.
 
-If you're using SQL to store this data, you might want to save each table's data as it's entered in your data entry form (and not wait until all the data is entered.)  Or you might want to create a database function that takes all the JSON data, parses it, and writes it to all the related tables in a single transaction.  There's a lot of ways to handle this, but suffice it to say this: it's a bit more complicated than saving the data in a NoSQL database.
+If you're using SQL to store this data, you might want to save each table's data as it's entered in your data entry form (and not wait until all the data is entered.) Or you might want to create a database function that takes all the JSON data, parses it, and writes it to all the related tables in a single transaction. There's a lot of ways to handle this, but suffice it to say this: it's a bit more complicated than saving the data in a NoSQL database.
 
 ### Retrieving the Data
-If we want to display all the data for a single day, it's pretty much the same.  With NoSQL you can grab the data for the user's day and then use it in your application.  Nice!  With SQL we need to query 4 tables to get all the data (or we could use a function to get it all in a single call.)  Of course, when displaying the data, we'd need to first break up our JSON data into pieces that are needed by each section of our dashboard screen, and you could argue that it's simpler to map each SQL table with the dashboard section on the screen, but that's a trivial point.
+
+If we want to display all the data for a single day, it's pretty much the same. With NoSQL you can grab the data for the user's day and then use it in your application. Nice! With SQL we need to query 4 tables to get all the data (or we could use a function to get it all in a single call.) Of course, when displaying the data, we'd need to first break up our JSON data into pieces that are needed by each section of our dashboard screen, and you could argue that it's simpler to map each SQL table with the dashboard section on the screen, but that's a trivial point.
 
 ### Analyzing the Data
-Now that we've saved the data and we can retrieve it and display it, let's use it for some analysis.  *Let's display a graph of how many total calories I've eaten over the past month.*  With SQL, this is a simple task:
+
+Now that we've saved the data and we can retrieve it and display it, let's use it for some analysis. _Let's display a graph of how many total calories I've eaten over the past month._ With SQL, this is a simple task:
 
 ```sql
-select 
-   date, sum(calories) as total_calories 
-from food_log 
-group by date 
-where user_id = 'xyz' 
-and day between '2022-01-01' and '2022-01-31' 
+select
+  date,
+  sum(calories) as total_calories
+from food_log
+group by date
+where user_id = 'xyz' and day between '2022-01-01' and '2022-01-31'
 order by date;
 ```
 
-Bam!  Done!  Now we can send those results to our graphing library and make a nice pretty picture of my eating habits.
+Bam! Done! Now we can send those results to our graphing library and make a nice pretty picture of my eating habits.
 
-But if we've stored this data in NoSQL, it gets a little more complicated.  We'll need to:
+But if we've stored this data in NoSQL, it gets a little more complicated. We'll need to:
 
 - grab all the data for the user for the month
 - parse each day's data to get the food log information
 - loop through each day and total the calories
 - send the aggregate data to our graphing module
 
-If this is something we're going to do regularly, it makes sense to calculate the total calories for each day and store it in the day's document so we can get at that data faster.  But that requires more work up front, and we still need to pull the data for each day and parse out that calorie total first.  And if we update the data we still need to recalculate things and update that total.  Eventually we'll want to do that with the water and exercise totals as well.  The code will eventually start to get longer and more complex.
+If this is something we're going to do regularly, it makes sense to calculate the total calories for each day and store it in the day's document so we can get at that data faster. But that requires more work up front, and we still need to pull the data for each day and parse out that calorie total first. And if we update the data we still need to recalculate things and update that total. Eventually we'll want to do that with the water and exercise totals as well. The code will eventually start to get longer and more complex.
 
 ### SQL and NoSQL Together - FTW
-Let's see how we can use the power of SQL together with the ease-of-use of NoSQL in the same database to make this all a bit easier.  We'll create a table for each day of data (for each user) and store the basic fields such as `weight` and `notes` first.  Then we'll just throw the `food_log`, `water_log`, and `exercise_log` fields in a `JSONB` field.
+
+Let's see how we can use the power of SQL together with the ease-of-use of NoSQL in the same database to make this all a bit easier. We'll create a table for each day of data (for each user) and store the basic fields such as `weight` and `notes` first. Then we'll just throw the `food_log`, `water_log`, and `exercise_log` fields in a `JSONB` field.
 
 ```sql
 CREATE TABLE calendar (
@@ -145,21 +148,23 @@ CREATE TABLE calendar (
     water_log jsonb,
     exercise_log jsonb
 );
--- (Optional) - create a foreign key relationship for the user_id field 
+-- (Optional) - create a foreign key relationship for the user_id field
 ALTER TABLE ONLY calendar
     ADD CONSTRAINT calendar_user_id_fkey FOREIGN KEY (user_id) REFERENCES auth.users(id);
 ```
 
-Now let's insert some data into the table.  PostgreSQL offers both JSON and JSONB fields, and since the latter are more optimized by the database and much faster for query processing, we’ll almost always want to use JSONB.  We’ll use JSONB fields for `food_log`, `water_log`, and `exercise_log` and just dump the data we got from our app right into those fields as a string:
+Now let's insert some data into the table. PostgreSQL offers both JSON and JSONB fields, and since the latter are more optimized by the database and much faster for query processing, we’ll almost always want to use JSONB. We’ll use JSONB fields for `food_log`, `water_log`, and `exercise_log` and just dump the data we got from our app right into those fields as a string:
 
 ```sql
-insert into calendar (date, user_id, weight, notes, food_log, water_log, exercise_log)
-values (
-   '2022-01-01', 
-   'xyz', 
-   172.6, 
-   'This new diet is awesome!',
-   '[
+insert into calendar
+  (date, user_id, weight, notes, food_log, water_log, exercise_log)
+values
+  (
+    '2022-01-01',
+    'xyz',
+    172.6,
+    'This new diet is awesome!',
+    '[
       { "title": "Apple", "calories": 72, "meal": "Breakfast"},
       { "title": "Oatmeal", "calories": 146, "meal": "Breakfast"},
       { "title": "Sandwich", "calories": 445, "meal": "Lunch"},
@@ -170,7 +175,7 @@ values (
       { "title": "Garlic Bread", "calories": 200, "meal": "Dinner"},
       { "title": "Broccoli", "calories": 32, "meal": "Dinner"}
      ]',
-   '[
+    '[
       {"time": "08:15", "qty": 1},
       {"time": "09:31", "qty": 1},
       {"time": "10:42", "qty": 2},
@@ -181,33 +186,33 @@ values (
       {"time": "18:40", "qty": 1},
       {"time": "19:05", "qty": 1}
     ]',
-   '[
+    '[
       {"time": "11:02", "duration": 0.5, "type": "Walking"}
     ]'
-);
+  );
 ```
 
-While that's a big insert statement, it sure beats doing inserts on 4 separate tables.  With all those food entries and water log entries, we would have had to made 1 entry in the main table, then 9 food_log entries, 9 water_log entries, and one exercise_log entry for a total of 20 database records.  We've wrapped that into a single record.
+While that's a big insert statement, it sure beats doing inserts on 4 separate tables. With all those food entries and water log entries, we would have had to made 1 entry in the main table, then 9 food_log entries, 9 water_log entries, and one exercise_log entry for a total of 20 database records. We've wrapped that into a single record.
 
 ## But How Do We Query This Data?
 
-Great, we're collecting the data now, and it's easy to insert the data into the database.  Editing the data isn't too bad either because we're just downloading the data to the client, updating the JSON field(s) as needed, and throwing them back into the database.  Not too hard.  But how can I query this data?  What about that task from before? *Let's display a graph of how many total calories I've eaten over the past month.*
+Great, we're collecting the data now, and it's easy to insert the data into the database. Editing the data isn't too bad either because we're just downloading the data to the client, updating the JSON field(s) as needed, and throwing them back into the database. Not too hard. But how can I query this data? What about that task from before? _Let's display a graph of how many total calories I've eaten over the past month._
 
-In this case, that data is stored inside the `food_log` field inside the `calendar` table.  If only PostgreSQL had a way of converting JSONB arrays into individual database records (recordsets).  Well, it does!  The `jsonb_array_elements` function will do this for us, allowing to create a simple table we can use to calculate our caloric intake.
+In this case, that data is stored inside the `food_log` field inside the `calendar` table. If only PostgreSQL had a way of converting JSONB arrays into individual database records (recordsets). Well, it does! The `jsonb_array_elements` function will do this for us, allowing to create a simple table we can use to calculate our caloric intake.
 
 Here's some SQL to turn that `food_log` array into individual output records:
 
+{/* prettier-ignore */}
 ```sql
-select 
+select
   user_id,
   date,
   jsonb_array_elements(food_log)->>'title' as title,
   jsonb_array_elements(food_log)->'calories' as calories,
   jsonb_array_elements(food_log)->'meal' as meal
-from calendar 
-where user_id = 'xyz' 
-   and date between 
-   '2022-01-01' and '2022-01-31';
+from calendar
+where user_id = 'xyz'
+  and date between '2022-01-01' and '2022-01-31';
 ```
 
 This returns a table that looks like this:
@@ -233,14 +238,15 @@ If we want to `sum` the calories to get some totals, we can't have a JSON object
 
 - `(jsonb_array_elements(food_log)->'calories')::INTEGER as calories` this returns an INTEGER
 
-Now we can't just throw the `sum` operator on this to get the total calories by day.  If we try this:
+Now we can't just throw the `sum` operator on this to get the total calories by day. If we try this:
 
+{/* prettier-ignore */}
 ```sql
-select 
+select
   date,
   sum((jsonb_array_elements(food_log)->'calories')::integer) as total_calories
-from calendar where user_id = 'xyz' 
-      and date between '2022-01-01' and '2022-01-31'
+from calendar where user_id = 'xyz'
+  and date between '2022-01-01' and '2022-01-31'
 group by date;
 ```
 
@@ -248,30 +254,31 @@ we get an error back from PostgreSQL: **Failed to run sql query: aggregate funct
 
 Instead, we need to think of this as a set of building blocks, where our first SQL statement returns a table:
 
+{/* prettier-ignore */}
 ```sql
-select 
+select
   date,
   (jsonb_array_elements(food_log)->'calories')::integer as calories
-from calendar where user_id = 'xyz' 
-      and date between 
-      '2022-01-01' and '2022-01-31';
+from calendar where user_id = 'xyz'
+  and date between '2022-01-01' and '2022-01-31';
 ```
 
 Now we can take that "table" statement, throw some (parenthesis) around it, and query **it**:
 
+{/* prettier-ignore */}
 ```sql
 with data as
-   (
-      select 
-        date,
-        (jsonb_array_elements(food_log)->'calories')::integer as calories
-      from calendar 
-      where user_id = 'xyz' 
-         and date between 
-         '2022-01-01' and '2022-01-31'
-   ) 
-select date, sum(calories) from 
-   data group by date;
+(
+  select
+    date,
+    (jsonb_array_elements(food_log)->'calories')::integer as calories
+  from calendar
+  where user_id = 'xyz'
+    and date between '2022-01-01' and '2022-01-31'
+)
+select date, sum(calories)
+from data
+group by date;
 ```
 
 This gives us exactly what we want:
@@ -283,39 +290,43 @@ This gives us exactly what we want:
 If we add more data for the rest of the days of the month, we'll have all the data we need for a beautiful graph.
 
 ### Searching the Data
-What if we want to answer the question: *How many calories were in the garlic bread I ate last month?*  This data is stored inside the `food_log` field in the `calendar` table.  We can use the same type of query we used before to "flatten" the `food_log` data so we can search it.
+
+What if we want to answer the question: _How many calories were in the garlic bread I ate last month?_ This data is stored inside the `food_log` field in the `calendar` table. We can use the same type of query we used before to "flatten" the `food_log` data so we can search it.
 
 To get every item I ate during the month of January, we can use:
 
+{/* prettier-ignore */}
 ```sql
-select 
+select
   date,
   jsonb_array_elements(food_log)->>'title' as title,
   (jsonb_array_elements(food_log)->'calories')::integer as calories
-from calendar 
-where user_id = 'xyz' 
-   and date between 
-   '2022-01-01' and '2022-01-31'
+from calendar
+where user_id = 'xyz'
+  and date between '2022-01-01' and '2022-01-31'
 ```
 
 Now to search for the **garlic bread** we can just put (parenthesis) around this to make a "table" and then search for the item we want:
 
+{/* prettier-ignore */}
 ```sql
-with my_food as 
+with my_food as
 (
-   select 
-     date,
-     jsonb_array_elements(food_log)->>'title' as title,
-     (jsonb_array_elements(food_log)->'calories')::integer as calories
-   from calendar 
-   where user_id = 'xyz' 
-   and date between 
-   '2022-01-01' and '2022-01-31'
-) 
-select title, calories 
-from my_food 
+  select
+    date,
+    jsonb_array_elements(food_log)->>'title' as title,
+    (jsonb_array_elements(food_log)->'calories')::integer as calories
+  from calendar
+  where user_id = 'xyz'
+    and date between '2022-01-01' and '2022-01-31'
+)
+select
+  title,
+  calories
+from my_food
 where title = 'Garlic Bread';
 ```
+
 which gives us:
 
 | title        | calories |
@@ -324,7 +335,7 @@ which gives us:
 
 ## Conclusion
 
-If we take a little time to study the [JSON Functions and Operators](https://www.postgresql.org/docs/9.5/functions-json.html) that PostgreSQL offers, we can turn Postgres into an easy-to-use NoSQL database that still retains all the power of SQL.  This gives us a super easy way to store our complex JSON data coming from our application code in our database.  Then we can use powerful SQL capabilities to analyze and present that data in our application.  It's the best of both worlds!
+If we take a little time to study the [JSON Functions and Operators](https://www.postgresql.org/docs/9.5/functions-json.html) that PostgreSQL offers, we can turn Postgres into an easy-to-use NoSQL database that still retains all the power of SQL. This gives us a super easy way to store our complex JSON data coming from our application code in our database. Then we can use powerful SQL capabilities to analyze and present that data in our application. It's the best of both worlds!
 
 ## More Postgres resources
 
@@ -334,4 +345,3 @@ If we take a little time to study the [JSON Functions and Operators](https://www
 - [Partial data dumps using Postgres Row Level Security](https://supabase.com/blog/partial-postgresql-data-dumps-with-rls)
 - [Postgres Views](https://supabase.com/blog/postgresql-views)
 - [Realtime Postgres RLS on Supabase](https://supabase.com/blog/realtime-row-level-security-in-postgresql)
-
diff --git a/apps/www/_blog/2022-12-01-transparent-column-encryption-with-postgres.mdx b/apps/www/_blog/2022-12-01-transparent-column-encryption-with-postgres.mdx
index 0759568c18b..be6c55497fd 100644
--- a/apps/www/_blog/2022-12-01-transparent-column-encryption-with-postgres.mdx
+++ b/apps/www/_blog/2022-12-01-transparent-column-encryption-with-postgres.mdx
@@ -206,12 +206,10 @@ The new label indicates which column is to be associated with the secret, and th
 Now that you have TCE setup for a table, it's easy to use by simply inserting data into the table, and querying that data by looking at its generated view. The view is named `decrypted_<table_name>` and by default is in the same schema as your table:
 
 ```sql
-INSERT INTO credit_cards (
-	credit_card_number,
-	account_id
-)
-VALUES
-    ('1234-5678-8765-4321', 123);
+insert into credit_cards
+  (credit_card_number, account_id)
+values
+  ('1234-5678-8765-4321', 123);
 ```
 
 Now that you have inserted data, look at the table and notice how the credit card number is encrypted. This is the data that is stored on disk, the encrypted card number, the key id, and the account id, **but the key itself is not stored**. This means if someone gets a backup or dump of your database, they cannot decrypt the credit card number, they do not have the key, only the key ID:
diff --git a/apps/www/_blog/2022-12-06-the-supabase-content-storm.mdx b/apps/www/_blog/2022-12-06-the-supabase-content-storm.mdx
index f25e4dc11fb..69be8b1074d 100644
--- a/apps/www/_blog/2022-12-06-the-supabase-content-storm.mdx
+++ b/apps/www/_blog/2022-12-06-the-supabase-content-storm.mdx
@@ -14,7 +14,7 @@ We're always trying to innovate at Supabase, so when we started planning [Launch
 
 ## What is the Content Storm?
 
-The idea was to get many different external content creators as possible to create Supabase-related content and *publish everything on the same day*. We contacted some well known Youtubers, community members, makers building with Supabase, the SupaSquad, and generally anyone within the Supabase community. We wanted this to be an opportunity for them to build their personal brand or promote their products and startups.
+The idea was to get many different external content creators as possible to create Supabase-related content and _publish everything on the same day_. We contacted some well known Youtubers, community members, makers building with Supabase, the SupaSquad, and generally anyone within the Supabase community. We wanted this to be an opportunity for them to build their personal brand or promote their products and startups.
 
 ## The aftermath of the storm
 
@@ -53,6 +53,6 @@ More than 30 creators participated in creating content in different formats and
 - [Twitter thread showing how to build a web app](https://twitter.com/thisisisheanesu/status/1600257146792181766) by Isheanesu.
 - [This service will run your entire app](https://www.instagram.com/reel/Cl1KWbtDGMR/) by Simon Baker (@allthecode).
 
-It's a lot! There are tons of great resources, going through everything would take a couple of days, so we recommend bookmarking this page! If you like the content, make sure to give feedback to the author and follow them on social. 
+It's a lot! There are tons of great resources, going through everything would take a couple of days, so we recommend bookmarking this page! If you like the content, make sure to give feedback to the author and follow them on social.
 
 And don't miss Launch Week 6, we've been working hard to make it our best Launch Week yet 🚀. Get your tickets [here](https://supabase.com/launch-week).
diff --git a/apps/www/_blog/2022-12-09-launch-week-6-hackathon.mdx b/apps/www/_blog/2022-12-09-launch-week-6-hackathon.mdx
index 5401d567ae6..515512f8c02 100644
--- a/apps/www/_blog/2022-12-09-launch-week-6-hackathon.mdx
+++ b/apps/www/_blog/2022-12-09-launch-week-6-hackathon.mdx
@@ -11,7 +11,6 @@ date: '2022-12-09'
 toc_depth: 3
 ---
 
-
 The official Supabase Hackathon starts on Friday 9th December at 8am Pacific Time and ends Monday 19th December at 00:01am.
 
 [Launch Week](https://supabase.com/launch-week) is about to kick off and we're running a hackathon in parallel.
@@ -32,7 +31,7 @@ See all the [winners from all the previous hackathons](https://supabase.com/blog
 - There are 5 prize categories.
   - Best overall project will win $1500 in GitHub sponsorships, and a Supabase Keyboard for each team member.
   - Most fun/interesting, best Flutter project, and best storage project will all win a limited edition Hackathon swag kit for each team member!
-  - Our friends at [Deno](https://deno.land/) will be judging a special guest category: Best Edge Functions Project! They will be providing some [special swag](https://deno.com/blog/edge-functions-supabase-launch-week-6-hackathon) for the winners! 
+  - Our friends at [Deno](https://deno.land/) will be judging a special guest category: Best Edge Functions Project! They will be providing some [special swag](https://deno.com/blog/edge-functions-supabase-launch-week-6-hackathon) for the winners!
 
 ## Details
 
@@ -47,13 +46,12 @@ See all the [winners from all the previous hackathons](https://supabase.com/blog
 There are 5 chances to win, there will be prizes for:
 
 - Best Overall Project ($1500 in GitHub Sponsorship & Supabase Keyboards)
-    - to be paid as 3x$500 GitHub Sponsorships (over 3 months)
+  - to be paid as 3x$500 GitHub Sponsorships (over 3 months)
 - Most Fun/Interesting (Swag kit)
 - Best Flutter Project (Swag kit)
 - Best Storage Project (Swag kit)
 - Best Edge Functions Project (Deno Swag kit)
 
-
 There will be winner and runner-up prizes for each category. Every team member on winning/runner-up teams gets a supaverified swag kit.
 
 ![Swag kit](/images/blog/lw6-hackathon/swagkit.png)
@@ -107,7 +105,6 @@ Don't forget to checkout the new feature's being announced as part of [Launch We
 - [Previous Hackathon Prize Winners](https://supabase.com/blog/launch-week-5-hackathon-winners)
 - [Who We Hire at Supabase - Founders Chat](https://youtu.be/-BG9XptyCKI)
 
-
 ### Additional Info
 
 - Any intellectual property developed during the hackathon will belong to the team that developed it. We expect that each team will have an agreement between themselves regarding the IP, but this is not required
@@ -125,4 +122,3 @@ Don't forget to checkout the new feature's being announced as part of [Launch We
 - [Point in Time Recovery is now available](https://supabase.com/blog/postgres-point-in-time-recovery)
 - [Custom Domain Names are now available](https://supabase.com/blog/custom-domain-names)
 - [Wrap Up: everything we shipped](https://supabase.com/blog/launch-week-6-wrap-up)
-
diff --git a/apps/www/_blog/2022-12-14-mfa-auth-via-rls.mdx b/apps/www/_blog/2022-12-14-mfa-auth-via-rls.mdx
index eff5501b53a..44e13c1e732 100644
--- a/apps/www/_blog/2022-12-14-mfa-auth-via-rls.mdx
+++ b/apps/www/_blog/2022-12-14-mfa-auth-via-rls.mdx
@@ -13,20 +13,25 @@ date: '2022-12-14'
 toc_depth: 3
 video: https://www.youtube.com/v/He7LI2mv9v0
 ---
+
 Today, we’re releasing Multi Factor Authentication for everyone.
 
 Additionally, in preparation for releasing SAML, we're "dogfooding" the feature with the introduction of Single Sign On (SSO) on our dashboard. Contact us at [growth@supabase.com](mailto:growth@supabase.com) if you want to [enable this on your Enterprise plan](https://supabase.com/docs/guides/platform/sso).
 
 <div className="video-container">
-  <iframe 
-        src="https://www.youtube-nocookie.com/embed/He7LI2mv9v0" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+  <iframe
+    src="https://www.youtube-nocookie.com/embed/He7LI2mv9v0"
+    title="YouTube video player"
+    frameborder="0"
+    allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+    allowfullscreen
+  ></iframe>
 </div>
 
 ## What is MFA?
 
 Multi-factor authentication (MFA), sometimes called two-factor authentication (2FA), adds an additional layer of security to your application by letting you verify users’ identity through extra steps. This typically consists of something you know, like a password, and something you have, like an authenticator application. We built MFA in response to customer requests - developers wanted enhanced security - be it for compliance, client requirements, or simply for peace of mind. As such, we started by building MFA support for Time-Based One Time Passwords (TOTP).
 
-
 ## An Overview of TOTP
 
 [TOTP](https://www.rfc-editor.org/rfc/rfc6238) works by generating a unique, one-time password that is valid for a limited amount of time, usually 30 seconds or less. This password is generated using a shared secret key that is known only to the device and Supabase Auth, along with the current time. To exchange the shared secret key, a user scans a QR code generated by the server in order to establish a connection. The QR code can be represented by a URI which conforms to the [Google Authenticator Key URI format](https://github.com/google/google-authenticator/wiki/Key-Uri-Format):
@@ -35,31 +40,30 @@ Multi-factor authentication (MFA), sometimes called two-factor authentication (2
 otpauth://totp/supabase.io:j@supacats.io?algorithm=SHA1&digits=6&issuer=supabase.io&period=30&secret=BFSXQHFB2BGAZIOQWCDBJUF7B54A52JQ
 ```
 
-The first portion of  `otpauth://totp/supabase.io` describes the protocol and issuer while `j@supacats.io` refers to the user. The remaining parameters refer to specifics around OTP generation. In this case, the OTP code is generated using a SHA1 hash of the secret combined with the timestamp and the OTP code is valid for `30s`
+The first portion of `otpauth://totp/supabase.io` describes the protocol and issuer while `j@supacats.io` refers to the user. The remaining parameters refer to specifics around OTP generation. In this case, the OTP code is generated using a SHA1 hash of the secret combined with the timestamp and the OTP code is valid for `30s`
 
 In the event that the user faces difficulties entering a QR code the user can also opt to manually type the secret into the authenticator device.
 
 ## MFA Flows: Enrollment and Verification
 
-An MFA flow can be broken into two key steps: Enrollment and Verification. During the *Enrollment* process Supabase Auth exchanges a randomly generated secret with the user’s authenticator application. During the *Verification* process, the device makes use of the timestamp together with the secret to produce a six digit code that the server can verify.
+An MFA flow can be broken into two key steps: Enrollment and Verification. During the _Enrollment_ process Supabase Auth exchanges a randomly generated secret with the user’s authenticator application. During the _Verification_ process, the device makes use of the timestamp together with the secret to produce a six digit code that the server can verify.
 
 ![Flowchart of an MFA flow](/images/blog/lw6-auth/mfa-flow.png)
-*Enrollment*
+_Enrollment_
 
-To generate a QR code, call the `/enroll` endpoint which returns an SVG encoded QR and the secret. Thereafter, create a challenge by calling the `/challenge` endpoint. Once the user has entered the six digit TOTP code generated by their authenticator app, call the`/verify`  endpoint with the corresponding factor and challenge details.
+To generate a QR code, call the `/enroll` endpoint which returns an SVG encoded QR and the secret. Thereafter, create a challenge by calling the `/challenge` endpoint. Once the user has entered the six digit TOTP code generated by their authenticator app, call the`/verify` endpoint with the corresponding factor and challenge details.
 
 You might wonder: why the need for the "challenge" step? This step creates an interval between MFA initiation and the action of making a verification. This is useful in cases like Yubikey authentication where a user might need to request a challenge before placing their finger on the device.
 
-
 ![MFA Enrollment Flow](/images/blog/lw6-auth/enrollment_flow.png)
-*Overview of Enrollment Flow*
+_Overview of Enrollment Flow_
 
 **Verification**
 
-On subsequent logins attempts, redirect a user to an MFA verification after they have completed the conventional sign in process. On the verification page, wait for the user to enter the six digit OTP code from the authenticator application and then call  the`/challenge` endpoint followed by the `/verify` endpoint. If a correct code is submitted, a JWT will be created with a few additional fields.
+On subsequent logins attempts, redirect a user to an MFA verification after they have completed the conventional sign in process. On the verification page, wait for the user to enter the six digit OTP code from the authenticator application and then call the`/challenge` endpoint followed by the `/verify` endpoint. If a correct code is submitted, a JWT will be created with a few additional fields.
 
 ![MFA Verification Flow](/images/blog/lw6-auth/verify_flow.png)
-*Overview of Verification Flow*
+_Overview of Verification Flow_
 
 ## Enforcement via Row Level Security
 
@@ -87,7 +91,7 @@ Using MFA without enforcing it is like buying an expensive door and never lockin
   ],
   // ...
 }
-````
+```
 
 The information encoded in these claims can be used for both full enforcement and partial enforcement across database queries.
 
@@ -99,7 +103,7 @@ create policy "Enforce MFA for all end users."
   using ( auth.jwt()->>'aal' = 'aal2' );
 ```
 
-*Enforce MFA for all end users*
+_Enforce MFA for all end users_
 
 ```sql
 create policy "Allow access on table only if user has gone through MFA"
@@ -118,20 +122,18 @@ create policy "Allow access on table only if user has gone through MFA"
     ));
 ```
 
-*Enforce MFA for selected users*
+_Enforce MFA for selected users_
 
 Note that both RLS policies are restrictive. By default, overlapping policies in PostgreSQL are permissive rather than restrictive. This means that RLS policies are combined with an `OR` clause and only one policy needs to pass in order for a row to be operated on. Therefore, we set RLS policies as restrictive to enforce the checks from multiple policies.
 
 Be mindful of your user’s preference, though. If a user has enabled MFA, they are expecting a higher level of security for their account. Consequently, we recommend that developers enforce MFA across all operations if a user has MFA enabled. You can check out [our MFA guide](https://supabase.com/docs/guides/auth/auth-mfa) for more details about MFA enforcement.
 
-
 ## What's Next
 
 For starters, we are looking to support WebAuthn and FIDO2 compliant devices such as Yubikeys. We also hope to allow users to receive email notifications when selected MFA actions are triggered. If you have MFA requirements which are not covered here feel free to write to us at support[at]supabase.io .
 
 We are grateful to our early MFA users for the support and feedback provided throughout this period. In particular, we would like to thank [Fabian Beer](https://madebyfabian.com), [Cogram](https://www.cogram.com), and [Happl](https://happl.com) whose detailed feedback helped to shape our implementation. We would also like to specially thank the community behind the [pquerna/otp](https://github.com/pquerna/otp) and [ajstarks/svgo](https://github.com/ajstarks/svgo) libraries - their work is indispensable to this implementation.
 
-
 ## More Launch Week 6
 
 - [Day 1: New Supabase Docs, built with Next.js](https://supabase.com/blog/new-supabase-docs-built-with-nextjs)
diff --git a/apps/www/_blog/2022-12-15-postgres-foreign-data-wrappers-rust.mdx b/apps/www/_blog/2022-12-15-postgres-foreign-data-wrappers-rust.mdx
index fa8bd3a668e..bd980334de1 100644
--- a/apps/www/_blog/2022-12-15-postgres-foreign-data-wrappers-rust.mdx
+++ b/apps/www/_blog/2022-12-15-postgres-foreign-data-wrappers-rust.mdx
@@ -143,14 +143,11 @@ You can even join remote data with your local tables to enrich existing operatio
 ```sql
 select
   users.id,
-	count(order_history.event)
+  count(order_history.event)
 from
-	snowflake.order_history
-join
-	auth.users on auth.users.id = snowflake.order_history.user_id
-where
-  order_history.event = 'purchase' and
-  order_history.user_id = '<some_user_id>';
+  snowflake.order_history
+  join auth.users on auth.users.id = snowflake.order_history.user_id
+where order_history.event = 'purchase' and order_history.user_id = '<some_user_id>';
 ```
 
 We can either run these queries on demand or, for better query performance, we can run them in the background (using something like [pg_cron](https://supabase.com/docs/guides/database/extensions/pgcron)), and materialize the data into a local table.
diff --git a/apps/www/_blog/2022-12-16-launch-week-6-community-day.mdx b/apps/www/_blog/2022-12-16-launch-week-6-community-day.mdx
index ed8855ba1e2..eb485c2bb11 100644
--- a/apps/www/_blog/2022-12-16-launch-week-6-community-day.mdx
+++ b/apps/www/_blog/2022-12-16-launch-week-6-community-day.mdx
@@ -127,7 +127,7 @@ Mobbin use Supabase Auth to power their [UI/UX library of Mobile and Web screens
 
 ### Topaz
 
-[Topaz](https://topaz.network/) is one of the fastest growing NFT networks and chose supabase as a backend to ensure they won't lose customers during peak traffic periods.  
+[Topaz](https://topaz.network/) is one of the fastest growing NFT networks and chose supabase as a backend to ensure they won't lose customers during peak traffic periods.
 
 ### Repeat.dev
 
@@ -184,7 +184,7 @@ Check out Jon's brand new, entirely free course on egghead to learn all about th
 
 ### Base Jump
 
-[usebasejump.com](https://usebasejump.com/) is "The fastest way to launch Supabase apps with NextJS". Basejump is open source. Contributions are both awesome and encouraged! 
+[usebasejump.com](https://usebasejump.com/) is "The fastest way to launch Supabase apps with NextJS". Basejump is open source. Contributions are both awesome and encouraged!
 
 ### supastarter
 
diff --git a/apps/www/_blog/2022-12-16-pg-graphql-v1.mdx b/apps/www/_blog/2022-12-16-pg-graphql-v1.mdx
index 3d2b838d7ef..78101645130 100644
--- a/apps/www/_blog/2022-12-16-pg-graphql-v1.mdx
+++ b/apps/www/_blog/2022-12-16-pg-graphql-v1.mdx
@@ -96,12 +96,12 @@ While v1.0 is an important milestone for stability, there's plenty of room to ex
   - `startsWith` for the `String` type
   - nestable `and`/ `or` blocks
 - Support for user-defined functions
-- Support for views 
+- Support for views
 
 Longer term we look forward to experimenting with more ambitions features like an API for migrations, integrations with 3rd-party services through [supabase/wrappers](https://github.com/supabase/wrappers), and a scalable solution for subscriptions.
 
 ## More pg_graphql
 
-- [Introducing pg_graphql: A GraphQL extension for PostgreSQL](https://supabase.com/blog/pg-graphql) 
+- [Introducing pg_graphql: A GraphQL extension for PostgreSQL](https://supabase.com/blog/pg-graphql)
 - [GraphQL is now available in Supabase](https://supabase.com/blog/graphql-now-available)
 - [pg_graphql v1.0](https://supabase.com/blog/pg-graphql-v1)
diff --git a/apps/www/_blog/2023-01-05-supabase-beta-december-2022.mdx b/apps/www/_blog/2023-01-05-supabase-beta-december-2022.mdx
index 08162d1e9d5..53457a5e9f3 100644
--- a/apps/www/_blog/2023-01-05-supabase-beta-december-2022.mdx
+++ b/apps/www/_blog/2023-01-05-supabase-beta-december-2022.mdx
@@ -91,7 +91,7 @@ Two key features to level up your projects are now available: Custom domains all
 
 It was great to see so many high-quality projects. The decision wasn't easy, but in the end, the panel of judges chose Depulso as the winner of the Best Overall Project.
 
-Congratulations 👏 to [@_iamkarthikeyan](https://twitter.com/_iamkarthikeyan) and [@SindhuMansi](https://twitter.com/SindhuMansi) who get each a Supabase Darkmode Keyboard and the $1500 Github sponsorship!
+Congratulations 👏 to [@\_iamkarthikeyan](https://twitter.com/_iamkarthikeyan) and [@SindhuMansi](https://twitter.com/SindhuMansi) who get each a Supabase Darkmode Keyboard and the $1500 Github sponsorship!
 
 - [Full list of Winners](https://supabase.com/blog/launch-week-6-hackathon-winners)
 - [See all the submissions](https://www.madewithsupabase.com/launch-week-6)
diff --git a/apps/www/_blog/2023-02-03-openai-embeddings-postgres-vector.mdx b/apps/www/_blog/2023-02-03-openai-embeddings-postgres-vector.mdx
index d773d57c016..d1e57927dff 100644
--- a/apps/www/_blog/2023-02-03-openai-embeddings-postgres-vector.mdx
+++ b/apps/www/_blog/2023-02-03-openai-embeddings-postgres-vector.mdx
@@ -14,7 +14,7 @@ toc_depth: 3
 
 A new PostgreSQL extension is now available in Supabase: [`pgvector`](https://github.com/pgvector/pgvector), an open-source vector similarity search.
 
-The exponential progress of AI functionality over the past year has inspired many new real world applications. One specific challenge has been the ability to store and query _embeddings_ at scale. 
+The exponential progress of AI functionality over the past year has inspired many new real world applications. One specific challenge has been the ability to store and query _embeddings_ at scale.
 In this post we'll explain what embeddings are, why we might want to use them, and how we can store and query them in PostgreSQL using `pgvector`.
 
 ## What are embeddings?
@@ -92,7 +92,7 @@ Next let's create a table to store our documents and their embeddings:
 create table documents (
   id bigserial primary key,
   content text,
-  embedding vector (1536)
+  embedding vector(1536)
 );
 ```
 
@@ -145,7 +145,7 @@ Once your table starts to grow with embeddings, you will likely want to add an i
 Each distance operator requires a different type of index. We expect to order by cosine distance, so we need `vector_cosine_ops` index. A good starting number of lists is 4 \* sqrt(table_rows):
 
 ```sql
-create index on documents 
+create index on documents
 using ivfflat (embedding vector_cosine_ops)
 with (lists = 100);
 ```
diff --git a/apps/www/_blog/2023-03-01-geo-queries-with-postgis-in-ionic-angular.mdx b/apps/www/_blog/2023-03-01-geo-queries-with-postgis-in-ionic-angular.mdx
index 8898cbe0f78..bfd211a9964 100644
--- a/apps/www/_blog/2023-03-01-geo-queries-with-postgis-in-ionic-angular.mdx
+++ b/apps/www/_blog/2023-03-01-geo-queries-with-postgis-in-ionic-angular.mdx
@@ -105,9 +105,13 @@ For our tests, I also added some dummy data. Feel free to use mine or use coordi
 ```sql
 -- add some dummy data
 insert into public.stores
-(name, description, location)
+  (name, description, location)
 values
-  ('The Galaxies.dev Shop', 'Galaxies.dev - your favourite place to learn', st_point(7.6005702, 51.8807174)),
+  (
+    'The Galaxies.dev Shop',
+    'Galaxies.dev - your favourite place to learn',
+    st_point(7.6005702, 51.8807174)
+  ),
   ('The Local Dev', 'Local people, always best', st_point(7.614454, 51.876565)),
   ('City Store', 'Get the supplies a dev needs', st_point(7.642581, 51.945606)),
   ('MEGA Store', 'Everything you need', st_point(13.404315, 52.511640));
@@ -188,9 +192,9 @@ Within the new project we need to add our Supabase credentials and a key for the
 export const environment = {
   production: false,
   mapsKey: 'YOUR-GOOGLE-MAPS-KEY',
-  supabaseUrl: "YOUR-URL",
-  supabaseKey: "YOUR-ANON-KEY",
-};
+  supabaseUrl: 'YOUR-URL',
+  supabaseKey: 'YOUR-ANON-KEY',
+}
 ```
 
 You can find those values in your Supabase project by clicking on the **Settings** icon and then navigating to **API** where it shows your **Project API keys**.
@@ -211,6 +215,7 @@ To use the Capacitor plugin we also need to update the permissions of our native
 ```
 
 Additionally, we need to add our Maps Key to the **android/app/src/main/AndroidManifest.xml**:
+
 ```xml
 <meta-data android:name="com.google.android.geo.API_KEY" android:value="YOUR_API_KEY_HERE"/>
 ```
@@ -223,46 +228,42 @@ Finally also add the required permissions for Android in the **android/app/src/m
 <uses-feature android:name="android.hardware.location.gps" />
 ```
 
-You can also find more information about using [Capacitor maps with Ionic in my Ionic Academy](https://ionicacademy.com/capacitor-google-maps-plugin/
-)!
+You can also find more information about using [Capacitor maps with Ionic in my Ionic Academy](https://ionicacademy.com/capacitor-google-maps-plugin/)!
 
 ### Finding Nearby Places with Database Functions
 
 Now the fun begins, and we can start by adding a function to our **src/app/services/stores.service.ts** that calls the database function (Remote Procedure Call) that we defined in the beginning:
 
 ```ts
-import { Injectable } from '@angular/core';
-import { DomSanitizer, SafeUrl } from '@angular/platform-browser';
-import { SupabaseClient, User, createClient } from '@supabase/supabase-js';
-import { environment } from 'src/environments/environment';
+import { Injectable } from '@angular/core'
+import { DomSanitizer, SafeUrl } from '@angular/platform-browser'
+import { SupabaseClient, User, createClient } from '@supabase/supabase-js'
+import { environment } from 'src/environments/environment'
 
 export interface StoreEntry {
-  lat?: number;
-  long?: number;
-  name: string;
-  description: string;
-  image?: File;
+  lat?: number
+  long?: number
+  name: string
+  description: string
+  image?: File
 }
 export interface StoreResult {
-  id: number;
-  lat: number;
-  long: number;
-  name: string;
-  description: string;
-  image?: SafeUrl;
-  dist_meters?: number;
+  id: number
+  lat: number
+  long: number
+  name: string
+  description: string
+  image?: SafeUrl
+  dist_meters?: number
 }
 @Injectable({
   providedIn: 'root',
 })
 export class StoresService {
-  private supabase: SupabaseClient;
+  private supabase: SupabaseClient
 
   constructor(private sanitizer: DomSanitizer) {
-    this.supabase = createClient(
-      environment.supabaseUrl,
-      environment.supabaseKey
-    );
+    this.supabase = createClient(environment.supabaseUrl, environment.supabaseKey)
   }
 
   // Get all places with calculated distance
@@ -270,8 +271,8 @@ export class StoresService {
     const { data, error } = await this.supabase.rpc('nearby_stores', {
       lat,
       long,
-    });
-    return data;
+    })
+    return data
   }
 }
 ```
@@ -281,13 +282,13 @@ This should return a nice list of `StoreResult` items that we can render in a li
 For that, let's display a modal from our **src/app/home/home.page.ts**:
 
 ```ts
-import { Component } from '@angular/core';
-import { ModalController } from '@ionic/angular';
-import { NearbyPage } from '../nearby/nearby.page';
+import { Component } from '@angular/core'
+import { ModalController } from '@ionic/angular'
+import { NearbyPage } from '../nearby/nearby.page'
 
 export interface StoreMarker {
-  markerId: string;
-  storeId: number;
+  markerId: string
+  storeId: number
 }
 
 @Component({
@@ -296,15 +297,13 @@ export interface StoreMarker {
   styleUrls: ['home.page.scss'],
 })
 export class HomePage {
-  constructor(
-    private modalCtrl: ModalController
-  ) {}
+  constructor(private modalCtrl: ModalController) {}
 
   async showNearby() {
     const modal = await this.modalCtrl.create({
       component: NearbyPage,
-    });
-    modal.present();
+    })
+    modal.present()
   }
 }
 ```
@@ -324,9 +323,7 @@ We also need a button to present that modal, so change the **src/app/home/home.p
   </ion-toolbar>
 </ion-header>
 
-<ion-content>
-
-</ion-content>
+<ion-content> </ion-content>
 ```
 
 Now we are able to use the `getNearbyStores` from our service on that modal page, and we also load the current user location using Capacitor.
@@ -336,10 +333,10 @@ Once we got the user coordinates, we pass them to our function and PostGIS will
 Go ahead and change the **src/app/nearby/nearby.page.ts** to this now:
 
 ```ts
-import { Component, OnInit } from '@angular/core';
-import { Geolocation } from '@capacitor/geolocation';
-import { StoresService, StoreResult } from '../services/stores.service';
-import { LoadingController, ModalController } from '@ionic/angular';
+import { Component, OnInit } from '@angular/core'
+import { Geolocation } from '@capacitor/geolocation'
+import { StoresService, StoreResult } from '../services/stores.service'
+import { LoadingController, ModalController } from '@ionic/angular'
 
 @Component({
   selector: 'app-nearby',
@@ -347,7 +344,7 @@ import { LoadingController, ModalController } from '@ionic/angular';
   styleUrls: ['./nearby.page.scss'],
 })
 export class NearbyPage implements OnInit {
-  stores: StoreResult[] = [];
+  stores: StoreResult[] = []
 
   constructor(
     private storesService: StoresService,
@@ -359,18 +356,18 @@ export class NearbyPage implements OnInit {
     // Show loading while getting data from Supabase
     const loading = await this.loadingCtrl.create({
       message: 'Loading nearby places...',
-    });
-    loading.present();
+    })
+    loading.present()
 
-    const coordinates = await Geolocation.getCurrentPosition();
+    const coordinates = await Geolocation.getCurrentPosition()
 
     if (coordinates) {
       // Get nearby places sorted by distance using PostGIS
       this.stores = await this.storesService.getNearbyStores(
         coordinates.coords.latitude,
         coordinates.coords.longitude
-      );
-      loading.dismiss();
+      )
+      loading.dismiss()
     }
   }
 }
@@ -397,9 +394,7 @@ At this point, you can already log the values, but we can also quickly display t
         {{ store.name }}
         <p>{{store.description }}</p>
       </ion-label>
-      <ion-note slot="end"
-        >{{store.dist_meters!/1000 | number:'1.0-2' }} km</ion-note
-      >
+      <ion-note slot="end">{{store.dist_meters!/1000 | number:'1.0-2' }} km</ion-note>
     </ion-item>
   </ion-list>
 </ion-content>
@@ -433,7 +428,7 @@ To add data to Supabase we create a new function in our **src/app/services/store
       })
       .select()
       .single();
-  
+
     if (data && info.image) {
       // Upload the image to Supabase
       const foo = await this.supabase.storage
@@ -486,9 +481,9 @@ Back in this new modal, we will define an empty `StoreEntry` object and then con
 Because we defined the rest of the functionality in our service, we can simply update the **src/app/store/store.page.ts** to:
 
 ```ts
-import { Component, OnInit } from '@angular/core';
-import { ModalController } from '@ionic/angular';
-import { StoreEntry, StoresService } from '../services/stores.service';
+import { Component, OnInit } from '@angular/core'
+import { ModalController } from '@ionic/angular'
+import { StoreEntry, StoresService } from '../services/stores.service'
 
 @Component({
   selector: 'app-store',
@@ -502,22 +497,19 @@ export class StorePage implements OnInit {
     image: undefined,
     lat: undefined,
     long: undefined,
-  };
+  }
 
-  constructor(
-    public modalCtrl: ModalController,
-    private storesService: StoresService
-  ) {}
+  constructor(public modalCtrl: ModalController, private storesService: StoresService) {}
 
   ngOnInit() {}
 
   imageSelected(ev: any) {
-    this.store.image = ev.detail.event.target.files[0];
+    this.store.image = ev.detail.event.target.files[0]
   }
 
   async addStore() {
-    this.storesService.addStore(this.store);
-    this.modalCtrl.dismiss();
+    this.storesService.addStore(this.store)
+    this.modalCtrl.dismiss()
   }
 }
 ```
@@ -550,18 +542,8 @@ The view is not really special and simply holds a bunch of input fields that are
     placeholder="Some about text"
     [(ngModel)]="store.description"
   />
-  <ion-input
-    type="number"
-    label="Latitude"
-    label-placement="stacked"
-    [(ngModel)]="store.lat"
-  />
-  <ion-input
-    type="number"
-    label="Longitude"
-    label-placement="stacked"
-    [(ngModel)]="store.long"
-  />
+  <ion-input type="number" label="Latitude" label-placement="stacked" [(ngModel)]="store.lat" />
+  <ion-input type="number" label="Longitude" label-placement="stacked" [(ngModel)]="store.long" />
   <ion-input
     label="Select store image"
     (ionChange)="imageSelected($event)"
@@ -595,14 +577,14 @@ But if you've come this far, I'm sure you can do it!
 Get started by adding the `CUSTOM_ELEMENTS_SCHEMA` to the **src/app/home/home.module.ts** which is required to use Capacitor native maps:
 
 ```ts
-import { NgModule } from '@angular/core';
-import { CommonModule } from '@angular/common';
-import { IonicModule } from '@ionic/angular';
-import { FormsModule } from '@angular/forms';
-import { HomePage } from './home.page';
+import { NgModule } from '@angular/core'
+import { CommonModule } from '@angular/common'
+import { IonicModule } from '@ionic/angular'
+import { FormsModule } from '@angular/forms'
+import { HomePage } from './home.page'
 
-import { HomePageRoutingModule } from './home-routing.module';
-import { CUSTOM_ELEMENTS_SCHEMA } from '@angular/core';
+import { HomePageRoutingModule } from './home-routing.module'
+import { CUSTOM_ELEMENTS_SCHEMA } from '@angular/core'
 
 @NgModule({
   imports: [CommonModule, FormsModule, IonicModule, HomePageRoutingModule],
@@ -617,19 +599,19 @@ In our **src/app/home/home.page.ts** we can now create the map by passing in a r
 Update the page with our first step that adds some new variables:
 
 ```ts
-import { Component, ElementRef, ViewChild } from '@angular/core';
-import { GoogleMap } from '@capacitor/google-maps';
-import { LatLngBounds } from '@capacitor/google-maps/dist/typings/definitions';
-import { ModalController } from '@ionic/angular';
-import { BehaviorSubject } from 'rxjs';
-import { environment } from 'src/environments/environment';
-import { NearbyPage } from '../nearby/nearby.page';
-import { StoreResult, StoresService } from '../services/stores.service';
-import { StorePage } from '../store/store.page';
+import { Component, ElementRef, ViewChild } from '@angular/core'
+import { GoogleMap } from '@capacitor/google-maps'
+import { LatLngBounds } from '@capacitor/google-maps/dist/typings/definitions'
+import { ModalController } from '@ionic/angular'
+import { BehaviorSubject } from 'rxjs'
+import { environment } from 'src/environments/environment'
+import { NearbyPage } from '../nearby/nearby.page'
+import { StoreResult, StoresService } from '../services/stores.service'
+import { StorePage } from '../store/store.page'
 
 export interface StoreMarker {
-  markerId: string;
-  storeId: number;
+  markerId: string
+  storeId: number
 }
 
 @Component({
@@ -638,22 +620,19 @@ export interface StoreMarker {
   styleUrls: ['home.page.scss'],
 })
 export class HomePage {
-  @ViewChild('map') mapRef!: ElementRef<HTMLElement>;
-  map!: GoogleMap;
-  mapBounds = new BehaviorSubject<LatLngBounds | null>(null);
-  activeMarkers: StoreMarker[] = [];
-  selectedMarker: StoreMarker | null = null;
-  selectedStore: StoreResult | null = null;
+  @ViewChild('map') mapRef!: ElementRef<HTMLElement>
+  map!: GoogleMap
+  mapBounds = new BehaviorSubject<LatLngBounds | null>(null)
+  activeMarkers: StoreMarker[] = []
+  selectedMarker: StoreMarker | null = null
+  selectedStore: StoreResult | null = null
 
-  constructor(
-    private storesService: StoresService,
-    private modalCtrl: ModalController
-  ) {}
+  constructor(private storesService: StoresService, private modalCtrl: ModalController) {}
 
   ionViewDidEnter() {
-    this.createMap();
+    this.createMap()
   }
-  
+
   async createMap() {
     this.map = await GoogleMap.create({
       forceCreate: true, // Prevent issues with live reload
@@ -667,22 +646,22 @@ export class HomePage {
         },
         zoom: 7,
       },
-    });
-    this.map.enableCurrentLocation(true);
+    })
+    this.map.enableCurrentLocation(true)
   }
 
   async showNearby() {
     const modal = await this.modalCtrl.create({
       component: NearbyPage,
-    });
-    modal.present();
+    })
+    modal.present()
   }
 
   async addStore() {
     const modal = await this.modalCtrl.create({
       component: StorePage,
-    });
-    modal.present();
+    })
+    modal.present()
   }
 }
 ```
@@ -1054,4 +1033,3 @@ Until next time and happy coding with Supabase!
 - [Authentication in Ionic Angular with Supabase](https://supabase.com/blog/authentication-in-ionic-angular)
 - [Building a Realtime Trello Board with Supabase and Angular](https://supabase.com/blog/building-a-realtime-trello-board-with-supabase-and-angular)
 - [Build a User Management App with Ionic Angular](https://supabase.com/docs/guides/getting-started/tutorials/with-ionic-angular)
-
diff --git a/apps/www/_blog/2023-03-09-supabase-beta-update-february-2023.mdx b/apps/www/_blog/2023-03-09-supabase-beta-update-february-2023.mdx
index 2f6f20dbf6a..29553ffa88e 100644
--- a/apps/www/_blog/2023-03-09-supabase-beta-update-february-2023.mdx
+++ b/apps/www/_blog/2023-03-09-supabase-beta-update-february-2023.mdx
@@ -102,13 +102,13 @@ Discover 100+ other apps in this [tweet](https://twitter.com/supabase/status/162
 
 - Langchain supports our database as a vector store, using pgvector. [Doc](https://hwchase17.github.io/langchainjs/docs/modules/indexes/vector_stores/supabase/) <br/>
 
-- refine week: building a CRUD app with refine & Supabase. [Full series](https://refine.dev/week-of-refine/) 
+- refine week: building a CRUD app with refine & Supabase. [Full series](https://refine.dev/week-of-refine/)
 
 - Build an Instagram Web App with Supabase and Next.js. [Tutorial](https://livecycle.io/blogs/nextjs-supabase-instagram/) <br/>
 
 - Supabase GeoQueries with PostGIS and Storage Upload. [Video](https://www.youtube.com/watch?v=-_Wpr7rwU8I) <br/>
 
-- How I used Supabase to build a winning hackathon project. [Article](https://blog.matt.lgbt/how-i-used-supabase-to-build-a-winning-hackathon-project) 
+- How I used Supabase to build a winning hackathon project. [Article](https://blog.matt.lgbt/how-i-used-supabase-to-build-a-winning-hackathon-project)
 
 - Using a Supabase API within FlutterFlow. [Video](https://www.youtube.com/watch?v=YzSXwlA3vWM) <br/>
 
diff --git a/apps/www/_blog/2023-04-07-designing-with-ai-midjourney.mdx b/apps/www/_blog/2023-04-07-designing-with-ai-midjourney.mdx
index d3952629f74..07f29e5190f 100644
--- a/apps/www/_blog/2023-04-07-designing-with-ai-midjourney.mdx
+++ b/apps/www/_blog/2023-04-07-designing-with-ai-midjourney.mdx
@@ -111,49 +111,42 @@ Since this table includes email addresses, we secure it using [RLS](https://supa
 By creating a view, we can selectively publicize parts of our table and also compute some additional values on the fly:
 
 ```sql
-drop
-  view if exists lw7_tickets_golden;
+drop view if exists lw7_tickets_golden;
 
-create
-or replace view lw7_tickets_golden as
-with
-  lw7_referrals as (
-    select
-      referred_by,
-      count(*) as referrals
-    from
-      lw7_tickets
-    where
-      referred_by is not null
-    group by
-      referred_by
-  )
-select
-  lw7_tickets."id",
-  lw7_tickets."name",
-  lw7_tickets."username",
-  lw7_tickets."ticketNumber",
-  lw7_tickets."createdAt",
-  lw7_tickets."sharedOnTwitter",
-  lw7_tickets."sharedOnLinkedIn",
-  lw7_tickets."bg_image_id",
-  case
-    when lw7_referrals.referrals is null then 0
-    ELSE lw7_referrals.referrals
-  end as referrals,
-  case
-    when lw7_tickets."sharedOnTwitter" is not null
-    and lw7_tickets."sharedOnLinkedIn" is not null then true
-    else false
-  end as golden
-from
-  lw7_tickets
-  left outer join lw7_referrals on lw7_tickets.username = lw7_referrals.referred_by;
+create or replace view lw7_tickets_golden as
+  with
+    lw7_referrals as (
+      select
+        referred_by,
+        count(*) as referrals
+      from lw7_tickets
+      where referred_by is not null
+      group by referred_by
+    )
+  select
+    lw7_tickets."id",
+    lw7_tickets."name",
+    lw7_tickets."username",
+    lw7_tickets."ticketNumber",
+    lw7_tickets."createdAt",
+    lw7_tickets."sharedOnTwitter",
+    lw7_tickets."sharedOnLinkedIn",
+    lw7_tickets."bg_image_id",
+    case
+      when lw7_referrals.referrals is null then 0
+      else lw7_referrals.referrals
+    end as referrals,
+    case
+      when lw7_tickets."sharedOnTwitter" is not null
+      and lw7_tickets."sharedOnLinkedIn" is not null then true
+      else false
+    end as golden
+  from
+    lw7_tickets
+    left outer join lw7_referrals on lw7_tickets.username = lw7_referrals.referred_by;
 
-select
-  *
-from
-  lw7_tickets_golden
+select *
+from lw7_tickets_golden;
 ```
 
 We can now retrieve that username by using the following code:
diff --git a/apps/www/_blog/2023-04-07-launch-week-7-hackathon.mdx b/apps/www/_blog/2023-04-07-launch-week-7-hackathon.mdx
index 8ea19a22a51..a4680e5d703 100644
--- a/apps/www/_blog/2023-04-07-launch-week-7-hackathon.mdx
+++ b/apps/www/_blog/2023-04-07-launch-week-7-hackathon.mdx
@@ -6,8 +6,8 @@ image: lw7-hackathon/thumbnail.png
 thumb: lw7-hackathon/thumbnail.png
 launchweek: 7
 tags:
-- launch-week
-- hackathon
+  - launch-week
+  - hackathon
 date: '2023-04-07'
 toc_depth: 2
 ---
@@ -25,8 +25,8 @@ Additionally, you can see all the [winners from previous hackathons](https://sup
 ## Key Facts
 
 - You have 10 days to build a new **Open Source** project using Supabase in some capacity.
-    - Starting 6:00 am PT Friday 7th April 2023
-    - The submission deadline is 11:59 pm Sunday midnight PT 16th April 2023
+  - Starting 6:00 am PT Friday 7th April 2023
+  - The submission deadline is 11:59 pm Sunday midnight PT 16th April 2023
 - Enter as an individual, or as a team of up to 5 people
 - Build whatever you want - a project, app, tool, library, or anything
 
@@ -46,7 +46,7 @@ There will be a winner and a runner-up prize for each category. Every team membe
 
 ## Submission
 
-You should submit your project using [this form](https://www.madewithsupabase.com/launch-week-7) before 11:59 pm Sunday midnight PT 16th April 2023. Extra points if you include a simple video demoing the app in the description. 
+You should submit your project using [this form](https://www.madewithsupabase.com/launch-week-7) before 11:59 pm Sunday midnight PT 16th April 2023. Extra points if you include a simple video demoing the app in the description.
 
 ## Judges
 
@@ -58,8 +58,8 @@ We will be looking for:
 - visually pleasing
 - technically impressive
 - use of Supabase features
-    - deep usage of a single feature or
-    - broad usage are both ok
+  - deep usage of a single feature or
+  - broad usage are both ok
 - FUN! 😃
 
 ## Rules
diff --git a/apps/www/_blog/2023-04-08-supabase-beta-update-march-2023.mdx b/apps/www/_blog/2023-04-08-supabase-beta-update-march-2023.mdx
index bc1f06b9583..b1d6a80fec1 100644
--- a/apps/www/_blog/2023-04-08-supabase-beta-update-march-2023.mdx
+++ b/apps/www/_blog/2023-04-08-supabase-beta-update-march-2023.mdx
@@ -71,16 +71,16 @@ After Monday's announcement, we are kicking off LW7 with a very cool Twitter Spa
 
 ![Community](/images/blog/2022-june/community.jpg)
 
--   Supabase hybrid search (`pgvector` + Full-Text search) with LangChain JS. [[Doc]](https://js.langchain.com/docs/modules/indexes/retrievers/supabase_hybrid)
--   Supabase Crash Course For .NET Developers: Building an API From Scratch. [[Video]](https://www.youtube.com/watch?v=uviVTDtYeeE)
--   Deno SaaSKit: an open-source SaaS template built with Fresh. [[Blog Post](https://deno.com/blog/announcing-deno-saaskit)]
--   Mastering Nuxt: Setting Up Supabase Auth With Nuxt 3. [[Article](https://masteringnuxt.com/blog/setting-up-supabase-auth-with-nuxt-3)]
--   Read data from Supabase and plot it in real-time on a Gradio Dashboard. [[Guide](https://gradio.app/creating-a-dashboard-from-supabase-data/)]
--   The story behind Alive and kicking. [[Video](https://www.youtube.com/watch?v=hhPiTREYobI)]
+- Supabase hybrid search (`pgvector` + Full-Text search) with LangChain JS. [[Doc]](https://js.langchain.com/docs/modules/indexes/retrievers/supabase_hybrid)
+- Supabase Crash Course For .NET Developers: Building an API From Scratch. [[Video]](https://www.youtube.com/watch?v=uviVTDtYeeE)
+- Deno SaaSKit: an open-source SaaS template built with Fresh. [[Blog Post](https://deno.com/blog/announcing-deno-saaskit)]
+- Mastering Nuxt: Setting Up Supabase Auth With Nuxt 3. [[Article](https://masteringnuxt.com/blog/setting-up-supabase-auth-with-nuxt-3)]
+- Read data from Supabase and plot it in real-time on a Gradio Dashboard. [[Guide](https://gradio.app/creating-a-dashboard-from-supabase-data/)]
+- The story behind Alive and kicking. [[Video](https://www.youtube.com/watch?v=hhPiTREYobI)]
 - Semantic Search with Supabase and OpenAI. [Video](https://www.youtube.com/watch?v=1dWfQLHUnVU)
 - ChatGPT with SvelteKit Forms & Supabase 🤖 Emoji App 🔴 LIVE Coding & Chill. [Video](https://www.youtube.com/watch?v=-hmYEcUaKUw)
 - Deploy a React App on App Platform with Self Hosted Supabase. [Tutorial](https://docs.digitalocean.com/developer-center/deploy-a-react-app-on-app-platform-with-self-hosted-supabase/)
--   Exploring Supabase's Postgres-powered features for GoLang applications. [Blog Post](https://dev.to/acethecloud/exploring-supabases-postgres-powered-features-for-golang-applications-ldb)
+- Exploring Supabase's Postgres-powered features for GoLang applications. [Blog Post](https://dev.to/acethecloud/exploring-supabases-postgres-powered-features-for-golang-applications-ldb)
 - How to build auth with Next.js App Router and Supabase Auth. [Tutorial](https://www.neorepo.com/blog/how-to-build-auth-with-nextjs-app-router-and-supabase-auth)
 - 8 best open-source low-code platforms. [Blog post](https://blog.n8n.io/open-source-low-code-platforms/)
 - How to Upload Images to a Supabase Storage Bucket From a Next.js App. [Tutorial](https://www.makeuseof.com/next-js-upload-images-supabase-storage-bucket)
@@ -94,4 +94,3 @@ React be like...
 As always, one of our favorite memes from last month. [Follow us on Twitter](https://twitter.com/supabase) for more.
 
 See you next month!
-
diff --git a/apps/www/_blog/2023-04-13-supabase-auth-sso-pkce.mdx b/apps/www/_blog/2023-04-13-supabase-auth-sso-pkce.mdx
index c1a4dfb36ea..b0ff0777bf7 100644
--- a/apps/www/_blog/2023-04-13-supabase-auth-sso-pkce.mdx
+++ b/apps/www/_blog/2023-04-13-supabase-auth-sso-pkce.mdx
@@ -225,6 +225,8 @@ export default async function handler(req: NextApiRequest, res: NextApiResponse)
 
 Since this is a major update that touches many of the authentication routes, we will roll it out gradually over the next few weeks. You will receive a notification in your dashboard when the feature is available for your project. Reach out to us if you want early access to this feature.
 
+**Update**: Server-Side Auth (PKCE) is now available on all projects. Please refer to our [Server Side Auth Guide](https://supabase.com/docs/guides/auth/server-side-rendering) for further details on how to add PKCE to your project.
+
 ## Native Apple login on iOS
 
 While PKCE support is great, that is not the only news for you mobile app developers out there.
diff --git a/apps/www/_blog/2023-04-14-dbdev.mdx b/apps/www/_blog/2023-04-14-dbdev.mdx
index f50a74c42a4..862375f736e 100644
--- a/apps/www/_blog/2023-04-14-dbdev.mdx
+++ b/apps/www/_blog/2023-04-14-dbdev.mdx
@@ -164,10 +164,8 @@ For example, you could apply a deny listing to your API using `hdr.in_deny_list(
 ```sql
 select
   *
-from
-  app.memos
-where
-  not hdr.in_deny_list ();
+from app.memos
+where not hdr.in_deny_list();
 ```
 
 ### olirice-index_advisor
diff --git a/apps/www/_blog/2023-04-21-whats-new-in-pg-graphql-v1-2.mdx b/apps/www/_blog/2023-04-21-whats-new-in-pg-graphql-v1-2.mdx
index d3cd7fb012c..8e5a362361f 100644
--- a/apps/www/_blog/2023-04-21-whats-new-in-pg-graphql-v1-2.mdx
+++ b/apps/www/_blog/2023-04-21-whats-new-in-pg-graphql-v1-2.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'What''s New in pg_graphql v1.2'
+title: "What's New in pg_graphql v1.2"
 description: 'New Features in the v1.2 release of pg_graphql'
 launchweek: 7
 tags:
@@ -37,11 +37,9 @@ create view "ProjectOwner" as
     acc.id,
     acc.name
   from
-    account acc
-    join role r
-      on r.id = acc.role_id
-  where
-    acc.role = 'project_owner'
+    account as acc
+    join role as r on r.id = acc.role_id
+  where acc.role = 'project_owner';
 ```
 
 Since all entities exposed by `pg_graphql` require primary keys, we must define that constraint for the view. We do that using a comment directive:
@@ -65,7 +63,7 @@ With associated `Edge` and `Connection` types. That enables querying via:
 
 ```graphql
 {
-  projectOwnerCollection (first: 2) {
+  projectOwnerCollection(first: 2) {
     edges {
       node {
         nodeId
@@ -131,7 +129,7 @@ Note that `startsWith` filters should be preferred where appropriate because the
 
 ```graphql
 {
-  generalLedgerCollection(filter: {identifierCode: {startsWith: "BX1:"}}) {
+  generalLedgerCollection(filter: { identifierCode: { startsWith: "BX1:" } }) {
     edges {
       node {
         nodeId
diff --git a/apps/www/_blog/2023-04-24-launch-week-7-hackathon-winners.mdx b/apps/www/_blog/2023-04-24-launch-week-7-hackathon-winners.mdx
index ce33b100751..c4fdd2a2de7 100644
--- a/apps/www/_blog/2023-04-24-launch-week-7-hackathon-winners.mdx
+++ b/apps/www/_blog/2023-04-24-launch-week-7-hackathon-winners.mdx
@@ -36,7 +36,7 @@ Rect takes short-form social media content as an input, and produces four kinds
 
 ### Winner
 
-[Supathreads](https://github.com/asrvd/supathreads) - by [@_asheeshh](https://twitter.com/_asheeshh)
+[Supathreads](https://github.com/asrvd/supathreads) - by [@\_asheeshh](https://twitter.com/_asheeshh)
 
 Supathreads creates concise and professional Twitter threads from your blog posts within seconds using the power of AI.
 
@@ -54,7 +54,7 @@ ChatVox takes the YouTube/Podcast link you enter or the local Video/Audio file (
 
 ### Winner
 
-[Replay.ai - spotlight search for your browsing history](https://github.com/KamaniBhavin/replay) - by [@bhavinkamani_](https://twitter.com/bhavinkamani_)
+[Replay.ai - spotlight search for your browsing history](https://github.com/KamaniBhavin/replay) - by [@bhavinkamani\_](https://twitter.com/bhavinkamani_)
 
 Replay is a Chrome extension that lets you search through all the pages in your browsing history to find the one you can't remember. It uses cosine similarity search to find the page based on the content of the page and the search query provided by the user.
 
@@ -64,7 +64,7 @@ Replay is a Chrome extension that lets you search through all the pages in your
 
 [Groove AI - AI Generated Drum Patterns](https://github.com/danryland/groove-ai) - by [@RealDanRyland](https://twitter.com/RealDanRyland)
 
-Groove AI generates drum patterns powered by AI and randomly plays the pattern whenever you open the page. You can modify the pattern by toggling each beat. 
+Groove AI generates drum patterns powered by AI and randomly plays the pattern whenever you open the page. You can modify the pattern by toggling each beat.
 
 ![Groove AI - AI Generated Drum Patterns](/images/blog/lw7-hackathon-winners/06_grooveai.png)
 
@@ -86,7 +86,6 @@ Schedurio is very helpful for Twitter content creators who are paying monthly fo
 
 ![Schedurio](/images/blog/lw7-hackathon-winners/08_schedurio.png)
 
-
 ## Most visually pleasing
 
 ### Winner
@@ -121,4 +120,4 @@ If you're inspired to build, check out some of the latest resources:
 
 - **[Quick Start Guides](https://supabase.com/docs/guides/getting-started)**
 - **[Supabase Storage Guide](https://supabase.com/docs/guides/storage)**
-- **[Edge Functions Guide](https://supabase.com/docs/guides/functions)**
\ No newline at end of file
+- **[Edge Functions Guide](https://supabase.com/docs/guides/functions)**
diff --git a/apps/www/_blog/2023-05-09-supabase-beta-update-april-2023.mdx b/apps/www/_blog/2023-05-09-supabase-beta-update-april-2023.mdx
index aaa8991391a..2a14bd6b79d 100644
--- a/apps/www/_blog/2023-05-09-supabase-beta-update-april-2023.mdx
+++ b/apps/www/_blog/2023-05-09-supabase-beta-update-april-2023.mdx
@@ -12,7 +12,7 @@ toc_depth: 3
 
 Brace yourself, this is one of the most feature-packed Beta Updates we've published so far.
 
-[Launch Week 7](https://supabase.com/launch-week) was a massive success with great feedback from the community. We also gave away lots of mechanical keyboards, including the Hackathon winner which we announce here!
+[Launch Week 7](https://supabase.com/launch-week) was a massive success with great feedback from the community. We also gave away lots of mechanical keyboards, including the Hackathon winner which we announce here!
 
 ## Day 1 - Supabase Logs: open source logging server
 
@@ -59,7 +59,7 @@ Supabase Studio got a major upgrade that goes from redesigns to improved develop
 [Blog Post](https://supabase.com/blog/supabase-studio-2.0)\
 [Video overview](https://www.youtube.com/watch?v=0rcNqHt5KWU)
 
-## Community highlights 
+## Community highlights
 
 ![Community highlights](/images/blog/2023-05-09-beta-update-april/newsletter-OG-day5-community.jpg)
 
@@ -71,24 +71,23 @@ Our community defines us. We're honored to work with, sponsor, and support incre
 
 ![dbdev: PostgreSQL Package Manager](/images/blog/2023-05-09-beta-update-april/newsletter-OG-day5-dbdev.jpg)
 
-[database.dev](https://database.dev/) fills the same role for PostgreSQL as `npm` for JavaScript or `pip` for Python, it enables publishing libraries and applications for repeatable deployment. Our goal is to create an open ecosystem for packaging and discovering SQL.
+[database.dev](https://database.dev/) fills the same role for PostgreSQL as `npm` for JavaScript or `pip` for Python, it enables publishing libraries and applications for repeatable deployment. Our goal is to create an open ecosystem for packaging and discovering SQL.
 
 [Blog post](https://supabase.com/blog/dbdev)
 
 ## More product announcements
 
-- Trusted Language Extensions for Postgres. [[Blog post]](https://supabase.com/blog/pg-tle)
-- What's New in pg_graphql v1.2. [[Blog post]](https://supabase.com/blog/whats-new-in-pg-graphql-v1-2)
-- GitHub Discussions are now a new knowledge source for search & AI (Troubleshooting category only for now). [[Check it out]](https://supabase.com/docs)
-- New API report with routing information for each chart, making it easier to debug API calls.  [[PR]](https://github.com/supabase/supabase/pull/14063)
+- Trusted Language Extensions for Postgres. [[Blog post]](https://supabase.com/blog/pg-tle)
+- What's New in pg_graphql v1.2. [[Blog post]](https://supabase.com/blog/whats-new-in-pg-graphql-v1-2)
+- GitHub Discussions are now a new knowledge source for search & AI (Troubleshooting category only for now). [[Check it out]](https://supabase.com/docs)
+- New API report with routing information for each chart, making it easier to debug API calls. [[PR]](https://github.com/supabase/supabase/pull/14063)
 - Storage permission changes: the developer role is now allowed to update the storage settings (previously was only owner and admin). [[PR]](https://github.com/supabase/supabase/pull/13883)
 
-
 ## Launch Week 7 Hackathon winners
 
 ![Launch Week 7 Hackathon winners](/images/blog/2023-05-09-beta-update-april/newsletter-hackathon.jpg)
 
-The community is loving `pgvector` to build AI apps so we decided to make it part of the traditional Launch Week Hackathon. The quality of the apps was out of this world, it wasn't easy, but in the end, we selected [Page Assist](https://github.com/n4ze3m/page-assist) - by [@n4ze3m ](https://twitter.com/n4ze3m)as the winner of the Best Overall Project. 
+The community is loving `pgvector` to build AI apps so we decided to make it part of the traditional Launch Week Hackathon. The quality of the apps was out of this world, it wasn't easy, but in the end, we selected [Page Assist](https://github.com/n4ze3m/page-assist) - by [@n4ze3m ](https://twitter.com/n4ze3m)as the winner of the Best Overall Project.
 
 [Full list of Winners](https://supabase.com/blog/launch-week-7-hackathon-winners)
 
@@ -106,12 +105,12 @@ With Supabase's pg_vector, Mendable.ai could build a more cost-effective solutio
 
 ![Community](/images/blog/2022-june/community.jpg)
 
-- FlutterFlow now supports Supabase Authentication. [Video guide](https://www.youtube.com/watch?v=tL-sLPfWzVE)
-- Supabase + ClickHouse: Combining the Best of the OLTP and OLAP Worlds. [Webinar](https://www.youtube.com/watch?v=LDWEsw41Zko)
-- Our friend Guillaume put together the most incredible course about Supabase, with the in and outs of the platform. [Full course](https://www.youtube.com/watch?v=8DTOTT7q0XA)
-- Supabase + LangChain starter template for building full stack AI apps. [Template](https://github.com/langchain-ai/langchain-template-supabase)
+- FlutterFlow now supports Supabase Authentication. [Video guide](https://www.youtube.com/watch?v=tL-sLPfWzVE)
+- Supabase + ClickHouse: Combining the Best of the OLTP and OLAP Worlds. [Webinar](https://www.youtube.com/watch?v=LDWEsw41Zko)
+- Our friend Guillaume put together the most incredible course about Supabase, with the in and outs of the platform. [Full course](https://www.youtube.com/watch?v=8DTOTT7q0XA)
+- Supabase + LangChain starter template for building full stack AI apps. [Template](https://github.com/langchain-ai/langchain-template-supabase)
 - Creating a Books Tracker App with .NET MAUI and Supabase. [Article](https://hackernoon.com/creating-a-books-tracker-app-with-net-maui-and-supabase)
-- Vanta Case Study - Supabase turns trust into a revenue-generating opportunity with Vanta. [Case Study](https://www.vanta.com/customers/supabase)
+  - Vanta Case Study - Supabase turns trust into a revenue-generating opportunity with Vanta. [Case Study](https://www.vanta.com/customers/supabase)
 
 ## Meme Zone
 
diff --git a/apps/www/_customers/mendableai.mdx b/apps/www/_customers/mendableai.mdx
index c4421a4f73e..1a911c9f952 100644
--- a/apps/www/_customers/mendableai.mdx
+++ b/apps/www/_customers/mendableai.mdx
@@ -1,7 +1,7 @@
 ---
-title: Mendable.ai switches from Pinecone to Supabase for PostgreSQL vector embeddings.
-name: Mendable.ai
-description: How Mendable.ai boosts efficiency and accuracy of chat powered search for documentation using Supabase with pg_vector.
+title: Mendable switches from Pinecone to Supabase for PostgreSQL vector embeddings.
+name: Mendable
+description: How Mendable boosts efficiency and accuracy of chat powered search for documentation using Supabase with pgvector.
 author: paul_copplestone
 author_title: Supabase
 author_url: https://github.com/kiwicopple
@@ -21,19 +21,19 @@ stats:
     { stat: '00,000', label: Example stat },
   ]
 misc: [{ label: 'Backed by', text: 'Y Combinator' }]
-about: Mendable.ai is Chat Powered Search for Documentation.
+about: Mendable is Chat Powered Search for Documentation.
 ---
 
-[Mendable.ai](http://mendable.ai/) provides a chat-powered search engine for technical documentation. Their AI-powered search tool makes it easier for developers and other technical users to find relevant information in complex documentation. Users can simply ask questions in natural language, and the tool returns the most relevant answers. Mendable.ai's search engine also provides detailed analytics, which helps teams identify knowledge gaps and areas for improvement in their documentation.
+[Mendable](http://mendable.ai/) provides a chat-powered search engine for technical documentation. Their AI-powered search tool makes it easier for developers and other technical users to find relevant information in complex documentation. Users can simply ask questions in natural language, and the tool returns the most relevant answers. Mendable's search engine also provides detailed analytics, which helps teams identify knowledge gaps and areas for improvement in their documentation. Mendable has integrated with some of the largest open source projects in the space such as Langchain and LlamaIndex.
 
 ## The Challenge
 
-Mendable.ai was experiencing tremendous success, with WAUs growing nearly 300% since March, and started looking for a tool to store and search through large amounts of vector data to improve the efficiency and accuracy of their similarity search operations for their Chat Powered Search for Documentation. They tried Faiss, Weviate, and Pinecone, but found them to be expensive and not very intuitive, especially when it came to storing metadata along with the vectors.
+Mendable was experiencing tremendous success, growing Weekly Active Users nearly 300% since March. They needed a tool to store and search through large amounts of vector data to improve the efficiency and accuracy of their similarity search operations. They tried Faiss, Weviate, and Pinecone, but found them to be expensive and not very intuitive, especially when it came to storing metadata along with the vectors.
 
 Why they chose Supabase:
-Mendable.ai discovered that Supabase supports pgvector and found it to be a simple and cost-effective solution. They were impressed with the open source nature of Supabase, as well as its ability to store metadata alongside the vectors. They also appreciated the intuitive interface and ease of use.
+Mendable discovered that Supabase supports pgvector and found it to be a simple and cost-effective solution. They were impressed with the open source nature of Supabase, as well as its ability to store metadata alongside the vectors. They also appreciated the intuitive interface and ease of use.
 
-<Quote img="caleb-peffer.jpg" caption="Caleb Peffer - CEO, Mendable.ai">
+<Quote img="caleb-peffer.jpg" caption="Caleb Peffer - CEO, Mendable">
   We tried other vector databases - we tried Faiss, we tried Weviate, we tried Pinecone. We found
   them to be incredibly expensive and not very intuitive. If you’re just doing vector search they’re
   great, but if you need to store a bunch of metadata that becomes a huge pain.
@@ -41,17 +41,17 @@ Mendable.ai discovered that Supabase supports pgvector and found it to be a simp
 
 ## What They Built
 
-Using Supabase and pgvector, Mendable.ai was able to build a more efficient and accurate search function for their AI chatbot. By storing vector data alongside metadata in Supabase, Mendable.ai was able to quickly and easily search through their customers documentation to find the most relevant responses to queries. They found that Supabase's solution was just as performant as dedicated vector databases, but without the high cost.
+Using Supabase and pgvector, Mendable was able to build a more efficient and accurate search function for their AI chatbot. By storing vector data alongside metadata in Supabase, Mendable was able to quickly and easily search through their customers documentation to find the most relevant responses to queries. They found that Supabase's solution was just as performant as dedicated vector databases, but without the high cost.
 
 ## The Results
 
-Thanks to Supabase and pgvector, Mendable.ai was able to significantly improve the efficiency and accuracy of their Chat Powered Search for Documentation. They were able to build faster and more cost-effectively using Supabase’s open source stack.
+Thanks to Supabase and pgvector, Mendable was able to significantly improve the efficiency and accuracy of their Chat Powered Search for Documentation. They were able to build faster and more cost-effectively using Supabase’s open source stack.
 
 ## Tech stack
 
-Mendable.ai's tech stack includes React, Next.js, Express, Vercel, and Supabase.
+Mendable's tech stack includes React, Next.js, Express, Vercel, and Supabase.
 
-<Quote img="caleb-peffer.jpg" caption="Caleb Peffer - CEO, Mendable.ai">
+<Quote img="caleb-peffer.jpg" caption="Caleb Peffer - CEO, Mendable">
   We looked at the alternatives and chose Supabase because it’s open source, it’s simpler, and, for
   all the ways we need use it, Supabase has been just as performant - if not more performant - than
   the other vector databases.
diff --git a/apps/www/components/CodeBlock/CodeBlock.tsx b/apps/www/components/CodeBlock/CodeBlock.tsx
index c45e96b6021..7b40664cea9 100644
--- a/apps/www/components/CodeBlock/CodeBlock.tsx
+++ b/apps/www/components/CodeBlock/CodeBlock.tsx
@@ -6,10 +6,11 @@ import bash from 'react-syntax-highlighter/dist/cjs/languages/hljs/bash'
 import js from 'react-syntax-highlighter/dist/cjs/languages/hljs/javascript'
 import py from 'react-syntax-highlighter/dist/cjs/languages/hljs/python'
 import sql from 'react-syntax-highlighter/dist/cjs/languages/hljs/sql'
+import kotlin from 'react-syntax-highlighter/dist/cjs/languages/hljs/kotlin'
 import monokaiCustomTheme from './CodeBlock.utils'
 
 export interface CodeBlockProps {
-  lang: 'js' | 'sql' | 'py' | 'bash' | 'ts' | 'tsx'
+  lang: 'js' | 'sql' | 'py' | 'bash' | 'ts' | 'tsx' | 'kotlin'
   startingLineNumber?: number
   hideCopy?: boolean
   showLineNumbers?: boolean
@@ -51,6 +52,7 @@ function CodeBlock(props: CodeBlockProps) {
   SyntaxHighlighter.registerLanguage('py', py)
   SyntaxHighlighter.registerLanguage('sql', sql)
   SyntaxHighlighter.registerLanguage('bash', bash)
+  SyntaxHighlighter.registerLanguage('kotlin', kotlin)
 
   // const large = props.size === 'large' ? true : false
   const large = false
diff --git a/i18n/README.ar.md b/i18n/README.ar.md
index 2f634548830..eb708f5d4b5 100644
--- a/i18n/README.ar.md
+++ b/i18n/README.ar.md
@@ -134,11 +134,11 @@ Supabase عبارة عن مجموعة من الأدوات مفتوحة المص
   </tr>
   <tr>
     <td>Kotlin</td>
-    <td>-</td>
-    <td><a href="https://github.com/supabase-community/postgrest-kt" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
-    <td><a href="https://github.com/supabase-community/gotrue-kt" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
-    <td>-</td>
-    <td>-</td>
+    <td><a href="https://github.com/supabase-community/supabase-kt" target="_blank" rel="noopener noreferrer">supabase-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Postgrest" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/GoTrue" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Realtime" target="_blank" rel="noopener noreferrer">realtime-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Storage" target="_blank" rel="noopener noreferrer">storage-kt</a></td>
   </tr>
   <tr>
     <td>Python</td>
diff --git a/i18n/README.bg.md b/i18n/README.bg.md
index 34d87827c84..d25974d7fa5 100644
--- a/i18n/README.bg.md
+++ b/i18n/README.bg.md
@@ -141,11 +141,11 @@ Supabase е [хоствана платформа](https://app.supabase.com). М
   </tr>
   <tr>
     <td>Kotlin</td>
-    <td>-</td>
-    <td><a href="https://github.com/supabase-community/postgrest-kt" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
-    <td><a href="https://github.com/supabase-community/gotrue-kt" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
-    <td>-</td>
-    <td>-</td>
+    <td><a href="https://github.com/supabase-community/supabase-kt" target="_blank" rel="noopener noreferrer">supabase-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Postgrest" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/GoTrue" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Realtime" target="_blank" rel="noopener noreferrer">realtime-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Storage" target="_blank" rel="noopener noreferrer">storage-kt</a></td>
   </tr>
   <tr>
     <td>Python</td>
diff --git a/i18n/README.bn.md b/i18n/README.bn.md
index 649a5f7f46c..298cdd07688 100644
--- a/i18n/README.bn.md
+++ b/i18n/README.bn.md
@@ -141,11 +141,12 @@ Supabase হল ওপেন সোর্স টুলের সংমিশ্
   </tr>
   <tr>
     <td>কোটলিন</td>
-    <td>-</td>
-    <td><a href="https://github.com/supabase-community/postgrest-kt" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
-    <td><a href="https://github.com/supabase-community/gotrue-kt" target="_blank" rel="noopener noreferrer">গোট্রু-kt</a></td>
-    <td>-</td>
-    <td>-</td>
+    <td>Kotlin</td>
+    <td><a href="https://github.com/supabase-community/supabase-kt" target="_blank" rel="noopener noreferrer">supabase-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Postgrest" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/GoTrue" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Realtime" target="_blank" rel="noopener noreferrer">realtime-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Storage" target="_blank" rel="noopener noreferrer">storage-kt</a></td>
   </tr>
   <tr>
     <td>পাইথন</td>
diff --git a/i18n/README.es.md b/i18n/README.es.md
index 602393663a2..612b2738002 100644
--- a/i18n/README.es.md
+++ b/i18n/README.es.md
@@ -147,8 +147,8 @@ Nuestra librería de cliente es modular. Cada sub-librería es una implementaci
   <tr>
     <td>Kotlin</td>
     <td><a href="https://github.com/supabase-community/supabase-kt" target="_blank" rel="noopener noreferrer">supabase-kt</a></td>
-    <td><a href="https://github.com/supabase-community/postgrest-kt" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
-    <td><a href="https://github.com/supabase-community/gotrue-kt" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Postgrest" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/GoTrue" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
     <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Realtime" target="_blank" rel="noopener noreferrer">realtime-kt</a></td>
     <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Storage" target="_blank" rel="noopener noreferrer">storage-kt</a></td>
     <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Functions" target="_blank" rel="noopener noreferrer">functions-kt</a></td>
diff --git a/i18n/README.fi.md b/i18n/README.fi.md
index c810718b5c0..793d0a3b717 100644
--- a/i18n/README.fi.md
+++ b/i18n/README.fi.md
@@ -147,12 +147,12 @@ Lähestymistapamme asiakaskirjastoissa on modulaarinen. Jokainen alikirjasto on
   </tr>
   <tr>
     <td>Kotlin</td>
-    <td>-</td>
-    <td><a href="https://github.com/supabase-community/postgrest-kt" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
-    <td><a href="https://github.com/supabase-community/gotrue-kt" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
-    <td>-</td>
-    <td>-</td>
-    <td>-</td>
+    <td><a href="https://github.com/supabase-community/supabase-kt" target="_blank" rel="noopener noreferrer">supabase-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Postgrest" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/GoTrue" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Realtime" target="_blank" rel="noopener noreferrer">realtime-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Storage" target="_blank" rel="noopener noreferrer">storage-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Functions" target="_blank" rel="noopener noreferrer">functions-kt</a></td>
   </tr>
   <tr>
     <td>Python</td>
diff --git a/i18n/README.fr.md b/i18n/README.fr.md
index 33cd09fee3f..ff4f40fffe1 100644
--- a/i18n/README.fr.md
+++ b/i18n/README.fr.md
@@ -137,11 +137,11 @@ Notre bibliothèque client est modulaire. Chaque sous-bibliothèque est une impl
   </tr>
   <tr>
     <td>Kotlin</td>
-    <td>-</td>
-    <td><a href="https://github.com/supabase-community/postgrest-kt" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
-    <td><a href="https://github.com/supabase-community/gotrue-kt" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
-    <td>-</td>
-    <td>-</td>
+    <td><a href="https://github.com/supabase-community/supabase-kt" target="_blank" rel="noopener noreferrer">supabase-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Postgrest" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/GoTrue" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Realtime" target="_blank" rel="noopener noreferrer">realtime-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Storage" target="_blank" rel="noopener noreferrer">storage-kt</a></td>
   </tr>
   <tr>
     <td>Python</td>
diff --git a/i18n/README.hi.md b/i18n/README.hi.md
index 7dd063c6082..b5e39febae6 100644
--- a/i18n/README.hi.md
+++ b/i18n/README.hi.md
@@ -139,12 +139,12 @@
     <td>-</td>
   </tr>
   <tr>
-    <td>कोटलिन</td>
-    <td>-</td>
-    <td><a href="https://github.com/supabase-community/postgrest-kt" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
-    <td><a href="https://github.com/supabase-community/gotrue-kt" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
-    <td>-</td>
-    <td>-</td>
+    <td>Kotlin</td>
+    <td><a href="https://github.com/supabase-community/supabase-kt" target="_blank" rel="noopener noreferrer">supabase-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Postgrest" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/GoTrue" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Realtime" target="_blank" rel="noopener noreferrer">realtime-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Storage" target="_blank" rel="noopener noreferrer">storage-kt</a></td>
   </tr>
   <tr>
     <td>पाइथन</td>
diff --git a/i18n/README.jp.md b/i18n/README.jp.md
index 0b999954e1b..dd14a029389 100644
--- a/i18n/README.jp.md
+++ b/i18n/README.jp.md
@@ -147,12 +147,12 @@ Supabase クライアントライブラリはモジュール化されていま
   </tr>
   <tr>
     <td>Kotlin</td>
-    <td>-</td>
-    <td><a href="https://github.com/supabase-community/postgrest-kt" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
-    <td><a href="https://github.com/supabase-community/gotrue-kt" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
-    <td>-</td>
-    <td>-</td>
-    <td>-</td>
+    <td><a href="https://github.com/supabase-community/supabase-kt" target="_blank" rel="noopener noreferrer">supabase-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Postgrest" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/GoTrue" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Realtime" target="_blank" rel="noopener noreferrer">realtime-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Storage" target="_blank" rel="noopener noreferrer">storage-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Functions" target="_blank" rel="noopener noreferrer">functions-kt</a></td>
   </tr>
   <tr>
     <td>Python</td>
diff --git a/i18n/README.ko.md b/i18n/README.ko.md
index 2e2eff83792..bf6531d4aeb 100644
--- a/i18n/README.ko.md
+++ b/i18n/README.ko.md
@@ -145,12 +145,12 @@ Supabase 클라이언트 라이브러리는 모듈식 입니다. 각 하위 라
   </tr>
   <tr>
     <td>Kotlin</td>
-    <td>-</td>
-    <td><a href="https://github.com/supabase-community/postgrest-kt" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
-    <td><a href="https://github.com/supabase-community/gotrue-kt" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
-    <td>-</td>
-    <td>-</td>
-    <td>-</td>
+    <td><a href="https://github.com/supabase-community/supabase-kt" target="_blank" rel="noopener noreferrer">supabase-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Postgrest" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/GoTrue" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Realtime" target="_blank" rel="noopener noreferrer">realtime-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Storage" target="_blank" rel="noopener noreferrer">storage-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Functions" target="_blank" rel="noopener noreferrer">functions-kt</a></td>
   </tr>
   <tr>
     <td>Python</td>
diff --git a/i18n/README.pt-br.md b/i18n/README.pt-br.md
index abad7cdd27b..bea72a069ba 100644
--- a/i18n/README.pt-br.md
+++ b/i18n/README.pt-br.md
@@ -148,8 +148,8 @@ Nossa biblioteca de cliente é modular. Cada sub-biblioteca é uma implementaç
   <tr>
     <td>Kotlin</td>
     <td><a href="https://github.com/supabase-community/supabase-kt" target="_blank" rel="noopener noreferrer">supabase-kt</a></td>
-    <td><a href="https://github.com/supabase-community/postgrest-kt" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
-    <td><a href="https://github.com/supabase-community/gotrue-kt" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Postgrest" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/GoTrue" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
     <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Realtime" target="_blank" rel="noopener noreferrer">realtime-kt</a></td>
     <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Storage" target="_blank" rel="noopener noreferrer">storage-kt</a></td>
     <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Functions" target="_blank" rel="noopener noreferrer">functions-kt</a></td>
diff --git a/i18n/README.sr.md b/i18n/README.sr.md
index e85529abdfa..27817cb4662 100644
--- a/i18n/README.sr.md
+++ b/i18n/README.sr.md
@@ -147,12 +147,12 @@ Naš pristup klijentskim bibliotekama je modularan. Svaka pod-biblioteka je samo
   </tr>
   <tr>
     <td>Kotlin</td>
-    <td>-</td>
-    <td><a href="https://github.com/supabase-community/postgrest-kt" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
-    <td><a href="https://github.com/supabase-community/gotrue-kt" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
-    <td>-</td>
-    <td>-</td>
-    <td>-</td>
+    <td><a href="https://github.com/supabase-community/supabase-kt" target="_blank" rel="noopener noreferrer">supabase-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Postgrest" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/GoTrue" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Realtime" target="_blank" rel="noopener noreferrer">realtime-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Storage" target="_blank" rel="noopener noreferrer">storage-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Functions" target="_blank" rel="noopener noreferrer">functions-kt</a></td>
   </tr>
   <tr>
     <td>Python</td>
diff --git a/i18n/README.ta.md b/i18n/README.ta.md
index 0806fbe79af..89cab1c35b2 100644
--- a/i18n/README.ta.md
+++ b/i18n/README.ta.md
@@ -142,11 +142,11 @@
   </tr>
   <tr>
     <td>கோட்லின்</td>
-    <td>-</td>
-    <td><a href="https://github.com/supabase-community/postgrest-kt" target="_blank" rel="noopener noreferrer">போஸ்ட்ஜீராஸ்ட்-கேடி</a></td>
-    <td><a href="https://github.com/supabase-community/gotrue-kt" target="_blank" rel="noopener noreferrer">கூட்ரூ-கேடி</a></td>
-    <td>-</td>
-    <td>-</td>
+    <td><a href="https://github.com/supabase-community/supabase-kt" target="_blank" rel="noopener noreferrer">supabase-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Postgrest" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/GoTrue" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Realtime" target="_blank" rel="noopener noreferrer">realtime-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Storage" target="_blank" rel="noopener noreferrer">storage-kt</a></td>
   </tr>
   <tr>
     <td>பித்தன்</td>
diff --git a/i18n/README.tr.md b/i18n/README.tr.md
index 94165e8fdd0..cfc70b36edc 100644
--- a/i18n/README.tr.md
+++ b/i18n/README.tr.md
@@ -134,11 +134,11 @@ Müşteri kitaplığımız modülerdir. Her bir alt kütüphane, tek bir harici
   </tr>
   <tr>
     <td>Kotlin</td>
-    <td>-</td>
-    <td><a href="https://github.com/supabase-community/postgrest-kt" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
-    <td><a href="https://github.com/supabase-community/gotrue-kt" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
-    <td>-</td>
-    <td>-</td>
+    <td><a href="https://github.com/supabase-community/supabase-kt" target="_blank" rel="noopener noreferrer">supabase-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Postgrest" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/GoTrue" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Realtime" target="_blank" rel="noopener noreferrer">realtime-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Storage" target="_blank" rel="noopener noreferrer">storage-kt</a></td>
   </tr>
   <tr>
     <td>Python</td>
diff --git a/i18n/README.vi-vn.md b/i18n/README.vi-vn.md
index 6e5994784ef..ff362a85a74 100644
--- a/i18n/README.vi-vn.md
+++ b/i18n/README.vi-vn.md
@@ -147,12 +147,11 @@ Phương pháp tiếp cận của chúng tôi cho các thư viện hỗ trợ l
   </tr>
   <tr>
     <td>Kotlin</td>
-    <td>-</td>
-    <td><a href="https://github.com/supabase-community/postgrest-kt" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
-    <td><a href="https://github.com/supabase-community/gotrue-kt" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
-    <td>-</td>
-    <td>-</td>
-    <td>-</td>
+    <td><a href="https://github.com/supabase-community/supabase-kt" target="_blank" rel="noopener noreferrer">supabase-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Postgrest" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/GoTrue" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Realtime" target="_blank" rel="noopener noreferrer">realtime-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Storage" target="_blank" rel="noopener noreferrer">storage-kt</a></td>
   </tr>
   <tr>
     <td>Python</td>
diff --git a/i18n/README.zh-cn.md b/i18n/README.zh-cn.md
index 639483df4fe..86acbcd758a 100644
--- a/i18n/README.zh-cn.md
+++ b/i18n/README.zh-cn.md
@@ -141,11 +141,11 @@ Supabase 是一个[托管平台](https://app.supabase.com)。你可以注册并
   </tr>
   <tr>
     <td>Kotlin</td>
-    <td>-</td>
-    <td><a href="https://github.com/supabase-community/postgrest-kt" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
-    <td><a href="https://github.com/supabase-community/gotrue-kt" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
-    <td>-</td>
-    <td>-</td>
+    <td><a href="https://github.com/supabase-community/supabase-kt" target="_blank" rel="noopener noreferrer">supabase-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Postgrest" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/GoTrue" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Realtime" target="_blank" rel="noopener noreferrer">realtime-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Storage" target="_blank" rel="noopener noreferrer">storage-kt</a></td>
   </tr>
   <tr>
     <td>Python</td>
diff --git a/i18n/README.zh-tw.md b/i18n/README.zh-tw.md
index 4a24a33628a..2723718db82 100644
--- a/i18n/README.zh-tw.md
+++ b/i18n/README.zh-tw.md
@@ -146,11 +146,10 @@ Supabase 是[託管平台](https://app.supabase.com)。只要註冊，不必安
   <tr>
     <td>Kotlin</td>
     <td><a href="https://github.com/supabase-community/supabase-kt" target="_blank" rel="noopener noreferrer">supabase-kt</a></td>
-    <td><a href="https://github.com/supabase-community/postgrest-kt" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
-    <td><a href="https://github.com/supabase-community/gotrue-kt" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Postgrest" target="_blank" rel="noopener noreferrer">postgrest-kt</a></td>
+    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/GoTrue" target="_blank" rel="noopener noreferrer">gotrue-kt</a></td>
     <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Realtime" target="_blank" rel="noopener noreferrer">realtime-kt</a></td>
     <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Storage" target="_blank" rel="noopener noreferrer">storage-kt</a></td>
-    <td><a href="https://github.com/supabase-community/supabase-kt/tree/master/Functions" target="_blank" rel="noopener noreferrer">functions-kt</a></td>
   </tr>
   <tr>
     <td>Python</td>
diff --git a/package-lock.json b/package-lock.json
index 581afac622a..d3c3ed3179d 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -22,7 +22,7 @@
         "eslint": "^7.32.0",
         "eslint-config-custom": "*",
         "json-stringify-safe": "^5.0.1",
-        "prettier": "^2.8.4",
+        "prettier": "^2.8.8",
         "prettier-plugin-sql-cst": "^0.5.0",
         "supabase": "^1.45.2",
         "ts-jest": "^27.0.7",
@@ -30919,9 +30919,9 @@
       }
     },
     "node_modules/prettier": {
-      "version": "2.8.7",
-      "resolved": "https://registry.npmjs.org/prettier/-/prettier-2.8.7.tgz",
-      "integrity": "sha512-yPngTo3aXUUmyuTjeTUT75txrf+aMh9FiD7q9ZE/i6r0bPb22g4FsE6Y338PQX1bmfy08i9QQCB7/rcUAVntfw==",
+      "version": "2.8.8",
+      "resolved": "https://registry.npmjs.org/prettier/-/prettier-2.8.8.tgz",
+      "integrity": "sha512-tdN8qQGvNjw4CHbY+XXk0JgCXn9QiF21a55rBe5LJAU+kDyC4WQn4+awm2Xfk2lQMk5fKup9XgzTZtGkjBdP9Q==",
       "dev": true,
       "bin": {
         "prettier": "bin-prettier.js"
@@ -63194,9 +63194,9 @@
       "integrity": "sha512-vkcDPrRZo1QZLbn5RLGPpg/WmIQ65qoWWhcGKf/b5eplkkarX0m9z8ppCat4mlOqUsWpyNuYgO3VRyrYHSzX5g=="
     },
     "prettier": {
-      "version": "2.8.7",
-      "resolved": "https://registry.npmjs.org/prettier/-/prettier-2.8.7.tgz",
-      "integrity": "sha512-yPngTo3aXUUmyuTjeTUT75txrf+aMh9FiD7q9ZE/i6r0bPb22g4FsE6Y338PQX1bmfy08i9QQCB7/rcUAVntfw==",
+      "version": "2.8.8",
+      "resolved": "https://registry.npmjs.org/prettier/-/prettier-2.8.8.tgz",
+      "integrity": "sha512-tdN8qQGvNjw4CHbY+XXk0JgCXn9QiF21a55rBe5LJAU+kDyC4WQn4+awm2Xfk2lQMk5fKup9XgzTZtGkjBdP9Q==",
       "dev": true
     },
     "prettier-plugin-sql": {
@@ -70213,4 +70213,4 @@
       "integrity": "sha512-Bq0B+ixT/DMyG8kgX2xWcI5jUvCwqrMxSFam7m0lAf78nf04hv6lNCsyLYdyYTrCVMqNDY/206K7eExYCeSyUQ=="
     }
   }
-}
+}
\ No newline at end of file
diff --git a/package.json b/package.json
index a33c008ccc8..5f5696c9a20 100644
--- a/package.json
+++ b/package.json
@@ -21,7 +21,7 @@
     "dev:docs": "turbo run dev --filter=docs --parallel",
     "dev:www": "turbo run dev --filter=www --parallel",
     "lint": "turbo run lint",
-    "format": "prettier --write \"apps/**/*.{js,jsx,ts,tsx,css,md,json}\"",
+    "format": "prettier --write \"apps/**/*.{js,jsx,ts,tsx,css,md,mdx,json}\"",
     "docker:dev": "cd docker && docker compose -f docker-compose.yml -f ./dev/docker-compose.dev.yml up --renew-anon-volumes",
     "docker:up": "cd docker && docker compose up",
     "docker:down": "cd docker && docker compose -f docker-compose.yml -f ./dev/docker-compose.dev.yml down --remove-orphans",
@@ -38,7 +38,7 @@
     "eslint": "^7.32.0",
     "eslint-config-custom": "*",
     "json-stringify-safe": "^5.0.1",
-    "prettier": "^2.8.4",
+    "prettier": "^2.8.8",
     "prettier-plugin-sql-cst": "^0.5.0",
     "supabase": "^1.45.2",
     "ts-jest": "^27.0.7",
diff --git a/packages/common/constants/client-libraries.ts b/packages/common/constants/client-libraries.ts
index fce066fc1f8..6749e1100eb 100644
--- a/packages/common/constants/client-libraries.ts
+++ b/packages/common/constants/client-libraries.ts
@@ -133,11 +133,23 @@ export const CLIENT_LIBRARIES = [
     libraries: [
       {
         name: 'postgrest-kt',
-        url: 'https://github.com/supabase-community/postgrest-kt',
+        url: 'https://github.com/supabase-community/supabase-kt/tree/master/Postgrest',
       },
       {
         name: 'gotrue-kt',
-        url: 'https://github.com/supabase-community/gotrue-kt',
+        url: 'https://github.com/supabase-community/supabase-kt/tree/master/GoTrue',
+      },
+      {
+        name: 'storage-kt',
+        url: 'https://github.com/supabase-community/supabase-kt/tree/master/Storage',
+      },
+      {
+        name: 'realtime-kt',
+        url: 'https://github.com/supabase-community/supabase-kt/tree/master/Realtime',
+      },
+      {
+        name: 'functions-kt',
+        url: 'https://github.com/supabase-community/supabase-kt/tree/master/Functions',
       },
     ],
   },
diff --git a/packages/ui/index.tsx b/packages/ui/index.tsx
index d27ca7d1e21..896df067066 100644
--- a/packages/ui/index.tsx
+++ b/packages/ui/index.tsx
@@ -40,6 +40,7 @@ export * from './src/components/SidePanel'
 export * from './src/components/Dropdown'
 export * from './src/components/ContextMenu'
 export * from './src/components/Popover'
+export * from './src/components/ExpandableVideo'
 
 // UTILITIES
 
diff --git a/packages/ui/src/components/CodeBlock/CodeBlock.tsx b/packages/ui/src/components/CodeBlock/CodeBlock.tsx
index 61887e80acc..6c735470069 100644
--- a/packages/ui/src/components/CodeBlock/CodeBlock.tsx
+++ b/packages/ui/src/components/CodeBlock/CodeBlock.tsx
@@ -13,13 +13,14 @@ import sql from 'react-syntax-highlighter/dist/cjs/languages/hljs/sql'
 import bash from 'react-syntax-highlighter/dist/cjs/languages/hljs/bash'
 import dart from 'react-syntax-highlighter/dist/cjs/languages/hljs/dart'
 import json from 'react-syntax-highlighter/dist/cjs/languages/hljs/json'
+import kotlin from 'react-syntax-highlighter/dist/cjs/languages/hljs/kotlin'
 
 import { useState } from 'react'
 import { useTheme } from 'common/Providers'
 
 export interface CodeBlockProps {
   title?: string
-  language: 'js' | 'jsx' | 'sql' | 'py' | 'bash' | 'ts' | 'dart' | 'json' | 'csharp'
+  language: 'js' | 'jsx' | 'sql' | 'py' | 'bash' | 'ts' | 'dart' | 'json' | 'csharp' | 'kotlin'
   linesToHighlight?: number[]
   hideCopy?: boolean
   hideLineNumbers?: boolean
@@ -74,6 +75,7 @@ export const CodeBlock = ({
   SyntaxHighlighter.registerLanguage('dart', dart)
   SyntaxHighlighter.registerLanguage('csharp', csharp)
   SyntaxHighlighter.registerLanguage('json', json)
+  SyntaxHighlighter.registerLanguage('kotlin', kotlin)
 
   const large = false
   // don't show line numbers if bash == lang
diff --git a/packages/ui/src/components/ExpandableVideo/ExpandableVideo.tsx b/packages/ui/src/components/ExpandableVideo/ExpandableVideo.tsx
new file mode 100644
index 00000000000..fb799acfe96
--- /dev/null
+++ b/packages/ui/src/components/ExpandableVideo/ExpandableVideo.tsx
@@ -0,0 +1,98 @@
+import React from 'react'
+import Image from 'next/image'
+import { IconPlay, Modal } from 'ui'
+import { useBreakpoint } from 'common'
+
+interface ExpandableVideoProps {
+  imgUrl: string
+  videoId: string
+  imgAltText?: string
+}
+
+function ExpandableVideo({ imgUrl, videoId, imgAltText }: ExpandableVideoProps) {
+  const [expandVideo, setExpandVideo] = React.useState(false)
+  const isMobile = useBreakpoint(768)
+
+  React.useEffect(() => {
+    function onKeyDown(e: KeyboardEvent) {
+      switch (e.key) {
+        case 'Escape':
+          return setExpandVideo(false)
+        default:
+          return
+      }
+    }
+
+    window.addEventListener('keydown', onKeyDown)
+    return () => {
+      window.removeEventListener('keydown', onKeyDown)
+    }
+  }, [])
+
+  React.useEffect(() => {
+    if (isMobile) setExpandVideo(false)
+  }, [isMobile])
+
+  return (
+    <>
+      <Modal
+        visible={expandVideo}
+        hideFooter
+        className={[
+          '!bg-[#f8f9fa]/95 dark:!bg-[#1c1c1c]/80',
+          '!border-[#e6e8eb]/90 dark:!border-[#282828]/90',
+          'transition ease-out',
+          'mx-auto backdrop-blur-md',
+        ].join(' ')}
+        onInteractOutside={(e) => {
+          // Only hide menu when clicking outside, not focusing outside
+          // Prevents Firefox dropdown issue that immediately closes menu after opening
+          if (e.type === 'dismissableLayer.pointerDownOutside') {
+            setExpandVideo(!expandVideo)
+          }
+        }}
+        size="xxlarge"
+      >
+        <div className="w-full flex items-center justify-center">
+          <div className="relative w-full">
+            <button
+              onClick={() => setExpandVideo(false)}
+              className="text-scale-1100 hover:text-scale-1200 absolute -top-8 right-0"
+            >
+              <p className="text-xs">Close</p>
+            </button>
+            <div className="video-container overflow-hidden rounded-lg">
+              <iframe
+                src={`https://www.youtube-nocookie.com/embed/${videoId}`}
+                allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+                allowFullScreen
+              />
+            </div>
+          </div>
+        </div>
+      </Modal>
+      <div
+        className="video-container overflow-hidden rounded hover:cursor-pointer"
+        onClick={() => setExpandVideo(true)}
+      >
+        <div
+          className={`absolute inset-0 z-10 text-whiteA-1200 flex flex-col items-center justify-center gap-3 backdrop-blur-sm
+                      before:content[''] before:-z-10 before:absolute before:inset-0 before:bg-black before:opacity-30 hover:before:opacity-50 before:transition-opacity
+                    `}
+        >
+          <IconPlay strokeWidth={2} size="small" />
+          <p className="text-sm">Watch video guide</p>
+        </div>
+        <Image
+          src={imgUrl}
+          alt={imgAltText ?? 'Video guide preview'}
+          layout="fill"
+          objectFit="cover"
+          className="absolute inset-0"
+        />
+      </div>
+    </>
+  )
+}
+
+export default ExpandableVideo
diff --git a/packages/ui/src/components/ExpandableVideo/index.tsx b/packages/ui/src/components/ExpandableVideo/index.tsx
new file mode 100644
index 00000000000..979662ad54b
--- /dev/null
+++ b/packages/ui/src/components/ExpandableVideo/index.tsx
@@ -0,0 +1 @@
+export * from './ExpandableVideo'
diff --git a/spec/common-client-libs-sections.json b/spec/common-client-libs-sections.json
index 4b362a55f21..d90b37c39bf 100644
--- a/spec/common-client-libs-sections.json
+++ b/spec/common-client-libs-sections.json
@@ -34,7 +34,8 @@
       "reference_dart_v1",
       "reference_python_v2",
       "reference_csharp_v0",
-      "reference_swift_v0"
+      "reference_swift_v0",
+      "reference_kotlin_v0"
     ]
   },
   {
@@ -47,7 +48,8 @@
       "reference_dart_v1",
       "reference_python_v2",
       "reference_csharp_v0",
-      "reference_swift_v0"
+      "reference_swift_v0",
+      "reference_kotlin_v0"
     ]
   },
   {
@@ -554,20 +556,12 @@
         "type": "function"
       },
       {
-        "id": "reset-password-for-email",
-        "title": "Send a password reset request",
-        "slug": "auth-resetpasswordforemail",
+        "id": "exchange-code-for-session",
+        "title": "Exchange an auth code for a session",
+        "slug": "auth-exchangecodeforsession",
         "product": "auth",
         "type": "function"
       },
-      {
-          "id": "exchange-code-for-session",
-          "title": "Exchange an auth code for a session",
-          "slug": "auth-exchangecodeforsession",
-          "product": "auth",
-          "type": "function"
-
-      },
       {
         "id": "mfa-enroll",
         "title": "Enroll a factor",
@@ -912,7 +906,8 @@
       "reference_dart_v0",
       "reference_python_v2",
       "reference_csharp_v0",
-      "reference_swift_v0"
+      "reference_swift_v0",
+      "reference_kotlin_v0"
     ],
     "items": [
       {
diff --git a/spec/supabase_kt_v0.yml b/spec/supabase_kt_v0.yml
new file mode 100644
index 00000000000..43b79a6458b
--- /dev/null
+++ b/spec/supabase_kt_v0.yml
@@ -0,0 +1,3566 @@
+openref: 0.1
+
+info:
+  id: reference/supabase-kotlin
+  title: Supabase Kotlin Client
+  description: |
+
+    Supabase Kotlin.
+
+  specUrl: https://github.com/supabase/supabase/edit/master/spec/supabase_kt_v0.yml
+  slugPrefix: '/'
+  libraries:
+    - name: 'Kotlin'
+      id: 'kt'
+      version: '0.0.1'
+
+functions:
+  - id: initializing
+    title: 'Initializing'
+    description: |
+      Independently of which Supabase module you are using, you will need to initialize the main client first and install the module.
+      
+      To create a new client, you can use the `createSupabaseClient` function.
+      
+      When installing a module, you can pass a block to configure it.
+
+    examples:
+      - id: initialize-client
+        name: Initialize Client
+        code: |
+          ```kotlin
+          val client = createSupabaseClient(
+              supabaseUrl = "https://xyzcompany.supabase.co", 
+              supabaseKey = "public-anon-key"
+          ) {
+              install(GoTrue)
+              install(Postgrest)
+              //install other modules
+          }
+          ```
+      - id: configure-gotrue
+        name: Configure GoTrue module
+        code: |
+          ```kotlin
+          val client = createSupabaseClient(
+              supabaseUrl = "https://xyzcompany.supabase.co", 
+              supabaseKey = "public-anon-key"
+          ) {
+              install(GoTrue) {
+                  alwaysAutoRefresh = false // default: true
+                  autoLoadFromStorage = false // default: true
+                  //and more...
+              }
+          }
+          ```
+        description: |
+          **Common:**
+          
+          `alwaysAutoRefresh` - whether the GoTrue plugin should always auto refresh expired sessions automatically. Default: `true`
+          
+          `autoLoadFromStorage` - whether the GoTrue plugin should automatically load the session from the session manager. Default: `true`
+          
+          `flowType` - Which authentication flow to use. Currently available: FlowType.PKCE and FlowType.IMPLICIT. Default: `FlowType.IMPLICIT`
+          
+          `codeVerifierCache` - Interface for saving and loading codes for the PKCE authentication flow. Default: `SettingsCodeVerifierCache`
+          
+          `customUrl` - Custom url for the GoTrue API. Can be safely ignored when using Supabase. Default: `null`
+          
+          `jwtToken` - Plugin specific JWT Token. Can be ignored when using the GoTrue plugin. Default: `null`
+          
+          `retryDelay` - Duration after which the GoTrue plugin should retry a failed session refresh. Default: `10.seconds`
+          
+          `sessionManager` - Interface for saving and loading the user session. Default: `SettingsSessionManager`
+          
+          **Android & IOS:**
+          
+          `scheme` - The scheme for the redirect url, when using deep linking. Default: `supabase`
+          
+          `host` - The host for the redirect url, when using deep linking. Default: `login`
+          
+          **Android:** 
+          
+          `enableLifecycleCallbacks` - Whether to stop auto-refresh on focus loss, and resume it on focus again. Default: `true`
+          
+          **Desktop:**
+          
+          `httpPort`: The port the web server is running on, when logging in with OAuth. Default: `0` (random port).
+          
+          `timeout`: The timeout for the web server, when logging in with OAuth. Default: `1.minutes`.
+          
+          `htmlTitle`: The title of the redirect page, when logging in with OAuth. Default: `"Supabase Auth"`.
+          
+          `htmlText`: The text of the redirect page, when logging in with OAuth. Default: `"Logged in. You may continue in your app."`.
+          
+          `htmlIconUrl`: The icon of the redirect page, when logging in with OAuth. Default: `"https://supabase.com/brand-assets/supabase-logo-icon.png"`.
+      - id: configure-postgrest
+        name: Configure PostgREST module
+        code: |
+          ```kotlin
+          val client = createSupabaseClient(
+              supabaseUrl = "https://xyzcompany.supabase.co", 
+              supabaseKey = "public-anon-key"
+          ) {
+              install(Postgrest) {
+                  defaultSchema = "schema" // default: "public"
+                  propertyConversionMethod = PropertyConversionMethod.SERIAL_NAME // default: PropertyConversionMethod.CAMEL_CASE_TO_SNAKE_CASE
+              }
+          }
+          ```
+        description: |
+          `propertyConversionMethod` - The method to use to convert the property names to the column names when applying filters & using the update method. Default: `PropertyConversionMethod.CAMEL_CASE_TO_SNAKE_CASE`
+          
+          `defaultSchema` - The default schema to use for database requests. Default: `public`
+          
+          `customUrl` - Custom url for the PostgREST API. Can be safely ignored when using Supabase. Default: `null`
+          
+          `jwtToken` - Plugin specific JWT Token. Can be ignored when using the GoTrue plugin. Default: `null`
+      - id: configure-storage
+        name: Configure Storage module
+        code: |
+          ```kotlin
+          val client = createSupabaseClient(
+              supabaseUrl = "https://xyzcompany.supabase.co", 
+              supabaseKey = "public-anon-key"
+          ) {
+              install(Storage) {
+                  transferTimeout = 90.seconds // Default: 120 seconds
+              }
+          }
+          ```
+        description: |
+          `transferTimeout` - the timeout for uploading and downloading files. Default: `120.seconds`
+          
+          `resumable.cache` - Interface for storing resumable upload urls. Default: `ResumableCache.Disk`
+          
+          `resumable.defaultChunkSize` - The default chunk size for resumable uploads. Supabase currently only supports a chunk size of 6MB, so be careful when changing this value. Default: `6MB`
+          
+          `resumable.retryTimeout` - the timeout for retrying resumable uploads when uploading a chunk fails. Default: `5.seconds`
+          
+          `resumable.onlyUpdateStateAfterChunk` - whether the upload state should only be updated after a chunk was uploaded successfully or also when the chunk is currently being uploaded. Default: `false`
+          
+          `customUrl` - Custom url for the Storage API. Can be safely ignored when using Supabase. Default: `null`
+          
+          `jwtToken` - Plugin specific JWT Token. Can be ignored when using the GoTrue plugin. Default: `null`
+      - id: configure-realtime
+        name: Configure Realtime module
+        code: |
+          ```kotlin
+          val client = createSupabaseClient(
+              supabaseUrl = "https://xyzcompany.supabase.co", 
+              supabaseKey = "public-anon-key"
+          ) {
+              install(Realtime) {
+                  reconnectDelay = 5.seconds // Default: 7 seconds
+              }
+          }
+          ```
+        description: |
+          `reconnectDelay` - The delay between reconnect attempts. Default: `7.seconds`
+          
+          `heartbeatInterval` - The interval between heartbeat messages. Default: `15.seconds`
+          
+          `disconnectOnSessionLoss` - Whether to disconnect from the websocket when the session is lost. Default: `true`
+          
+          `secure` - Whether to use wss or ws. Defaults to [SupabaseClient.useHTTPS] when null
+          
+          `websocketConfig` - Custom Ktor websocket config
+          
+          `customUrl` - Custom url for the Realtime websocket. Can be safely ignored when using Supabase. Default: `null`
+          
+          `jwtToken` - Plugin specific JWT Token. Can be ignored when using the GoTrue plugin. Default: `null`
+      - id: configure-functions
+        name: Configure Functions plugin
+        code: |
+          ```kotlin
+          val client = createSupabaseClient(
+              supabaseUrl = "https://xyzcompany.supabase.co", 
+              supabaseKey = "public-anon-key"
+          ) {
+              install(Functions) {
+                  //no custom settings
+              }
+          }
+          ```
+        description: |
+          `customUrl` - Custom url for the Functions API. Can be safely ignored when using Supabase. Default: `null`
+          
+          `jwtToken` - Plugin specific JWT Token. Can be ignored when using the GoTrue plugin. Default: `null`   
+      - id: configure-graphql
+        name: Configure GraphQL plugin
+        code: |
+          ```kotlin
+          val client = createSupabaseClient(
+              supabaseUrl = "https://xyzcompany.supabase.co", 
+              supabaseKey = "public-anon-key"
+          ) {
+              install(GraphQL) {
+                  apolloConfiguration {
+                    //custom configuration
+                  }
+              }
+          }
+          ```
+        description: |
+          `apolloConfiguration` - Custom configuration for the ApolloClient
+          
+          `customUrl` - Custom url for the GraphQL API. Can be safely ignored when using Supabase. Default: `null`
+          
+          `jwtToken` - Plugin specific JWT Token. Can be ignored when using the GoTrue plugin. Default: `null`
+          
+          **You can access the created ApolloClient via `client.graphql.apolloClient`, which automatically adds the required headers depending on your session.**
+
+  - id: select
+    title: 'Fetch data: select()'
+    notes: |
+      Perform a SELECT query on the table or view.
+      - When calling a `decode` method, you have to provide a [serializable class](/docs/reference/kotlin/installing#add-kotlinx-serialization-required-for-postgrest-and-realtime-serialization) as the type parameter.
+      - You can provide a `Columns` object to select specific columns.
+      - You can provide a [filter](/docs/reference/kotlin/using-filters) block to filter the results
+    examples:
+      - id: getting-your-data
+        name: Getting your data
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val city = client.postgrest["cities"].select().decodeSingle<City>()
+          ```
+      - id: selecting-specific-columns
+        name: Selecting specific columns
+        description: You can select specific fields from your tables.
+        code: |
+          ```kotlin
+          val city = client.postgrest["cities"].select(columns = Columns.list("id, name")).decodeSingle<City>()
+          ```
+      - id: query-foreign-tables
+        name: Query foreign tables
+        description: If your database has foreign key relationships, you can query related tables too.
+        code: |
+          ```kotlin
+          val country = client.postgrest["countries"]
+                      .select(
+                          columns = Columns.raw(
+                                          """
+                                          id,
+                                          name,
+                                          cities (
+                                              id,
+                                              name
+                                          )
+                                          """)
+                      )
+                      .decodeSingle<Country>()
+          ```
+        note: |
+          What about join tables
+          If you're in a situation where your tables are **NOT** directly related, but instead are joined by a _join table_,
+          you can still use the `select()` method to query the related data. The PostgREST engine detects the relationship automatically.
+          For more details, [follow the link](https://postgrest.org/en/latest/api.html#embedding-through-join-tables).
+      - id: query-the-same-foreign-table-multiple-times
+        name: Query the same foreign table multiple times
+        description: |
+          Sometimes you will need to query the same foreign table twice.
+          In this case, you can use the name of the joined column to identify
+          which join you intend to use. For convenience, you can also give an
+          alias for each column. For example, if we had a shop of products,
+          and we wanted to get the supplier and the purchaser at the same time
+          (both in the users) table
+        code: |
+          ```kotlin
+          val message = client.postgrest["messages"]
+                      .select(columns = Columns.raw(
+                                        """            
+                                        content,
+                                        from: sender_id(name),
+                                        to: receiver_id(name)
+                                        """))
+                      .decodeSingle<Message>()
+          ```
+      - id: querying-with-count-option
+        name: Querying with count option
+        description: |
+          You can get the number of rows by using the count option.
+          Allowed values for count option are [Count.EXACT](https://postgrest.org/en/stable/api.html#exact-count), [Count.PLANNED](https://postgrest.org/en/stable/api.html#planned-count) and [Count.ESTIMATED](https://postgrest.org/en/stable/api.html#estimated-count).
+        code: |
+          ```kotlin
+          val count = client.postgrest["countries"]
+                      .select(head = true, count = Count.EXACT)
+                      .count()!!
+          ```
+      - id: querying-json-data
+        name: Querying JSON data
+        description: |
+          If you have data inside of a JSONB column, you can apply select
+          and query filters to the data values. Postgres offers a
+          [number of operators](https://www.postgresql.org/docs/current/functions-json.html)
+          for querying JSON data. Also see
+          [PostgREST docs](http://postgrest.org/en/v7.0.0/api.html#json-columns) for more details.
+        code: |
+          ```kotlin
+          val user = client.postgrest["users"]
+                      .select(columns = Columns.raw(
+                                      """
+                                      id, name
+                                      address->city
+                                      """)
+                      .decodeSingle<User>()
+          ```
+
+  - id: insert
+    title: 'Create data: insert()'
+    $ref: '@supabase/postgrest-js."lib/PostgrestQueryBuilder".PostgrestQueryBuilder.insert'
+    notes: |
+      - When calling an `insert` method, you have to provide a [serializable value](/docs/reference/kotlin/installing#add-kotlinx-serialization-required-for-postgrest-and-realtime-serialization).
+      - By default, every time you run `insert()`, the client library will make a `select` to return the full record.
+      This is convenient, but it can also cause problems if your policies are not configured to allow the `select` operation.
+      If you are using Row Level Security and you are encountering problems, try setting the `returning` param to `Returning.MINIMAL`.
+    examples:
+      - id: create-a-record
+        name: Create a record
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val city = City(name = "The Shire", countryId = 554)
+          client.postgrest["cities"].insert(city, returning = Returning.MINIMAL) //returning defaults to Returning.REPRESENTATION
+          ```
+      - id: bulk-create
+        name: Bulk create
+        description: |
+          When running a bulk create, the operation is handled in a single transaction. If any of the inserts fail, all other operations are
+          rolled back.
+        code: |
+          ```kotlin
+          val theShire = City(name = "The Shire", countryId = 554)
+          val rohan = City(name = "Rohan", countryId = 554)
+          client.postgrest["cities"].insert(listOf(theShire, rohan), returning = Returning.MINIMAL) //returning defaults to Returning.REPRESENTATION
+          ```
+      - id: fetch-inserted-data
+        name: Fetch inserted record
+        code: |
+          ```kotlin
+          val theShire = City(name = "The Shire", countryId = 554)
+          val rohan = City(name = "Rohan", countryId = 554)
+          val result = client.postgrest["cities"].insert(listOf(theShire, rohan)).decodeList<City>()
+          ```
+
+  - id: update
+    title: 'Modify data: update()'
+    notes: |
+      - `update()` should always be combined with a [filter](/docs/reference/kotlin/using-filters) block to avoid updating all records.
+      - When calling `insert` or `update`, you have to provide a [serializable value](/docs/reference/kotlin/installing#add-kotlinx-serialization-required-for-postgrest-and-realtime-serialization) in the function parameter.      
+    examples:
+      - id: updating-your-data
+        name: Updating your data
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.postgrest["countries"].update(
+              {
+                 Country::name setTo "Australia"
+                 //or
+                 set("name", "Australia")
+              }
+          ) {
+             Country::id eq 1
+             //or
+             eq("id", 1)
+          }
+          ```
+      - id: update-a-record-and-return-it
+        name: Update a record and return it
+        code: |
+          ```kotlin
+          val newCountry = client.postgrest["countries"].update(
+              {
+                 Country::name setTo "Australia"
+                 //or
+                 set("name", "Australia")
+              }
+          ) {
+             Country::id eq 1
+             //or
+             eq("id", 1)
+          }.decodeSingle<Country>()
+          ```
+        data:
+          sql: |
+            ```sql
+            create table
+              countries (id int8 primary key, name text);
+
+            insert into
+              countries (id, name)
+            values
+              (1, 'Taiwan');
+            ```
+        response: |
+          ```json
+          {
+            "data": [
+              {
+                "id": 1,
+                "name": "Australia"
+              }
+            ],
+            "status": 200,
+            "statusText": "OK"
+          }
+          ```
+        hideCodeBlock: true
+      - id: updating-json-data
+        name: Updating JSON data
+        description: |
+          Postgres offers a
+          [number of operators](https://www.postgresql.org/docs/current/functions-json.html)
+          for working with JSON data. Right now it is only possible to update an entire JSON document,
+          but we are [working on ideas](https://github.com/PostgREST/postgrest/issues/465) for updating individual keys.
+        code: |
+          ```kotlin
+          val address = Address(street = "Melrose Place", postcode = 90210)
+          client.postgrest["users"].update(
+              {
+                 User::address setTo address
+              }
+          ) {
+             User::id eq 1
+             //or
+             eq("address->postcode", 90210)
+          }.decodeSingle<Country>()
+          ```
+
+  - id: upsert
+    title: 'Upsert data: upsert()'
+    $ref: '@supabase/postgrest-js."lib/PostgrestQueryBuilder".PostgrestQueryBuilder.upsert'
+    notes: |
+      - Primary keys should be included in the data payload in order for an update to work correctly.
+      - Primary keys  must be natural, not surrogate. There are however, [workarounds](https://github.com/PostgREST/postgrest/issues/1118) for surrogate primary keys.
+      - If you need to insert new data and update existing data at the same time, use [Postgres triggers](https://github.com/supabase/postgrest-js/issues/173#issuecomment-825124550).
+      - When calling `insert` or `update`, you have to provide a [serializable value](/docs/reference/kotlin/installing#add-kotlinx-serialization-required-for-postgrest-and-realtime-serialization) in the function parameter.      
+    examples:
+      - id: upsert-your-data
+        name: Upsert your data
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val toUpsert = Message(id = 3, message = "foo", username = "supabot")
+          client.postgrest["messages"].insert(toUpsert, upsert = true)
+          ```
+      - id: upserting-into-tables-with-constraints
+        name: Upserting into tables with constraints
+        description: |
+          Running the following will cause Supabase to upsert data into the `users` table.
+          If the username 'supabot' already exists, the `onConflict` argument tells Supabase to overwrite that row
+          based on the column passed into `onConflict`.
+        isSpotlight: true
+        code: |
+          ```kotlin
+          let toUpsert = User(username = "supabot")
+          client.postgrest["users"].insert(toUpsert, upsert = true, onConflict = "username")                          
+          ```
+      - id: upsert-return-row-count
+        name: Return the exact number of rows
+        isSpotlight: true
+        code: |
+          ```kotlin
+          let toUpsert = User(username = "supabot")
+          val count = client.postgrest["users"].insert(toUpsert, upsert = true, onConflict = "username", count = Count.EXACT).count()   
+          ```
+
+  - id: delete
+    title: 'Delete data: delete()'
+    $ref: '@supabase/postgrest-js."lib/PostgrestQueryBuilder".PostgrestQueryBuilder.delete'
+    notes: |
+      - `delete()` should always be combined with a [filter](/docs/reference/kotlin/using-filters) block to target the item(s) you wish to delete.
+      - If you use `delete()` with filters and you have
+        [RLS](/docs/learn/auth-deep-dive/auth-row-level-security) enabled, only
+        rows visible through `SELECT` policies are deleted. Note that by default
+        no rows are visible, so you need at least one `SELECT`/`ALL` policy that
+        makes the rows visible.
+    examples:
+      - id: delete-records
+        name: Delete records
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.postgrest["cities"].delete {
+             City::id eq 666
+             //or
+             eq("id", 666)
+          }      
+          ```
+      - id: fetch-delete-records
+        name: Fetch deleted records
+        code: |
+          ```kotlin
+          val deletedCity = client.postgrest["cities"].delete {
+             City::id eq 666
+             //or
+             eq("id", 666)
+          }.decodeSingle<City>()   
+          ```
+  - id: rpc
+    title: 'Stored Procedures: rpc()'
+    description: |
+      You can call stored procedures as a "Remote Procedure Call".
+
+      That's a fancy way of saying that you can put some logic into your database then call it from anywhere.
+      It's especially useful when the logic rarely changes - like password resets and updates.
+      
+      - When calling `rpc` with parameters, you have to provide a [serializable value](/docs/reference/kotlin/installing#add-kotlinx-serialization-required-for-postgrest-and-realtime-serialization) in the function parameter.      
+    examples:
+      - id: call-a-stored-procedure
+        name: Call a stored procedure
+        isSpotlight: true
+        description: This is an example invoking a stored procedure.
+        code: |
+          ```kotlin
+          client.postgrest.rpc("hello_world")
+          ```
+      - id: with-parameters
+        name: With Parameters
+        code: |
+          ```kotlin
+          val rpcParams = City(name "The Shire")
+          client.postgrest.rpc("echo_city", rpcParams)
+          ```
+  - id: using-filters
+    title: Using Filters
+    description: |
+      Filters allow you to only return rows that match certain conditions.
+
+      Filters can be used on `select()`, `update()`, and `delete()` queries.
+      
+      You can use two different types for applying filters:
+      ```kotlin
+      eq("country_id", 1)
+      ```
+      And using a class property:
+      ```kotlin
+      City::countryId eq 1
+      ```
+      
+      As you can see on the property syntax: 
+      the name of the `countryId` gets converted to `country_id`. 
+      
+      By default, this is done by converting camel case to snake case, but you can customize this by changing the `PropertyConversionMethod` in the Postgrest Config
+
+      If a database function returns a table response, you can also apply filters.
+    examples:
+      - id: applying-filters
+        name: Applying a filter block
+        description: |
+          Filters can be applied on any of these functions: `select()`, `update()`, `upsert()`,
+          `delete()`, and `rpc()`
+        code: |
+          ```kotlin
+          client.postgrest["cities"].select(columns = Columns.list("name, country_id")) {
+              City::name eq "The Shire"
+              //or
+              eq("name", "The Shire")
+          }      
+          ```
+      - id: multiple-filters
+        name: Multiple filters on one column
+        description: |
+          Filters can be applied on any of these functions: `select()`, `update()`, `upsert()`,
+          `delete()`, and `rpc()`
+        code: |
+          ```kotlin
+          client.postgrest["cities"].select(columns = Columns.list("name, country_id")) {
+              and { //when both are true
+                 City::population gt 40000
+                 City::population lt 700000
+              }
+              or { //when either one of the filters are true
+                 City::name eq "London"
+                 City::name eq "Berlin"
+              }
+          }  
+          ```
+      - id: filter-by-value-within-json-column
+        name: Filter by values within a JSON column
+        description: |
+          Filters can be built up one step at a time and then executed. For example:
+        data:
+          sql: |
+            ```sql
+            create table
+              users (
+                id int8 primary key,
+                name text,
+                address jsonb
+              );
+
+            insert into
+              users (id, name, address)
+            values
+              (1, 'Michael', '{ "postcode": 90210 }'),
+              (2, 'Jane', null);
+            ```
+        response: |
+          ```json
+          {
+            "data": [
+              {
+                "id": 1,
+                "name": "Michael",
+                "address": {
+                  "postcode": 90210
+                }
+              }
+            ],
+            "status": 200,
+            "statusText": "OK"
+          }
+          ```
+        code: |
+          ```kotlin
+          client.postgrest["users"].select {
+             eq("address->postcode", 90210)
+          }      
+          ```
+      - id: filter-foreign-tables
+        name: Filter Foreign Tables
+        code: |
+          ```kotlin
+          client.postgrest["countries"].select(
+                columns = Columns.raw("""
+                                      name,
+                                      cities!inner (
+                                        name
+                                      )  
+                                      """)
+          ) {
+              eq("cities.name", "Bali")
+          }      
+          ```
+        data:
+          sql: |
+            ```sql
+            create table
+              countries (id int8 primary key, name text);
+            create table
+              cities (
+                id int8 primary key,
+                country_id int8 not null references countries,
+                name text
+              );
+
+            insert into
+              countries (id, name)
+            values
+              (1, 'Germany'),
+              (2, 'Indonesia');
+            insert into
+              cities (id, country_id, name)
+            values
+              (1, 2, 'Bali'),
+              (2, 1, 'Munich');
+            ```
+          response: |
+            ```json
+            {
+              "data": [
+                {
+                  "name": "Indonesia",
+                  "cities": [
+                    {
+                      "name": "Bali"
+                    }
+                  ]
+                }
+              ],
+              "status": 200,
+              "statusText": "OK"
+            }
+            ```
+  - id: or
+    title: or()
+    description: |
+      Finds all rows satisfying at least one of the filters.
+    notes: |
+    examples:
+      - id: with-select
+        name: With `select()`
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.postgrest["countries"].select(columns = Columns.list("name")) {
+              or {
+                  Country::id eq 2
+                  Country::name eq "Algeria"
+                  //or
+                  eq("id", 2)
+                  eq("name", "Algeria")
+              }
+          }      
+          ```
+      - id: use-or-with-and
+        name: Use `or` with `and`
+        code: |
+          ```kotlin
+          client.postgrest["countries"].select(columns = Columns.list("name")) {
+              or {
+                  Country::id gt 3
+                  and {
+                     Country::id eq 1
+                     Country::name eq "Afghanistan"
+                  }
+              }
+          }      
+          ```
+
+  - id: not
+    title: filterNot()
+    description: |
+      Finds all rows that don't satisfy the filter.
+    notes: |
+      - `.filterNot()` expects you to use the raw [PostgREST syntax](https://postgrest.org/en/stable/api.html#horizontal-filtering-rows) for the filter names and values.
+    examples:
+      - id: with-select
+        name: With `select()`
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.postgrest["countries"].select {
+              filterNot("name", FilterOperation.IS, "")
+          }   
+          ```
+
+  - id: eq
+    title: eq()
+    description: |
+      Finds all rows whose value on the stated `column` exactly matches the specified `value`.
+    examples:
+      - id: with-select
+        name: With `select()`
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.postgrest["cities"].select(columns = Columns.list("name", "country_id")) {
+              City::name eq "The Shire"
+              //or
+              eq("name", "The Shire")
+          }      
+          ```
+      - id: with-update
+        name: With `update()`
+        code: |
+          ```kotlin
+          val toUpdate = City(name = "Mordor")
+          client.postgrest["cities"].update(toUpdate) {
+              City::name eq "San Francisco"
+              //or
+              eq("name", "San Francisco")
+          }                 
+          ```
+      - id: with-delete
+        name: With `delete()`
+        code: |
+          ```kotlin
+          client.postgrest["cities"].delete {
+              City::name eq "Mordor"
+              //or
+              eq("name", "Mordor")
+          }   
+          ```
+      - id: with-rpc
+        name: With `rpc()`
+        code: |
+          ```kotlin
+          client.postgrest.rpc("function") {
+              City::name eq "Mordor"
+              //or
+              eq("name", "Mordor")
+          }      
+          ```
+
+  - id: neq
+    title: neq()
+    description: |
+      Finds all rows whose value on the stated `column` doesn't match the specified `value`.
+    examples:
+      - id: with-select
+        name: With `select()`
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.postgrest["cities"].select(columns = Columns.list("name", "country_id")) {
+              City::name neq "The Shire"
+              //or
+              neq("name", "The Shire")
+          }      
+          ```
+      - id: with-update
+        name: With `update()`
+        code: |
+          ```kotlin
+          val toUpdate = City(name = "Mordor")
+          client.postgrest["cities"].update(toUpdate) {
+              City::name neq "The Shire"
+              //or
+              neq("name", "The Shire")
+          }
+          ```
+      - id: with-delete
+        name: With `delete()`
+        code: |
+          ```kotlin
+          client.postgrest["cities"].delete {
+              City::name neq "The Shire"
+              //or
+              neq("name", "The Shire")
+          }
+          ```
+      - id: with-rpc
+        name: With `rpc()`
+        code: |
+          ```kotlin
+          client.rpc("echo_all_cities") {
+              neq("address->postcode", 90210)
+          }      
+          ```
+
+  - id: gt
+    title: gt()
+    description: |
+      Finds all rows whose value on the stated `column` is greater than the specified `value`.
+    examples:
+      - id: with-select
+        name: With `select()`
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.postgrest["cities"].select(columns = Columns.list("name")) {
+             City::countryId gt 300
+             //or
+             gt("country_id", 300)
+          }
+          ```
+      - id: with-update
+        name: With `update()`
+        code: |
+          ```kotlin
+          val toUpdate = City(name = "Mordor")
+          client.postgrest["cities"].update(toUpdate) {
+             City::countryId gt 300
+             //or
+             gt("country_id", 300)
+          }
+          ```
+      - id: with-delete
+        name: With `delete()`
+        code: |
+          ```kotlin
+          client.postgrest["cities"].delete {
+             City::countryId gt 300
+             //or
+             gt("country_id", 300)
+          }
+          ```
+      - id: with-rpc
+        name: With `rpc()`
+        code: |
+          ```kotlin
+          client.postgrest.rpc("echo_all_cities") {
+             City::countryId gt 250
+             //or
+             gt("country_id", 300)
+          }      
+          ```
+
+  - id: gte
+    title: gte()
+    description: |
+      Finds all rows whose value on the stated `column` is greater than or equal to the specified `value`.
+    examples:
+      - id: with-select
+        name: With `select()`
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.postgrest["cities"].select(columns = Columns.list("name")) {
+             City::countryId gte 300
+             //or
+             gte("country_id", 300)
+          }
+          ```
+      - id: with-update
+        name: With `update()`
+        code: |
+          ```kotlin
+          val toUpdate = City(name = "Mordor")
+          client.postgrest["cities"].update(toUpdate) {
+             City::countryId gte 300
+             //or
+             gte("country_id", 300)
+          }
+          ```
+      - id: with-delete
+        name: With `delete()`
+        code: |
+          ```kotlin
+          client.postgrest["cities"].delete {
+             City::countryId gte 300
+             //or
+             gte("country_id", 300)
+          }
+          ```
+      - id: with-rpc
+        name: With `rpc()`
+        code: |
+          ```kotlin
+          client.postgrest.rpc("echo_all_cities") {
+             City::countryId gte 250
+             //or
+             gte("country_id", 300)
+          }      
+          ```
+
+  - id: lt
+    title: lt()
+    description: |
+      Finds all rows whose value on the stated `column` is less than the specified `value`.
+    examples:
+      - id: with-select
+        name: With `select()`
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.postgrest["cities"].select(columns = Columns.list("name")) {
+             City::countryId lt 300
+             //or
+             lt("country_id", 300)
+          }
+          ```
+      - id: with-update
+        name: With `update()`
+        code: |
+          ```kotlin
+          val toUpdate = City(name = "Mordor")
+          client.postgrest["cities"].update(toUpdate) {
+             City::countryId lt 300
+             //or
+             lt("country_id", 300)
+          }
+          ```
+      - id: with-delete
+        name: With `delete()`
+        code: |
+          ```kotlin
+          client.postgrest["cities"].delete {
+             City::countryId lt 300
+             //or
+             lt("country_id", 300)
+          }
+          ```
+      - id: with-rpc
+        name: With `rpc()`
+        code: |
+          ```kotlin
+          client.postgrest.rpc("echo_all_cities") {
+             City::countryId lt 250
+             //or
+             lt("country_id", 300)
+          }      
+          ```
+
+  - id: lte
+    title: lte()
+    description: |
+      Finds all rows whose value on the stated `column` is less than or equal to the specified `value`.
+    examples:
+      - id: with-select
+        name: With `select()`
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.postgrest["cities"].select(columns = Columns.list("name")) {
+             City::countryId lte 300
+             //or
+             lte("country_id", 300)
+          }
+          ```
+      - id: with-update
+        name: With `update()`
+        code: |
+          ```kotlin
+          val toUpdate = City(name = "Mordor")
+          client.postgrest["cities"].update(toUpdate) {
+             City::countryId lte 300
+             //or
+             lte("country_id", 300)
+          }
+          ```
+      - id: with-delete
+        name: With `delete()`
+        code: |
+          ```kotlin
+          client.postgrest["cities"].delete {
+             City::countryId lte 300
+             //or
+             lte("country_id", 300)
+          }
+          ```
+      - id: with-rpc
+        name: With `rpc()`
+        code: |
+          ```kotlin
+          client.postgrest.rpc("echo_all_cities") {
+             City::countryId lte 250
+             //or
+             lte("country_id", 300)
+          }      
+          ```
+
+  - id: like
+    title: like()
+    description: |
+      Finds all rows whose value in the stated `column` matches the supplied `pattern` (case sensitive).
+    examples:
+      - id: with-select
+        name: With `select()`
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.postgrest["cities"].select(columns = Columns.list("name")) {
+             City::name like "%la%"
+             //or
+             like("name", "%la%")
+          }      
+          ```
+      - id: with-update
+        name: With `update()`
+        code: |
+          ```kotlin
+          val toUpdate = City(name = "Mordor")
+          client.postgrest["cities"].update(toUpdate) {
+             City::name like "%la%"
+             //or
+             like("name", "%la%")
+          }      
+          ```
+      - id: with-delete
+        name: With `delete()`
+        code: |
+          ```kotlin
+          client.postgrest["cities"].delete {
+             City::name like "%la%"
+             //or
+             like("name", "%la%")
+          }      
+          ```
+      - id: with-rpc
+        name: With `rpc()`
+        code: |
+          ```kotlin
+          client.postgrest.rpc("echo_all_cities") {
+             City::name like "%la%"
+             //or
+             like("name", "%la%")
+          }     
+          ```
+
+  - id: ilike
+    title: ilike()
+    description: |
+      Finds all rows whose value in the stated `column` matches the supplied `pattern` (case insensitive).
+    examples:
+      - id: with-select
+        name: With `select()`
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.postgrest["cities"].select(columns = Columns.list("name")) {
+             City::name ilike "%la%"
+             //or
+             ilike("name", "%la%")
+          }      
+          ```
+      - id: with-update
+        name: With `update()`
+        code: |
+          ```kotlin
+          val toUpdate = City(name = "Mordor")
+          client.postgrest["cities"].update(toUpdate) {
+             City::name ilike "%la%"
+             //or
+             ilike("name", "%la%")
+          }      
+          ```
+      - id: with-delete
+        name: With `delete()`
+        code: |
+          ```kotlin
+          client.postgrest["cities"].delete {
+             City::name ilike "%la%"
+             //or
+             ilike("name", "%la%")
+          }      
+          ```
+      - id: with-rpc
+        name: With `rpc()`
+        code: |
+          ```kotlin
+          client.postgrest.rpc("echo_all_cities") {
+             City::name ilike "%la%"
+             //or
+             ilike("name", "%la%")
+          }     
+          ```
+
+  - id: is
+    title: is_()
+    description: |
+      A check for exact equality (null, true, false), finds all rows whose value on the stated `column` exactly match the specified `value`.
+
+      `is_` and `in_` filter methods are suffixed with `_` to avoid collisions with reserved keywords.
+    examples:
+      - id: with-select
+        name: With `select()`
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.postgrest["cities"].select(columns = Columns.list("name")) {
+             City::name isExact null
+             //or
+             exact("name", null)
+          }      
+          ```
+      - id: with-update
+        name: With `update()`
+        code: |
+          ```kotlin
+          val toUpdate = City(name = "Mordor")
+          client.postgrest["cities"].update(toUpdate) {
+             City::name isExact null
+             //or
+             exact("name", null)
+          }      
+          ```
+      - id: with-delete
+        name: With `delete()`
+        code: |
+          ```kotlin
+          client.postgrest["cities"].delete {
+              City::name isExact null
+             //or
+             exact("name", null)
+          }      
+          ```
+      - id: with-rpc
+        name: With `rpc()`
+        code: |
+          ```kotlin
+          client.postgrest.rpc("echo_all_cities") {
+             City::name isExact null
+             //or
+             exact("name", null)
+          }     
+          ```
+
+  - id: in
+    title: in_()
+    description: |
+      Finds all rows whose value on the stated `column` is found on the specified `values`.
+    examples:
+      - id: with-select
+        name: With `select()`
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.postgrest["cities"].select(columns = Columns.list("name")) {
+             City::name isIn listOf("Rio de Janeiro", "San Francisco")
+             //or
+             isIn("name", listOf("Rio de Janeiro", "San Francisco"))
+          }      
+          ```
+      - id: with-update
+        name: With `update()`
+        code: |
+          ```kotlin
+          val toUpdate = City(name = "Mordor")
+          client.postgrest["cities"].update(toUpdate) {
+             City::name isIn listOf("Rio de Janeiro", "San Francisco")
+             //or
+             isIn("name", listOf("Rio de Janeiro", "San Francisco"))
+          }      
+          ```
+      - id: with-delete
+        name: With `delete()`
+        code: |
+          ```kotlin
+          client.postgrest["cities"].delete {
+             City::name isIn listOf("Rio de Janeiro", "San Francisco")
+             //or
+             isIn("name", listOf("Rio de Janeiro", "San Francisco"))
+          }      
+          ```
+      - id: with-rpc
+        name: With `rpc()`
+        code: |
+          ```kotlin
+          client.postgrest.rpc("echo_all_cities") {
+             City::name isIn listOf("Rio de Janeiro", "San Francisco")
+             //or
+             isIn("name", listOf("Rio de Janeiro", "San Francisco"))
+          }     
+          ```
+
+  - id: contains
+    title: contains()
+    examples:
+      - id: with-select
+        name: With `select()`
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.postgrest["cities"].select(columns = Columns.list("name")) {
+             City::mainExports contains listOf("oil")
+             //or
+             contains("main_exports", listOf("oil"))
+          }      
+          ```
+      - id: with-update
+        name: With `update()`
+        code: |
+          ```kotlin
+          val toUpdate = City(name = "Mordor")
+          client.postgrest["cities"].update(toUpdate) {
+             City::mainExports contains listOf("oil")
+             //or
+             contains("main_exports", listOf("oil"))
+          }      
+          ```
+      - id: with-delete
+        name: With `delete()`
+        code: |
+          ```kotlin
+          client.postgrest["cities"].delete {
+             City::mainExports contains listOf("oil")
+             //or
+             contains("main_exports", listOf("oil"))
+          }      
+          ```
+      - id: with-rpc
+        name: With `rpc()`
+        code: |
+          ```kotlin
+          client.postgrest.rpc("echo_all_cities") {
+             City::mainExports contains listOf("oil")
+             //or
+             contains("main_exports", listOf("oil"))
+          }     
+          ```
+
+  - id: range-lt
+    title: rangeLt()
+    description: |
+      Only relevant for range columns. Match only rows where every element in column is less than any element in range.
+    examples:
+      - id: with-select
+        name: With `select()`
+        isSpotlight: true
+        code: |
+          ```kotlin
+            client.postgrest["reservations"].select {
+               Reservation::during rangeLt ("2000-01-02 08:30" to "2000-01-02 09:30")
+               //or
+               rangeLt("during", "2000-01-02 08:30" to "2000-01-02 09:30") 
+            }      
+          ```
+        data:
+          sql: |
+            ```sql
+            create table
+              reservations (
+                id int8 primary key,
+                room_name text,
+                during tsrange
+              );
+
+            insert into
+              reservations (id, room_name, during)
+            values
+              (1, 'Emerald', '[2000-01-01 13:00, 2000-01-01 15:00)'),
+              (2, 'Topaz', '[2000-01-02 09:00, 2000-01-02 10:00)');
+            ```
+        response: |
+          ```json
+          {
+            "data": [
+              {
+                "id": 1,
+                "room_name": "Emerald",
+                "during": "[\"2000-01-01 13:00:00\",\"2000-01-01 15:00:00\")"
+              }
+            ],
+            "status": 200,
+            "statusText": "OK"
+          }
+          ```
+        description: |
+          Postgres supports a number of [range
+          types](https://www.postgresql.org/docs/current/rangetypes.html). You
+          can filter on range columns using the string representation of range
+          values.
+        hideCodeBlock: true
+
+  - id: range-gt
+    title: rangeGt()
+    description: |
+      Only relevant for range columns. Match only rows where every element in column is greater than any element in range.
+
+    examples:
+      - id: with-select
+        name: With `select()`
+        isSpotlight: true
+        code: |
+          ```kotlin
+            client.postgrest["reservations"].select {
+               Reservation::during rangeGt ("2000-01-02 08:30" to "2000-01-02 09:30")
+               //or
+               rangeGt("during", "2000-01-02 08:30" to "2000-01-02 09:30") 
+            }      
+          ```
+        data:
+          sql: |
+            ```sql
+            create table
+              reservations (
+                id int8 primary key,
+                room_name text,
+                during tsrange
+              );
+
+            insert into
+              reservations (id, room_name, during)
+            values
+              (1, 'Emerald', '[2000-01-01 13:00, 2000-01-01 15:00)'),
+              (2, 'Topaz', '[2000-01-02 09:00, 2000-01-02 10:00)');
+            ```
+        response: |
+          ```json
+            {
+              "data": [
+                {
+                  "id": 2,
+                  "room_name": "Topaz",
+                  "during": "[\"2000-01-02 09:00:00\",\"2000-01-02 10:00:00\")"
+                }
+              ],
+              "status": 200,
+              "statusText": "OK"
+            }
+            ```
+        description: |
+          Postgres supports a number of [range
+          types](https://www.postgresql.org/docs/current/rangetypes.html). You
+          can filter on range columns using the string representation of range
+          values.
+        hideCodeBlock: true
+
+  - id: range-gte
+    title: rangeGte()
+    description: |
+      Only relevant for range columns. Match only rows where every element in column is either contained in range or greater than any element in range.
+    examples:
+      - id: with-select
+        name: With `select()`
+        isSpotlight: true
+        code: |
+          ```kotlin
+            client.postgrest["reservations"].select {
+               Reservation::during rangeGte ("2000-01-02 08:30" to "2000-01-02 09:30")
+               //or
+               rangeGte("during", "2000-01-02 08:30" to "2000-01-02 09:30") 
+            }      
+          ```
+        data:
+          sql: |
+            ```sql
+            create table
+              reservations (
+                id int8 primary key,
+                room_name text,
+                during tsrange
+              );
+
+            insert into
+              reservations (id, room_name, during)
+            values
+              (1, 'Emerald', '[2000-01-01 13:00, 2000-01-01 15:00)'),
+              (2, 'Topaz', '[2000-01-02 09:00, 2000-01-02 10:00)');
+            ```
+        response: |
+          ```json
+            {
+              "data": [
+                {
+                  "id": 2,
+                  "room_name": "Topaz",
+                  "during": "[\"2000-01-02 09:00:00\",\"2000-01-02 10:00:00\")"
+                }
+              ],
+              "status": 200,
+              "statusText": "OK"
+            }
+            ```
+        description: |
+          Postgres supports a number of [range
+          types](https://www.postgresql.org/docs/current/rangetypes.html). You
+          can filter on range columns using the string representation of range
+          values.
+        hideCodeBlock: true
+
+  - id: range-lte
+    title: rangeLte()
+    description: |
+      Only relevant for range columns. Match only rows where every element in column is either contained in range or less than any element in range.
+
+    $ref: '@supabase/postgrest-js.PostgrestFilterBuilder.rangeLte'
+    examples:
+      - id: with-select
+        name: With `select()`
+        isSpotlight: true
+        code: |
+          ```kotlin
+            client.postgrest["reservations"].select {
+               Reservation::during rangeLte ("2000-01-02 08:30" to "2000-01-02 09:30")
+               //or
+               rangeLte("during", "2000-01-02 08:30" to "2000-01-02 09:30") 
+            }      
+          ```
+        data:
+          sql: |
+            ```sql
+            create table
+              reservations (
+                id int8 primary key,
+                room_name text,
+                during tsrange
+              );
+
+            insert into
+              reservations (id, room_name, during)
+            values
+              (1, 'Emerald', '[2000-01-01 13:00, 2000-01-01 15:00)'),
+              (2, 'Topaz', '[2000-01-02 09:00, 2000-01-02 10:00)');
+            ```
+        response: |
+          ```json
+            {
+              "data": [
+                {
+                  "id": 1,
+                  "room_name": "Emerald",
+                  "during": "[\"2000-01-01 13:00:00\",\"2000-01-01 15:00:00\")"
+                }
+              ],
+              "status": 200,
+              "statusText": "OK"
+            }
+            ```
+        description: |
+          Postgres supports a number of [range
+          types](https://www.postgresql.org/docs/current/rangetypes.html). You
+          can filter on range columns using the string representation of range
+          values.
+        hideCodeBlock: true
+
+  - id: range-adjacent
+    title: rangeAdjacent()
+    description: |
+      Only relevant for range columns. Match only rows where column is mutually exclusive to range and there can be no element between the two ranges.
+
+    examples:
+      - id: with-select
+        name: With `select()`
+        isSpotlight: true
+        code: |
+          ```kotlin
+            client.postgrest["reservations"].select {
+               Reservation::during adjacent ("2000-01-02 08:30" to "2000-01-02 09:30")
+               //or
+               adjacent("during", "2000-01-02 08:30" to "2000-01-02 09:30") 
+            }      
+          ```
+        data:
+          sql: |
+            ```sql
+            create table
+              reservations (
+                id int8 primary key,
+                room_name text,
+                during tsrange
+              );
+
+            insert into
+              reservations (id, room_name, during)
+            values
+              (1, 'Emerald', '[2000-01-01 13:00, 2000-01-01 15:00)'),
+              (2, 'Topaz', '[2000-01-02 09:00, 2000-01-02 10:00)');
+            ```
+        response: |
+          ```json
+          {
+            "data": [
+              {
+                "id": 1,
+                "room_name": "Emerald",
+                "during": "[\"2000-01-01 13:00:00\",\"2000-01-01 15:00:00\")"
+              }
+            ],
+            "status": 200,
+            "statusText": "OK"
+          }
+          ```
+
+        hideCodeBlock: true
+
+  - id: overlaps
+    title: overlaps()
+    $ref: '@supabase/postgrest-js.PostgrestFilterBuilder.overlaps'
+    description: |
+      Only relevant for array and range columns. Match only rows where column and value have an element in common.
+
+    examples:
+      - id: on-array-columns
+        name: On array columns
+        code: |
+          ```kotlin
+          client.postgrest["issues"].select(columns = Columns.list("title")) {
+             Issue::tags overlaps listOf("is:closed", "severity:high")
+             //or
+             overlaps("tags", listOf("is:closed", "severity:high"))
+          }      
+          ```
+        data:
+          sql: |
+            ```sql
+            create table
+              issues (
+                id int8 primary key,
+                title text,
+                tags text[]
+              );
+
+            insert into
+              issues (id, title, tags)
+            values
+              (1, 'Cache invalidation is not working', array['is:open', 'severity:high', 'priority:low']),
+              (2, 'Use better names', array['is:open', 'severity:low', 'priority:medium']);
+            ```
+        response: |
+          ```json
+          {
+            "data": [
+              {
+                "title": "Cache invalidation is not working"
+              }
+            ],
+            "status": 200,
+            "statusText": "OK"
+          }
+          ```
+        hideCodeBlock: true
+        isSpotlight: true
+      - id: on-range-columns
+        name: On range columns
+        code: |
+          ```kotlin
+          client.postgrest["issues"].select(columns = Columns.list("title")) {
+             Issue::tags overlaps listOf("is:closed", "severity:high")
+             //or
+             overlaps("tags", listOf("is:closed", "severity:high"))
+          }      
+          ```
+        data:
+          sql: |
+            ```sql
+            create table
+              reservations (
+                id int8 primary key,
+                room_name text,
+                during tsrange
+              );
+
+            insert into
+              reservations (id, room_name, during)
+            values
+              (1, 'Emerald', '[2000-01-01 13:00, 2000-01-01 15:00)'),
+              (2, 'Topaz', '[2000-01-02 09:00, 2000-01-02 10:00)');
+            ```
+        response: |
+          ```json
+          {
+            "data": [
+              {
+                "id": 1,
+                "room_name": "Emerald",
+                "during": "[\"2000-01-01 13:00:00\",\"2000-01-01 15:00:00\")"
+              }
+            ],
+            "status": 200,
+            "statusText": "OK"
+          }
+          ```
+        description: |
+          Postgres supports a number of [range
+          types](https://www.postgresql.org/docs/current/rangetypes.html). You
+          can filter on range columns using the string representation of range
+          values.
+        hideCodeBlock: true
+
+  - id: text-search
+    title: textSearch()
+    description: |
+      Only relevant for text and tsvector columns. Match only rows where `column` matches the query string in `query`.
+
+      For more information, see [Postgres full text search](https://supabase.com/docs/guides/database/full-text-search).
+    examples:
+      - id: text-search
+        name: Text search
+        code: |
+          ```kotlin
+          client.postgrest["quotes"].select(columns = Columns.list("catchphrase")) {
+             textSearch(column = "catchphrase", query = "'fat' & 'cat'", config = "english", type = TextSearchType.YOUR_TYPE)
+          }
+          ```
+      - id: basic-normalization
+        name: Basic normalization
+        description: Uses PostgreSQL's `plainto_tsquery` function.
+        code: |
+          ```kotlin
+          client.postgrest["quotes"].select(columns = Columns.list("catchphrase")) {
+             textSearch(column = "catchphrase", query = "'fat' & 'cat'", config = "english", type = TextSearchType.PLAINTO)
+          }
+          ```
+      - id: full-normalization
+        name: Full normalization
+        description: Uses PostgreSQL's `phraseto_tsquery` function.
+        code: |
+          ```kotlin
+          client.postgrest["quotes"].select(columns = Columns.list("catchphrase")) {
+             textSearch(column = "catchphrase", query = "'fat' & 'cat'", config = "english", type = TextSearchType.PHRASETO)
+          }
+          ```
+      - id: web-search
+        name: Websearch
+        description: |
+          Uses PostgreSQL's `websearch_to_tsquery` function.
+          This function will never raise syntax errors, which makes it possible to use raw user-supplied input for search, and can be used
+          with advanced operators.
+
+          - `unquoted text`: text not inside quote marks will be converted to terms separated by & operators, as if processed by plainto_tsquery.
+          - `"quoted text"`: text inside quote marks will be converted to terms separated by <-> operators, as if processed by phraseto_tsquery.
+          - `OR`: the word “or” will be converted to the | operator.
+          - `-`: a dash will be converted to the ! operator.
+
+        code: |
+          ```kotlin
+          client.postgrest["quotes"].select(columns = Columns.list("catchphrase")) {
+             textSearch(column = "catchphrase", query = "'fat' & 'cat'", config = "english", type = TextSearchType.WEBSEARCH)
+          }
+          ```
+
+  - id: filter
+    title: filter()
+    $ref: '@supabase/postgrest-js.PostgrestFilterBuilder.filter'
+    notes: |
+      filter() expects you to use the raw PostgREST syntax for the filter values.
+    examples:
+      - id: with-select
+        name: With `select()`
+        code: |
+          ```kotlin
+          client.postgrest["countries"].select {
+             filter(column = "name", operator = FilterOperator.IN, value = "('Algeria', 'Japan')")
+          }      
+          ```
+        data:
+          sql: |
+            ```sql
+            create table
+              countries (id int8 primary key, name text);
+
+            insert into
+              countries (id, name)
+            values
+              (1, 'Afghanistan'),
+              (2, 'Albania'),
+              (3, 'Algeria');
+            ```
+        response: |
+          ```json
+          {
+            "data": [
+              {
+                "id": 3,
+                "name": "Algeria"
+              }
+            ],
+            "status": 200,
+            "statusText": "OK"
+          }
+          ```
+        hideCodeBlock: true
+        isSpotlight: true
+      - id: on-a-foreign-table
+        name: On a foreign table
+        code: |
+          ```kotlin
+          client.postgrest["countries"].select(
+             columns = Columns.raw("""
+                                   name,
+                                   cities!inner (
+                                     name
+                                   )
+                                   """)
+          ) {
+             filter(column = "cities.name", operator = FilterOperator.EQ, value = "Bali")
+          }        
+          ```
+        data:
+          sql: |
+            ```sql
+            create table
+              countries (id int8 primary key, name text);
+            create table
+              cities (
+                id int8 primary key,
+                country_id int8 not null references countries,
+                name text
+              );
+
+            insert into
+              countries (id, name)
+            values
+              (1, 'Germany'),
+              (2, 'Indonesia');
+            insert into
+              cities (id, country_id, name)
+            values
+              (1, 2, 'Bali'),
+              (2, 1, 'Munich');
+            ```
+        response: |
+          ```json
+          {
+            "data": [
+              {
+                "name": "Indonesia",
+                "cities": [
+                  {
+                    "name": "Bali"
+                  }
+                ]
+              }
+            ],
+            "status": 200,
+            "statusText": "OK"
+          }
+          ```
+        hideCodeBlock: true
+  - id: order
+    title: order()
+    description: |
+      Order the query result by column.
+    $ref: '@supabase/postgrest-js.PostgrestTransformBuilder.order'
+    examples:
+      - id: with-select
+        name: With `select()`
+        code: |
+          ```kotlin
+          client.postgrest["countries"].select(columns = Columns.list("id", "name")) {
+             order(column = "id", order = Order.ASCENDING)
+          }
+          ```
+        data:
+          sql: |
+            ```sql
+            create table
+              countries (id int8 primary key, name text);
+
+            insert into
+              countries (id, name)
+            values
+              (1, 'Afghanistan'),
+              (2, 'Albania'),
+              (3, 'Algeria');
+            ```
+        response: |
+          ```json
+          {
+            "data": [
+              {
+                "id": 3,
+                "name": "Algeria"
+              },
+              {
+                "id": 2,
+                "name": "Albania"
+              },
+              {
+                "id": 1,
+                "name": "Afghanistan"
+              }
+            ],
+            "status": 200,
+            "statusText": "OK"
+          }
+          ```
+        hideCodeBlock: true
+        isSpotlight: true
+      - id: on-a-foreign-table
+        name: On a foreign table
+        code: |
+          ```kotlin
+          client.postgrest["countries"].select(
+              columns = Columns.raw(
+                  """
+                              name,
+                              cities (
+                                name
+                              )
+                        """
+              )
+          ) {
+              order(column = "id", order = Order.ASCENDING, foreignTable = "cities")
+          }
+            ```
+        data:
+          sql: |
+            ```sql
+            create table
+              countries (id int8 primary key, name text);
+            create table
+              cities (
+                id int8 primary key,
+                country_id int8 not null references countries,
+                name text
+              );
+
+            insert into
+              countries (id, name)
+            values
+              (1, 'United States'),
+              (2, 'Vanuatu');
+            insert into
+              cities (id, country_id, name)
+            values
+              (1, 1, 'Atlanta'),
+              (2, 1, 'New York City');
+            ```
+        response: |
+          ```json
+          {
+            "data": [
+              {
+                "name": "United States",
+                "cities": [
+                  {
+                    "name": "New York City"
+                  },
+                  {
+                    "name": "Atlanta"
+                  }
+                ]
+              },
+              {
+                "name": "Vanuatu",
+                "cities": []
+              }
+            ],
+            "status": 200,
+            "statusText": "OK"
+          }
+          ```
+        description: |
+          Ordering on foreign tables doesn't affect the ordering of
+          the parent table.
+        hideCodeBlock: true
+
+  - id: limit
+    title: limit()
+    description: |
+      Limit the query result by count.
+    $ref: '@supabase/postgrest-js.PostgrestTransformBuilder.limit'
+    examples:
+      - id: with-select
+        name: With `select()`
+        code: |
+          ```kotlin
+          client.postgrest["countries"].select {
+              limit(count = 20)
+          }
+          ```
+        data:
+          sql: |
+            ```sql
+            create table
+              countries (id int8 primary key, name text);
+
+            insert into
+              countries (id, name)
+            values
+              (1, 'Afghanistan'),
+              (2, 'Albania'),
+              (3, 'Algeria');
+            ```
+        response: |
+          ```json
+          {
+            "data": [
+              {
+                "name": "Afghanistan"
+              }
+            ],
+            "status": 200,
+            "statusText": "OK"
+          }
+          ```
+        hideCodeBlock: true
+        isSpotlight: true
+      - id: on-a-foreign-table
+        name: On a foreign table
+        code: |
+          ```kotlin
+          client.postgrest["countries"].select(
+              columns = Columns.raw(
+                  """
+                              name,
+                              cities (
+                                name
+                              )
+                        """
+              )
+          ) {
+              limit(count = 20, foreignTable = "cities")
+          }
+          ```
+        data:
+          sql: |
+            ```sql
+            create table
+              countries (id int8 primary key, name text);
+            create table
+              cities (
+                id int8 primary key,
+                country_id int8 not null references countries,
+                name text
+              );
+
+            insert into
+              countries (id, name)
+            values
+              (1, 'United States');
+            insert into
+              cities (id, country_id, name)
+            values
+              (1, 1, 'Atlanta'),
+              (2, 1, 'New York City');
+            ```
+        response: |
+          ```json
+          {
+            "data": [
+              {
+                "name": "United States",
+                "cities": [
+                  {
+                    "name": "Atlanta"
+                  }
+                ]
+              }
+            ],
+            "status": 200,
+            "statusText": "OK"
+          }
+          ```
+        hideCodeBlock: true
+  - id: range
+    title: range()
+    description: |
+      Limit the query result by from and to inclusively.
+    examples:
+      - id: with-select
+        name: With `select()`
+        code: |
+          ```kotlin
+          client.postgrest["countries"].select {
+              range(1L..5L)
+          }
+          ```
+        data:
+          sql: |
+            ```sql
+            create table
+              countries (id int8 primary key, name text);
+
+            insert into
+              countries (id, name)
+            values
+              (1, 'Afghanistan'),
+              (2, 'Albania'),
+              (3, 'Algeria');
+            ```
+        response: |
+          ```json
+          {
+            "data": [
+              {
+                "name": "Afghanistan"
+              },
+              {
+                "name": "Albania"
+              }
+            ],
+            "status": 200,
+            "statusText": "OK"
+          }
+          ```
+        hideCodeBlock: true
+        isSpotlight: true
+  - id: auth-api
+    title: 'Overview'
+    notes: |
+      - The auth methods can be accessed via the Supabase GoTrue Auth client.
+    examples:
+      - id: create-auth-client
+        name: Create gotrue client
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val client = createSupabaseClient(supabaseURL = "https://xyzcompany.supabase.co'", supabaseKey = "public-anon-key") { ... }
+          val gotrue = client.gotrue
+          ```
+  - id: sign-up
+    title: 'signUp()'
+    $ref: '@supabase/gotrue-js.GoTrueClient.signUp'
+    notes: |
+      Creates a new user.
+      - By default, the user needs to verify their email address before logging in. To turn this off, disable **Confirm email** in [your project](https://app.supabase.com/project/_/auth/providers).
+      - **Confirm email** determines if users need to confirm their email address after signing up.
+        - If **Confirm email** is enabled, the return value is null and you will be logged in instead.
+        - If **Confirm email** is disabled, the return value is the user and you won't be logged in automatically.
+      - When the user confirms their email address, they are redirected to the [`SITE_URL`](https://supabase.com/docs/reference/auth/config#site_url) by default. You can modify your `SITE_URL` or add additional redirect URLs in [your project](https://app.supabase.com/project/_/auth/url-configuration).
+      - [supabase-kt](https://github.com/supabase-community/supabase-kt/) has default platform implementations: 
+          - On JVM, you can currently only verify a sign up through the token. To send the token, rather than a redirect url, you have to change `{{ .ConfirmationURL }}` in your sign up email to `{{ .Token }}`
+          - [deep links](https://developer.android.com/training/app-links/deep-linking) (Android), 
+          - [url schemes](https://developer.apple.com/documentation/xcode/defining-a-custom-url-scheme-for-your-app) (IOS) 
+              - To enable deeplinking/url scheme support on Android/IOS set the `host` and the `scheme` in the GoTrue Config and call `client.handleDeeplinks(intent)` (Android) and `client.handleDeeplinks(url)` (IOS) on startup
+          - the website origin (JS)
+      - If signUpWith() is called for an existing confirmed user:
+        - If **Confirm email** is enabled in [your project](https://app.supabase.com/project/_/auth/providers), an obfuscated/fake user object is returned.
+        - If **Confirm email** is disabled, the error message, `User already registered` is returned.
+    examples:
+      - id: sign-up-phone
+        name: Sign up with email
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val user = client.gotrue.signUpWith(Email) {
+              email = "example@email.com" 
+              password = "example-password"
+          }
+          ```
+      - id: sign-up-phone
+        name: Sign up with a phone number
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val user = client.gotrue.signUpWith(Phone) {
+              phoneNumber = "+4912345679" 
+              password = "example-password"
+          }
+          ```   
+      - id: sign-up-with-additional-user-metadata
+        name: Sign up with additional user metadata
+        isSpotlight: false
+        code: |
+          ```kotlin
+          val user = client.gotrue.signUpWith(Email) {
+              email = "example@email.com" 
+              password = "example-password"
+              data = buildJsonObject {
+                 put("first_name", "John")
+                 put("age", 24)
+              }
+          }                     
+          ```
+      - id: sign-up-with-redirect
+        name: Sign up with a redirect URL
+        description: |
+          - See [redirect URLs and wildcards](/docs/guides/auth/overview#redirect-urls-and-wildcards) to add additional redirect URLs to your project.
+        code: |
+          ```kotlin
+          val user = client.gotrue.signUpWith(Email, redirectUrl = "https://example.com") {
+              email = "example@email.com" 
+              password = "example-password"
+          }
+          ```
+  - id: sign-in-with-password
+    title: 'loginWith()'
+    $ref: '@supabase/gotrue-js.GoTrueClient.signInWithPassword'
+    notes: |
+      Logs in an existing user.
+      - Requires either an email and password or a phone number and password.
+    examples:
+      - id: sign-in-with-email-and-password
+        name: Sign in with email and password
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.gotrue.loginWith(Email) {
+              email = "example@email.com" 
+              password = "example-password"
+          }
+          ```
+      - id: sign-in-with-phone-and-password
+        name: Sign in with phone and password
+        isSpotlight: false
+        code: |
+          ```kotlin
+          client.gotrue.loginWith(Phone) {
+              phoneNumber = "+4912345679" 
+              password = "example-password"
+          }
+          ```  
+      - id: sign-in-with-id-token
+        name: Sign in with id token
+        isSpotlight: false
+        code: |
+          ```kotlin
+          client.gotrue.loginWith(IDToken) {
+              idToken = "token"
+              clientId = "oauth client id"
+              provider = Google //Or Apple
+              //optional:
+              nonce = "nonce"
+              data = buildJsonObject {
+                  //...
+              }
+          }
+          ```      
+  - id: sign-in-with-otp
+    title: 'sendOtpTo()'
+    $ref: '@supabase/gotrue-js.GoTrueClient.signInWithOtp'
+    notes: |
+      Sends a OTP to the user's email or phone number.
+      - Requires either an email or phone number.
+      - This method is used for passwordless sign-ins where a OTP is sent to the user's email or phone number.
+      - If the user doesn't exist, `sendOtpTo()` will signup the user instead. To restrict this behavior, you can set `createUser` to `false`.
+      - If you're using an email, you can configure whether you want the user to receive a magiclink or a OTP.
+      - If you're using phone, you can configure whether you want the user to receive a OTP.
+      - The magic link's destination URL is determined by the [`SITE_URL`](/docs/reference/auth/config#site_url).
+      - See [redirect URLs and wildcards](/docs/guides/auth/overview#redirect-urls-and-wildcards) to add additional redirect URLs to your project.
+      - [supabase-kt](https://github.com/supabase-community/supabase-kt/) has default platform implementations: 
+        - On JVM, you can currently only verify a OTP through the token. To send the token, rather than a redirect url, you have to change `{{ .ConfirmationURL }}` in your OTP email to `{{ .Token }}`
+        - [deep links](https://developer.android.com/training/app-links/deep-linking) (Android), 
+        - [url schemes](https://developer.apple.com/documentation/xcode/defining-a-custom-url-scheme-for-your-app) (IOS) 
+            - To enable deeplinking/url scheme support on Android/IOS set the `host` and the `scheme` in the GoTrue Config and call `client.handleDeeplinks(intent)` (Android) and `client.handleDeeplinks(url)` (IOS) on startup
+        - the website origin (JS)
+      - Magic links and OTPs share the same implementation. To send users a one-time code instead of a magic link, [modify the magic link email template](https://app.supabase.com/project/_/auth/templates) to include `{{ .Token }}` instead of `{{ .ConfirmationURL }}`.
+    examples:
+      - id: sign-in-with-email
+        name: Sign in with email
+        isSpotlight: true
+        description: The user will be sent an email which contains either a magiclink or a OTP or both. By default, a given user can only request a OTP once every 60 seconds.
+        code: |
+          ```kotlin
+          client.gotrue.sendOtpTo(Email) {
+              email = "example@email.com" 
+          }
+          ```  
+      - id: sign-in-with-sms-otp
+        name: Sign in with SMS OTP
+        isSpotlight: false
+        description: The user will be sent a SMS which contains a OTP. By default, a given user can only request a OTP once every 60 seconds.
+        code: |
+          ```kotlin
+          client.gotrue.sendOtpTo(Phone) {
+              phoneNumber = "+4912345679" 
+          }
+          ```
+  - id: sign-in-with-oauth
+    title: 'loginWith(OAuthProvider)'
+    $ref: '@supabase/gotrue-js.GoTrueClient.signInWithOAuth'
+    notes: |
+      - This method is used for signing in using a third-party provider.
+      - Supabase supports many different [third-party providers](https://supabase.com/docs/guides/auth#providers).
+      - [supabase-kt](https://github.com/supabase-community/supabase-kt/) has default platform implementations: 
+          - HTTP Callback Server (JVM), 
+          - [deep links](https://developer.android.com/training/app-links/deep-linking) (Android), 
+          - [url schemes](https://developer.apple.com/documentation/xcode/defining-a-custom-url-scheme-for-your-app) (IOS) 
+              - To enable deeplinking/url scheme support on Android/IOS set the `host` and the `scheme` in the GoTrue Config and call `client.handleDeeplinks(intent)` (Android) and `client.handleDeeplinks(url)` (IOS) on startup
+          - the website origin (JS)
+    examples:
+      - id: sign-in-using-a-third-party-provider
+        name: Sign in using a third-party provider
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.gotrue.loginWith(Github)
+          ```
+      - id: sign-in-using-a-third-party-provider with scopes
+        name: Sign in using a third-party provider with scopes
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.gotrue.loginWith(Github) {
+              scopes.add("email")
+          }
+          ```
+
+      - id: sign-in-using-a-third-party-provider-with-redirect
+        name: Create a custom url
+        isSpotlight: false
+        description: |
+          - When the third-party provider successfully authenticates the user, the provider redirects the user to the URL specified in the `redirectUrl` parameter. This parameter defaults to the [`SITE_URL`](/docs/reference/auth/config#site_url). It does not redirect the user immediately after invoking this method.
+          - See [redirect URLs and wildcards](/docs/guides/auth/overview#redirect-urls-and-wildcards) to add additional redirect URLs to your project.
+          - oAuthUrl() provides the URL which needs to be opened in a browser.
+          - The redirectTo URL needs to be setup correctly in your project under Authentication -> URL Configuration -> Redirect URLs.
+          - To see how you can use a custom in-app browser on Android, check our [demo](https://github.com/supabase-community/supabase-kt/tree/development/demos/android-login) on GitHub.
+        code: |
+          ```kotlin
+          val url = client.gotrue.oAuthUrl(Github, redirectUrl = "https://example.com")
+          ```
+      - id: sign-in-with-scopes
+        name: Create a custom url with scopes
+        isSpotlight: false
+        description: |
+          If you need additional data from an OAuth provider, you can include a space-separated list of scopes in your request to get back an OAuth provider token.
+          You may also need to specify the scopes in the provider's OAuth app settings, depending on the provider. The list of scopes will be documented by the third-party provider you are using and specifying scopes will enable you to use the OAuth provider token to call additional APIs supported by the third-party provider to get more information.
+        code: |
+          ```kotlin
+          val url = client.gotrue.oAuthUrl(Github, redirectUrl = "https://example.com") {
+              scopes.add("email")
+          }
+          ```
+  - id: sign-in-with-sso
+    title: 'signInWithSSO()'
+    $ref: '@supabase/gotrue-js.GoTrueClient.signInWithSSO'
+    notes: |
+      - Before you can call this method you need to [establish a connection](/docs/guides/auth/sso/auth-sso-saml#managing-saml-20-connections) to an identity provider. Use the [CLI commands](/docs/reference/cli/supabase-sso) to do this.
+      - If you've associated an email domain to the identity provider, you can use the `SSO.withDomain()` function in the `loginWith` method to start a sign-in flow.
+      - In case you need to use a different way to start the authentication flow with an identity provider, you can use the `SSO.withProviderId` function. For example:
+          - Mapping specific user email addresses with an identity provider.
+          - Using different hints to identity the identity provider to be used by the user, like a company-specific page, IP address or other tracking information.
+      - [supabase-kt](https://github.com/supabase-community/supabase-kt/) has default platform implementations: 
+          - HTTP Callback Server (JVM), 
+          - [deep links](https://developer.android.com/training/app-links/deep-linking) (Android), 
+          - [url schemes](https://developer.apple.com/documentation/xcode/defining-a-custom-url-scheme-for-your-app) (IOS) 
+              - To enable deeplinking/url scheme support on Android/IOS set the `host` and the `scheme` in the GoTrue Config and call `client.handleDeeplinks(intent)` (Android) and `client.handleDeeplinks(url)` (IOS) on startup
+          - the website origin (JS)
+
+    examples:
+      - id: sign-in-with-domain
+        name: Sign in with email domain
+        isSpotlight: true
+        code: |
+          ```kotlin
+            // You can extract the user's email domain and use it to trigger the
+            // authentication flow with the correct identity provider.
+
+            client.gotrue.loginWith(SSO.withDomain("company.com"))
+            
+            //the url was opened automatically, if you don't want that, provide a custom redirect url
+          ```
+      - id: sign-in-with-provider-uuid
+        name: Sign in with provider UUID
+        isSpotlight: true
+        code: |
+          ```kotlin
+            // Useful when you need to map a user's sign in request according
+            // to different rules that can't use email domains.
+
+            client.gotrue.loginWith(SSO.withProvider("21648a9d-8d5a-4555-a9d1-d6375dc14e92"))
+            
+            //the url was opened automatically, if you don't want that, provide a custom redirect url
+          ```        
+  - id: sign-out
+    title: 'logout()'
+    $ref: '@supabase/gotrue-js.GoTrueClient.signOut'
+    notes: |
+      Logs out the current user.
+      - In order to use the `logout()` method, the user needs to be signed in first.
+    examples:
+      - id: sign-out
+        name: Sign out
+        isSpotlight: true
+        code: |
+          ```js
+          client.gotrue.logout()
+          ```
+  - id: verify-otp
+    title: 'Verify OTPs'
+    $ref: '@supabase/gotrue-js.GoTrueClient.verifyOtp'
+    notes: |
+      Log in a user given a User supplied OTP received via mobile.
+    examples:
+      - id: verify-email-otp(otp)
+        name: Verify an Email OTP
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.gotrue.verifyEmailOtp(type = OtpType.Email.INVITE, email = "example@email.com", token = "token")
+          ```
+        description: |
+          Available types are:
+            - `OtpType.Email.MAGIC_LINK`
+            - `OtpType.Email.SIGNUP`
+            - `OtpType.Email.INVITE`
+            - `OtpType.Email.RECOVERY`
+            - `OtpType.Email.EMAIL_CHANGE`
+      - id: verify-phone-otp(otp)
+        name: Verify an Phone OTP
+        isSpotlight: false
+        code: |
+          ```kotlin
+          client.gotrue.verifyPhoneOtp(type = OtpType.Phone.SMS, phoneNumber = "+491234567", token = "token")
+          ```
+        description: |
+          Available types are:
+            - `OtpType.Phone.SMS`
+            - `OtpType.Phone.PHONE_CHANGE`
+  - id: get-session
+    title: 'Get current session'
+    $ref: '@supabase/gotrue-js.GoTrueClient.getSession'
+    notes: |
+      Returns the current session, or `null` if there is none.
+    examples:
+      - id: get-the-session-data
+        name: Get the session data
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val session = client.gotrue.currentSessionOrNull()
+          ```
+  - id: get-user
+    title: 'getUser()'
+    $ref: '@supabase/gotrue-js.GoTrueClient.getUser'
+    description: |
+      - This method gets the user object from the current session.
+      - Fetches the user object from the database instead of local session.
+      - Should be used only when you require the most current user data. For faster results, `getCurrentSessionOrNull()?.user` is recommended.
+    examples:
+      - id: get-the-logged-in-user-with-the-current-existing-session
+        name: Get the logged in user with the current session
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val user = client.gotrue.retrieveUserForCurrentSession(updateSession = true)
+          ```
+        description: |
+          `updateSession` updates the local session with the new user
+      - id: get-different-user
+        name: Get a user based on their access token
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val user = client.gotrue.retrieveUser("JWT")
+          ```    
+  - id: update-user
+    title: 'modifyUser()'
+    $ref: '@supabase/gotrue-js.GoTrueClient.updateUser'
+    notes: |
+      Modifies the user data.
+      - In order to use the `modifyUser()` method, the user needs to be signed in first.
+      - By default, email updates sends a confirmation link to both the user's current and new email.
+      To only send a confirmation link to the user's new email, disable **Secure email change** in your project's [email auth provider settings](https://app.supabase.com/project/_/auth/providers).
+    examples:
+      - id: update-the-email-for-an-authenticated-user
+        name: Update the email for an authenticated user
+        description: Sends a "Confirm Email Change" email to the new email address.
+        isSpotlight: false
+        code: |
+          ```kotlin
+          val user = client.gotrue.modifyUser(Email) {
+             email = "newEmail@email.com"
+          }
+          ```
+      - id: update-the-password-for-an-authenticated-user
+        name: Update the password for an authenticated user
+        isSpotlight: false
+        code: |
+          ```kotlin
+          val user = client.gotrue.modifyUser(Email) {
+             password = "secretPassword"
+          }
+          ```
+      - id: update-the-users-metadata
+        name: Update the user's metadata
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val user = client.gotrue.modifyUser(Email, buildJsonObject { 
+             put("name", "John")
+          })
+          ```
+  - id: set-session
+    title: 'importSession()'
+    $ref: '@supabase/gotrue-js.GoTrueClient.setSession'
+    notes: |
+      Changes the local session.
+      - `importSession()` takes in a UserSession.
+      - [Refresh token rotation](/docs/reference/auth/config#refresh_token_rotation_enabled) is enabled by default on all projects to guard against replay attacks.
+      - You can configure the [`REFRESH_TOKEN_REUSE_INTERVAL`](https://supabase.com/docs/reference/auth/config#refresh_token_reuse_interval) which provides a short window in which the same refresh token can be used multiple times in the event of concurrency or offline issues.
+    examples:
+      - id: refresh-the-session
+        name: Set local session
+        description: Sets the local session from refresh_token and returns current session or an error if the refresh_token is invalid.
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.gotrue.importSession(UserSession(accessToken = "token", refreshToken = "refresh", expiresIn = 2000, tokenType = "Bearer", user = null))
+          ```
+  - id: refresh-session
+    title: 'refreshSession()'
+    $ref: '@supabase/gotrue-js.GoTrueClient.refreshSession'
+    notes: |
+      This method will refresh the session whether the current one is expired or not.
+      
+      - This is done automatically, but can be disabled in the GoTrue config.
+    examples:
+      - id: refresh-current-session
+        name: Refresh current session
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val session = client.gotrue.refreshCurrentSession()
+          ```
+      - id: refresh-session-using-the-current-session
+        name: Refresh session using the refresh token
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val session = client.gotrue.refreshSession(refreshToken = "refreshToken")
+          ```
+  - id: on-auth-state-change
+    title: 'sessionStatus'
+    $ref: '@supabase/gotrue-js.GoTrueClient.onAuthStateChange'
+    notes: |
+      Listen to session changes.
+    examples:
+      - id: listen-to-auth-changes
+        name: Listen to auth changes
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.gotrue.sessionStatus.collect {
+              when(it) {
+                  is SessionStatus.Authenticated -> println(it.session.user)
+                  SessionStatus.LoadingFromStorage -> println("Loading from storage")
+                  SessionStatus.NetworkError -> println("Network error")
+                  SessionStatus.NotAuthenticated -> println("Not authenticated")
+              }
+          }
+          ```
+        description: |
+          Types of statuses:
+          - `NotAuthenticated`, 
+          - `LoadingFromStorage`, 
+          - `NetworkError`, 
+          - `Authenticated(sesssion)`
+  - id: reset-password-for-email
+    title: 'Send a password reset request'
+    notes: |
+      Sends a password reset request to the given email address.
+      - The password reset flow consist of 2 broad steps: (i) Allow the user to login via the password reset link; (ii) Update the user's password.
+      - The `sendRecoveryEmail()` only sends a password reset link to the user's email.
+      To update the user's password, see [`modifyUser()`](/docs/reference/kotlin/auth-updateuser).
+      - When the user clicks the reset link in the email they are redirected back to your application.
+      You can configure the URL that the user is redirected to with the `redirectUrl` parameter.
+      See [redirect URLs and wildcards](/docs/guides/auth#redirect-urls-and-wildcards) to add additional redirect URLs to your project.
+      - After the user has been redirected successfully, prompt them for a new password and call `modifyUser()`:
+        ```kotlin
+        client.gotrue.modifyUser(Email) {
+            password = "1234567"
+        }
+        ```
+    examples:
+      - id: send-password-reset-email
+        name: Send password reset email
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.gotrue.sendRecoveryEmail(email = "example@email.com")
+          ```
+  - id: mfa-enroll
+    title: 'Enroll a factor'
+    $ref: '@supabase/gotrue-js.GoTrueMFAApi.enroll'
+    notes: |
+      Enrolls a new factor.
+      - Currently, `totp` is the only supported `factorType`. The returned `id` should be used to create a challenge.
+      - To create a challenge, see [`mfa.createChallenge()`](/docs/reference/kotlin/auth-mfa-challenge).
+      - To verify a challenge, see [`mfa.verifyChallenge()`](/docs/reference/kotlin/auth-mfa-verify).
+      - To create and verify a challenge in a single step, see [`mfa.createChallengeAndVerify()`](/docs/reference/kotlin/auth-mfa-challengeandverify).
+    examples:
+      - id: enroll-totp-factor
+        name: Enroll a time-based, one-time password (TOTP) factor
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val factor = client.gotrue.mfa.enroll(factorType = FactorType.TOTP)
+
+          // Use the id to create a challenge.
+          // The challenge can be verified by entering the code generated from the authenticator app.
+          // The code will be generated upon scanning the qr_code or entering the secret into the authenticator app.
+          val (id, type, qrCode) = factor.data //qrCode is a svg as a string
+          val (factorId, factorType, _) = factor
+          ```
+      - id: get-local-verified-factors
+        name: Check the local user for verified factors
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val verifiedFactors = client.gotrue.mfa.verifiedFactors
+          ```  
+      - id: retrieve-verified-factors
+        name: Retrieve verified factors
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val verifiedFactors = client.gotrue.mfa.retrieveFactorsForCurrentUser()
+          ```       
+  - id: mfa-challenge
+    title: 'mfa.challenge()'
+    $ref: '@supabase/gotrue-js.GoTrueMFAApi.challenge'
+    notes: |
+      Creates a challenge for a factor.
+      - An [enrolled factor](/docs/reference/kotlin/auth-mfa-enroll) is required before creating a challenge.
+      - To verify a challenge, see [`mfa.verifyChallenge()`](/docs/reference/kotlin/auth-mfa-verify).
+    examples:
+      - id: create-mfa-challenge
+        name: Create a challenge for a factor
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val challenge = client.gotrue.mfa.createChallenge(factorId = "34e770dd-9ff9-416c-87fa-43b31d7ef225")
+          ```
+  - id: mfa-verify
+    title: 'mfa.verify()'
+    $ref: '@supabase/gotrue-js.GoTrueMFAApi.verify'
+    notes: |
+      Verifies a challenge for a factor.
+      - To verify a challenge, please [create a challenge](/docs/reference/kotlin/auth-mfa-challenge) first.
+    examples:
+      - id: verify-challenge
+        name: Verify a challenge for a factor
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.gotrue.mfa.verifyChallenge(
+              factorId = "34e770dd-9ff9-416c-87fa-43b31d7ef225",
+              challengeId = "4034ae6f-a8ce-4fb5-8ee5-69a5863a7c15",
+              code = "123456",
+              saveSession = true // this is set to true by default, but you can set it to false if you want to handle the session yourself
+          )
+          ```
+  - id: mfa-challenge-and-verify
+    title: 'mfa.challengeAndVerify()'
+    $ref: '@supabase/gotrue-js.GoTrueMFAApi.challengeAndVerify'
+    notes: |
+      Creates and verifies a challenge for a factor.
+      - An [enrolled factor](/docs/reference/kotlin/auth-mfa-enroll) is required before invoking `createChallengeAndVerify()`.
+      - Executes [`mfa.createChallenge()`](/docs/reference/kotlin/auth-mfa-challenge) and [`mfa.verifyChallenge()`](/docs/reference/kotlin/auth-mfa-verify) in a single step.
+    examples:
+      - id: challenge-and-verify
+        name: Create and verify a challenge for a factor
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.gotrue.mfa.createChallengeAndVerify(
+              factorId = "34e770dd-9ff9-416c-87fa-43b31d7ef225",
+              code = "123456",
+              saveSession = true // this is set to true by default, but you can set it to false if you want to handle the session yourself
+          )
+          ```
+  - id: mfa-unenroll
+    title: 'mfa.unenroll()'
+    $ref: '@supabase/gotrue-js.GoTrueMFAApi.unenroll'
+    notes: |
+      Unenroll removes a MFA factor. A user has to have an `AAL2` authentication level in order to unenroll a verified factor.
+    examples:
+      - id: unenroll-a-factor
+        name: Unenroll a factor
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.gotrue.mfa.unenroll(factorId = "34e770dd-9ff9-416c-87fa-43b31d7ef225")
+          ```
+  - id: mfa-get-authenticator-assurance-level
+    title: 'mfa.getAuthenticatorAssuranceLevel()'
+    $ref: '@supabase/gotrue-js.GoTrueMFAApi.getAuthenticatorAssuranceLevel'
+    notes: |
+      - Authenticator Assurance Level (AAL) is the measure of the strength of an authentication mechanism.
+      - In Supabase, having an AAL of `aal1` refers to having the 1st factor of authentication such as an email and password or OAuth sign-in while `aal2` refers to the 2nd factor of authentication such as a time-based, one-time-password (TOTP).
+      - If the user has a verified factor, the `next` field will return `AuthenticatorAssuranceLevel.AAL2`, else, it will return `AuthenticatorAssuranceLevel.AAL1`.
+    examples:
+      - id: get-aal
+        name: Get the AAL details of the current session
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val (current, next) = client.gotrue.mfa.getAuthenticatorAssuranceLevel()
+          ```    
+      - id: aal-enabled
+        name: Check whether the user has atleast one verified factor
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val enabled = client.gotrue.mfa.isMfaEnabled
+          //flow variant, automatically emitting new values on session changes
+          val enabledFlow = client.gotrue.mfa.isMfaEnabledFlow
+          ``` 
+      - id: aal-enabled-for-current-session
+        name: Check whether the user is logged in using AAL2
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val loggedInUsingMfa = client.gotrue.mfa.loggedInUsingMfa
+          //flow variant, automatically emitting new values on session changes
+          val loggedInUsingMfaFlow = client.gotrue.mfa.loggedInUsingMfaFlow
+          ```   
+  - id: admin-api
+    title: 'Overview'
+    notes: |
+      - Any method under the `client.gotrue.admin` namespace requires a `service_role` key.
+      - These methods are considered admin methods and should be called on a trusted server. Never expose your `service_role` key in the browser.
+    examples:
+      - id: create-auth-admin-client
+        name: Create server-side auth client
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val client = createSupabaseClient(
+              supabaseUrl = "https://id.supabase.co",
+              supabaseKey = "service_role"
+          ) {
+              install(GoTrue) {
+                  autoLoadFromStorage = false
+                  alwaysAutoRefresh = false
+              }
+          }
+
+          // Access auth admin api
+          val adminGoTrueClient = client.gotrue.admin
+          ```
+
+  - id: get-user-by-id
+    title: 'getUserById()'
+    $ref: '@supabase/gotrue-js.GoTrueAdminApi.getUserById'
+    notes: |
+      Fetches the user object from the database based on the user's id.
+      - The `retrieveUserById()` method requires the user's id which maps to the `auth.users.id` column.
+    examples:
+      - id: fetch-the-user-object-using-the-access-token-jwt
+        name: Fetch the user object using the access_token jwt
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val user = client.gotrue.admin.retrieveUserById(uid = "f2a0b0a0-6b1a-4b7a-8f1a-4b7a6b1a8f1a")
+          ```
+
+  - id: list-users
+    title: 'listUsers()'
+    $ref: '@supabase/gotrue-js.GoTrueAdminApi.listUsers'
+    notes: |
+      Retrieves a list of users.
+      - Defaults to return 50 users per page.
+    examples:
+      - id: get-a-full-list-of-users
+        name: Get a page of users
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val users = client.gotrue.admin.retrieveUsers()
+          ```
+      - id: get-paginated-list-of-users
+        name: Paginated list of users
+        isSpotlight: false
+        code: |
+          ```kotlin
+          val users = client.gotrue.admin.retrieveUsers(
+              page = 1,
+              perPage = 100
+          )
+          ```
+  - id: create-user
+    title: 'createUser()'
+    $ref: '@supabase/gotrue-js.GoTrueAdminApi.createUser'
+    notes: |
+      Creates a new user.
+      - To confirm the user's email address or phone number, set `autoConfirm` to true. Both arguments default to false.
+    examples:
+      - id: create-a-new-user-with-email-custom-user-metadata
+        name: Create user with email
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val userWithEmail = client.gotrue.admin.createUserWithEmail {
+              email = "example@email.com"
+              password = "secretpassword"
+              userMetadata {
+                  put("name", "John")
+              }
+          }
+          ```
+      - id: create-a-new-user-with-phone-custom-user-metadata
+        name: Create user with phone
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val userWithPhone = client.gotrue.admin.createUserWithPhone {
+              phoneNumber = "+49123456789"
+              password = "secretpassword"
+              userMetadata {
+                  put("name", "John")
+              }
+          }
+          ```    
+      - id: auto-confirm-the-users-email
+        name: Auto-confirm the user's email
+        code: |
+          ```kotlin
+          val userWithEmail = client.gotrue.admin.createUserWithEmail {
+              email = "example@email.com"
+              password = "secretpassword"
+              autoConfirm = true
+          }
+          ```
+      - id: auto-confirm-the-users-phone-number
+        name: Auto-confirm the user's phone number
+        code: |
+          ```kotlin
+          val userWithPhone = client.gotrue.admin.createUserWithPhone {
+              phoneNumber = "+49123456789"
+              password = "secretpassword"
+              autoConfirm = true
+          }
+          ```
+  - id: delete-user
+    title: 'deleteUser()'
+    $ref: '@supabase/gotrue-js.GoTrueAdminApi.deleteUser'
+    notes: |
+      Deletes a user from the database.
+      - The `deleteUser()` method requires the user's ID, which maps to the `auth.users.id` column.
+    examples:
+      - id: removes-a-user
+        name: Removes a user
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.gotrue.admin.deleteUser(uid = "uid")
+          ```
+
+  - id: invite-user-by-email
+    title: 'inviteUserByEmail()'
+    $ref: '@supabase/gotrue-js.GoTrueAdminApi.inviteUserByEmail'
+    notes: |
+      Sends an invite link to the user's email address.
+    examples:
+      - id: invite-a-user
+        name: Invite a user
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.gotrue.admin.inviteUserByEmail(
+              email = "example@email.com",
+              //optional:
+              redirectTo = "https://example.com/redirect",
+              data = buildJsonObject {
+                  put("custom", "value")
+              }
+          )
+          ```
+
+  - id: generate-link
+    title: 'generateLink()'
+    $ref: '@supabase/gotrue-js.GoTrueAdminApi.generateLink'
+    notes: |
+      Generates email links and OTPs to be sent via a custom email provider.
+    examples:
+      - id: generate-a-signup-link
+        name: Generate a signup link
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val (url, user) = client.gotrue.admin.generateLinkFor(LinkType.Signup) {
+              email = "example@email.com"
+              password = "secretpassword"
+          }
+          ```
+      - id: generate-an-invite-link
+        name: Generate an invite link
+        isSpotlight: false
+        code: |
+          ```kotlin
+          val (url, user) = client.gotrue.admin.generateLinkFor(LinkType.Invite) {
+              email = "example@email.com"
+          }
+          ```
+      - id: generate-a-magic-link
+        name: Generate a magic link
+        isSpotlight: false
+        code: |
+          ```kotlin
+          val (url, user) = client.gotrue.admin.generateLinkFor(LinkType.MagicLink) {
+              email = "example@email.com"
+          }
+          ```
+      - id: generate-a-recovery-link
+        name: Generate a recovery link
+        isSpotlight: false
+        code: |
+          ```kotlin
+          val (url, user) = client.gotrue.admin.generateLinkFor(LinkType.Recovery) {
+              email = "example@email.com"
+          }
+          ```
+      - id: generate-links-to-change-current-email-address
+        name: Generate links to change current email address
+        isSpotlight: false
+        code: |
+          ```kotlin
+          // generate an email change link to be sent to the current email address
+          val (url, user) = client.gotrue.admin.generateLinkFor(LinkType.EmailChangeCurrent) {
+              email = "example@email.com"
+              newEmail = "newEmail@email.com"
+          }
+
+          // generate an email change link to be sent to the new email address
+          val (url, user) = client.gotrue.admin.generateLinkFor(LinkType.EmailChangeNew) {
+              email = "example@email.com"
+              newEmail = "newEmail@email.com"
+          }
+          ```
+
+  - id: update-user-by-id
+    title: 'updateUserById()'
+    $ref: '@supabase/gotrue-js.GoTrueAdminApi.updateUserById'
+    notes: |
+      Updates the user data.
+    examples:
+      - id: updates-a-users-email
+        name: Updates a user's email
+        isSpotlight: false
+        code: |
+          ```kotlin
+          client.gotrue.admin.updateUserById(uid = "id") {
+              email = "example@email.com"
+          }
+          ```
+      - id: updates-a-users-password
+        name: Updates a user's password
+        isSpotlight: false
+        code: |
+          ```js
+          client.gotrue.admin.updateUserById(uid = "id") {
+              password = "password"
+          }
+          ```
+      - id: updates-a-users-metadata
+        name: Updates a user's metadata
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.gotrue.admin.updateUserById(uid = "id") {
+              userMetadata = buildJsonObject { 
+                  put("key", "value")
+              }
+          }
+          ```
+      - id: updates-a-users-app-metadata
+        name: Updates a user's app_metadata
+        isSpotlight: false
+        code: |
+          ```kotlin
+          client.gotrue.admin.updateUserById(uid = "id") {
+              appMetadata = buildJsonObject { 
+                  put("key", "value")
+              }
+          }
+          ```
+      - id: confirms-a-users-email-address
+        name: Confirms a user's email address
+        isSpotlight: false
+        code: |
+          ```kotlin
+          client.gotrue.admin.updateUserById(uid = "id") {
+              emailConfirm = true
+          }
+          ```
+      - id: confirms-a-users-phone-number
+        name: Confirms a user's phone number
+        isSpotlight: false
+        code: |
+          ```kotlin
+          client.gotrue.admin.updateUserById(uid = "id") {
+              phoneConfirm = true
+          }
+          ```
+  - id: mfa-list-factors
+    title: 'mfa.listFactors()'
+    notes: |
+      Lists all factors associated to a user.
+    $ref: '@supabase/gotrue-js.GoTrueAdminMFAApi.listFactors'
+    examples:
+      - id: list-factors
+        name: List all factors for a user
+        isSpotlight: true
+        code: |
+          ```kotlin
+          const factors = client.gotrue.admin.retrieveFactors(uid = "id")
+          ```
+  - id: mfa-delete-factor
+    title: 'mfa.deleteFactor()'
+    $ref: '@supabase/gotrue-js.GoTrueAdminMFAApi.deleteFactor'
+    notes: |
+      Deletes a factor on a user. This will log the user out of all active sessions if the deleted factor was verified.
+    examples:
+      - id: delete-factor
+        name: Delete a factor for a user
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.gotrue.admin.deleteFactor(uid = "id", factorId = "factor_id")
+          ```                       
+  - id: invoke
+    title: 'invoke()'
+    description: |
+      Invokes a Supabase Function. See the [guide](/docs/guides/functions) for details on writing Functions.
+      - When invoking a function with parameters, you have to provide a [serializable value](/docs/reference/kotlin/installing#add-kotlinx-serialization-required-for-postgrest-and-realtime-serialization) in the function parameter.            
+    notes: |
+      - Requires an Authorization header.
+    examples:
+      - id: basic-invocation
+        name: Basic invocation
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.functions.invoke("function_name")
+          ```
+      - id: basic-invocation-with-body
+        name: Basic invocation with body
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.functions.invoke(
+            function = "function_name",
+            body = buildJsonObject {
+                put("foo", "bar")
+            },
+            headers = Headers.build {
+                append(HttpHeaders.ContentType, "application/json")
+            }
+          )
+          ```    
+      - id: reuse-function
+        name: Reuse function by saving it to a variable
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val function = client.functions.buildEdgeFunction(
+            function = "function", 
+            headers = Headers.build { 
+                /*Default headers*/
+                //when you are sending a body you may want to add this header:
+                append(HttpHeaders.ContentType, "application/json")
+              }
+            )
+          //invoke it:
+          function()
+          //invoke it with a body:
+          function(body)
+          //invoke it with custom headers:
+          function(body) {
+              set("Header", "Value")
+          }
+          ```    
+  - id: subscribe
+    description: |
+      Subscribe to realtime changes in your database.
+    title: 'on().subscribe()'
+    notes: |
+      - Realtime is disabled by default for new Projects for better database performance and security. You can turn it on by [managing replication](/docs/guides/database/api#managing-realtime).
+      - If you want to receive the "previous" data for updates and deletes, you will need to set `REPLICA IDENTITY` to `FULL`, like this: `ALTER TABLE your_table REPLICA IDENTITY FULL;`
+      - When using a method with a generic type like `track`, `broadcast` or `broadcastFlow`, you have to provide a [serializable class](/docs/reference/kotlin/installing#add-kotlinx-serialization-required-for-postgrest-and-realtime-serialization) as the type parameter.
+    examples:
+      - id: connect-to-realtime-client
+        name: Connect to Realtime 
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.realtime.connect()
+          ```
+      - id: liste-to-broadcasts
+        name: Listen to broadcasts
+        code: |
+          ```kotlin
+          @Serializable
+          data class Message(val content: String, val sender: String)
+          
+          val channel = client.realtime.createChannel("channelId") {
+              //optional config
+          }
+          
+          val broadcastFlow = channel.broadcastFlow<Message>(event = "message")
+      
+          //in a new coroutine (or use Flow.onEach().launchIn(scope)):
+          broadcastFlow.collect { //it: Message
+              println(it)
+          }
+          
+          channel.join(blockUntilJoined = true)
+          
+          channel.broadcast(event = "message", Message("I joined!", "John"))
+          ```   
+      - id: listen-to-presence-updates
+        name: Listen to presence updates
+        code: | 
+          ```kotlin
+          @Serializable
+          data class PresenceState(val username: String)
+          
+          val connectedUsers = mutableSetOf<PresenceState>()
+          val channel = client.realtime.createChannel("channelId") {
+              //optional config
+          }
+      
+          val presenceChangeFlow = channel.presenceChangeFlow()
+          
+          //in a new coroutine (or use Flow.onEach().launchIn(scope)):
+          presenceChangeFlow.collect {
+              connectedUsers += it.decodeJoinsAs<PresenceState>()
+              connectedUsers -= it.decodeLeavesAs<PresenceState>()
+          }
+          
+          channel.join(blockUntilJoined = true)
+          //send own state
+          channel.track(PresenceState(username = "John"))    
+      - id: listen-to-all-database-changes
+        name: Listen to all database changes
+        code: |
+          ```kotlin
+          val channel = client.realtime.createChannel("channelId") {
+              //optional config
+          }
+          val changeFlow = channel.postgresChangeFlow<PostgresAction>(schema = "public")
+          
+          //in a new coroutine (or use Flow.onEach().launchIn(scope)):
+          changeFlow.collect {
+              when(it) {
+                  is PostgresAction.Delete -> println("Deleted: ${it.oldRecord}")
+                  is PostgresAction.Insert -> println("Inserted: ${it.record}")
+                  is PostgresAction.Select -> println("Selected: ${it.record}")
+                  is PostgresAction.Update -> println("Updated: ${it.oldRecord} with ${it.record}")
+              }
+          }
+          
+          channel.join()
+          ```
+      - id: listen-to-a-specific-table
+        name: Listen to a specific table
+        code: |
+          ```kotlin
+          val channel = client.realtime.createChannel("channelId") {
+              //optional config
+          }
+          val changeFlow = channel.postgresChangeFlow<PostgresAction>(schema = "public") {
+              table = "users"
+          }
+          
+          //in a new coroutine (or use Flow.onEach().launchIn(scope)):
+          changeFlow.collect {
+              when(it) {
+                  is PostgresAction.Delete -> println("Deleted: ${it.oldRecord}")
+                  is PostgresAction.Insert -> println("Inserted: ${it.record}")
+                  is PostgresAction.Select -> println("Selected: ${it.record}")
+                  is PostgresAction.Update -> println("Updated: ${it.oldRecord} with ${it.record}")
+              }
+          }
+          
+          channel.join()
+          ```
+      - id: listen-to-inserts
+        name: Listen to inserts
+        code: |
+          ```kotlin
+          val channel = client.realtime.createChannel("channelId") {
+              //optional config
+          }
+          val changeFlow = channel.postgresChangeFlow<PostgresAction.Insert>(schema = "public") {
+              table = "users"
+          }
+      
+          //in a new coroutine (or use Flow.onEach().launchIn(scope)):
+          changeFlow.collect {
+              println(it.record)
+          }
+      
+          channel.join()
+          ```
+      - id: listen-to-updates
+        name: Listen to updates
+        description: |
+          By default, Supabase will send only the updated record. If you want to receive the previous values as well you can
+          enable full replication for the table you are listening too:
+
+          ```sql
+          alter table "your_table" replica identity full;
+          ```
+        code: |
+          ```kotlin
+          val channel = client.realtime.createChannel("channelId") {
+              //optional config
+          }
+          val changeFlow = channel.postgresChangeFlow<PostgresAction.Update>(schema = "public") {
+              table = "users"
+          }
+      
+          //in a new coroutine (or use Flow.onEach().launchIn(scope)):
+          changeFlow.collect {
+              println(it.record)
+              println(it.oldRecord)
+          }
+      
+          channel.join()
+          ```
+      - id: listen-to-deletes
+        name: Listen to deletes
+        description: |
+          By default, Supabase does not send deleted records. If you want to receive the deleted record you can
+          enable full replication for the table you are listening too:
+
+          ```sql
+          alter table "your_table" replica identity full;
+          ```
+        code: |
+          ```kotlin
+          val channel = client.realtime.createChannel("channelId") {
+              //optional config
+          }
+          val changeFlow = channel.postgresChangeFlow<PostgresAction.Delete>(schema = "public") {
+              table = "users"
+          }
+      
+          //in a new coroutine (or use Flow.onEach().launchIn(scope)):
+          changeFlow.collect {
+              println(it.oldRecord)
+          }
+      
+          channel.join()
+          ```
+      - id: listening-to-row-level-changes
+        name: Listen to row level changes
+        description: You can listen to individual rows using the format `{table}:{col}=eq.{val}` - where `{col}` is the column name, and `{val}` is the value which you want to match.
+        code: |
+          ```kotlin
+          val channel = client.realtime.createChannel("channelId") {
+             //optional config
+          }
+          val changeFlow = channel.postgresChangeFlow<PostgresAction.Delete>(schema = "public") {
+              table = "users"
+              filter = "id.eq.1"
+          }
+      
+          //in a new coroutine:
+          changeFlow.collect {
+              println(it.oldRecord)
+          }
+      
+          channel.join()
+          ```
+
+  - id: remove-channel
+    description: |
+      Unsubscribes and removes Realtime channel from Realtime client.
+    title: 'removeChannel()'
+    notes: |
+      - Removing a channel is a great way to maintain the performance of your project's Realtime service as well as your database if you're listening to Postgres changes.
+      - Supabase will automatically handle cleanup 30 seconds after a client is disconnected, but unused channels may cause degradation as more clients are simultaneously subscribed.
+    examples:
+      - id: removes-a-channel
+        name: Remove a channel
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val channel = client.realtime.createChannel("channelId") {
+              //optional config
+          }
+          //...
+          client.realtime.removeChannel(channel)
+          ```
+      - id: unsubscribe-channel
+        name: Unsubscribe from a channel
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val channel = client.realtime.createChannel("channelId") {
+              //optional config
+          }
+          //...
+          channel.leave()
+          ```
+  - id: list-buckets
+    title: listBuckets()
+    $ref: '@supabase/storage-js.packages/StorageBucketApi.default.listBuckets'
+    notes: |
+      - RLS policy permissions required:
+        - `buckets` table permissions: `select`
+        - `objects` table permissions: none
+      - Refer to the [Storage guide](/docs/guides/storage#access-control) on how access control works
+    examples:
+      - id: list-buckets
+        name: List buckets
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val buckets = client.storage.retrieveBuckets()
+          ```
+
+  - id: get-bucket
+    title: getBucket()
+    $ref: '@supabase/storage-js.packages/StorageBucketApi.default.getBucket'
+    notes: |
+      - RLS policy permissions required:
+        - `buckets` table permissions: `select`
+        - `objects` table permissions: none
+      - Refer to the [Storage guide](/docs/guides/storage#access-control) on how access control works
+    examples:
+      - id: get-bucket
+        name: Get bucket
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val bucket = client.storage.retrieveBucketById(bucketId = "avatars")
+          ```
+
+  - id: create-bucket
+    title: createBucket()
+    $ref: '@supabase/storage-js.packages/StorageBucketApi.default.createBucket'
+    notes: |
+      - RLS policy permissions required:
+        - `buckets` table permissions: `insert`
+        - `objects` table permissions: none
+      - Refer to the [Storage guide](/docs/guides/storage#access-control) on how access control works
+    examples:
+      - id: create-bucket
+        name: Create bucket
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.storage.createBucket(name = "icons", id = "icons") {
+              public = true
+              fileSizeLimit = 5.megabytes
+          }
+          ```
+
+  - id: empty-bucket
+    title: emptyBucket()
+    $ref: '@supabase/storage-js.packages/StorageBucketApi.default.emptyBucket'
+    notes: |
+      - RLS policy permissions required:
+        - `buckets` table permissions: `select`
+        - `objects` table permissions: `select` and `delete`
+      - Refer to the [Storage guide](/docs/guides/storage#access-control) on how access control works
+    examples:
+      - id: empty-bucket
+        name: Empty bucket
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.storage.emptyBucket(bucketId = "icons")
+          ```
+  - id: delete-bucket
+    title: deleteBucket()
+    $ref: '@supabase/storage-js.packages/StorageBucketApi.default.deleteBucket'
+    notes: |
+      - RLS policy permissions required:
+        - `buckets` table permissions: `select` and `delete`
+        - `objects` table permissions: none
+      - Refer to the [Storage guide](/docs/guides/storage#access-control) on how access control works
+    examples:
+      - id: delete-bucket
+        name: Delete bucket
+        isSpotlight: true
+        code: |
+          ```kotlin
+          client.storage.deleteBucket(bucketId = "icons")
+          ```
+
+  - id: from-upload
+    title: from.upload()
+    $ref: '@supabase/storage-js.packages/StorageFileApi.default.upload'
+    notes: |
+      - RLS policy permissions required:
+        - `buckets` table permissions: none
+        - `objects` table permissions: `insert`
+      - Refer to the [Storage guide](/docs/guides/storage#access-control) on how access control works
+      - Resumable uploads use a `Disk` cache by default to store the upload urls. You can customize that in the GoTrue config by changing the `resumable.cache` property.
+    examples:
+      - id: upload-file
+        name: Upload file
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val bucket = client.storage["avatars"]
+          bucket.upload("myIcon.png", byteArray, upsert = false)
+          //on JVM you can use java.io.File
+          bucket.upload("myIcon.png", file, upsert = false)
+          ```
+      - id: upload-file-with-progress
+        name: Upload file with progress
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val bucket = client.storage["avatars"]
+          bucket.uploadAsFlow("test.png", byteArrayOf()).collect {
+              when(it) {
+                  is UploadStatus.Progress -> println("Progress: ${it.totalBytesSend.toFloat() / it.contentLength * 100}%")
+                  is UploadStatus.Success -> println("Success")
+              }
+          }
+          ```    
+      - id: create-resumable-upload
+        name: Create resumable upload
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val bucket = client.storage["avatars"]
+          //JVM/Android:
+          val upload = bucket.resumable.createOrContinueUpload("icon.png", File("icon.png"))
+          //Other platforms:
+          val upload = bucket.resumable.createOrContinueUpload(data = byteArray, source = "this is for continuing previous uploads later", path = "icon.png")
+          val upload = bucket.resumable.createOrContinueUpload( //Probably better to write an extension function
+              channel = { offset -> /* create ByteReadChannel and seek to offset */ },
+              source = "this is for continuing previous uploads later",
+              size = dataSize,
+              path = "icon.png"
+          )                
+          ```   
+      - id: start-resumable-upload
+        name: Start and resumable upload
+        isSpotlight: true    
+        code: |
+          ```kotlin
+          upload.startOrResumeUploading()
+          ```
+      - id: pause-resumable-upload
+        name: Pause resumable upload
+        code: |
+          ```kotlin
+          upload.pause()
+          ```
+      - id: cancel-resumable-upload
+        name: Cancel resumable upload
+        code: |
+          ```kotlin
+          upload.cancel()
+          ```    
+        description: |
+          This will also remove the upload url from the cache
+      - id: listen-to-upload-state
+        name: Listen to the resumable upload state
+        code: |
+          ```kotlin
+          upload.stateFlow.collect {
+              println("Progress: ${it.progress * 100}%")
+              println("Paused: ${it.paused}")
+              println("Is done: ${it.isDone}")
+          }
+          ```    
+      - id: continue-previous-upload
+        name: Continue previous uploads
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val bucket = client.storage["avatars"]
+          
+          //only on JVM/Android:
+          bucket.resumable.continuePreviousFileUploads()
+              .map { it.await() } //await all uploads. This just makes sure the uploads have an update-to-date url. You can also do this in parallel
+              .forEach { upload ->
+                  upload.startOrResumeUploading()
+              }
+      
+          //on other platforms you may have to continue uploads from the source (Probably better to write an extension function): 
+          bucket.resumable.continuePreviousUploads { source, offset ->
+              //create ByteReadChannel from source and seek to offset
+          }
+              .map { it.await() } //await all uploads. This just makes sure the uploads have an update-to-date url. You can also do this in parallel
+              .forEach { upload ->
+                  upload.startOrResumeUploading()
+              }
+          ```          
+
+  - id: from-update
+    title: from.update()
+    $ref: '@supabase/storage-js.packages/StorageFileApi.default.update'
+    notes: |
+      - RLS policy permissions required:
+        - `buckets` table permissions: none
+        - `objects` table permissions: `update` and `select`
+      - Refer to the [Storage guide](/docs/guides/storage#access-control) on how access control works
+    examples:
+      - id: update-file
+        name: Update file
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val bucket = client.storage["avatars"]
+          bucket.update("myIcon.png", byteArray, upsert = false)
+          //on JVM you can use java.io.File
+          bucket.update("myIcon.png", file, upsert = false)
+          ```
+
+  - id: from-move
+    title: from.move()
+    $ref: '@supabase/storage-js.packages/StorageFileApi.default.move'
+    notes: |
+      - RLS policy permissions required:
+        - `buckets` table permissions: none
+        - `objects` table permissions: `update` and `select`
+      - Refer to the [Storage guide](/docs/guides/storage#access-control) on how access control works
+    examples:
+      - id: move-file
+        name: Move file
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val bucket = client.storage["avatars"]
+          bucket.move("icon1.png", "icon2.png")
+          ```
+
+  - id: from-create-signed-url
+    title: from.createSignedUrl()
+    $ref: '@supabase/storage-js.packages/StorageFileApi.default.createSignedUrl'
+    notes: |
+      - RLS policy permissions required:
+        - `buckets` table permissions: none
+        - `objects` table permissions: `select`
+      - Refer to the [Storage guide](/docs/guides/storage#access-control) on how access control works
+    examples:
+      - id: create-signed-url
+        name: Create Signed URL
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val bucket = client.storage["avatars"]
+          val url = bucket.createSignedUrl(path = "icon.png", expiresIn = 3.minutes)
+          ```
+      - id: create-signed-url-with-transformation
+        name: Create Signed URL with transformation
+        code: |
+          ```kotlin
+          val bucket = client.storage["avatars"]
+          val url = bucket.createSignedUrl(path = "icon.png", expiresIn = 3.minutes) {
+              size(100, 100)
+              fill()
+              quality = 80
+          }    
+          ```
+  - id: from-download
+    title: from.download()
+    $ref: '@supabase/storage-js.packages/StorageFileApi.default.download'
+    notes: |
+      - RLS policy permissions required:
+        - `buckets` table permissions: none
+        - `objects` table permissions: `select`
+      - Refer to the [Storage guide](/docs/guides/storage#access-control) on how access control works
+    examples:
+      - id: download-file-authenticated
+        name: Download file from non-public bucket
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val bucket = client.storage["avatars"]
+          val bytes = bucket.downloadAuthenticated("test.png")
+          //or on JVM:
+          bucket.downloadAuthenticatedTo("test.png", File("test.png"))
+          ```
+      - id: download-file-public
+        name: Download file from public bucket
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val bucket = client.storage["avatars"]
+          val bytes = bucket.downloadPublic("test.png")
+          //or on JVM:
+          bucket.downloadPublicTo("test.png", File("test.png"))
+          ```    
+      - id: download-with-transformation
+        name: Download file with transformation
+        code: |
+          ```kotlin
+          val bucket = client.storage["avatars"]
+          val bytes = bucket.downloadPublic("test.png") {
+              size(100, 100)
+              fill()
+              quality = 100
+          }
+          //or on JVM:
+          bucket.downloadPublicTo("test.png", File("test.png")) {
+              size(100, 100)
+              fill()
+              quality = 100
+          }
+          ```  
+      - id: download-with-progress
+        name: Download file with progress 
+        code: |
+          ```kotlin
+          val bucket = client.storage["avatars"]
+          bucket.downloadAuthenticatedAsFlow("icon.png").collect {
+              when(it) {
+                  is DownloadStatus.ByteData -> println("Downloaded ${it.data.size} bytes")
+                  is DownloadStatus.Progress -> println("Downloaded ${it.totalBytesReceived.toFloat() / it.contentLength * 100}%")
+                  DownloadStatus.Success -> println("Downloaded successfully")
+              }
+          }
+          //or on JVM:
+          bucket.downloadAuthenticatedToAsFlow("icon.png", File("icon.png")).collect {
+              when(it) {
+                  is DownloadStatus.Progress -> println("Downloaded ${it.totalBytesReceived.toFloat() / it.contentLength * 100}%")
+                  DownloadStatus.Success -> println("Downloaded successfully")
+                  else -> {} //The ByteData status will never occur as we are writing directly to a file
+              }
+          }
+          ```       
+  - id: from-remove
+    title: from.remove()
+    $ref: '@supabase/storage-js.packages/StorageFileApi.default.remove'
+    notes: |
+      - RLS policy permissions required:
+        - `buckets` table permissions: none
+        - `objects` table permissions: `delete` and `select`
+      - Refer to the [Storage guide](/docs/guides/storage#access-control) on how access control works
+    examples:
+      - id: delete-file
+        name: Delete file
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val bucket = client.storage["avatars"]
+          bucket.delete("test.png", "test2.png")
+          ```
+
+  - id: from-list
+    title: from.list()
+    $ref: '@supabase/storage-js.packages/StorageFileApi.default.list'
+    notes: |
+      - RLS policy permissions required:
+        - `buckets` table permissions: none
+        - `objects` table permissions: `select`
+      - Refer to the [Storage guide](/docs/guides/storage#access-control) on how access control works
+    examples:
+      - id: list-files-in-a-bucket
+        name: List files in a bucket
+        isSpotlight: true
+        code: |
+          ```kotlin
+          val bucket = client.storage["avatars"]
+          val files = bucket.list()
+          ```
diff --git a/studio/components/interfaces/Organization/BillingSettings/TaxID/TaxID.tsx b/studio/components/interfaces/Organization/BillingSettings/TaxID/TaxID.tsx
index 31dffe44d4f..02a33a6333e 100644
--- a/studio/components/interfaces/Organization/BillingSettings/TaxID/TaxID.tsx
+++ b/studio/components/interfaces/Organization/BillingSettings/TaxID/TaxID.tsx
@@ -1,6 +1,6 @@
 import { FC, useEffect, useState } from 'react'
 import { isEqual } from 'lodash'
-import { Input, Button, IconPlus, Select, IconX } from 'ui'
+import { Input, Button, IconPlus, IconX, Listbox } from 'ui'
 import { PermissionAction } from '@supabase/shared-types/out/constants'
 
 import { checkPermissions, useFlag, useStore } from 'hooks'
@@ -193,19 +193,24 @@ const TaxID: FC<Props> = ({ loading, taxIds, onTaxIdsUpdated }) => {
                     const selectedTaxId = TAX_IDS.find((option) => option.name === taxId.name)
                     return (
                       <div key={`tax-id-${idx}`} className="flex items-center space-x-2">
-                        <Select
+                        <Listbox
                           value={selectedTaxId?.name}
-                          onChange={(e: any) => onUpdateTaxId(taxId.id, 'name', e.target.value)}
+                          onChange={(e: any) => onUpdateTaxId(taxId.id, 'name', e)}
                           disabled={!canUpdateTaxIds}
+                          className="w-[200px]"
                         >
                           {TAX_IDS.sort((a, b) => a.country.localeCompare(b.country)).map(
                             (option) => (
-                              <Select.Option key={option.name} value={option.name}>
+                              <Listbox.Option
+                                key={option.name}
+                                value={option.name}
+                                label={option.name}
+                              >
                                 {option.country} - {option.name}
-                              </Select.Option>
+                              </Listbox.Option>
                             )
                           )}
-                        </Select>
+                        </Listbox>
                         <Input
                           value={taxId.value}
                           placeholder={selectedTaxId?.placeholder ?? ''}
diff --git a/studio/components/interfaces/TableGridEditor/APIDocumentationPanel.tsx b/studio/components/interfaces/TableGridEditor/APIDocumentationPanel.tsx
index 4565ba6ee28..d03907ffbef 100644
--- a/studio/components/interfaces/TableGridEditor/APIDocumentationPanel.tsx
+++ b/studio/components/interfaces/TableGridEditor/APIDocumentationPanel.tsx
@@ -3,7 +3,7 @@ import { SidePanel, IconBookOpen } from 'ui'
 
 import { useStore } from 'hooks'
 import { useParams } from 'common/hooks'
-import { GeneralContent, ResourceContent } from '../Docs'
+import { ResourceContent } from '../Docs'
 import LangSelector from '../Docs/LangSelector'
 import GeneratingTypes from '../Docs/GeneratingTypes'
 import ActionBar from './SidePanelEditor/ActionBar'
@@ -105,14 +105,6 @@ const APIDocumentationPanel = ({ visible, onClose }: APIDocumentationPanelProps)
                       autoApiService={autoApiService}
                     />
                   </div>
-                  <GeneralContent
-                    autoApiService={autoApiService}
-                    selectedLang={selectedLang}
-                    showApiKey={true}
-                    page={page}
-                  />
-
-                  <GeneratingTypes selectedLang={selectedLang} />
 
                   {jsonSchema?.definitions && (
                     <ResourceContent
@@ -126,6 +118,9 @@ const APIDocumentationPanel = ({ visible, onClose }: APIDocumentationPanelProps)
                       refreshDocs={async () => await refetch()}
                     />
                   )}
+                  <div className="mt-8">
+                    <GeneratingTypes selectedLang={selectedLang} />
+                  </div>
                 </>
               ) : (
                 <div className="p-6 mx-auto text-center sm:w-full md:w-3/4">
diff --git a/studio/components/to-be-cleaned/Docs/Pages/Introduction.tsx b/studio/components/to-be-cleaned/Docs/Pages/Introduction.tsx
index a125f6c4006..c64f2f5457e 100644
--- a/studio/components/to-be-cleaned/Docs/Pages/Introduction.tsx
+++ b/studio/components/to-be-cleaned/Docs/Pages/Introduction.tsx
@@ -1,24 +1,6 @@
-import Image from 'next/image'
 import { AutoApiService } from 'data/config/project-api-query'
-import { BASE_PATH } from 'lib/constants'
 import Snippets from '../Snippets'
 import CodeSnippet from '../CodeSnippet'
-import { useTheme } from 'common'
-
-const libs = [
-  {
-    name: 'Javascript',
-    url: 'https://supabase.com/docs/reference/javascript/introduction',
-    icon: 'javascript',
-  },
-  { name: 'Flutter', url: 'https://supabase.com/docs/reference/dart/introduction', icon: 'dart' },
-  {
-    name: 'Python',
-    url: 'https://supabase.com/docs/reference/python/introduction',
-    icon: 'python',
-  },
-  { name: 'C#', url: 'https://supabase.com/docs/reference/csharp/introduction', icon: 'csharp' },
-]
 
 interface Props {
   autoApiService: AutoApiService
@@ -26,84 +8,10 @@ interface Props {
 }
 
 export default function Introduction({ autoApiService, selectedLang }: Props) {
-  const { isDarkMode } = useTheme()
-
   return (
     <>
-      <h2 className="doc-heading">Introduction</h2>
-      <div className="doc-section doc-section--introduction">
-        <article className="text ">
-          <p>
-            This API provides an easy way to integrate with your Postgres database. The API
-            documentation below is specifically generated for your database.
-          </p>
-          <p>
-            This is an <b>auto-generating</b> API, so as you make changes to your database, this
-            documentation will change too.
-          </p>
-          <p>
-            <b>Note:</b> if you make changes to a field (column) name or type, the API interface for
-            those fields will change correspondingly. Therefore, please make sure to update your API
-            implementation accordingly whenever you make changes to your Supabase schema from the
-            graphical interface.
-          </p>
-
-          <div className="not-prose mb-6">
-            <p>Read the reference documentation:</p>
-            <div className="flex items-center gap-4 mt-2">
-              {libs.map((lib, i) => (
-                <a
-                  key={i}
-                  href={lib.url}
-                  target="_blank"
-                  rel="noreferrer"
-                  className="
-                  flex items-center gap-1 rounded-md px-3 py-1
-                  bg-scale-300 dark:bg-scale-500
-                  hover:bg-scale-500 hover:dark:bg-scale-700 transition-colors
-                  !text-scale-1100 hover:text-scale-1100
-                  "
-                >
-                  <Image
-                    src={`${BASE_PATH}/img/icons/reference-${
-                      isDarkMode ? lib.icon : `${lib.icon}-light`
-                    }.svg`}
-                    width={16}
-                    height={16}
-                    alt={lib.name}
-                  />
-                  {lib.name}
-                </a>
-              ))}
-            </div>
-          </div>
-        </article>
-      </div>
-
-      <h2 className="doc-heading">API URL</h2>
-      <div className="doc-section ">
-        <article className="text ">
-          <p>The API URL for your project.</p>
-        </article>
-        <article className="code">
-          <CodeSnippet
-            selectedLang={selectedLang}
-            snippet={Snippets.endpoint(autoApiService.endpoint)}
-          />
-        </article>
-      </div>
-
-      <h2 className="doc-heading">Client Libraries</h2>
       <div className="doc-section doc-section--client-libraries">
-        <article className="text">
-          <p>Your API consists of both a RESTful interface and a Realtime interface.</p>
-          <p>
-            For interacting with the Realtime streams, we provide client libraries that handle the
-            websockets.
-          </p>
-        </article>
         <article className="code">
-          <CodeSnippet selectedLang={selectedLang} snippet={Snippets.install()} />
           <CodeSnippet
             selectedLang={selectedLang}
             snippet={Snippets.init(autoApiService.endpoint)}
diff --git a/studio/components/ui/Charts/AreaChart.tsx b/studio/components/ui/Charts/AreaChart.tsx
index c917fe45e71..d7050f5926a 100644
--- a/studio/components/ui/Charts/AreaChart.tsx
+++ b/studio/components/ui/Charts/AreaChart.tsx
@@ -113,7 +113,7 @@ const AreaChart: React.FC<AreaChartProps> = ({
         </RechartAreaChart>
       </Container>
       {data && (
-        <div className="text-scale-900 -mt-5 flex items-center justify-between text-xs">
+        <div className="text-scale-900 -mt-2 flex items-center justify-between text-xs">
           <span>{dayjs(data[0][xAxisKey]).format(customDateFormat)}</span>
           <span>{dayjs(data[data?.length - 1]?.[xAxisKey]).format(customDateFormat)}</span>
         </div>
diff --git a/studio/pages/api/storage/[ref]/buckets/[id]/objects/sign.ts b/studio/pages/api/storage/[ref]/buckets/[id]/objects/sign.ts
index d235508ab84..c89791ab5f3 100644
--- a/studio/pages/api/storage/[ref]/buckets/[id]/objects/sign.ts
+++ b/studio/pages/api/storage/[ref]/buckets/[id]/objects/sign.ts
@@ -29,7 +29,7 @@ const handlePost = async (req: NextApiRequest, res: NextApiResponse) => {
 
   // change the domain name to the SUPABASE_PUBLIC_URL since SUPABASE_URL is not accessible from the client
   const signedUrl = new URL(data.signedUrl)
-  signedUrl.hostname = new URL(process.env.SUPABASE_PUBLIC_URL!).hostname
+  signedUrl.host = new URL(process.env.SUPABASE_PUBLIC_URL!).host
   data.signedUrl = signedUrl.href
 
   return res.status(200).json(data)
diff --git a/studio/styles/ui.scss b/studio/styles/ui.scss
index e080e04ecde..e2cb9d9e6cb 100644
--- a/studio/styles/ui.scss
+++ b/studio/styles/ui.scss
@@ -255,7 +255,7 @@
   }
 
   &.Docs--table-editor .doc-section__table-name {
-    @apply mt-12;
+    @apply mt-4;
   }
 
   .text {
@@ -448,4 +448,4 @@
   line {
     @apply stroke-scale-1000;
   }
-}
\ No newline at end of file
+}
diff --git a/supabase/functions/og-images/handler.tsx b/supabase/functions/og-images/handler.tsx
index 1e7b9ae98bf..27e1de9e683 100644
--- a/supabase/functions/og-images/handler.tsx
+++ b/supabase/functions/og-images/handler.tsx
@@ -30,7 +30,7 @@ export async function handler(req: Request) {
 
   switch (site) {
     case 'docs':
-      return new ImageResponse(( <Docs title={title} description={description} type={type} icon={icon} /> ),
+      return new ImageResponse(( <Docs title={title} description={description !== 'undefined' ? description : ''} type={type} icon={icon} /> ),
         {
           width: 1200,
           height: 630,