Skip to content

Commit 9700b6f

Browse files
committed
Merge branch 'docs/draft-multipath-routing' of https://github.com/vuestorefront/vue-storefront into docs/draft-multipath-routing
2 parents c8e0ca6 + 7816c19 commit 9700b6f

File tree

1 file changed

+2
-2
lines changed
  • docs/content/guides/7.multistore/3.patterns/5.subpath

1 file changed

+2
-2
lines changed

Diff for: docs/content/guides/7.multistore/3.patterns/5.subpath/1.subpath.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ navigation:
88
# How to Make Sub-path Routing
99

1010

11-
Sub-path routing allows you to serve different store configurations from the same Alokai deployment using URL paths. This approach is ideal when you need to maintain multiple stores with different configurations but want to manage them from a single codebase.
11+
Sub-path routing allows you to serve different store configurations from the same Alokai deployment using URL paths. This approach is useful if the multibrand per-domain does not address your requirements.
1212

1313
::info
1414
This guide focuses on implementing multi-store functionality through URL paths (like `/electronics`, `/apparel`). If domain-based separation is sufficient for your use case (like `electronics.example.com`, `apparel.example.com`), the [multibrand feature](https://docs.alokai.com/guides/multistore/tooling-and-concepts) is the preferred approach.
@@ -554,7 +554,7 @@ export default {
554554
Then use these variants in your components:
555555

556556
```vue
557-
<!-- apps/storefront-unified-nuxt/components/ui/NavbarTop.vue -->
557+
// apps/storefront-unified-nuxt/components/ui/NavbarTop.vue
558558
<template>
559559
<header
560560
:class="[

0 commit comments

Comments
 (0)