\r\n\r\nHere you can check the text is not in context (the next entry should be `Getting Started | Frameworks`):\r\n\r\n\r\n\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.",[2933],{"name":2905,"color":2906},758,"Provide text entry for `VPDocFooter`","https://github.com/vuejs/vitepress/issues/758",0.74365735,{"description":2939,"labels":2940,"number":2941,"owner":2871,"repository":2872,"state":2873,"title":2942,"updated_at":2943,"url":2944,"score":2945},"### Is your feature request related to a problem? Please describe.\n\nHi there!\r\n\r\nI want to expand the theme to add content in the red box below, but we do not have slots in these two positions, I would like to ask if there is a good way? \r\n\r\n\r\n\r\n\n\n### Describe the solution you'd like\n\nIs it possible to add `doc-title-after`, `doc-footer-before` slots like that.\n\n### Describe alternatives you've considered\n\nFor example, if I wanted to add content after the title, the schemes I tried were as follows:\r\n\r\n- [x] ~Use custom components under the heading of each MD document.~\r\n- [x] ~Expand the custom content in the `doc-before` slot position, then move it when the page loads.~\r\n\r\nObviously, they are either troublesome or have problems.\n\n### Additional context\n\nI'm sorry to disturb you. In addition to completely customizing the theme, do you have a better plan to guide me? I am just like an amateur in front end. \r\nSay thank you in advance.\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.",[],1050,"Provide more slots when extending the default theme","2023-01-21T14:28:41Z","https://github.com/vuejs/vitepress/issues/1050",0.7440411,{"description":2947,"labels":2948,"number":2950,"owner":2871,"repository":2872,"state":2873,"title":2951,"updated_at":2952,"url":2953,"score":2954},"### Describe the bug\n\nHello, awesome effort, looking forward to how this project grows.\r\n\r\nContext: adding documentation with Vitepress to a vue3 library that uses aliases inside `/@`. \r\n\r\nAdded `resolve.alias` using a `vite.config.ts` based on this https://github.com/vuejs/vitepress/issues/241 \r\n\r\nIt worked, but suddenly ignored completely the config on `docs/.vitepress/config.ts` (title, sidebar, nav, etc)\r\n\r\n```js\r\n// docs/.vitepress/config.ts\r\n\r\nmodule.exports = {\r\n title: 'Vue Dynamic Forms',\r\n description,\r\n themeConfig: {\r\n repo: 'asigloo/vue-dynamic-forms',\r\n logo: '/logo.svg',\r\n nav: [\r\n {\r\n text: 'Migration Guide',\r\n link: '/v3/guide/migration-guide',\r\n },\r\n ],\r\n sidebar: {\r\n '/': [\r\n {\r\n text: 'Guide',\r\n children: [\r\n {\r\n text: 'Introduction',\r\n link: '/guide/',\r\n },\r\n {\r\n text: 'Getting Started',\r\n link: '/guide/getting-started',\r\n },\r\n {\r\n text: 'Usage',\r\n link: '/guide/usage',\r\n },\r\n ],\r\n },\r\n ],\r\n },\r\n },\r\n}\r\n\r\n```\r\n\r\n\r\n\n\n### Reproduction\n\n- Add a `vite.config.ts` inside `docs` root \r\n- Add a `title`, also add `themeConfig`, `nav` or `sidebar` on `docs/.vitepress/config.ts` \r\n- Run `vitepress dev docs` \n\n### Expected behavior\n\n`vite.config.ts` `docs/.vitepress/config.ts` configs can live together \r\n\r\nor\r\n\r\nAn option to add `alias` to `docs/.vitepress/config.ts` \n\n### System Info\n\n```shell\nSystem:\r\n OS: macOS 11.4\r\n CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz\r\n Memory: 544.29 MB / 16.00 GB\r\n Shell: 5.8 - /bin/zsh\r\n Binaries:\r\n Node: 16.3.0 - ~/.nvm/versions/node/v16.3.0/bin/node\r\n Yarn: 1.22.10 - /usr/local/bin/yarn\r\n npm: 7.19.1 - ~/Projects/github/vue-dynamic-forms/node_modules/.bin/npm\r\n Browsers:\r\n Chrome: 92.0.4515.159\r\n Firefox: 89.0.1\r\n Safari: 14.1.1\r\n npmPackages:\r\n vitepress: ^0.16.1 => 0.15.6 \r\n```\n```\n\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] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2949],{"name":2868,"color":2869},373,"ThemeConfig is ignored when using vite.config.ts inside docs","2023-01-21T14:32:46Z","https://github.com/vuejs/vitepress/issues/373",0.7487588,{"description":2956,"labels":2957,"number":2961,"owner":2871,"repository":2872,"state":2873,"title":2962,"updated_at":2963,"url":2964,"score":2965},"### Describe the bug\n\nwhen link uses `\\\\`, next page is always the current route, And the buttons on the previous page are not displayed\n\n### Reproduction\n\n[minimal reproduction](https://stackblitz.com/edit/vite-uvdizffs?file=docs%2F2.md,docs%2F3.md,docs%2F.vitepress%2Fconfig.ts)\n\n### Expected behavior\n\nThe reason why I have this problem is that I use node `fs` to read my file directory and generate sidebar through the `path` module. I have now solved the problem by replacing `\\\\` in link, but it took me quite a while to find this problem.\n\n### System Info\n\n```Text\nSystem:\n OS: Windows 11 10.0.22631\n CPU: (12) x64 Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz\n Memory: 1.07 GB / 7.90 GB\n Binaries:\n Node: 18.20.2 - C:\\Program Files\\nodejs\\node.EXE\n Yarn: 1.22.22 - C:\\Program Files\\nodejs\\yarn.CMD\n npm: 10.5.0 - C:\\Program Files\\nodejs\\npm.CMD\n pnpm: 9.12.2 - C:\\Program Files\\nodejs\\pnpm.CMD\n Browsers:\n Chrome: bookmarks.html\ninitial_preferences\n Edge: Chromium (129.0.2792.52)\n Internet Explorer: 11.0.22621.3527\n npmPackages:\n vitepress: ^1.6.3 => 1.6.3\n```\n\n### Additional context\n\n\n\n### Validations\n\n- [x] Check if you're on the [latest VitePress version](https://github.com/vuejs/vitepress/releases/latest).\n- [x] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\n- [x] Read the [docs](https://vitepress.dev).\n- [x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2958],{"name":2959,"color":2960},"wont fix","EDEED1",4691,"docFooter parsing error when sidebar link uses \\\\","2025-04-15T05:42:33Z","https://github.com/vuejs/vitepress/issues/4691",0.74881124,["Reactive",2967],{},["Set"],["ShallowReactive",2970],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fgyFamywrJyvpM_v8qTi4oMYvmNnahOOYuQOJLvUwXmY":-1},"/vuejs/vitepress/1606"]