\r\n```\r\n\r\nAlternatively, use the `desc` defined in the `container` to write Markdown syntax.\r\n\r\n```md\r\n::: demo src=\"../demo.vue\" title=\"Demo block\"\r\n\r\nThis is a `description` that can be written using Markdown.\r\n\r\n:::\r\n```\r\n\r\n### Describe the solution you'd like\r\n\r\nTo address this, I have created the [markdown-it-vitepress-demo](https://github.com/hairyf/markdown-it-vitepress-demo) plugin. I'm not sure if it can be helpful.\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- https://github.com/vuejs/vitepress/issues/987\r\n- https://github.com/vuejs/vitepress/issues/1349\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.",[2867],{"name":2868,"color":2869},"stale","ededed",2432,"vuejs","vitepress","open","feat(demo): built-in markdown plugin provides support for showcasing demo capabilities.","2024-07-17T14:37:26Z","https://github.com/vuejs/vitepress/issues/2432",0.71306807,{"description":2879,"labels":2880,"number":2884,"owner":2871,"repository":2872,"state":2885,"title":2886,"updated_at":2887,"url":2888,"score":2889},"### Is your feature request related to a problem? Please describe.\r\n\r\nWhen I write documentation, I sometimes want to have some sort of introductory paragraph to set some context for the readers. These kinds of introductory paragraphs are often visually emphasized to catch attention and get even more impactful. Usually, the emphasis relies on styling (e.g. bigger font size, bolder font weights, etc).\r\n\r\nI really think it would be convenient for many users to be able to specify introductions in a straight-forward and _markdownish_ way, so that such content gets emphasized through styling while preserving other markdown rules and features .\r\n\r\n### Describe the solution you'd like\r\n\r\nTo address this need, we basically want to take a whole identified block and apply some styles to make it stand out. It turns out this kind of feature already exists in Vitepress: [custom containers](https://vitepress.dev/guide/markdown#custom-containers). These perfectly match our needs because:\r\n- they can be clearly identified because the syntax really pops out\r\n- their content still benefit from markdown syntax\r\n- they contextually provide their content a special, highlighted role\r\n\r\nMy belief is that it makes sense to also provide a `intro` custom container because those share a common philosophy. However, there is a slight difference : unlike other custom containers, I feel like it does not make any sense for `intro`s to include default and custom titles because well… they're introductions).\r\n\r\n### Describe alternatives you've considered\r\n\r\nI used to work this around by explicitly wrapping my introductory paragraph with a `\u003Cp class=\"intro\">\u003C/p>` block, and defining some CSS on the `.intro` selector, since it is supported. This works just fine, but being in a explicit HTML block prevents me from benefiting from other markdown features. For example, this would not work as expected:\r\n\r\n```md\r\n\u003Cp class=\"intro\">\r\n [click me](https://github.com)\r\n\u003C/p>\r\n```` \r\n\r\n### Additional context\r\n\r\nI've came up with the following draft PR: #2474. It's marked as draft because [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/main/.github/contributing.md) state that we \"should open a suggestion issue first \", but could not resist to give it a try.\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.",[2881],{"name":2882,"color":2883},"theme","0754FB",2473,"closed","Introduction custom container","2023-07-29T00:04:10Z","https://github.com/vuejs/vitepress/issues/2473",0.65062815,{"description":2891,"labels":2892,"number":2893,"owner":2871,"repository":2872,"state":2885,"title":2894,"updated_at":2895,"url":2896,"score":2897},"### Is your feature request related to a problem? Please describe.\n\nNo\n\n### Describe the solution you'd like\n\nThe custom container are a very useful feature and it can be configurable in the .vitepress/config.js file with color for \r\nname,border, border-dark, background, background-dark in the config file with these 5 options i think it will make a better for a better blog points.\n\n### Describe alternatives you've considered\n\nHaving the lack of customization for the custom container boxes. I am aware that you can create components to do the same things but the \"::: name :::\" syntax is better to view in markdown as well as more read able than having it wrapped inside a html tag.\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.",[],1246,"Adding Custom Containers from the config.js file ","2023-01-21T14:26:51Z","https://github.com/vuejs/vitepress/issues/1246",0.66994363,{"description":2899,"labels":2900,"number":2901,"owner":2871,"repository":2872,"state":2885,"title":2902,"updated_at":2903,"url":2904,"score":2905},"### Is your feature request related to a problem? Please describe.\n\n当我在文档里插入图片发布后,图片中有部分内容在页面上较为模糊。我试过markdown-it-custom-attrs插件,但是好像没有生效。\n\n### Describe the solution you'd like\n\n在vitepress中集成图片灯箱的功能,或者有什么办法可以集成相关组件(希望给一个示例)\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.",[],2674,"能否增加一个图片点击放大的功能。","2023-08-01T00:04:35Z","https://github.com/vuejs/vitepress/issues/2674",0.6732019,{"description":2907,"labels":2908,"number":2909,"owner":2871,"repository":2872,"state":2885,"title":2910,"updated_at":2911,"url":2912,"score":2913},"### Is your feature request related to a problem? Please describe.\n\n@mdit-vue/plugin-toc had recently made a change to allow nested headers in HTML on markdown pages. Please update this package.\n\n### Describe the solution you'd like\n\nUpdate @mdit-vue/plugin-toc dependency\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.",[],1919,"Update dependency @mdit-vue/plugin-toc","2023-02-20T00:04:33Z","https://github.com/vuejs/vitepress/issues/1919",0.68478644,{"description":2915,"labels":2916,"number":2917,"owner":2871,"repository":2872,"state":2885,"title":2918,"updated_at":2919,"url":2920,"score":2921},"### Is your feature request related to a problem? Please describe.\n\nFeature and/or problem (in the latter case is just a lacking documentation).\n\n### Describe the solution you'd like\n\nSince VP already uses Iconify, I'd like to be able to use inline iconify icons in markdown, is it possible somehow maybe like dropping a tag like if it was template? Eg:\r\n\r\n```\r\n## Sample text\r\nHere's an inline icon: \u003CIcon icon=\"mdi-light:home\" />\r\n```\r\nI think this is pretty reasonable to have.\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.",[],3068,"Use Iconify icons in inline markdown","2023-10-20T00:04:33Z","https://github.com/vuejs/vitepress/issues/3068",0.6883305,{"description":2923,"labels":2924,"number":2928,"owner":2871,"repository":2872,"state":2885,"title":2929,"updated_at":2930,"url":2931,"score":2932},"### Is your feature request related to a problem? Please describe.\n\nno\n\n### Describe the solution you'd like\n\nIf the highlight function is passed in `options: MarkdownOptions`, this function will be invoked, otherwise the default will be used.\r\n\r\n```ts\r\n const md = MarkdownIt({ \r\n html: true, \r\n linkify: true, \r\n highlight: options.highlight || await highlight(options.theme), \r\n ...options \r\n }) as MarkdownRenderer \r\n```\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.",[2925],{"name":2926,"color":2927},"build","377ba8",754,"Custom highlight","2023-01-21T14:32:58Z","https://github.com/vuejs/vitepress/issues/754",0.69465274,{"description":2934,"labels":2935,"number":2937,"owner":2871,"repository":2872,"state":2885,"title":2938,"updated_at":2939,"url":2940,"score":2941},"### Is your feature request related to a problem? Please describe.\r\n\r\nId like to not use a `|` in the browser title bar of my application, instead, any other string.\r\n\r\n### Describe the solution you'd like\r\n\r\nin config.js, at some place...\r\n\r\n```js\r\n{\r\n ...\r\n titleDelimiter: '·',\r\n ...\r\n}\r\n```\r\n\r\n### Describe alternatives you've considered\r\n\r\n_No response_\r\n\r\n### Additional context\r\n\r\nI should think it would be able to take even an HTML entity like `·` and render that.\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.",[2936],{"name":2882,"color":2883},1195,"Provide option to change title delimiter","2023-01-21T14:26:36Z","https://github.com/vuejs/vitepress/issues/1195",0.69536746,{"description":2943,"labels":2944,"number":2946,"owner":2871,"repository":2872,"state":2885,"title":2947,"updated_at":2948,"url":2949,"score":2950},"### Is your feature request related to a problem? Please describe.\n\nIn VuePress it was possible to set default titles for TIP, INFO, WARNING, DANGER, DETAILS in config but in VitePress it doesn't work anymore.\n\n### Describe the solution you'd like\n\nAdd something like this in a config:\r\n```js\r\nthemeConfig: {\r\n\tcontainer: {\r\n\t\ttip: 'Tip',\r\n\t\tinfo: 'Info',\r\n\t\twarning: \"Warning\",\r\n\t\tdanger: 'Danger',\r\n\t\tdetails: \"Details\"\r\n\t},\r\n}\r\n```\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.",[2945],{"name":2868,"color":2869},1947,"Add i18n support for default Custom Container titles","2023-08-11T00:04:11Z","https://github.com/vuejs/vitepress/issues/1947",0.6982337,{"description":2952,"labels":2953,"number":2954,"owner":2871,"repository":2872,"state":2885,"title":2955,"updated_at":2956,"url":2957,"score":2958},"### Is your feature request related to a problem? Please describe.\n\n希望增加一个换算器就是类似于wetab上面的那种,功能比较多\r\n\r\n\r\n\n\n### Describe the solution you'd like\n\n希望增加一个换算器就是类似于wetab上面的那种,功能比较多 \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.",[],3670,"希望增加一个换算器","2024-04-28T12:27:43Z","https://github.com/vuejs/vitepress/issues/3670",0.705586,["Reactive",2960],{},["Set"],["ShallowReactive",2963],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f2mPc98nfMZkdwmr_yynTgu7xQHt5IxMK9QEx_bXIEUg":-1},"/vuejs/vitepress/765"]