feat: migrate to @nuxt/ui-pro and @nuxt/content v3

[HugoRCD]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 📰 Content (a new article or a change in the content folder)
• 🐞 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

📝 Checklist

• I have linked an issue or discussion.

• I have updated the documentation accordingly.

• App

  • Compatibility v4
  • UI v3
    • Colors (gray to neutral, css variables, etc...)
  • Content v3
  • Blog
  • Lean
  • Packages
  • Search

• Server

  • Flux RSS
  • Sitemap
  • Plugin Content
  • API
    • content/packages
    • owner/repo/readme
    • utils/rss

[pi0]

Thanks for PR. this website is not highest priority at the moment and likely many things have to be reworked later..

If you have time to help on undocs that would be amazing ❤️

[HugoRCD]

Thanks for PR. this website is not highest priority at the moment and likely many things have to be reworked later..

If you have time to help on undocs that would be amazing ❤️

I wasn't sure which one to prioritize, but I can pause this one to help on Undocs then 😁

[maximepvrt]

I think that the packages' content files could be simplified by, for example, removing the documentation attribute and instead systematically defining the documentation URL directly in the package.json (using the homepage).

This would also have the advantage of providing direct access to the documentation via https://www.npmjs.com/, improving consistency and reducing the need for duplicate information.

• build: add homepage field to package.json nitrojs/nitro#3329
• build: add homepage field to package.json h3js/h3#1030

What do you think about this approach?