docs: fix links

Author: larbish

docus/content/1.getting-started/1.introduction.md

@@ -109,7 +109,7 @@ Default:
 - `callback`: This is the path the user will be redirect to after supabase login redirection. Should match configured `redirectTo` option of your [signIn method](https://supabase.com/docs/reference/javascript/auth-signinwithoauth). Should also be configured in your Supabase dashboard under `Authentication -> URL Configuration -> Redirect URLs`.
 - `include`: Routes to include in the redirect. `['/admin(/*)?']` will enable the redirect only for the `admin` page and all sub-pages.
 - `exclude`: Routes to exclude from the redirect. `['/foo', '/bar/**']` will exclude the `foo` page and all pages in your `bar` folder.
-- `saveRedirectToCookie`: Automatically sets a cookie containing the path an unauthenticated user tried to access. The value can be accessed using the [`useSupabaseCookieRedirect`](/usage/composables/usesupabasecookieredirect) composable to redirect the user to the page they previously tried to visit. 
+- `saveRedirectToCookie`: Automatically sets a cookie containing the path an unauthenticated user tried to access. The value can be accessed using the [`useSupabaseCookieRedirect`](/composables/usesupabasecookieredirect) composable to redirect the user to the page they previously tried to visit. 
 
 ### `cookiePrefix`
 
@@ -163,7 +163,7 @@ Default:
 
 Customize the Supabase client options [available here](https://supabase.com/docs/reference/javascript/initializing#parameters).
 
-If `useSsrCookies` is enabled, these options will be merged with values from `@supabase/ssr`, and some of the [options cannot be customized](/get-started#usessrcookies).
+If `useSsrCookies` is enabled, these options will be merged with values from `@supabase/ssr`, and some of the [options cannot be customized](/getting-started/introduction#usessrcookies).
 
 ```ts
   clientOptions: {
@@ -179,7 +179,7 @@ If `useSsrCookies` is enabled, these options will be merged with values from `@s
 ### `cookieName`
 
 ::warning
-This option is deprecated, use [`cookiePrefix`](/get-started#cookieprefix) instead.
+This option is deprecated, use [`cookiePrefix`](/getting-started/introduction#cookieprefix) instead.
 ::
 
 Default: `sb`
@@ -189,7 +189,7 @@ Cookie name used for storing the redirect path when using the `redirectOptions.c
 ### `redirectOptions.cookieRedirect`
 
 ::warning
-This option is deprecated, use [`redirectOptions.saveRedirectToCookie`](/get-started#redirectoptions) instead.
+This option is deprecated, use [`redirectOptions.saveRedirectToCookie`](/getting-started/introduction#redirectoptions) instead.
 ::
 
 Default: `false`
@@ -198,7 +198,7 @@ Use the `cookieRedirect` option to store the redirect path in a cookie.
 
 ## Demo
 
-A live demo is made for you to see this module in action on [n3-supabase.netlify.app](https://n3-supabase.netlify.app), read more in the [demo section](/demo).
+A live demo is made for you to see this module in action on [n3-supabase.netlify.app](https://n3-supabase.netlify.app), read more in the [demo section](/getting-started/demo).
 
 [![Supabase demo with Nuxt 3](https://user-images.githubusercontent.com/904724/160422461-8f87500a-8dec-4413-86b2-ba04e1b2d17b.png)](https://n3-supabase.netlify.app)
 

docus/content/1.getting-started/2.authentication.md

@@ -8,12 +8,12 @@ With the default options, the module requires a log-in page and a confirm page t
 All you need to do is to create a `login.vue` and `confirm.vue` page in the `pages` folder.
 
 ::tip
-For advanced users who want to implement the auth behaviour themselves, you can disable or override the [redirect options](/get-started#redirect).
+For advanced users who want to implement the auth behaviour themselves, you can disable or override the [redirect options](/getting-started/introduction#redirect).
 ::
 
 ## Log-in page - `/login`
 
-Each time a user is trying to access a page that needs authentication, he will automatically be redirected to the configured log in page. If you want to allow access to "public" page, you just need to add them in the [exclude](/get-started#redirectoptions) redirect option. Alternatively, you can enable the redirect only for certain routes using the [include](/get-started#redirectoptions) redirect option.
+Each time a user is trying to access a page that needs authentication, he will automatically be redirected to the configured log in page. If you want to allow access to "public" page, you just need to add them in the [exclude](/getting-started/introduction#redirectoptions) redirect option. Alternatively, you can enable the redirect only for certain routes using the [include](/getting-started/introduction#redirectoptions) redirect option.
 
 ::warning
 Ensure to activate the authentication providers you want in the Supabase Dashboard under `Authentication -> Providers`.
@@ -49,7 +49,7 @@ const signInWithOtp = async () => {
 </template>
 ```
 
-Once the authorization flow is triggered using the `auth` wrapper of the [useSupabaseClient](/usage/composables/usesupabaseclient) composable, the session management is handled automatically and the user will be redirected to the page you specify in the redirect option (`/confirm` by default).
+Once the authorization flow is triggered using the `auth` wrapper of the [useSupabaseClient](/composables/usesupabaseclient) composable, the session management is handled automatically and the user will be redirected to the page you specify in the redirect option (`/confirm` by default).
 
 ## Confirm page - `/confirm`
 
@@ -78,9 +78,9 @@ watch(user, () => {
 
 ### Redirect path
 
-You can easily handle redirection to the initial requested route after login using the [`useSupabaseCookieRedirect`](/usage/composables/usesupabasecookieredirect) composable and the [`saveRedirectToCookie`](/get-started#redirectoptions) option.
+You can easily handle redirection to the initial requested route after login using the [`useSupabaseCookieRedirect`](/composables/usesupabasecookieredirect) composable and the [`saveRedirectToCookie`](/getting-started/introduction#redirectoptions) option.
 
-By setting the `saveRedirectToCookie` option to `true`, the module will automatically save the current path to a cookie when the user is redirected to the login page. When the user logs in, you can then retrieve the saved path from the cookie and redirect the user to it on the [`/confirm`](/authentication#confirm-page-confirm) page:
+By setting the `saveRedirectToCookie` option to `true`, the module will automatically save the current path to a cookie when the user is redirected to the login page. When the user logs in, you can then retrieve the saved path from the cookie and redirect the user to it on the [`/confirm`](/getting-started/authentication#confirm-page-confirm) page:
 
 ```vue [pages/confirm.vue]
 <script setup lang="ts">
@@ -103,5 +103,5 @@ watch(user, () => {
 ```
 
 ::tip
-If you want to manually set the redirect path, you can do so by disabling [`saveRedirectToCookie`](/get-started#redirectoptions), and then set the value using the  [`useSupabaseCookieRedirect`](/usage/composables/usesupabasecookieredirect) composable directly.
+If you want to manually set the redirect path, you can do so by disabling [`saveRedirectToCookie`](/getting-started/introduction#redirectoptions), and then set the value using the  [`useSupabaseCookieRedirect`](/composables/usesupabasecookieredirect) composable directly.
 ::

docus/content/1.getting-started/3.demo.md

@@ -13,8 +13,8 @@ You can play with the demo on [n3-supabase.netlify.app](https://n3-supabase.netl
 
 ## Running locally
 
-Follow the instruction in the [demo Readme](https://github.com/nuxt-community/supabase-module/tree/main/demo).
+Follow the instruction in the [demo Readme](https://github.com/nuxt-community/supabase-module/tree/main/getting-started/demo).
 
 ## Source code
 
-The source code is available on Github in the [demo/ directory](https://github.com/nuxt-community/supabase-module/tree/main/demo).
+The source code is available on Github in the [demo/ directory](https://github.com/nuxt-community/supabase-module/tree/main/getting-started/demo).

docus/content/2.composables/useSupabaseClient.md

@@ -7,14 +7,14 @@ description: Make requests to the Supabase API with the useSupabaseClient compos
 
 This composable is using [supabase-js](https://github.com/supabase/supabase-js/) under the hood, it gives access to the [Supabase client](https://supabase.com/docs/reference/javascript/initializing).
 
-> The client is initialized with the `SUPABASE_KEY` you must have in your `.env` file. It establishes the connection with the database and make use of user JWT to apply [RLS Policies](https://supabase.com/docs/learn/auth-deep-dive/auth-row-level-security) implemented in Supabase. If you want to bypass policies, you can use the [serverSupabaseServiceRole](/usage/services/serversupabaseservicerole).
+> The client is initialized with the `SUPABASE_KEY` you must have in your `.env` file. It establishes the connection with the database and make use of user JWT to apply [RLS Policies](https://supabase.com/docs/learn/auth-deep-dive/auth-row-level-security) implemented in Supabase. If you want to bypass policies, you can use the [serverSupabaseServiceRole](/services/serversupabaseservicerole).
 
 ## Authentication
 
 The useSupabaseClient composable is providing all methods to manage authorization under `useSupabaseClient().auth`. For more details please see the [supabase-js auth documentation](https://supabase.com/docs/reference/javascript/auth-api). Here is an example for signing in and out:
 
 ::tip
-If you want a full explanation on how to handle the authentication process, please read this [section](/authentication).
+If you want a full explanation on how to handle the authentication process, please read this [section](/getting-started/authentication).
 ::
 
 ```ts
@@ -38,7 +38,7 @@ const signOut = async () => {
 </script>
 ```
 
-Please also take a look at [Get Started](/authentication) for the authorization flow.
+Please also take a look at [Get Started](/getting-started/authentication) for the authorization flow.
 
 ## Database Request
 
@@ -101,7 +101,7 @@ onUnmounted(() => {
 
 ## Typescript
 
-Database typings are passed to the client out of the box if the database generated types are found at `./types/database.types.ts` or [your configured types path](/get-started#types). Check Supabase [documentation](https://supabase.com/docs/reference/javascript/release-notes#typescript-support) for further information.
+Database typings are passed to the client out of the box if the database generated types are found at `./types/database.types.ts` or [your configured types path](/getting-started/introduction#types). Check Supabase [documentation](https://supabase.com/docs/reference/javascript/release-notes#typescript-support) for further information.
 
 ```shell
 ## Generate types from live database

docus/content/2.composables/useSupabaseCookieRedirect.md

@@ -7,9 +7,9 @@ The `useSupabaseCookieRedirect` composable provides a simple way to handle stori
 
 ## Usage
 
-This composable can be [manually used](#manual-usage) to save and retrieve a redirect path. However, the redirect path can automatically be set via the `saveRedirectToCookie` option in the [redirectOptions](/get-started#redirectoptions).
+This composable can be [manually used](#manual-usage) to save and retrieve a redirect path. However, the redirect path can automatically be set via the `saveRedirectToCookie` option in the [redirectOptions](/getting-started/introduction#redirectoptions).
 
-The redirect path is not automatically used. Instead you must implement the logic to redirect the user to the saved path, for example on the [`/confirm`](/authentication#confirm-page-confirm) page.
+The redirect path is not automatically used. Instead you must implement the logic to redirect the user to the saved path, for example on the [`/confirm`](/getting-started/authentication#confirm-page-confirm) page.
 
 ```vue
 <script setup>
@@ -51,4 +51,4 @@ const currentPath = redirectInfo.path.value
 const path = redirectInfo.pluck()
 ``` 
 
-The cookie is saved with the name `{cookiePrefix}-redirect-path` where `cookiePrefix` is defined in the [runtime config](/get-started#runtime-config).
+The cookie is saved with the name `{cookiePrefix}-redirect-path` where `cookiePrefix` is defined in the [runtime config](/getting-started/introduction#runtime-config).

docus/content/2.composables/useSupabaseSession.md

@@ -12,16 +12,16 @@ const session = useSupabaseSession()
 ```
 
 ::tip
-If you just need the User's information you can use [useSupabaseUser](/usage/composables/usesupabaseuser) which returns just the User information of the session. 
+If you just need the User's information you can use [useSupabaseUser](/composables/usesupabaseuser) which returns just the User information of the session. 
 ::
 
 ## Auth middleware
 
 ::tip
-By default, the module is implementing a redirect middleware. All pages of your application are automatically redirected to the [login](/get-started#redirectoptions) page. However, you can allow redirection to "public" pages by setting the [exclude](/get-started#redirectoptions) redirect option. Alternatively, you can enable the redirect only for certain routes using the [include](/get-started#redirectoptions) redirect option.
+By default, the module is implementing a redirect middleware. All pages of your application are automatically redirected to the [login](/getting-started/introduction#redirectoptions) page. However, you can allow redirection to "public" pages by setting the [exclude](/getting-started/introduction#redirectoptions) redirect option. Alternatively, you can enable the redirect only for certain routes using the [include](/getting-started/introduction#redirectoptions) redirect option.
 ::
 
-If the [redirect](/get-started#redirect) option is disabled, you can protect your authenticated routes by creating a custom middleware in your project, here is an example:
+If the [redirect](/getting-started/introduction#redirect) option is disabled, you can protect your authenticated routes by creating a custom middleware in your project, here is an example:
 
 ```ts [middleware/auth.ts]
 export default defineNuxtRouteMiddleware((to, _from) => {

docus/content/2.composables/useSupabaseUser.md

@@ -14,10 +14,10 @@ const user = useSupabaseUser()
 ## Auth middleware
 
 ::tip
-By default, the module is implementing a redirect middleware. All pages of your application are automatically redirected to the [login](/get-started#redirectoptions) page. However, you can allow redirection to "public" pages by setting the [exclude](/get-started#redirectoptions) redirect option. Alternatively, you can enable the redirect only for certain routes using the [include](/get-started#redirectoptions) redirect option.
+By default, the module is implementing a redirect middleware. All pages of your application are automatically redirected to the [login](/getting-started/introduction#redirectoptions) page. However, you can allow redirection to "public" pages by setting the [exclude](/getting-started/introduction#redirectoptions) redirect option. Alternatively, you can enable the redirect only for certain routes using the [include](/getting-started/introduction#redirectoptions) redirect option.
 ::
 
-If the [redirect](/get-started#redirect) option is disabled, you can protect your authenticated routes by creating a custom middleware in your project, here is an example:
+If the [redirect](/getting-started/introduction#redirect) option is disabled, you can protect your authenticated routes by creating a custom middleware in your project, here is an example:
 
 ```ts [middleware/auth.ts]
 export default defineNuxtRouteMiddleware((to, _from) => {

docus/content/3.services/1.serverSupabaseClient.md

@@ -7,7 +7,7 @@ description: Make requests to the Supabase API on server side with the serverSup
 This section assumes you're familiar with [Nitro](https://v3.nuxtjs.org/guide/concepts/server-engine), the server engine powered by Nuxt.
 ::
 
-This function is working similary as the [useSupabaseClient](/usage/composables/usesupabaseclient) composable but is designed to be used in [server routes](https://nuxt.com/docs/guide/directory-structure/server#server-routes).
+This function is working similary as the [useSupabaseClient](/composables/usesupabaseclient) composable but is designed to be used in [server routes](https://nuxt.com/docs/guide/directory-structure/server#server-routes).
 
 Define your server route and just import the `serverSupabaseClient` from `#supabase/server`. Be careful,  `serverSupabaseClient` is returning a promise.
 

docus/content/3.services/2.serverSupabaseServiceRole.md

@@ -11,7 +11,7 @@ This section assumes you're familiar with [Nitro](https://v3.nuxtjs.org/guide/co
 
 This function is designed to work only in [server routes](https://nuxt.com/docs/guide/directory-structure/server#server-routes), there is no vue composable equivalent.
 
-It works similary as the [serverSupabaseClient](/usage/services/serversupabaseclient) but it provides a client with super admin rights that can bypass your [Row Level Security](https://supabase.com/docs/guides/auth/row-level-security).
+It works similary as the [serverSupabaseClient](/services/serversupabaseclient) but it provides a client with super admin rights that can bypass your [Row Level Security](https://supabase.com/docs/guides/auth/row-level-security).
 
 > The client is initialized with the `SUPABASE_SERVICE_KEY` you must have in your `.env` file. Checkout the doc if you want to know more about [Supabase keys](https://supabase.com/docs/learn/auth-deep-dive/auth-deep-dive-jwts#jwts-in-supabase).
 

docus/content/3.services/3.serverSupabaseSession.md

@@ -7,10 +7,10 @@ description: Get your Supabase user's session from serverside with the serverSup
 This section assumes you're familiar with [Nitro](https://v3.nuxtjs.org/guide/concepts/server-engine), the server engine powered by Nuxt.
 ::
 
-This function is similar to the [useSupabaseSession](/usage/composables/usesupabasesession) composable but is used in [server routes](https://nuxt.com/docs/guide/directory-structure/server#server-routes).
+This function is similar to the [useSupabaseSession](/composables/usesupabasesession) composable but is used in [server routes](https://nuxt.com/docs/guide/directory-structure/server#server-routes).
 
 ::warning
-Be advised that `serverSupabaseSession` is considered unsafe, since the session comes from the client and users can tamper with it. For checking if the user is logged in, always use  [serverSupabaseUser](/usage/services/serversupabaseuser)
+Be advised that `serverSupabaseSession` is considered unsafe, since the session comes from the client and users can tamper with it. For checking if the user is logged in, always use  [serverSupabaseUser](/services/serversupabaseuser)
 ::
 
 Define your server route and import the `serverSupabaseSession` from `#supabase/server`.