` and even pass frontmatter to it or props to it, but I am unable to take that component and say - ok - I want you to appear in the Aside slot. Using the methods described in the documentation do not work when it is instantiated within markdown.md. What I am trying to do here is set up `Local Layout Slots` - that are only for that specific page or categories of pages. Using `layout: LayoutSlot` does not work as a workaround.\r\n\r\n**For Method 2** - I would also like to actually know how to create Custom Layouts with more detail, for example adding `\u003Ccontent />` to a template, disabled the sidebar and navigation information, and I have not figured out how to add the \u003Csidebar /> or navigation, or other built-in theme components - back in the same way I was able to do `\u003Ccontent />` . I don't understand how to style the CSS in the content section only of my local markdown.md files*(fully) or why when following the same structure as the documentation by `layout: CustomLayout` in Yaml Markdown will not activate the same way it does when I register it globally - even when nothing has changed about the code itself. I understand there is documentation for these things, but the documentation is not clear enough or makes some basic assumptions about knowledge that extend beyond what the documentation explains.\r\n\r\n\r\n**For Method 3** - Lets say I have a `markdown.md` and I have set up some `$frontmatter`. I have also set up a `Layout Slot`, that appends Globally (even though my goal is Local application only) - I am unable to get the Global Components to read the `$frontmatter` from the local markdown pages, and workarounds to pass the `$frontmatter` as props to the global component do not work - it only ever passes to local instances of the component. Is what I want to do possible (I know it is because of `outline.js` but upon inspection of outline.js the code it uses is awfully complicated for my brain - and with $frontmatter so easy, I would think why wouldn't it be able to pass to the global component for that page). I am sure there is something I am missing, but when reading documentation on how to access frontmatter, it didn't cover this topic.\r\n\r\nI have no idea if these are bugs or user errors, or a combination. But I do know 4-5 days in now and I need some help. Thank you.\r\n\r\n",[2934],{"name":2935,"color":2936},"question","5D5FAE",2757,"Unable to assign local Component to Layout Slot ","2023-08-18T00:04:12Z","https://github.com/vuejs/vitepress/issues/2757",0.6986284,{"description":2943,"labels":2944,"number":2948,"owner":2863,"repository":2864,"state":2898,"title":2949,"updated_at":2950,"url":2951,"score":2952},"### Describe the bug\r\n\r\nComponents at the start of a line/paragraph don't render their contents as Markdown despite other Markdown renders doing so.\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/vite-jgrywo?file=docs%2Findex.md\r\n\r\nLook at \"Some Markdown\" line. I expected it to render as Markdown...\r\n\r\n### Expected behavior\r\n\r\nIt should render as Markdown. When rendered by other systems at least it does. e.g. VS Code Markdown preview.\r\n\r\n### System Info\r\n\r\n```Text\r\nSystem:\r\n OS: Linux 5.0 undefined\r\n CPU: (8) 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.20.3 - /usr/local/bin/node\r\n Yarn: 1.22.19 - /usr/local/bin/yarn\r\n npm: 10.2.3 - /usr/local/bin/npm\r\n pnpm: 8.15.6 - /usr/local/bin/pnpm\r\n npmPackages:\r\n vitepress: latest => 1.2.3\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nVitePress:\r\n\r\n\r\nVS Code:\r\n\r\n\r\n\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.",[2945],{"name":2946,"color":2947},"wont fix","EDEED1",4017,"Components at the start of a line/paragraph don't render their contents as Markdown","2024-07-11T04:42:20Z","https://github.com/vuejs/vitepress/issues/4017",0.7003075,{"description":2954,"labels":2955,"number":2956,"owner":2863,"repository":2864,"state":2898,"title":2957,"updated_at":2958,"url":2959,"score":2960},"### Describe the bug\n\nI used a Vite plugin (which automatically restarts the server after modifying the MD file), but when the search was set to local search, the plugin failed to restart, perhaps because the search cache was not cleared\n\n### Reproduction\n\n```js\r\nimport { defineConfig } from \"vitepress\";\r\nimport fs from \"fs\";\r\n\r\nfunction autoRestart() {\r\n let restartPromise;\r\n return {\r\n name: \"auto-restart\",\r\n configureServer(server) {\r\n server.watcher.on(\"all\", (event, path) => {\r\n if (path.endsWith(\".md\")) {\r\n if (!restartPromise) {\r\n restartPromise = (async () => {\r\n console.log(\"Restarting server...\");\r\n // TODO: clearCache()?\r\n // [vitepress] MiniSearch: duplicate ID\r\n // [vitepress] server restart failed\r\n await server.restart();\r\n // await fs.promises.utimes(server.config.vitepress.configPath, new Date(), new Date());\r\n })().finally(() => {\r\n restartPromise = undefined;\r\n });\r\n }\r\n }\r\n });\r\n },\r\n }\r\n}\r\nexport default defineConfig({\r\n vite: {\r\n plugins: [\r\n autoRestart(),\r\n ],\r\n },\r\n themeConfig: {\r\n search: {\r\n provider: \"local\",\r\n }\r\n },\r\n});\r\n```\r\n\r\nWhen modifying the MD file did not restart successfully, but after turning off local search, the code can restart successfully\r\n\r\n```sh\r\nRestarting server...\r\n[vitepress] MiniSearch: duplicate ID\r\n[vitepress] server restart failed\r\n```\n\n### Expected behavior\n\nPerhaps a method is needed to `clearCache()` to restart, or the contents of the sidebar can be modified at any time during runtime to take effect in real-time\r\n\r\nlike this:\r\nhttps://github.com/vuejs/vitepress/blob/2ac64b8d4180f2a7c54fda57df7f3a0a52488d62/src/node/shortcuts.ts#L76-L88\r\nhttps://github.com/vuejs/vitepress/blob/2ac64b8d4180f2a7c54fda57df7f3a0a52488d62/src/node/plugin.ts#L371-L394\n\n### System Info\n\n```Text\nSystem:\r\n OS: macOS 15.0\r\n CPU: (8) arm64 Apple M1\r\n Memory: 130.73 MB / 8.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 22.9.0 - /opt/homebrew/bin/node\r\n npm: 10.8.3 - /opt/homebrew/bin/npm\r\n pnpm: 9.12.0 - /opt/homebrew/bin/pnpm\r\n Browsers:\r\n Edge: 129.0.2792.79\r\n Safari: 18.0\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.",[],4251,"Failed to restart using Vite plugin after setting up local search","2024-10-19T04:43:05Z","https://github.com/vuejs/vitepress/issues/4251",0.70069104,["Reactive",2962],{},["Set"],["ShallowReactive",2965],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fR4zeLTjNaMKjioKRGmHewKLq5aRm3Lh0vAa5EySdUbU":-1},"/vuejs/vitepress/3704"]