\r\n\r\n::: zh-CN\r\n中文\r\n:::\r\n\r\n::: en\r\nEnglish\r\n:::\r\n```\r\n\r\nThis reduces maintenance costs.\r\n\r\nI came up with a very low cost implementation - [CSS-I18N](https://github.com/valaxyjs/css-i18n)\r\nAnd I implemented it in my own project [valaxy](https://github.com/YunYouJun/valaxy).\r\n\r\nIt works well. You can preview it [here](https://valaxy.site/guide/i18n).\r\nAnd this is my implementation: [How to realize CSS i18n?](https://valaxy.site/posts/i18n#css-i18n-another-solution)\r\n\r\n---\r\n\r\nIt is very cost-effective and I hope to integrate it with vitepress.\r\nIf you agree with my proposal, please let me know and I can create a PR for vitepress.\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.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.",[2899],{"name":2871,"color":2872},3047,"CSS i18n in one page","2025-03-02T18:10:37Z","https://github.com/vuejs/vitepress/issues/3047",0.7854083,{"description":2906,"labels":2907,"number":2909,"owner":2874,"repository":2875,"state":2876,"title":2910,"updated_at":2911,"url":2912,"score":2913},"### Describe the bug\n\nDead links in the sidebar are not reported.\n\n### Reproduction\n\nOn vitepress.new, the following sidebar\r\n```\r\nsidebar: [\r\n {\r\n // text: 'Guide',\r\n items: [\r\n { text: 'Example', link: '/example' },\r\n { text: 'Foo', link: '/Foo'},\r\n { text: 'Bar', link: '/Bar'}\r\n ],\r\n },\r\n ],\r\n```\r\nbuilds even if Bar doesn't exist. \n\n### Expected behavior\n\nI'd expect `Bar` to not show up in the sidebar, or to be reported as a dead link.\n\n### System Info\n\n```Text\nvitepress.new\n```\n\n\n### Additional context\n\n_No response_\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.",[2908],{"name":2871,"color":2872},3244,"Dead links in sidebar not reported","2023-12-26T20:33:00Z","https://github.com/vuejs/vitepress/issues/3244",0.79187036,{"description":2915,"labels":2916,"number":2920,"owner":2874,"repository":2875,"state":2921,"title":2922,"updated_at":2923,"url":2924,"score":2925},"Currently one needs to do this:\r\n\r\n```yaml\r\n---\r\nlayout: home\r\nhero:\r\n image:\r\n light:\r\n src: /light.svg\r\n alt: logo\r\n dark:\r\n src: /dark.svg\r\n alt: logo\r\n---\r\n```\r\n\r\nThis can be simplified to:\r\n\r\n```yaml\r\n---\r\nlayout: home\r\nhero:\r\n image:\r\n light: /light.svg\r\n dark: /dark.svg\r\n alt: logo\r\n---\r\n```",[2917],{"name":2918,"color":2919},"theme","0754FB",1436,"closed","allow specifying common alt for logo","2023-01-21T14:25:07Z","https://github.com/vuejs/vitepress/issues/1436",0.7497484,{"description":2927,"labels":2928,"number":2929,"owner":2874,"repository":2875,"state":2921,"title":2930,"updated_at":2931,"url":2932,"score":2933},"### Is your feature request related to a problem? Please describe.\n\nCurrently, when changing languages, the navbar links stay the same.\n\n### Describe the solution you'd like\n\nNavbar should have links based on the languages selected.\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.",[],1089,"Navbar for i18n","2023-01-21T14:28:59Z","https://github.com/vuejs/vitepress/issues/1089",0.75043577,{"description":2935,"labels":2936,"number":2937,"owner":2874,"repository":2875,"state":2921,"title":2938,"updated_at":2939,"url":2940,"score":2941},"### Is your feature request related to a problem? Please describe.\n\nI've embed a video in my markdown by search the help of Typora.\r\nIt works fine in Typora.\r\nIt is like this in my markdown:\r\n```\r\n\u003Cvideo controls=\"controls\" src=\"在家办公指南.assets\\Video_2020-02-23_230241.mp4\" />\r\n```\r\nIt works fine with the localhost via the command ` yarn docs:dev`\r\nbut when `yarn docs:build`, I got an error.\r\nHow can I do?\n\n### Describe the solution you'd like\n\nSupport the video control.\r\n\r\nI set up the site in LAN and won't expose to the WAN, the storage is no problem.\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.",[],1477,"embed video in markdown with vitepress","2023-01-21T14:25:05Z","https://github.com/vuejs/vitepress/issues/1477",0.75123394,{"description":2943,"labels":2944,"number":2946,"owner":2874,"repository":2875,"state":2921,"title":2947,"updated_at":2948,"url":2949,"score":2950},"### Is your feature request related to a problem? Please describe.\n\nI want to use the existing structure of VitePress, with kind of the same Layout, but different styling. I was thinking I would just build a custom theme, but it seems like I cannot access e.g. the navbar configs. Or at least I wouldnt know how?\n\n### Describe the solution you'd like\n\nI would like to know how I can build my own custom theme, using all the default data that i would provide otherwise using the default theme.\n\n### Describe alternatives you've considered\n\nUsing the default theme but changing it up, but I doubt that it's flexible enough. another thing would be to just for vitepress and implementing my own default theme, but I doubt that it's thought to be done like that.\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.",[2945],{"name":2918,"color":2919},912,"Extending/Mimicing default components in custom theme","2023-01-21T14:32:40Z","https://github.com/vuejs/vitepress/issues/912",0.7517975,{"description":2952,"labels":2953,"number":2957,"owner":2874,"repository":2875,"state":2921,"title":2958,"updated_at":2959,"url":2960,"score":2961},"### Describe the bug\r\n\r\n\r\n\r\n\r\n### Reproduction\r\n\r\n```ts\r\nexport default defineConfig({\r\n // ...\r\n sidebar: [{\r\n text: 'Recursos',\r\n collapsed: false,\r\n items: [\r\n {\r\n text: 'Máquinas virtuales',\r\n link: '/recursos/vms',\r\n },\r\n {\r\n text: 'Commons Library',\r\n link: 'https://faq.utnso.com.ar/commons'\r\n },\r\n {\r\n text: 'Linux man pages',\r\n link: 'https://man7.org/linux/man-pages/'\r\n },\r\n {\r\n text: 'Enunciado del TP',\r\n link: 'https://faq.utnso.com.ar/enunciado'\r\n },\r\n {\r\n text: 'Documento de Pruebas',\r\n link: 'https://faq.utnso.com.ar/pruebas',\r\n },\r\n {\r\n text: 'TPs Anteriores',\r\n link: '/recursos/tps-anteriores',\r\n },\r\n ]\r\n }]\r\n});\r\n```\r\n\r\n### Expected behavior\r\n\r\n\r\n\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: Linux 6.0 Pop!_OS 22.04 LTS\r\n CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz\r\n Memory: 8.17 GB / 15.41 GB\r\n Container: Yes\r\n Shell: 5.8.1 - /usr/bin/zsh\r\n Binaries:\r\n Node: 16.14.0 - ~/.nvm/versions/node/v16.14.0/bin/node\r\n Yarn: 1.22.19 - ~/.nvm/versions/node/v16.14.0/bin/yarn\r\n npm: 8.3.1 - ~/.nvm/versions/node/v16.14.0/bin/npm\r\n Browsers:\r\n Firefox: 109.0.1\r\n npmPackages:\r\n vitepress: 1.0.0-alpha.47 => 1.0.0-alpha.47\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nI was able to align it properly by setting:\r\n```scss\r\n.VPSidebarItem {\r\n .VPLink.link {\r\n display: flex;\r\n flex-grow: unset;\r\n }\r\n\r\n .VPLink.link svg {\r\n align-self: center;\r\n }\r\n}\r\n```\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] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2954],{"name":2955,"color":2956},"bug: pending triage","e99695",1962,"External link icon in sidebar not aligned properly","2023-03-05T00:04:51Z","https://github.com/vuejs/vitepress/issues/1962",0.766283,{"description":2963,"labels":2964,"number":2966,"owner":2874,"repository":2875,"state":2921,"title":2967,"updated_at":2968,"url":2969,"score":2970},"### Describe the bug\n\n\r\n\r\nno Ctrl+Space autocomplete on anything in the `export default { ... }` block in `theme/index.ts`\r\n\r\n```ts\r\n// https://vitepress.dev/guide/custom-theme\r\nimport { h } from 'vue'\r\nimport Theme from 'vitepress/theme'\r\nimport './style.css'\r\n\r\nexport default {\r\n extends: Theme,\r\n Layout: () => {\r\n return h(Theme.Layout, null, {\r\n // https://vitepress.dev/guide/extending-default-theme#layout-slots\r\n })\r\n },\r\n enhanceApp({ app, router, siteData }) {\r\n // ...\r\n app.\r\n // ^ NO autocomplete here 😢\r\n }\r\n}\r\n```\n\n### Reproduction\n\nhttps://stackblitz.com/edit/vite-bjyf4o?file=.vitepress%2Ftheme%2Findex.ts\n\n### Expected behavior\n\n\r\n\n\n### System Info\n\n```Text\nSystem:\r\n OS: Linux 5.0 undefined\r\n CPU: (2) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz\r\n Memory: 0 Bytes / 0 Bytes\r\n Shell: 1.0 - /bin/jsh\r\n Binaries:\r\n Node: 18.18.0 - /usr/local/bin/node\r\n Yarn: 1.22.19 - /usr/local/bin/yarn\r\n npm: 9.4.2 - /usr/local/bin/npm\r\n pnpm: 8.9.2 - /usr/local/bin/pnpm\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.22 => 1.0.0-rc.22\n```\n\n\n### Additional context\n\ni think the solution is to add a `satisfies import('vitepress').Theme` or similar in the docs examples and in the `vitepress init` wizard\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.",[2965],{"name":2888,"color":2889},3116,"no autocomplete on enhanceApp() or other things in theme/index.ts export default","2023-10-30T00:04:37Z","https://github.com/vuejs/vitepress/issues/3116",0.7662998,["Reactive",2972],{},["Set"],["ShallowReactive",2975],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fSGlHE4B93_Y7dqZT5Hjn4inxp4YXvWp1O-Nj8UQ9xd8":-1},"/vuejs/vitepress/4013"]