Reorganiaiton of the docs and updates

[malikdotjs]

Is your feature request related to a problem? Please describe.

Currently, the documentation for the Supabase Nuxt module lacks a clear structure, making it difficult for new users to navigate and understand. This can be frustrating, especially for developers who are not familiar with the module and are looking for quick and straightforward instructions, as I experienced myself when I first started.

Describe the solution you'd like

I propose reorganizing the documentation to make it more user-friendly and easier to follow. This would include adding clear sections for installation, configuration, and usage, as well as detailed examples for common use cases.

What I propose:

1. Introduction

2. Get Started

   • Installation
   • Configuration

3. Authentication

   • Email & Password
   • OTP (One Time Password)
   • OAuth
   • Session Management
   • Reset Password

4. Composables

   • useSupabaseClient
   • useSupabaseAuth
   • useSupabaseStorage

5. Server

   • serverSupabaseClient
   • serverSupabaseServiceRole
   • serverSupabaseSession
   • serverSupabaseUser

6. Changelog

7. Roadmap

Additional context

I have already forked the repository and started reorganizing the documentation.

You can find my progress here: https://github.com/maliksvd/supabase/tree/main/docs/content

[larbish]

Hey @maliksvd, that's a great initiative. Just so you know I was thinking of rebuild the all docs with Nuxt Content v3 and Nuxt UIPro v3. But there are both in alpha for the moment. What do you think about waiting for more stable releases ? You can already work on the structure however.

[larbish]

Hey @maliksvd, we've released Nuxt Content v3 and a v3 branch has been created on the UI Pro Documentation starter with both Content x UI v3. I don't have time to do the migration currently but I'll do it asap. If you want to take care of this and apply your new doc structure, you more than welcome!

[malikdotjs]

Hello @larbish, Yes, I'm totally up for it. I'll take care of the migration and apply the new doc structure. Thanks for letting me know! 😊

[github-actions[bot]]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.