` to be served at `/blog/` and `\u003CArticle />` to be served at inner routes\r\n3. Use custom layout component in `.vitepress/theme/index.js`\r\n```js\r\nexport default {\r\n ...DefaultTheme,\r\n Layout,\r\n};\r\n```\r\n3. Define routing logic in `Layout.vue` component\r\n```js\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CBlog v-if=\"isIndex\" />\r\n \u003CArticle v-else />\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nimport { computed } from 'vue';\r\nimport { useRoute } from 'vitepress';\r\nimport Blog from './Blog.vue';\r\nimport Article from './Article.vue';\r\n\r\nconst route = useRoute();\r\nconst isIndex = computed(() => {\r\n return route.path.replace(/index.html$/, '') === '/';\r\n});\r\n\u003C/script>\r\n\r\n```\r\n\r\n### Expected behavior\r\n\r\nI expect that\r\n1. Blog component is served at `/blog/`\r\n2. Article component is served at `/blog/**/*` routes\r\n3. No `Hydration completed but contains mismatches.` error in the console\r\n4. No blinking screen that happens because the page is rendered as Article in SSR and then transformed into Blog during hydration\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: macOS 11.6\r\n CPU: (8) x64 Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz\r\n Memory: 176.77 MB / 16.00 GB\r\n Shell: 5.8 - /bin/zsh\r\n Binaries:\r\n Node: 16.1.0 - ~/.nvm/versions/node/v16.1.0/bin/node\r\n Yarn: 1.22.10 - /usr/local/bin/yarn\r\n npm: 7.17.0 - ~/.nvm/versions/node/v16.1.0/bin/npm\r\n Browsers:\r\n Brave Browser: 92.1.28.106\r\n Chrome: 96.0.4664.45\r\n Firefox: 90.0.2\r\n Safari: 15.0\r\n npmPackages:\r\n vitepress: ^0.20.1 => 0.20.1\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/coc)\r\n- [X] Read the [docs](https://vitepress.vuejs.org/).\r\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[],446,"route.path doesn't work correctly with base option","2023-01-21T14:35:45Z","https://github.com/vuejs/vitepress/issues/446",0.6830256,{"description":2953,"labels":2954,"number":2955,"owner":2868,"repository":2869,"state":2870,"title":2956,"updated_at":2957,"url":2958,"score":2959},"In Vitepress (vuejs/vitepress), the page HTML base path (`site.base`) and the static assets base path (`vite config.base`, equivalent to `publicPath` in webpack) are not handled separately. This causes issues when deploying the HTML and CDN separately (with the HTML being served from a dedicated domain and the CDN deployed on a general CDN service). The built pages cannot navigate correctly or the static assets fail to load properly.\r\n\r\nThe current code handling both `site.base` and `vite.config.base` consistently can be found at the following link:\r\n\r\nhttps://github.com/vuejs/vitepress/blob/b16340acbd3c60fee023daadb0ec5a0292060a1e/src/node/build/bundle.ts#L60\r\n\r\nIt would be beneficial to separate the handling of these two base paths to better support different deployment scenarios.",[],2144," Separate handling of page HTML base path and static assets base path in Vitepress","2023-04-04T00:03:58Z","https://github.com/vuejs/vitepress/issues/2144",0.68405867,["Reactive",2961],{},["Set"],["ShallowReactive",2964],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fWvi6w0-pLxgzWnNg8Un1ZWWGlxAmjr7eb5BR5z8VpX8":-1},"/vuejs/vitepress/252"]