\n \u003CNuxtPage /> \u003C!-- renders children like index.vue, favorite.vue -->\n \u003C/div>\n\u003C/template>\n```\n\nThis improves clarity by:\n\n* Explicitly distinguishing **nested layout files** from **page files**.\n* Avoiding the overloaded role of `parent.vue`.\n* Making folder structures self-explanatory.\n\n### Benefits\n\n* More intuitive project structure for large apps.\n* Easier onboarding for new developers (clear separation of layouts vs. pages).\n* Cleaner, scalable convention that aligns with the mental model of “global layouts” vs. “section layouts.”\n\n### Additional information\n\n- [x] 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).",[3170],{"name":3171,"color":3172},"pending triage","E99695",33073,"[Enhancement] Better Syntax/Convention for Nested Layouts in Nuxt","2025-08-27T05:51:23Z","https://github.com/nuxt/nuxt/issues/33073",0.7581189,{"description":3179,"labels":3180,"number":3191,"owner":3161,"repository":3161,"state":3192,"title":3193,"updated_at":3194,"url":3195,"score":3196},"### Describe the feature\n\nCurrently, the pages module has a very limited configuration option. It can be enabled/disabled and we can change the dir name. I would like to improve this to bring it on par with the configuration available for components and composables.\r\n\r\nExample: in the following directory structure I want to automatically load only Vue files (could be customizable with a glob pattern).\r\n```\r\npages\r\n somePage\r\n index.vue\r\n pageSpecificHelper.ts\r\n pageAsyncData.ts\r\n generated\r\n GQLGeneratedTypes.ts\r\n```\r\nCurrently, I have a couple of workarounds like adding `-` prefixes, or `ignore` config (though it affects all auto-imports).\r\n\r\nI would be happy to work on this myself. The idea I have would be to allow `pages` config to be an object with an option for `pattern` (or use the existing `ScanDir` interface for more configuration) and then change [this line in resolvePagesRoutes](https://github.com/nuxt/framework/blob/main/packages/nuxt/src/pages/utils.ts#L38) with fallback to the current pattern.\r\n\r\n---\r\n\r\nMore broadly speaking, I imagine that a more consistent and granular configuration of auto-imports would benefit many bigger projects. But this would be a bigger change affecting components, composables, plugins, and pages configuration. \n\n### Additional information\n\n- [X] 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://v3.nuxtjs.org/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/framework/discussions) and [issues](https://github.com/nuxt/framework/issues).",[3181,3182,3185,3188],{"name":3152,"color":3153},{"name":3183,"color":3184},"3.x","29bc7f",{"name":3186,"color":3187},"workaround available","11376d",{"name":3189,"color":3190},"❌ won't do","705B27",12333,"closed","Improved pages module configuration","2024-11-28T05:07:59Z","https://github.com/nuxt/nuxt/issues/12333",0.73252416,{"description":3198,"labels":3199,"number":3209,"owner":3161,"repository":3210,"state":3192,"title":3211,"updated_at":3212,"url":3213,"score":3214},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.14.0`\n- Nuxt Version: `3.16.1`\n- CLI Version: `3.23.1`\n- Nitro Version: `2.11.7`\n- Package Manager: `pnpm@10.6.5`\n- Builder: `-`\n- User Config: `modules`, `devtools`, `css`, `routeRules`, `future`, `compatibilityDate`, `eslint`\n- Runtime Modules: `@nuxt/eslint@1.2.0`, `@nuxt/ui-pro@3.0.1`, `@vueuse/nuxt@13.0.0`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/silent-currying-qhjsy6\n\n### Description\n\n* 当 Avatar 有图片内容时可以作为 UPopover 的 Trigger 被触发\n* 当 Avatar 展示子插槽内容,不能成功触发 UPopover\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3200,3203,3206],{"name":3201,"color":3202},"bug","d73a4a",{"name":3204,"color":3205},"v3","49DCB8",{"name":3207,"color":3208},"triage","ffffff",3710,"ui","cant use u-avatar as triggers for u-popover","2025-03-28T09:27:27Z","https://github.com/nuxt/ui/issues/3710",0.7343268,{"description":3216,"labels":3217,"number":3219,"owner":3161,"repository":3161,"state":3192,"title":3220,"updated_at":3221,"url":3222,"score":3223},"### Describe the feature\n\n**Why need feature?**\nDb collection has multiple pages like below.\npageConfig: {\n name: 'home',\n layout: 'layout1'\n widgets:['image','card']\n}\n\nDb collection has multiple layouts like below.\nlayoutConfig:{\n name: 'layout1',\n widgets: ['header', 'slot', 'footer']\n}\n\nGenerate runtime layouts using db collection array of object. And link it by pages.\n\n**Existing feature:** \nNow, developers pre define layouts in nuxt3 like custom.vue, default.vue, desktop/index.vue, layout1.vue, etc in layouts directory.\n\nWe can call layout in page like below using layouts directory.\ndefinePageMeta({\n layout: pageConfig.layout\n}) or setPageLayout(pageConfig.layout)\n\n**Proposed system**:\nFile name should be [name].vue in layouts directory. The 'name'' should be captured like route params. Using name value, find details of ui from db and create it. Now layout is ready.\n\nWhile page printing, use below modified syntax\n\ndefinePageMeta({\n layout: {\n name: pageConfig.layout\n }\n}) or setPageLayout({name: pageConfig.layout})\n\nIf same name came when routing between different pages, should not be re-rendered.\n\nLayouts performance is best one because rendering content in slot only until layout changed.\n\n### Additional information\n\n- [x] 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).",[3218],{"name":3171,"color":3172},32114,"Dynamic Layouts Request","2025-09-10T09:26:12Z","https://github.com/nuxt/nuxt/issues/32114",0.7343828,{"labels":3225,"number":3230,"owner":3161,"repository":3161,"state":3192,"title":3231,"updated_at":3232,"url":3233,"score":3234},[3226,3227],{"name":3152,"color":3153},{"name":3228,"color":3229},"2.x","d4c5f9",8145,"Multiple pages and layout directories, for modules and monorepos","2023-01-22T15:52:44Z","https://github.com/nuxt/nuxt/issues/8145",0.7424364,{"description":3236,"labels":3237,"number":3241,"owner":3161,"repository":3242,"state":3192,"title":3243,"updated_at":3244,"url":3245,"score":3246},"Currently it is not possible to use google as a provider for Material Symbols. \r\n\r\nLooking at the current implementation of the google provider it seems it's only looking at the meta data for fonts found at: https://fonts.google.com/metadata/fonts \r\n\r\n![Uploading image.png…]()\r\n\r\n\r\nMetadata for googles Material Symbols can be found at https://fonts.google.com/metadata/icons",[3238],{"name":3239,"color":3240},"provider","1161A4",127,"fonts","Add support for Google Material Symbols","2024-09-11T22:00:40Z","https://github.com/nuxt/fonts/issues/127",0.7488391,{"description":3248,"labels":3249,"number":3253,"owner":3161,"repository":3161,"state":3192,"title":3254,"updated_at":3255,"url":3256,"score":3257},"### Describe the feature\r\n\r\nHey 👋🏻\r\n\r\nRight now, custom meta in `definePageMeta` can only be sent in as key-value pair. While this is helpful already, it'd be even more amazing to have some function á la `validate` - so you can pass in the current route + params - or the possibility to define `computed`s like for `layout` (in theory).\r\n\r\nThis would increase flexibility of page meta, but I'm not sure if it is technically feasible 🤔\r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://v3.nuxtjs.org/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/framework/discussions) and [issues](https://github.com/nuxt/framework/issues).",[3250,3251,3252],{"name":3183,"color":3184},{"name":3171,"color":3172},{"name":3201,"color":3202},15463,"`definePageMeta` - Custom values should be more than just k/v pairs","2023-01-19T17:51:05Z","https://github.com/nuxt/nuxt/issues/15463",0.75195646,{"labels":3259,"number":3265,"owner":3161,"repository":3161,"state":3192,"title":3266,"updated_at":3267,"url":3268,"score":3269},[3260,3261,3262],{"name":3152,"color":3153},{"name":3183,"color":3184},{"name":3263,"color":3264},"pages","00DFB5",13476,"Extending pages meta in `extendPages` hook overrides page meta defined using `definePageMeta`","2023-01-19T16:57:28Z","https://github.com/nuxt/nuxt/issues/13476",0.75222397,{"description":3271,"labels":3272,"number":3277,"owner":3161,"repository":3210,"state":3192,"title":3278,"updated_at":3279,"url":3280,"score":3281},"### Description\n\nHello, we are currently a small team using nuxt UI pro version 2. We've seen that the new Nuxt UI 3 version is in alpha and we'd like to know if a stable release is planned soon?\n\nWe've seen that Nuxt UI 3 is going to take a long time to migrate and we'd like to start work quickly. Do you think it's cost-effective to make the switch now, or is it better to wait for a more stable version?\n\nThanks for reading ^^",[3273,3276],{"name":3274,"color":3275},"question","d876e3",{"name":3204,"color":3205},3371,"Nuxt UI V3 official release date","2025-02-21T09:22:07Z","https://github.com/nuxt/ui/issues/3371",0.7524227,["Reactive",3283],{},["Set"],["ShallowReactive",3286],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fv_xGdejNYwhbN7MvPRflM476oda-KPeG9nrUNx2mdS8":-1},"/nuxt/fonts/96"]