\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.",[2908],{"name":2877,"color":2878},3047,"CSS i18n in one page","2025-03-02T18:10:37Z","https://github.com/vuejs/vitepress/issues/3047",0.7594987,{"description":2915,"labels":2916,"number":2917,"owner":2866,"repository":2867,"state":2918,"title":2919,"updated_at":2920,"url":2921,"score":2922},"when use some new language blocks in `md`, such as `wgsl`, it shows `No language registration for wgsl`\r\n\r\nThe shiki support add custom languages: https://github.com/shikijs/shiki/blob/main/docs/languages.md#supporting-your-own-languages-with-shiki\r\n\r\nThen, how to use it in VitePress to add custom languages?",[],1331,"closed","How to add register language/grammar for shiki?","2023-01-21T14:25:07Z","https://github.com/vuejs/vitepress/issues/1331",0.71798885,{"description":2924,"labels":2925,"number":2926,"owner":2866,"repository":2867,"state":2918,"title":2927,"updated_at":2928,"url":2929,"score":2930},"https://github.com/vuejs/vitepress/blob/e6f9dd33c73411ded5461670f68ed4fe8c5923fa/src/node/plugin.ts#L405-L408\r\n\r\nthis doesn't consider rewrites",[],4172,"watchers not being triggered on data updates in pages with rewrites","2024-09-09T04:43:00Z","https://github.com/vuejs/vitepress/issues/4172",0.73081744,{"description":2932,"labels":2933,"number":2937,"owner":2866,"repository":2867,"state":2918,"title":2938,"updated_at":2939,"url":2940,"score":2941},"### Describe the bug\n\nJust follow the document, add workflow and push docs to repo.\r\nVitepress works well locally with `pnpm docs:dev`, but after deploy to github pages, it losts the index.md content, or in another word, useful part of them, as you can see, it does have the notes part\r\n[](https://imgse.com/i/xniiA1)\r\nI have checked the local build file, it contains the correct content.\r\nSince i used the exact workflow and already set the `base` config, i can't figure out why it leads to this.\n\n### Reproduction\n\nclone this repo [Youbei](https://github.com/Hellager/Youbei) and deploy its docs to the github pages\n\n### Expected behavior\n\nGithub pages show normally like docs in local\r\n[](https://imgse.com/i/xniuBd)\n\n### System Info\n\n```shell\nSystem:\r\n OS: Windows 10 10.0.19044\r\n CPU: (8) x64 Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz\r\n Memory: 2.11 GB / 7.78 GB\r\n Binaries:\r\n Node: 16.13.1 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.19 - ~\\AppData\\Local\\pnpm\\yarn.CMD\r\n npm: 8.1.2 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (105.0.1343.50)\r\n Internet Explorer: 11.0.19041.1566\r\n npmPackages:\r\n vitepress: 1.0.0-alpha.17 => 1.0.0-alpha.17\n```\n\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] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2934],{"name":2935,"color":2936},"bug: pending triage","e99695",1413,"Deploying to github pages and lost both router and content ","2023-01-21T14:25:20Z","https://github.com/vuejs/vitepress/issues/1413",0.7311873,{"description":2943,"labels":2944,"number":2949,"owner":2866,"repository":2867,"state":2918,"title":2950,"updated_at":2951,"url":2952,"score":2953},"### Is your feature request related to a problem? Please describe.\r\n\r\nHello,\r\n\r\nActually, I have to create a loader for each language, and then import all of them in my vue component.\r\n\r\n```ts\r\n// @ts-expect-error - vitepress types are not available\r\nimport { data as rootData } from '../../data/posts.data'\r\n// @ts-expect-error - vitepress types are not available\r\nimport { data as frData } from '../../data/fr-posts.data'\r\nimport { computed } from 'vue';\r\n\r\nconst data: Record\u003Cstring, any> = {\r\n root: rootData,\r\n fr: frData\r\n}\r\n\r\nconst { localeIndex } = useData()\r\n\r\nconst posts = computed(() => data[localeIndex.value])\r\n```\r\n\r\n### Describe the solution you'd like\r\n\r\nI would like to have to only create a single content loader and based on my locales configuration (and maybe an option) retrive all content.\r\n\r\nFor example: `posts/*.md` should get `posts/*.md` (the root) and `fr/posts/*.md` (the fr locale).\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.",[2945,2948],{"name":2946,"color":2947},"has-workaround","1B4515",{"name":2877,"color":2878},4072,"Support i18n in `contentLoader`","2024-10-08T04:44:35Z","https://github.com/vuejs/vitepress/issues/4072",0.734149,{"description":2955,"labels":2956,"number":2960,"owner":2866,"repository":2867,"state":2918,"title":2961,"updated_at":2962,"url":2963,"score":2964},"### Is your feature request related to a problem? Please describe.\n\nI would like to format sidebar items' text content as inline code blocks\r\n\r\nHere we can see I attempted providing markdown, and also edited the first three items in the browser to be `code` tags\r\n\u003Cimg width=\"266\" alt=\"image\" src=\"https://user-images.githubusercontent.com/5033303/195881206-206b8123-5c67-43ed-a2ab-221f82fe2e5c.png\">\r\n\n\n### Describe the solution you'd like\n\n- allow markdown in SidebarItem's `text` property\r\n- allow HTML strings in SidebarItem's `text` property\n\n### Describe alternatives you've considered\n\njust using the default display\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.",[2957],{"name":2958,"color":2959},"theme","0754FB",1486,"allow HTML strings in SidebarItem `text`","2023-01-21T14:22:59Z","https://github.com/vuejs/vitepress/issues/1486",0.7343196,["Reactive",2966],{},["Set"],["ShallowReactive",2969],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f672tnO82_H-6ziNPY3mpPSy17duQ9rgK3BgsuEBnMrI":-1},"/vuejs/vitepress/1411"]