\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).",[3179],{"name":3168,"color":3180},"E99695",33073,"[Enhancement] Better Syntax/Convention for Nested Layouts in Nuxt","2025-08-27T05:51:23Z","https://github.com/nuxt/nuxt/issues/33073",0.6931786,{"description":3187,"labels":3188,"number":3195,"owner":3155,"repository":3155,"state":3196,"title":3197,"updated_at":3198,"url":3199,"score":3200},"### Describe the feature\r\n\r\nNuxt routing using folders is a nightmare for complex routes.\r\nCan I suggest a way to generate our custom router file without using the pages:extend hook?\r\n\r\nThe option to define a custom route in router.options.ts is also not good because Nuxt will not extend any new routes you return from the routes function with metadata defined in definePageMeta.\r\n\r\nWe should be able to choose to use a pre-generated routes with page directories or use our own custom rules routing file. With your own custom routing files we could be able to use everything from vue router like regex for matching route.\r\n\r\nThank you.\r\n\r\n### Additional information\r\n\r\n- [ ] 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://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3189,3192],{"name":3190,"color":3191},"enhancement","8DEF37",{"name":3193,"color":3194},"3.x","29bc7f",25386,"closed","Add a way to use our own custom routes without folder structure","2024-01-26T10:26:59Z","https://github.com/nuxt/nuxt/issues/25386",0.6469576,{"description":3202,"labels":3203,"number":3207,"owner":3155,"repository":3155,"state":3196,"title":3208,"updated_at":3209,"url":3210,"score":3211},"I would like to have the following URL\r\n/recipes/:slug\r\nto show a page with a recipe.\r\n\r\nHowever, I don't want a page under URL /recipes.\r\n\r\nIf I understand the docs correctly this is not possible? If I create the folder structure (in pages/)\r\n/recipes\r\n________/_slug\r\n________________/index.vue\r\n=> the slug becomes optional and visiting /recipes would also render the index.vue but without a slug.\r\n \r\nIf I have the structure\r\n/recipes\r\n________/_slug\r\n________________/index.vue\r\n________/index.vue\r\n=> the slug becomes required, but now I get a URL /recipes for which I don't want a page.\r\n\r\nQuestion: is this possible using the automated route generation in Nuxt or should I create my router file myself?\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c2547\">#c2547\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3204],{"name":3205,"color":3206},"2.x","d4c5f9",2932,"Dynamic route without index file","2023-01-18T16:09:49Z","https://github.com/nuxt/nuxt/issues/2932",0.6703836,{"description":3213,"labels":3214,"number":3217,"owner":3155,"repository":3155,"state":3196,"title":3218,"updated_at":3219,"url":3220,"score":3221},"### Describe the feature\n\nCurrently for nest routes if we have a page (`/parent/index.vue`) with `\u003CNuxtPage />` and a child page (`/parent/child.vue`) on the same level as the parent, `\u003CNuxtPage />` doesn't render the child pages's content.\r\n\r\n\r\n\r\nFrom the docs i have to make it `parent.vue` outside the `parent` folder.\r\n\r\n\r\nIn our project we have many pages and we have a folder structure where we separated the style from the template, example:\r\n\r\n\r\nso jumping between the `parent.vue` file all the way to the child folder then the `child.vue` file is a bit of a bother \r\nit would be great if the above scenario with the `index.vue` as a parent would work 🙏\r\n\r\n\r\n\r\n\r\n\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).",[3215,3216],{"name":3193,"color":3194},{"name":3168,"color":3180},22426,"\u003CNuxtPage /> with index.vue issue","2023-08-01T11:49:39Z","https://github.com/nuxt/nuxt/issues/22426",0.67492104,{"description":3223,"labels":3224,"number":3227,"owner":3155,"repository":3155,"state":3196,"title":3228,"updated_at":3229,"url":3230,"score":3231},"### Describe the feature\n\n### Feature Description:\r\nI am working on a project that requires the dynamic generation of a menu list during server-side rendering based on the project’s directory structure or a predefined route configuration. This feature would allow developers to automatically create a navigation menu without the need for manual updates every time a new page or route is added.\r\n\r\n### Use Case:\r\nConsider a large-scale application with numerous pages. Manually updating the menu each time a new page is introduced can be cumbersome and prone to errors. Being able to automatically generate the menu based on the directory or a route configuration file would greatly simplify this process, making it more efficient and less error-prone.\r\n\r\n### Suggested Implementation:\r\n- Directory-Based Approach: Nuxt could scan the project’s directory for files matching a specific pattern (e.g., all .vue files in a pages directory) and use this information to generate the menu.\r\n- Route Configuration Approach: Alternatively, Nuxt could read a predefined route configuration file (e.g., router.js or a similar naming convention) and use the information within to generate the menu.\r\nAdditional Considerations:\r\n- The feature should allow for nested menu structures to accommodate for nested routes if needed.\r\n- Developers should be able to customize the menu generation process, for example by specifying which files or routes to include or exclude.\r\n- It would be beneficial if the feature could also generate an accompanying menu component that could be easily imported into the application.\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).",[3225,3226],{"name":3193,"color":3194},{"name":3168,"color":3180},27241,"Dynamic Menu Generation Based on Directory or Route Configuration in Nuxt 3 SSR","2024-05-16T13:06:26Z","https://github.com/nuxt/nuxt/issues/27241",0.67843795,{"labels":3233,"number":3236,"owner":3155,"repository":3155,"state":3196,"title":3237,"updated_at":3238,"url":3239,"score":3240},[3234,3235],{"name":3193,"color":3194},{"name":3168,"color":3180},14152,"Nested custom routing not working using `pages.extend` hook","2023-01-19T17:25:51Z","https://github.com/nuxt/nuxt/issues/14152",0.68205565,{"description":3242,"labels":3243,"number":3248,"owner":3155,"repository":3155,"state":3196,"title":3249,"updated_at":3250,"url":3251,"score":3252},"Hi, can you take a look at my detailed (hopefully) explanation of this thorny issue I've had a while now with Nuxt? To summarize, I wanna be able to create a default page template under /pages say _slug.vue for new pages from a dir under /content to use to render. However, if no matching route (matching with filename in .md) is found then I still want the error 404 layout/template to load.\r\n\r\nhttps://www.loom.com/share/30b0aef7fab24d35a09fc01409e35afe\r\n\r\nHelp appreciated. Gracias",[3244,3247],{"name":3245,"color":3246},"stale","ffffff",{"name":3205,"color":3206},9440,"How do you create a default page template for new pages to use","2023-01-18T22:05:29Z","https://github.com/nuxt/nuxt/issues/9440",0.68359584,{"description":3254,"labels":3255,"number":3259,"owner":3155,"repository":3155,"state":3196,"title":3260,"updated_at":3261,"url":3262,"score":3263},"### Is your feature request related to a problem? Please describe.\r\nI have a detail page with a lot of information visualized in unique ways that only make sense to that page.\r\nBecause my `components` folder gets used for re-usable components, I have a subfolder in the same folder that route is located.\r\n\r\nMy `pages` folder looks a little something like this:\r\n```\r\nroutes\r\n- route-1\r\n - index.vue\r\n - -components\r\n - SomeComponentUniqueToThisRoute.vue\r\n - AnotherComponentUniqueToThisRoute.vue\r\n- route-2\r\n - index.vue\r\n - -components\r\n - SomeComponentUniqueToThisRoute.vue\r\n - AnotherComponentUniqueToThisRoute.vue\r\n .....\r\n```\r\n\r\nif I now go to `/route-2/-components/SomeComponentUniqueToThisRoute` it loads that component, obviously, because Nuxt thinks it's a page.\r\n\r\nIn the [documentation](https://nuxtjs.org/docs/2.x/directory-structure/pages#ignoring-pages) it says that I can already hide components by prefixing them with a `-`. But sadly this does not work on folders atm.\r\n\r\n### Describe the solution you'd like\r\nI want nuxt to **not** generate routes from `.vue` files in folders prefixed with a `-` by default, without the help of [.nuxtignore](https://nuxtjs.org/docs/2.x/configuration-glossary/configuration-ignore). Exactly like it already does for components.\r\n\r\nAll sub-folders and their .vue files should not be turned in to pages as well.\r\n\r\n### Describe alternatives you've considered\r\nHaving all components in my `-components` folder starting with a `-` would do the trick, but that is ugly and breaks vue's naming conventions.\r\n\r\nI could also write a couple of `.nuxtignore` rules that exclude the folders, but my application has many (around 25) -components folders that I would have to exclude. It is also another thing I have to explain to people who help me with this project, which isn't ideal.",[3256,3257,3258],{"name":3190,"color":3191},{"name":3193,"color":3194},{"name":3205,"color":3206},11497,"Feature request: Ability to ignore whole directories inside `pages`","2025-01-06T11:25:47Z","https://github.com/nuxt/nuxt/issues/11497",0.6836487,["Reactive",3265],{},["Set"],["ShallowReactive",3268],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fV6NRpI_EsvAjHX6I645v7eQ_S6exWa-OsymBUbE4LFk":-1},"/nuxt/nuxt/31426"]