Divyansh Singh

Removed that line for now, let's see if we can reintroduce that functionality properly.

#856 will fix this

Actually adding a favicon doesn't need any config. Just put a `favicon.ico` in your public directory. Config is required when you've that icon file with some different name or base...

I don't think we need the context on the titles. IMO the current titles looks much cleaner. Also, spelling of introduction is wrong ("Inroduction"). I am keeping the PR open...

This is expected. `/foo/` resolves to `/foo/index.html` and `/foo` resolves `/foo.html`

Regarding this I've another doubt. That /docs is technically considered outside the base. Then why is our router intercepting such a link in first place? 👀 What happens when you...

Hi! This is actually the commonmark standard. You need to separate markdown and html/vue by at least a blank line. I'm not sure why the content is being duplicated. But...

Ah, this issue is also on https://vitepress.vuejs.org/guide/deploying.html > Later I found that it is intentional and VuePress is also doing the same. Yeah it was to create more space. But...

> moreover specifying a VSCode region alongside with a language (e.g. @/source/component.vue#props{typescript}) doesn't seem to work. That language thing was added recently, so its not in the latest release yet....

It doesn't look nice with sidebar, that's why its not there. If you want to create a PR, then make it optional to enable footer (using frontmatter or some theme...