You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So the idea is to first start with writing documentation for nuxt.com similar to https://nextjs.org/docs/app/building-your-application where we could show guides about Performance, Security, SEO, Accessibility, and possibly some more.
After we have that, we can start building the Hints module where we could highlight the issue (i.e. image element that does not have a performance format) and point to the documentation where user would be able to fix that based on the guide provided by Nuxt.
Unless we wan't to keep it separate for each module? Like SEO best practices in the Nuxt SEO, Security best practices in Nuxt Security and so on?
Also, how should we approach writing the actual docs for Nuxt.com? Should we create a PR already to the documentation repository or start with a Google Docs/Notion document first? :)
Activity
Baroshem commentedon Mar 21, 2025
So the idea is to first start with writing documentation for nuxt.com similar to https://nextjs.org/docs/app/building-your-application where we could show guides about Performance, Security, SEO, Accessibility, and possibly some more.
After we have that, we can start building the Hints module where we could highlight the issue (i.e. image element that does not have a performance format) and point to the documentation where user would be able to fix that based on the guide provided by Nuxt.
Unless we wan't to keep it separate for each module? Like SEO best practices in the Nuxt SEO, Security best practices in Nuxt Security and so on?
Also, how should we approach writing the actual docs for Nuxt.com? Should we create a PR already to the documentation repository or start with a Google Docs/Notion document first? :)