Skip to content

Conversation

@brendonmatos
Copy link
Contributor

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality)
  • ✨ 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

I’m currently using Deepwiki as an MCP to get up-to-date guidance while working with Nuxt/UI. At the moment, updates to Deepwiki are done manually, but it can be configured for automatic updates by having a badge.

This is how i've generated the badge:
https://deepwiki.com/badge-maker?url=https%3A%2F%2Fdeepwiki.com%2Fnuxt%2Fui

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Oct 23, 2025

npm i https://pkg.pr.new/@nuxt/ui@5291

commit: 432c61d

@benjamincanac benjamincanac changed the title chore: add deepwiki badge to autoupdate deep wiki chore(readme): add DeepWiki badge Oct 23, 2025
@benjamincanac benjamincanac merged commit 4f93530 into nuxt:v4 Oct 23, 2025
16 checks passed
benjamincanac added a commit that referenced this pull request Oct 23, 2025
@benjamincanac
Copy link
Member

benjamincanac commented Oct 23, 2025

I've actually changed my mind after seeing the badge live on the README so I reverted the commit. I don't think this should belong alongside the other most important badges.

We do provide an official MCP server: https://ui.nuxt.com/docs/getting-started/ai/mcp and I don't feel confortable advertising a service I can't be sure the data is correct.

@brendonmatos
Copy link
Contributor Author

Yea totally fair. No problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

v4 #4488

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants