meeting notes

[huang-julien]

have a devtools integration with tabs

• nuxt-hydration
• accessibility
• best practices in general
  • CSP
  • about nuxt but we need one first within the nuxt docs
• lighthouse best practices
  • CSP
  • COOP
  • deprecated APIs
  • third-party cookies
• images
  • aspect ratio
  • sizes
• meta tags
• console logs/error etc...

Priority

• having and define nuxt best practices
  • in seperate tabs
  • seperate plugin etc...

actions: 20-03

show theses notes to the meetings
focus on the docs
security notes for nitro

[Baroshem]

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? :)