\n\n\n### Additional context\n\n_No response_",[3150,3153,3156],{"name":3151,"color":3152},"enhancement","a2eeef",{"name":3154,"color":3155},"v3","49DCB8",{"name":3157,"color":3158},"triage","ffffff",4786,"ui","[Documentation] Add Tree Data example in Table documentation","2025-08-19T03:41:07Z","https://github.com/nuxt/ui/issues/4786",0.7119921,{"description":3166,"labels":3167,"number":3171,"owner":3141,"repository":3160,"state":3142,"title":3172,"updated_at":3173,"url":3174,"score":3175},"### Description\n\nOptions in `SelectMenu` might need a description below the title e.g. like the watch dropdown on github:\n\n\u003Cimg width=\"362\" height=\"378\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/78093701-742b-49ad-8b60-e26435a3bca5\" />\n\nIt can be worked around using `item-label` slot, but it would be nice if developer can use `items` props only to implement it for simpler way.\n\nBelow, I have tried to create it using Reka UI `combobox` component, the component used by SelectMenu.\n\n\u003Cimg width=\"329\" height=\"460\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/e5cda771-3f8e-4369-bb3b-d5159f84d425\" />\n\n### Additional context\n\n_No response_",[3168,3169,3170],{"name":3151,"color":3152},{"name":3154,"color":3155},{"name":3157,"color":3158},4661,"SelectMenu: add description props to show text below title","2025-08-06T02:19:32Z","https://github.com/nuxt/ui/issues/4661",0.71664953,{"description":3177,"labels":3178,"number":3183,"owner":3141,"repository":3160,"state":3142,"title":3184,"updated_at":3185,"url":3186,"score":3187},"### Package\n\nv4.0.0-alpha.x\n\n### Description\n\n## ✨ Overview\n\nNuxt UI + `@nuxt/content` provides beautifully styled prose components like:\n\n- `ProseH1`, `ProseH2`, ...\n- `ProseP`\n- `ProseOl`, `ProseUl`\n- `ProseHr`, `ProseEm`, etc.\n\n## 💡 What I’m Proposing\nI'd love to see these components:\n\n1. ✅ **Exposed in Nuxt UI directly** – so we can use them even without `@nuxt/content`.\n2. ✅ **Aliased to cleaner, shorter component names** that match Nuxt UI naming conventions.\n\n## 🔄 Suggested Mapping\n\nCurrent Name | Proposed Nuxt UI Alias\n-- | --\n`ProseH1` | `UH1`\n`ProseH2` | `UH2`\n`ProseP` | `UP`\n`ProseOl` | `UOl`\n`ProseUl` | `UUl`\n`ProseHr` | `UHr`\n`ProseEm` | `UEm`\n\n\nThese would align perfectly with the existing pattern of `UButton`, `UCard`, `UContainer`, etc.\n\n## 📦 Why This Matters\n\n- 🧩 `Consistency`: Reuse the same design system across both prose and layout components.\n- 🔁 `Reusability`: Apply these components in any page, not just markdown.\n- 🧘♂️`Cleaner Templates`: Shorter names = easier to read/write.\n- 💅 `Design Coherence`: Unified look and feel across content and UI components.\n\n## 🧪 Example Use Case\n\n```vue\n\u003Ctemplate>\n \u003Cdiv>\n \u003CUH1>Welcome to Our Site\u003C/UH1>\n \u003CUP>This paragraph uses Nuxt UI's prose styling.\u003C/UP>\n \u003CUOl>\n \u003Cli>Beautiful Typography\u003C/li>\n \u003Cli>Consistent Spacing\u003C/li>\n \u003Cli>No Extra Setup\u003C/li>\n \u003C/UOl>\n \u003C/div>\n\u003C/template>\n```\n\n### Additional context\n\n_No response_",[3179,3180,3181],{"name":3151,"color":3152},{"name":3157,"color":3158},{"name":3182,"color":3155},"v4",4875,"🚀 Feature Request: Expose `Prose*` Components in Nuxt UI with Shorter Aliases (`UH1`, `UP`, `UOl`, etc.)","2025-09-02T14:19:50Z","https://github.com/nuxt/ui/issues/4875",0.72588587,{"description":3189,"labels":3190,"number":3192,"owner":3141,"repository":3141,"state":3142,"title":3193,"updated_at":3194,"url":3195,"score":3196},"### Describe the feature\n\nIt would be great if Nuxt UI could provide a built-in, customizable **feature tour / onboarding guide** component. This would allow developers to guide users through key parts of an application with step-by-step tooltips and highlighted elements.\n\n**Motivation**\n\n* Helps improve user onboarding and product discovery.\n* Provides a consistent and reusable UI pattern for walkthroughs across Nuxt projects.\n* Currently, developers must rely on external libraries (e.g., Driver.js, Shepherd.js) or build a custom solution. A Nuxt UI-native solution would integrate seamlessly with existing components and theming.\n\n**Proposed Features**\n\n* Ability to define **steps** with `selector`, `title`, `description`, and `position`.\n* Configurable **highlight styles** (border, shadow, spotlight cut-out).\n* Built-in **navigation controls** (Next, Previous, Finish).\n* Option to scroll to target elements automatically.\n* Theming support with Nuxt UI tokens.\n* Accessibility support (keyboard navigation, ARIA roles).\n\n**Example API (pseudo-code)**\n\n```vue\n\u003CUTour :steps=\"steps\" v-model=\"active\" />\n\n\u003Cscript setup lang=\"ts\">\nconst steps = [\n { selector: '#step1', title: 'Welcome', description: 'This is the first step', position: 'bottom' },\n { selector: '#step2', title: 'Next Feature', description: 'Learn about this one too', position: 'right' }\n]\n\u003C/script>\n```\n\n**Alternatives Considered**\n\n* External libraries like Driver.js or Shepherd.js, but they don’t fit Nuxt UI’s design system and require additional integration effort.\n\n**Additional Context**\nThis would help Nuxt developers deliver a polished onboarding experience without reinventing the wheel.\n\n### Additional information\n\n- [ ] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [x] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [x] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3191],{"name":3138,"color":3139},33111,"Interactive Feature Tour Component","2025-09-02T09:15:22Z","https://github.com/nuxt/nuxt/issues/33111",0.7278063,{"description":3189,"labels":3198,"number":3199,"owner":3141,"repository":3160,"state":3142,"title":3193,"updated_at":3200,"url":3201,"score":3202},[],4874,"2025-09-02T12:21:11Z","https://github.com/nuxt/ui/issues/4874",0.72841567,{"labels":3204,"number":3210,"owner":3141,"repository":3141,"state":3211,"title":3212,"updated_at":3213,"url":3214,"score":3215},[3205,3207],{"name":3151,"color":3206},"8DEF37",{"name":3208,"color":3209},"2.x","d4c5f9",8903,"closed","pagesapi","2023-01-22T15:52:45Z","https://github.com/nuxt/nuxt/issues/8903",0.6964026,{"description":3217,"labels":3218,"number":3221,"owner":3141,"repository":3160,"state":3211,"title":3222,"updated_at":3223,"url":3224,"score":3225},"### Description\n\n🙏 First of all, thank you to the Nuxt UI team for your outstanding contributions!\n\nNuxt UI has greatly improved the developer experience for building modern Nuxt applications.\n\n---\n\nDescription\n\nCurrently, nuxt/ui provides a powerful set of UI components and form elements, but it lacks a built-in dynamic schema-form system. In many enterprise applications, we spend a lot of repetitive time writing similar form templates and CRUD logic.\n\nI propose adding a \u003Cschema-form> component, similar to [Ant Design ProComponents Schema Form](https://procomponents.ant.design/en-US/components/schema-form), to help developers quickly build dynamic forms with minimal boilerplate.\n\nMotivation\n\t•\tReduce repetitive code for standard CRUD forms.\n\t•\tCentralize form configuration into JSON schema.\n\t•\tAutomatically handle form rendering, validation, and API requests.\n\t•\tSimplify maintenance and improve developer productivity for admin panels and back-office tools.\n\n---\nProposed API\n\nA possible schema-form component interface could be:\n\n```vue\n\u003CSchemaForm\n :schema=\"{\n title: 'User Info',\n mode: 'create', // or 'update'\n api: {\n detail: '/api/user/detail',\n create: '/api/user/create',\n update: '/api/user/update'\n },\n fields: [\n { label: 'Username', name: 'username', component: 'input', rules: [{ required: true }] },\n { label: 'Email', name: 'email', component: 'input' },\n { label: 'Role', name: 'role', component: 'select', options: [\n { label: 'Admin', value: 'admin' },\n { label: 'User', value: 'user' }\n ]}\n ],\n initialValues: { role: 'user' }\n }\"\n @submit-success=\"onSubmit\"\n/>\n```\n---\nFeatures\n\t•\t✅ Schema-driven form rendering (fields, labels, validation, components)\n\t•\t✅ Auto-fetch detail API for edit mode\n\t•\t✅ Built-in submit to create/update APIs\n\t•\t✅ Support for u-input, u-select, u-date-picker, and custom components\n\t•\t✅ Works seamlessly with Nuxt UI design system\n\n---\n\nBenefits\n\t•\tSignificant reduction in repetitive CRUD form code\n\t•\tAligns with enterprise admin panel requirements\n\t•\tMatches developer experience from frameworks like Ant Design ProComponents\n\t•\tMakes Nuxt UI more competitive for dashboard/admin scenarios\n\n---\n\nAlternatives\n\nRight now, developers must:\n\t•\tManually write each form template (using u-form, u-form-item, etc.)\n\t•\tHandle API fetching/submission manually with useFetch\n\t•\tDuplicate similar code across multiple CRUD pages\n\n---\n\nReferences\n\t•\tAnt Design ProComponents Schema Form: https://procomponents.ant.design/en-US/components/schema-form\n\n\n### Additional context\n\n_No response_",[3219,3220],{"name":3151,"color":3152},{"name":3157,"color":3158},4653,"[Feature Request] Add dynamic schema-form similar to Ant Design ProComponents Schema Form for reducing CRUD workload","2025-08-07T17:19:54Z","https://github.com/nuxt/ui/issues/4653",0.69886935,{"labels":3227,"number":3230,"owner":3141,"repository":3141,"state":3211,"title":3231,"updated_at":3232,"url":3233,"score":3234},[3228,3229],{"name":3151,"color":3206},{"name":3208,"color":3209},9107,"Tu","2023-01-22T15:52:51Z","https://github.com/nuxt/nuxt/issues/9107",0.7037432,{"description":3236,"labels":3237,"number":3241,"owner":3141,"repository":3160,"state":3211,"title":3242,"updated_at":3243,"url":3244,"score":3245},"### Description\n\nIt would be great to include these visuals directly in the component documentation pages, especially for layout components, to quickly understand their purpose at a glance.\n\n\n\nFor example, the visual could be added to the right side of the UPageHeader in the documentation. Clicking on the image could open a modal with a larger view for better readability.\n\n### Additional context\n\nlinked to this comment : https://github.com/nuxt/ui/issues/1289#issuecomment-2677068264",[3238,3239,3240],{"name":3151,"color":3152},{"name":3154,"color":3155},{"name":3157,"color":3158},3522,"Add visual to component documentation pages","2025-05-23T13:31:22Z","https://github.com/nuxt/ui/issues/3522",0.70752907,["Reactive",3247],{},["Set"],["ShallowReactive",3250],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fi_0tEcrA9UQvPsegdUzmFWLCQComVm08BWJok0p3PGM":-1},"/nuxt/ui/4788"]