\r\n```\r\nand in post or page that process by vitepress is correct url:\r\n```\r\n\u003Cimg src=\"/blog/xxxx/images/xxx.png\" />\r\n```\r\nhow can I make the right process by ourself ?",[],3072,"closed","[Query] How image url inside markdown transform to right url ?","2023-10-21T00:05:52Z","https://github.com/vuejs/vitepress/issues/3072",0.6606282,{"description":2906,"labels":2907,"number":2910,"owner":2874,"repository":2875,"state":2900,"title":2911,"updated_at":2912,"url":2913,"score":2914},"### Describe the bug\n\nWhen you define a link to an image in frontmatter or in config.js, the file is note copy in the dist folder, whereas for a link in the markdown file directly it works, also when you define a public folder with your pictures it copy the content of the folder directly in dist folder and not in a public folder in dist folder. \n\n### Reproduction\n\nat this in a makdown file that represents the home page :\r\nfeatures:\r\n - icon: \r\n src: /public/compiler.png\r\ncreate a public folder in docs with the image\r\n\r\nand build the project\r\n\r\n\n\n### Expected behavior\n\nit will be preferable if the content of public folder will be copy in a dist/public folder, because here you can just enter :\r\nfeatures:\r\n - icon: \r\n src: compiler.png\r\n\r\nbut it is not very clear\n\n### System Info\n\n```sh\nnpm run docs:build\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,2909],{"name":2868,"color":2869},{"name":2871,"color":2872},2422,"No inclusion of assets in frontmatter of markdown file and js config","2023-08-11T00:04:07Z","https://github.com/vuejs/vitepress/issues/2422",0.6767484,{"description":2916,"labels":2917,"number":2921,"owner":2874,"repository":2875,"state":2900,"title":2922,"updated_at":2923,"url":2924,"score":2925},"\u003C!--\r\nNOTE:\r\nVitePress is still WIP, and it is not compatible with VuePress.\r\nPlease do not open issue about default theme missing features or something doesn't work like VuePress.\r\n-->\r\n\r\n**Describe the bug**\r\nIn the markdown file, When reference a image file with encoded URL, it works in the dev mode, but it would faild to build.\r\n\r\n**To Reproduce**\r\nSteps to reproduce the behavior:\r\n1. a image file named `image (01).png`.\r\n1. a markdown file with content like this: ``\r\n1. run `vitepress build`\r\n\r\n**Expected behavior**\r\nShould build successfully.\r\n\r\n**System Info**\r\n- vitepress version: 0.11.5\r\n- vite version: 2.0.0-beta.62\r\n- Node version: 2.0.0-beta.62\r\n- OS version: Windows 10\r\n",[2918],{"name":2919,"color":2920},"duplicate","cfd3d7",220,"can not handle encoded image URLs in build mode","2023-01-21T16:23:56Z","https://github.com/vuejs/vitepress/issues/220",0.695529,{"description":2927,"labels":2928,"number":2929,"owner":2874,"repository":2875,"state":2900,"title":2930,"updated_at":2931,"url":2932,"score":2933},"### Is your feature request related to a problem? Please describe.\n\nCurrently, Vitepress provides functions like `usePage` or `frontmatter` to retrieve frontmatter data of the rendered page. However, there is no built-in functionality to retrieve frontmatter data of multiple Markdown files within a directory.\r\n\r\nImagine I'm crafting a custom layout, possibly for a portfolio or blog page. Within my project directory, I have folders like `project/blog/` or `project/portfolio` alongside the main `index.md`. Inside these directories lie numerous Markdown files, each containing frontmatter data similar to this:\r\n\r\n```md\r\n---\r\ntitle: Blog Post Title\r\ndate: 2024-03-27\r\nauthor: John Doe\r\ntags: [blog, update]\r\nlayout: blog\r\n---\r\n\r\n# Blog Post Title\r\n\r\nThis is the content of your blog post, written in Markdown format.\r\n\r\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Sed eget turpis nec leo euismod fringilla vitae ut quam.\r\n```\r\n\r\nHowever, my challenge arises when attempting to access the frontmatter data of all these files. While Vitepress offers functions like usePage or frontmatter to retrieve individual page data, there isn't an equivalent function like usePages to access data from multiple files simultaneously.\n\n### Describe the solution you'd like\n\nI would like to propose the addition of a new function or hook, such as `usePages`, that allows developers to retrieve frontmatter data of all Markdown files within a specified directory. This would provide more flexibility and enable the creation of custom layouts for portfolio or blog-related pages.\n\n### Describe alternatives you've considered\n\nAs an alternative, developers currently have to manually parse Markdown files using Node.js scripts before building the Vitepress project. However, this approach is less convenient and may not integrate seamlessly with the Vitepress development workflow.\n\n### Additional context\n\nBy adding support for retrieving frontmatter data of multiple Markdown files, developers can streamline the development process and create more dynamic and customizable layouts for their Vitepress projects. This feature would enhance the flexibility and usability of Vitepress, making it even more appealing for building static websites and blogs.\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.",[],3710,"Feature Request: Add Support for Retrieving Frontmatter Data from Multiple Markdown Files","2024-04-28T12:25:23Z","https://github.com/vuejs/vitepress/issues/3710",0.7024468,{"description":2935,"labels":2936,"number":2937,"owner":2874,"repository":2875,"state":2900,"title":2938,"updated_at":2939,"url":2940,"score":2941},"### Is your feature request related to a problem? Please describe.\r\n\r\nI'm using vitepress in an existing project for documentation, and I want to keep the docs build in a separate directory for instance:\r\n\r\n```\r\ndocs\r\n - assets\r\n - xxx.js\r\n - index.html\r\nsrc\r\n - App.vue\r\n```\r\n\r\nBut I can't load `/docs/index.html` since the assets use an absolute url `/assets/xxx.js`.\r\n\r\n### Describe the solution you'd like\r\n\r\nCan we allow relative url in the `index.html` so that when loading `docs/index.html` it's still working ?\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/coc)\r\n- [X] Read the [docs](https://vitepress.vuejs.org/).\r\n- [X] Read the [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/master/.github/contributing.md).\r\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[],381,"Allow relative path for assets / scripts in out index.html","2023-01-21T14:33:00Z","https://github.com/vuejs/vitepress/issues/381",0.704576,{"description":2943,"labels":2944,"number":2945,"owner":2874,"repository":2875,"state":2900,"title":2946,"updated_at":2947,"url":2948,"score":2949},"### Describe the bug\r\n\r\nWhen I create a new folder in the root directory and create an md file in the new folder. Then click the 'Display detailed list' button and search. Details are not displayed in the search results. And an error appears in the console.\r\n```\r\nGET http://localhost:4173/assets/guide/test_index.md.undefined.js net::ERR_ABORTED 404 (Not Found)\r\nTypeError: Failed to fetch dynamically imported module: http://localhost:4173/assets/guide/test_index.md.undefined.js\r\n```\r\n\r\n### Reproduction\r\n\r\n**1. Install (Default configuration)**\r\n```\r\nnpm init -y\r\nnpm i -D vitepress\r\nnpx vitepress init\r\n```\r\nFile structure:\r\n```\r\n.\r\n├─ .vitepress\r\n│ └─ config.ts\r\n├─ api-examples.md\r\n├─ markdown-examples.md\r\n├─ index.md\r\n└─ package.json\r\n```\r\n\r\n**2. Create folders and files**\r\nFile structure:\r\n```\r\n.\r\n├─ guide\r\n│ └─ test.md\r\n├─ .vitepress\r\n│ └─ config.ts\r\n├─ api-examples.md\r\n├─ markdown-examples.md\r\n├─ index.md\r\n└─ package.json\r\n```\r\nguide/test.md\r\n```\r\n# vite\r\nvitepress\r\n```\r\n\r\n**3. Turn on local search**\r\nconfig.ts\r\n```\r\nimport { defineConfig } from 'vitepress'\r\n\r\n// https://vitepress.dev/reference/site-config\r\nexport default defineConfig({\r\n title: \"My Awesome Project\",\r\n description: \"A VitePress Site\",\r\n themeConfig: {\r\n search: {\r\n provider: 'local'\r\n },\r\n // https://vitepress.dev/reference/default-theme-config\r\n nav: [\r\n { text: 'Home', link: '/' },\r\n { text: 'Examples', link: '/markdown-examples' }\r\n ],\r\n\r\n sidebar: [\r\n {\r\n text: 'Examples',\r\n items: [\r\n { text: 'Markdown Examples', link: '/markdown-examples' },\r\n { text: 'Runtime API Examples', link: '/api-examples' }\r\n ]\r\n }\r\n ],\r\n\r\n socialLinks: [\r\n { icon: 'github', link: 'https://github.com/vuejs/vitepress' }\r\n ]\r\n }\r\n})\r\n```\r\n\r\n**4. Build and preview**\r\n```\r\nnpm run docs:build\r\nnpm run docs:preview\r\n```\r\n\r\n**5. Search**\r\n\r\n\r\n\r\n### Expected behavior\r\n\r\nShow the details.\r\n\r\n### System Info\r\n\r\n```shell\r\nWindows 10 22H2\r\nNodeJS v16.14.0\r\nEdge 112.0.1722.48\r\nVitepress 1.0.0-alpha.72\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] 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.",[],2245,"detailed view in local search breaks if fetched excerpt has useData call","2023-05-20T00:04:05Z","https://github.com/vuejs/vitepress/issues/2245",0.71081316,{"description":2951,"labels":2952,"number":2953,"owner":2874,"repository":2875,"state":2900,"title":2954,"updated_at":2955,"url":2956,"score":2957},"### Describe the bug\r\n\r\nIf you include one or more Markdown files in another page, the local search index \"sees them all\" as separate pages - i.e. not as 1 single page which can be navigated to via the local search box. \r\n\r\n### Reproduction\r\n\r\n1. Add the following Markdown files to a Vitepress project\r\n\r\n **part_1.md**\r\n ```\r\n Hello\r\n ```\r\n \r\n **part_2.md**\r\n ```\r\n World\r\n ```\r\n \r\n **index.md**\r\n ```\r\n \u003C!--@include: ./part_1.md-->\r\n \r\n \u003C!--@include: ./part_2.md-->\r\n ```\r\n \r\n2. Configure local search and search for the word \"Hello\".\r\n\r\n\r\n### Expected behavior\r\n\r\nGiven the example above, I would expect:\r\n\r\n1. It is not possible to navigate to `part_1.md` or `part_2.md` pages at all.\r\n2. Searching for the word \"Hello\" will show `index.md` as the only result.\r\n\r\n### System Info\r\n\r\n```sh\r\nSystem:\r\n OS: Linux 6.2 Ubuntu 23.04 23.04 (Lunar Lobster)\r\n CPU: (16) x64 Intel(R) Core(TM) i9-10885H CPU @ 2.40GHz\r\n Memory: 55.33 GB / 62.54 GB\r\n Container: Yes\r\n Shell: 5.2.15 - /bin/bash\r\n Binaries:\r\n Node: 18.17.1 - /usr/bin/node\r\n npm: 9.6.7 - /usr/bin/npm\r\n Browsers:\r\n Chrome: 116.0.5845.96\r\n Chromium: 116.0.5845.96\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.4 => 1.0.0-rc.4 \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.",[],2812,"process includes before creating search index","2023-09-18T00:04:21Z","https://github.com/vuejs/vitepress/issues/2812",0.71228206,{"description":2959,"labels":2960,"number":2967,"owner":2874,"repository":2875,"state":2900,"title":2968,"updated_at":2969,"url":2970,"score":2971},"There are situations where a markdown file can become really long.\r\n\r\nIs it possible to \"cook\" a single MD file that my VitePress will show as 1 page, but have its contents be a combination of multiple MD files?\r\n\r\nEg. (just an example syntax so you know what I'm trying to achieve)\r\n\r\n```md\r\n\u003Cscript>\r\nimport basics from './parts/basics.md'\r\nimport reference from './parts/reference.md'\r\n\u003C/script>\r\n\r\n# Docs\r\n\r\n## Basics\r\n\r\n{{ basics }}\r\n\r\n## API Reference\r\n\r\n{{ reference }}\r\n\r\n```",[2961,2964],{"name":2962,"color":2963},"docs","0075ca",{"name":2965,"color":2966},"question","5D5FAE",411,"question: how to import a markdown file & display its contents in another markdown file","2023-01-21T14:32:38Z","https://github.com/vuejs/vitepress/issues/411",0.7157592,["Reactive",2973],{},["Set"],["ShallowReactive",2976],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fTlikYfTGSILcIvRXJBBZoo3_301pI89KjwEn2p2tFS8":-1},"/vuejs/vitepress/2999"]