Divyansh Singh

@peterbe Do your markdown files have some data in frontmatter that can tell their breadcrumb path? Asking because the final part of breadcrumb can be inferred from title, but not...

If you can maintain an object like this: ```ts const names = { 'my-cool-directory': 'My Cool Dir', ... } ``` You can use https://vitepress.dev/reference/site-config#transformpagedata to do something like this: ```ts...

> And need to make sure it can be used together with `:line-numebrs` so it won't break anything This will be difficult. Code wrapping doesn't work properly with current line...

Yeah we can add the wrap feature.

One question regarding the middleware part, do people have use cases where they will be using an internal `publicPath`? PS: Not sure about the naming too, `publicPath` might sound confusing...

> won't be parsed as an image for there is a blank space Yeah, that's compliant with commonmark spec. You can either manually percent encode it (to `%20`) or use...

Try using https://github.com/emersonbottero/vitepress-plugin-search or https://docs.oramasearch.com/open-source/plugins/plugin-vitepress once.

> I think those are already hidden somehow. I can definitely add styling for those, though! they aren't, check on the deploy preview: https://deploy-preview-2913--vitepress-docs.netlify.app/ also why hide navbar and footer?

The workaround mentioned there could work for you. Use `.includes()` inside the `filter` function? We aren't planning to move away from minisearch though. So, there won't be direct way probably.

ah sorry, you need `boostDocument`. you'll get the search term as second param. returning any falsy value skips the search result.