` 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).",[2957,2958],{"name":2935,"color":2936},{"name":2920,"color":2959},"E99695",22426,"\u003CNuxtPage /> with index.vue issue","2023-08-01T11:49:39Z","https://github.com/nuxt/nuxt/issues/22426",0.67492104,{"description":2966,"labels":2967,"number":2970,"owner":2907,"repository":2907,"state":2938,"title":2971,"updated_at":2972,"url":2973,"score":2974},"### 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).",[2968,2969],{"name":2935,"color":2936},{"name":2920,"color":2959},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":2976,"number":2979,"owner":2907,"repository":2907,"state":2938,"title":2980,"updated_at":2981,"url":2982,"score":2983},[2977,2978],{"name":2935,"color":2936},{"name":2920,"color":2959},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":2985,"labels":2986,"number":2991,"owner":2907,"repository":2907,"state":2938,"title":2992,"updated_at":2993,"url":2994,"score":2995},"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",[2987,2990],{"name":2988,"color":2989},"stale","ffffff",{"name":2947,"color":2948},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":2997,"labels":2998,"number":3002,"owner":2907,"repository":2907,"state":2938,"title":3003,"updated_at":3004,"url":3005,"score":3006},"### 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.",[2999,3000,3001],{"name":2932,"color":2933},{"name":2935,"color":2936},{"name":2947,"color":2948},11497,"Feature request: Ability to ignore whole directories inside `pages`","2025-01-06T11:25:47Z","https://github.com/nuxt/nuxt/issues/11497",0.6836487,{"labels":3008,"number":3011,"owner":2907,"repository":2907,"state":2938,"title":3012,"updated_at":3013,"url":3014,"score":3015},[3009,3010],{"name":2920,"color":2959},{"name":2947,"color":2948},8484,"trouble generating dynamic routes while using nuxt content module","2023-01-22T15:38:24Z","https://github.com/nuxt/nuxt/issues/8484",0.6838266,["Reactive",3017],{},["Set"],["ShallowReactive",3020],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fV6NRpI_EsvAjHX6I645v7eQ_S6exWa-OsymBUbE4LFk":-1},"/nuxt/nuxt/31426"]