docs: migrate documentation to Nuxt UI

[BobbieGoede]

🔗 Linked issue

• Docs: Add code snippets for Presets #114

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSDoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Resolves #114

Thanks to the amazing work by @MuhammadM1998 on updating Nuxt I18n's docs (nuxt-modules/i18n#2740) I had good reference for doing the same on the docs here (thanks again!).

Most of the pages remain unchanged, mostly the presets page and the main page have updates. @Tahul if you have some ideas on spicing up the main/homepage (it's a bit incomplete currently) let me know or feel free to commit to this branch.

Also, this uses Nuxt UI Pro, I'm not sure what steps are required to make deployment and such work 🤷‍♂️

📝 Checklist

• I have linked an issue or discussion.
• I have added tests (if possible).
• I have updated the documentation accordingly.

[Tahul]

I have a Nuxt UI pro license; I'll put the key :)

You rock @BobbieGoede ; thank you so much

[Tahul]

looks really neat :)

have some steps in mind before merging:

• rephrase blocks to make it simpler
• animate every element (blocks as well as headings and illustration)
• split docs/ into 3 different root sections (Get Started, Features, API)
• maybe change the default animation settings for presets & examples, looks a bit too quick (?)

[BobbieGoede]

@Tahul
To keep things moving I have actually disabled the animations that I previously added to the docs, the contents of the docs haven't been edited by much either.

I think it's worth merging this update first and make improvements separately to prevent blocking ourselves 😅

[BobbieGoede]

@Tahul
I have no idea how Netlify works, do we (actually you 😂) need to make changes to the docs deployment for this PR to work or will merging this PR work and deploy as usual?