ArcGIS\r\n details: Use the ArcGIS Maps SDK for JavaScript to build compelling web apps that unlock your data’s potential with interactive user experiences and stunning 2D and 3D visualizations.\r\n link: https://developers.arcgis.com/javascript/latest/\r\n target: \"_blank\"\r\n```\r\nIt runs well in dev, but when I deployed on gh-pages in a custom repository, the site comes like \\\u003Cusername\\>.github.io/\\\u003Crepo\\>/xxx.So I set base option in ./docs/.vitepress/config.mts, the logo.png runs well under this option.but in `index.md>home layout>features`,it didn't work.\r\nif add a \\\u003Crepo\\> before src link, worked but I should change it every time when add or remove a feature:\r\n```md\r\nfeatures:\r\n - title: \u003Cimg src= \"/gest_webgis/imgs/ArcGIS.png\" alt=\"ArcGIS\" class=\"inline-block\"/>ArcGIS\r\n details: Use the ArcGIS Maps SDK for JavaScript to build compelling web apps that unlock your data’s potential with interactive user experiences and stunning 2D and 3D visualizations.\r\n link: https://developers.arcgis.com/javascript/latest/\r\n target: \"_blank\"\r\n```\r\nHow can I use a `withBase` helper in vitepress within formatter in md files?\r\n\r\n### Reproduction\r\n\r\nwrite an img tag in `home layout > features>title`,set base option in ./docs/.vitepress/index.{js,mts}\r\n\r\n\r\n### Expected behavior\r\n\r\nthe /imgs/xxx.png should automatically change into ${baseUrl}/imgs/xxx.png at runtime or use withBase helper in home features\r\n\r\n### System Info\r\n\r\n```Text\r\nwin11, gitpub pages\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Validations\r\n\r\n- [X] Check if you're on the [latest VitePress version](https://github.com/vuejs/vitepress/releases/latest).\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] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2924],{"name":2914,"color":2915},3139,"How to use a `withBase` helper in vitepress within formatter in md files?","2023-11-02T00:04:19Z","https://github.com/vuejs/vitepress/issues/3139",0.70181525,{"description":2931,"labels":2932,"number":2938,"owner":2872,"repository":2873,"state":2896,"title":2939,"updated_at":2940,"url":2941,"score":2942},"### Is your feature request related to a problem? Please describe.\n\n Hi team, currently there is no `StackOverlfow` icon in the `SocialLinkIcon` type, which makes it difficult for the developers to add their relevant StackOverflow links to their documentation sites.\n\n### Describe the solution you'd like\n\nAdd the `StackOverflow` icon to the `SocialLinkIcon` type,.\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.",[2933,2934,2937],{"name":2866,"color":2867},{"name":2935,"color":2936},"has-workaround","1B4515",{"name":2869,"color":2870},4135,"Add `StackOverflow` icon to the `SocialLinkIcon` type.","2024-11-12T04:43:09Z","https://github.com/vuejs/vitepress/issues/4135",0.7182825,{"description":2944,"labels":2945,"number":2947,"owner":2872,"repository":2873,"state":2896,"title":2948,"updated_at":2949,"url":2950,"score":2951},"### Describe the bug\n\nI was trying to follow these instructions [here](https://vitepress.dev/guide/extending-default-theme#customizing-css) just to change the color of the Title on the home page.\r\nAccording [this section](https://vitepress.dev/guide/custom-theme#theme-resolving), just by creating the `.vitepress/theme/index.js` and `.vitepress/theme/custom.css` files that the [Customizing CSS](https://vitepress.dev/guide/extending-default-theme#customizing-css) suggests should be enough to have it being read.\r\nBut no. That alone does not work.\r\n\r\nI had to add `import './theme/custom.css'` to the `config.ts` file first to force it to read the custom css.\r\n\r\n**edit:**\r\nmore recently I tried renaming the `.vitepress/theme/index.js` to `.ts` and then it woke up! now it is aware of that file...\r\nLooks like a bug, no?\n\n### Reproduction\n\nI was trying to follow these instructions [here](https://vitepress.dev/guide/extending-default-theme#customizing-css) just to change the color of the Title on the home page.\r\nAccording [this section](https://vitepress.dev/guide/custom-theme#theme-resolving), just by creating the `.vitepress/theme/index.js` and `.vitepress/theme/custom.css` files that the [Customizing CSS](https://vitepress.dev/guide/extending-default-theme#customizing-css) suggests should be enough to have it being read.\r\nBut no. That alone does not work.\r\n\r\nI had to add `import './theme/custom.css'` to the `config.ts` file first to force it to read the custom css.\r\n\r\n**edit:**\r\nmore recently I tried renaming the `.vitepress/theme/index.js` to `.ts` and then it woke up! now it is aware of that file...\r\nLooks like a bug, no?\n\n### Expected behavior\n\nbe able to follow along the initial instructions on custom css\n\n### System Info\n\n```sh\nmac os catalina latest vitepress nodejs 16 npm 6.9\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.",[2946],{"name":2914,"color":2915},2612,"simple css overriding ain't happening","2023-08-21T00:04:12Z","https://github.com/vuejs/vitepress/issues/2612",0.7242091,{"description":2953,"labels":2954,"number":2955,"owner":2872,"repository":2873,"state":2896,"title":2956,"updated_at":2957,"url":2958,"score":2959},"### Is your feature request related to a problem? Please describe.\n\nLet's say we got a folder structure like this:\r\n\r\n\r\n└─ foo\r\n ├─ 1.0.0.md\r\n ├─ 2.0.0.md\r\n └─ 3.0.0.md\r\n\r\nRight now we would have routes like:\r\n `/foo/1.0.0.html`\r\n `/foo/2.0.0.html`\r\n `/foo/3.0.0.html`\r\n\r\nI'd like to also have a route or alias like the following: `/foo/latest` which will point to the latest version (this can all be determined on build time by looking at the file, I already have a function that gives me the latest \"route\", in this case `/foo/3.0.0.html`.\r\n\r\nHow can I make this `/foo/latest` route exist and be an alias to the one I wanted?\n\n### Describe the solution you'd like\n\nAllow us to define route aliases or redirects\n\n### Describe alternatives you've considered\n\nI've tried with rewrites but that allowed me to make the latest version redirected to /latest instead. I want the reverse.\n\n### Additional context\n\nIf this is not something you think vitepress should have because it's not SSG friendly (there is no latest.html file) then I understand.\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.",[],2922,"Route Alias or Redirect","2023-09-16T00:04:02Z","https://github.com/vuejs/vitepress/issues/2922",0.72428524,{"description":2961,"labels":2962,"number":2964,"owner":2872,"repository":2873,"state":2896,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### Describe the bug\n\n\r\n\n\n### Reproduction\n\nN/A\n\n### Expected behavior\n\nN/A\n\n### System Info\n\n```shell\nN/A\n```\n\n\n### Additional context\n\nN/A\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.",[2963],{"name":2866,"color":2867},1714,"The content of the Badge component's text property is displayed in the outline header","2023-01-29T00:04:25Z","https://github.com/vuejs/vitepress/issues/1714",0.724629,["Reactive",2970],{},["Set"],["ShallowReactive",2973],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f5Nry0zy3GLdandyhxbQ1SimgmrQ_9gY89ZFZMfQEHLY":-1},"/vuejs/vitepress/559"]