` to every `.md` documents. However, I think this is not a proper way to do it as it's used in every documents.\r\n\r\n\r\n\r\n### Describe the solution you'd like\r\n\r\nAdding a slot before or after the document content.\r\n\r\n`\u003Ctemplate #doc-before>\u003C/template>`\r\n`\u003Ctemplate #doc-after>\u003C/template>`\r\n\r\n### Describe alternatives you've considered\r\n\r\n_No response_\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\r\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\r\n- [X] Read the [docs](https://vitepress.vuejs.org).\r\n- [X] Read the [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/main/.github/contributing.md).\r\n- [X] Check that there isn't already an issue that asks for the same feature to avoid creating a duplicate.",[],762,"closed","Slot for top or bottom of document","2023-01-21T14:34:09Z","https://github.com/vuejs/vitepress/issues/762",0.65527797,{"description":2886,"labels":2887,"number":2888,"owner":2869,"repository":2870,"state":2880,"title":2889,"updated_at":2890,"url":2891,"score":2892},"### Is your feature request related to a problem? Please describe.\n\nVitepress currently does not have a way to directly add more information to the VPFooter of a VPDoc page. This makes it more difficult to add text or other content inside the document footer.\n\n### Describe the solution you'd like\n\nI've been running a local version of vitepress where I've added the `doc-footer-content-before` slot. This way, I can add more content inside the footer of a VPDoc page.\n\n### Describe alternatives you've considered\n\nI am aware that there exists a `doc-footer-before` slot, but it's outside the footer element. This makes it harder to apply consistent styling, as VPFooter has a margin that affects content inserted with the `doc-footer-before` slot. It's also not the best option in terms of HTML semantics.\n\n### Additional context\n\nBelow is a screenshot where two lines of text have been added with the already existing `doc-footer-before`.\r\n\r\n\r\n\r\nBelow is a screenshot where the proposed `doc-footer-content-before` slot has been used instead.\r\n\r\n\r\n\r\nI'm open to hear your opinion on the issue.\r\n\r\nI would be glad to upstream the proposed change.\n\n### Validations\n\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\n- [X] Read the [docs](https://vitepress.dev).\n- [X] Read the [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/main/.github/contributing.md).\n- [X] Check that there isn't already an issue that asks for the same feature to avoid creating a duplicate.",[],2082,"Add a doc-footer-content-before slot","2023-03-23T00:04:28Z","https://github.com/vuejs/vitepress/issues/2082",0.66849893,{"description":2894,"labels":2895,"number":2896,"owner":2869,"repository":2870,"state":2880,"title":2897,"updated_at":2898,"url":2899,"score":2900},"### Is your feature request related to a problem? Please describe.\r\n\r\nI was looking at the default theme extension slots for how to add a banner to the website but didn't find anything ideal. I ended up using nav bar content with some hacky CSS to create a new row, but this doesn't look great yet and it already took me a bit of time so far.\r\n\r\n\r\n\r\n### Describe the solution you'd like\r\n\r\nI would like there to be a central place to pass some data to a banner content array that when populated will display a strip above the nav bar consisting of a colour and text.\r\n\r\n### Describe alternatives you've considered\r\n\r\nA slot would work too, but lower level. I think banner is common enough to support is as first class data in the theme config?\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\r\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\r\n- [X] Read the [docs](https://vitepress.dev).\r\n- [X] Read the [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/main/.github/contributing.md).\r\n- [X] Check that there isn't already an issue that asks for the same feature to avoid creating a duplicate.",[],4190,"Default theme optional banner(s)","2024-10-10T04:44:25Z","https://github.com/vuejs/vitepress/issues/4190",0.6923064,{"description":2902,"labels":2903,"number":2907,"owner":2869,"repository":2870,"state":2880,"title":2908,"updated_at":2909,"url":2910,"score":2911},"### Is your feature request related to a problem? Please describe.\n\nWhen we want add a common footer section for every page, we have to add other code with \"Content component\". \r\nFor example:\r\n\r\n``` vue\r\n\u003Cdiv class='doc-content-wrapper'>\r\n \u003Cdiv class='doc-content-container'>\r\n \u003CContent\r\n ref='content'\r\n class='doc-content'\r\n @vnode-mounted='updateLink'\r\n @vnode-updated='updateLink'\r\n />\r\n \u003Cdiv class='doc-content'>\r\n \u003CVPComponentCssVar v-if='componentName'\r\n :component-name='componentName'>\u003C/VPComponentCssVar>\r\n \u003C/div>\r\n \u003CVPPageFooter />\r\n \u003CVPPageNav />\r\n \u003C/div>\r\n \u003C/div>\r\n```\n\n### Describe the solution you'd like\n\nAdd a footer and header slot to Content component.\n\n### Describe alternatives you've considered\n\n_No response_\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Follow our [Code of Conduct](https://vuejs.org/coc)\n- [X] Read the [docs](https://vitepress.vuejs.org/).\n- [X] Read the [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/master/.github/contributing.md).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2904],{"name":2905,"color":2906},"need more info","bdbefc",543,"Please add slots for Content component.","2023-01-21T16:04:18Z","https://github.com/vuejs/vitepress/issues/543",0.7142821,{"description":2913,"labels":2914,"number":2915,"owner":2869,"repository":2870,"state":2880,"title":2916,"updated_at":2917,"url":2918,"score":2919},"### Is your feature request related to a problem? Please describe.\r\n\r\nI would like to replace sections in the default theme with my own components and sections for the home page. For example I want to replace the `VPHomeFeatures` with my own features component and not rely on the vitepress `VPHomeFeatures` component. The slots `vp-home-feature-before` and `vp-home-feature-after` are not sufficient, because I want to replace the actual component itself.\r\n\r\nSection from from `src/client/theme-default/components/VPHome.vue` where the feature component is defined in the theme:\r\n```\r\n \u003Cslot name=\"home-features-before\" />\r\n \u003CVPHomeFeatures />\r\n \u003Cslot name=\"home-features-after\" />\r\n```\r\n\r\n### Describe the solution you'd like\r\n\r\nA simple solution is to introduce more slots in the default theme such that a developer can replace components on the home page with his own custom components.\r\n\r\nI think we should introduce at least two new slots:\r\n- `home-features`\r\n- `home-hero`\r\n\r\nThe improved section from `src/client/theme-default/components/VPHome.vue` would simply be:\r\n```\r\n \u003Cslot name=\"home-features-before\" />\r\n \u003Cslot name=\"home-features\" />\r\n \u003CVPHomeFeatures />\r\n \u003C/slot>\r\n \u003Cslot name=\"home-features-after\" />\r\n```\r\n\r\n\r\n\r\n### Describe alternatives you've considered\r\n\r\nThe alternative is to tell vite to replace the `VPHome.vue` component (or Features component for that matter) with a custom `VPHome.vue` component using aliases in the configuration, e.g.:\r\n\r\n```\r\nvite: {\r\n resolve: {\r\n alias: [\r\n {\r\n find: /^.*\\/VPHome\\.vue$/,\r\n replacement: fileURLToPath(\r\n new URL('./theme/components/VPHome.vue', import.meta.url),\r\n ),\r\n },\r\n ],\r\n },\r\n },\r\n```\r\n\r\n### Additional context\r\n\r\nIf this is something the maintainers want to consider, I can prepare a quick MR for this feature asap after approval.\r\n\r\n### Validations\r\n\r\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\r\n- [X] Read the [docs](https://vitepress.dev).\r\n- [X] Read the [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/main/.github/contributing.md).\r\n- [X] Check that there isn't already an issue that asks for the same feature to avoid creating a duplicate.",[],3558,"More slots in the default theme to replace components completely","2024-02-15T00:05:28Z","https://github.com/vuejs/vitepress/issues/3558",0.7145587,{"description":2921,"labels":2922,"number":2926,"owner":2869,"repository":2870,"state":2880,"title":2927,"updated_at":2928,"url":2929,"score":2930},"### Is your feature request related to a problem? Please describe.\n\nRight now it’s not possible to change the text in the prev/next links that are displayed at the bottom of pages with the default theme.\r\n\u003Cimg width=\"378\" alt=\"Screenshot 2022-07-01 at 23 45 56\" src=\"https://user-images.githubusercontent.com/18370980/176971436-a1d5d9d3-2cb2-4088-a94d-69307d0b20a7.png\">\r\n \r\nThis is not very elegant when you’re working with non-English docs :)\n\n### Describe the solution you'd like\n\nI guess a `themeConfig.docFooter.[prev|next]` option, or something similar, would do the trick.\n\n### Describe alternatives you've considered\n\nOne option would be building a custom theme that extends the default one and overriding [VPDocFooter.vue](https://github.com/vuejs/vitepress/blob/main/src/client/theme-default/components/VPDocFooter.vue), but imo this feature could also benefit a lot of users of the default theme.\n\n### Additional context\n\nThanks for being awesome!\n\n### Validations\n\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\n- [X] Read the [docs](https://vitepress.vuejs.org).\n- [X] Read the [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/main/.github/contributing.md).\n- [X] Check that there isn't already an issue that asks for the same feature to avoid creating a duplicate.",[2923],{"name":2924,"color":2925},"theme","0754FB",893,"Make it possible to change the \"Previous page\" and \"Next page\" labels in the default theme","2023-01-21T14:32:49Z","https://github.com/vuejs/vitepress/issues/893",0.7270861,{"description":2932,"labels":2933,"number":2935,"owner":2869,"repository":2870,"state":2880,"title":2936,"updated_at":2937,"url":2938,"score":2939},"### Is your feature request related to a problem? Please describe.\n\nThe default page layout is 'doc', which is hard coded. It will easier the user's life to be able to provide an aletrnative layout so that he doesn't need to write a whole theme.\n\n### Describe the solution you'd like\n\nUse dynamic component in VPContent, and add a config option in the themeConfig.\n\n### Describe alternatives you've considered\n\n_No response_\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\n- [X] Read the [docs](https://vitepress.vuejs.org).\n- [X] Read the [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/main/.github/contributing.md).\n- [X] Check that there isn't already an issue that asks for the same feature to avoid creating a duplicate.",[2934],{"name":2905,"color":2906},1376,"Customize default page layout","2023-01-21T14:23:05Z","https://github.com/vuejs/vitepress/issues/1376",0.7377738,{"description":2941,"labels":2942,"number":2944,"owner":2869,"repository":2870,"state":2880,"title":2945,"updated_at":2946,"url":2947,"score":2948},"### Is your feature request related to a problem? Please describe.\n\n[Prev Next Links](https://vitepress.dev/reference/default-theme-prev-next-links) can only customize using Frontmatter in each markdown file\n\n### Describe the solution you'd like\n\nI think there must be someone else who thinks like me: **I don't want Prev Next Links**\r\n\r\nusing `custom.css` or customize in each markdown file is too hack and hope it can be edit in either global config\n\n### Describe alternatives you've considered\n\n_No response_\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\n- [X] Read the [docs](https://vitepress.dev).\n- [X] Read the [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/main/.github/contributing.md).\n- [X] Check that there isn't already an issue that asks for the same feature to avoid creating a duplicate.",[2943],{"name":2924,"color":2925},2079,"Add support for custom Prev Next Links in themeConfig","2023-06-18T00:04:58Z","https://github.com/vuejs/vitepress/issues/2079",0.7421088,{"description":2950,"labels":2951,"number":2955,"owner":2869,"repository":2870,"state":2880,"title":2956,"updated_at":2957,"url":2958,"score":2959},"In the `themeConfig` section, under [footer](https://vitepress.vuejs.org/config/theme-configs#footer), there seems to be a grammatical mistake. \r\n\r\n### Ergo\r\n\r\nFooter configuration. You can add a message and copyright. The footer will `displayed` only when the page doesn't `contain sidebar` due to `design reason`.\r\n\r\n## Suggested change\r\nFooter Configuration. You can add a message or copyright text on the footer, however, it will only be displayed when the page doesn't contain a sidebar. This is due to design concerns.\r\n\r\nI just paraphrased the sentence a little bit, but it can be simplified even further. Also, if approved, I can make a quick PR for this.",[2952],{"name":2953,"color":2954},"docs","0075ca",1606,"Grammartical typo in footer section of the themeConfig page","2023-01-21T14:20:35Z","https://github.com/vuejs/vitepress/issues/1606",0.7424964,["Reactive",2961],{},["Set"],["ShallowReactive",2964],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$faH68P25O3Ogprev24jMTAOtk79-0dOkaoSS48o9r7ME":-1},"/vuejs/vitepress/1050"]