Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Introduction to multibrand #7382

Draft
wants to merge 7 commits into
base: docs/multibrand
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
44 changes: 33 additions & 11 deletions docs/content/guides/1.index.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,26 +9,48 @@ Welcome to the guides section of the documentation. Here you will find a collect

At **Alokai**, we are committed to providing the best possible experience for our users. We are constantly working on improving our documentation and adding new guides to help you get the most out of the platform.

## Getting Help
If you have any questions or need help with anything, please don't hesitate to get in touch with us in our [Discord](https://discord.vuestorefront.io/). We are always happy to help.

## Alokai Guides

## Learn Alokai

::grid{:columns='3'}
Follow this path to understand how to use Alokai and start building your Alokai application following performance best practices.
::steps

#section-1
:card{to="/guides/alokai-essentials" title="Alokai Essentials" description="Learn how to build Alokai Application: From 0 to Hero. Understand how different parts of our stack will help you to build your Alokai application." icon="tabler:123"}
#step-1
::card{title="Alokai Essentials" to="/guides/alokai-essentials" class="mb-5 !h-auto"}
#description
Learn how to build Alokai Application: From 0 to Hero. Understand how different parts of our stack will help you to build your Alokai application.
::

#section-2
:card{to="/guides/performance" title="Performance" description="Improve your website's user experience and increase conversions by optimizing your website's performance." icon="gg:performance"}
#step-2
::card{title="Customization" to="/guides/customization-next-js" class="mb-5 !h-auto"}
#description
Alokai is not a cookie-cutter solution, it is meant to be able to handle even the most complex use cases. This guide will take you through the most common customization scenarios.
::

#section-3
:card{to="/guides/customization-next-js" title="Customization" description="Alokai is not a cookie-cutter solution, it is meant to be able to handle even the most complex use cases. This guide will take you through the most common customization scenarios." icon="tabler:tool"}
#step-3
::card{title="Performance" to="/guides/performance" class="mb-5"}
#description
Every 100ms added to loading time costed Amazon 1% less sales. Don't let the poor performance to ruin your sales. Learn how to optimize your store for speed.
::

::


## Advanced

::card{title="Multistore" to="/guides/multistore" class="mb-5 !h-auto"}
#description
Learn how to create efficient and unified multigeo/multibrand/multivendor setups with Alokai.
::

::card{title="Kubernetes Probes" to="/guides/kubernetes-probe" class="mb-5"}
#description
Learn how to implement health check endpoints for your Alokai Cloud applications running on Kubernetes. This guide covers liveness and readiness probes implementation to ensure proper application monitoring and reliability.
::


::info
Can't find what you're looking for? Check out our [cookbook](/cookbook) for more guides and tutorials.
::
::

2 changes: 1 addition & 1 deletion docs/content/guides/3.performance/_dir.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
title: Performance Guide
title: Performance
sidebarRoot: true
navigation:
icon: gg:performance
Expand Down
26 changes: 20 additions & 6 deletions docs/content/guides/6.multistore/1.introduction/1.index.md
Original file line number Diff line number Diff line change
@@ -1,20 +1,34 @@
---
title: Challenges with multistore setups
title: Challenges of Multistore Setups
layout: default
---
# Challenges of Multistore Setups

# Challenges with multistore setups
## Adaptive Setups Are Now More Important Than Ever

Let's get started!
Markets and technologies evolve rapidly. Organizations must adapt quickly to stay competitive. Agility is not optional—it’s a core requirement for survival. The businesses that thrive are those that don’t just react to change but anticipate and embrace it.

::card{title="Next: How Alokai is uniquely positioned to solve this problem better than others" icon="tabler:number-1-small" }
New technologies emerge at an unprecedented pace, customer expectations shift constantly, and competitors are always looking for an edge. In this landscape, relying on static solutions or legacy systems is a liability. Companies that successfully integrate emerging innovations without disrupting operations gain a competitive advantage. The challenge is maintaining this adaptability while ensuring systems remain efficient and scalable.

#description
Businesses must now be built for continuous adaptation. Technologies evolve faster than ever, making adaptability the most valuable capability. Organizations must design their eCommerce infrastructure to be flexible, scalable, and integration-ready. A future-proof technology stack enables businesses to pivot seamlessly, staying ahead of market shifts and competitive pressures.

Companies investing in adaptable eCommerce solutions position themselves to iterate quickly, minimize technical debt, and maintain long-term scalability. Those that prioritize agility through technology will outpace competitors in efficiency and innovation.

## Challenges and Hidden Complexity of Multistore Setups

Scaling an eCommerce business across multiple brands, geographies, and touchpoints sounds like a natural next step. But the reality? It’s a logistical and technical minefield. As companies expand, agility often takes a hit—slowing down innovation, increasing overhead, and complicating operations.

Businesses often start with a single eCommerce platform, designed for a specific market and use case. Growth then happens through expansion into new touchpoints (mobile apps, marketplaces, social commerce), new geographies, or acquiring brands with their own tech stacks. Over time, what was once a streamlined setup becomes fragmented, introducing complexity that makes agility and scalability difficult.

How do you maintain speed and adaptability while managing multiple storefronts, integrating new acquisitions, and expanding into new markets? Let’s break down the key challenges and why solving them isn’t as straightforward as it seems.

::card{title="Next: How Alokai Solves It" icon="tabler:number-2-small" to="/guides/multistore/how-alokai-solves-it"}

#description
TODO

#cta
:::docs-button{to="/guides/multistore/introduction/alokai-solve-this-problem"}
:::docs-button{to="/guides/multistore/how-alokai-solves-it"}
Next
:::
::
Original file line number Diff line number Diff line change
@@ -1,11 +1,9 @@
---
title: How Alokai is uniquely positioned to solve this problem better than others
title: How Alokai Solves It
layout: default
navigation:
icon: tabler:number-1-small
---

# How Alokai is uniquely positioned to solve this problem better than others
# How Alokai is uniquely positioned to solve this problem better than others.


::card{title="Next: Use cases" icon="tabler:number-2-small" }
Expand Down
34 changes: 29 additions & 5 deletions docs/content/guides/6.multistore/1.introduction/3.use-cases.md
Original file line number Diff line number Diff line change
@@ -1,14 +1,38 @@
---
title: Use cases
title: Use Cases
layout: default
navigation:
icon: tabler:number-2-small
---

# Use cases
# Use Cases

## Scaling to New Touchpoints

::card{title="Next: Tooling and concepts" icon="tabler:number-3-small" }
Expanding to new touchpoints—mobile apps, marketplaces, in-store kiosks—introduces unexpected complexities that can slow down innovation and increase operational burdens.

- **Inconsistent Feature Rollouts** – Each touchpoint often requires separate development, meaning that new features must be built and deployed multiple times. A product recommendation engine, for example, might launch on the website first, take weeks to arrive on mobile, and never make it to in-store kiosks due to technical constraints.
- **Fragmented Development and Maintenance** – Every platform comes with its own technical stack, integration requirements, and release cycles. Maintaining consistency across them requires redundant effort, slowing down iteration and increasing costs.
- **Difficult Debugging and Troubleshooting** – Bugs behave differently across touchpoints. A checkout issue might occur only in the mobile app but not on the website, forcing teams to debug and fix problems separately rather than solving them in one place.
- **Performance and Data Synchronization Issues** – Real-time inventory updates, pricing changes, and user sessions need to be in sync across all touchpoints. Without a centralized approach, discrepancies arise, leading to poor customer experiences.

Without a unified system, businesses struggle with inefficiencies, delayed feature releases, and higher maintenance costs. Instead of focusing on growth and innovation, they get bogged down in managing a fragmented ecosystem of loosely connected storefronts.

[TBD] SOLUTIONS

## Expanding into New Geographies

Expanding into new geographies introduces additional layers of complexity that often lead businesses to launch separate storefronts per region. These challenges arise from the need to accommodate region-specific requirements and operational differences:

- **Localized Vendor and Payment Providers** – Different regions require different payment gateways, logistics partners, and tax compliance setups. Integrating each separately leads to redundant systems and inefficiencies.
- **Localized UI and UX Adjustments** – Languages, currencies, date formats, and even browsing behaviors differ across geographies. Without a flexible system, businesses are forced to create region-specific versions of their applications.
- **Infrastructure and Performance Issues** – Serving customers in different regions from a single data center leads to slow load times. Without a distributed hosting strategy, performance degrades significantly.

Due to these challenges, many businesses resort to launching separate eCommerce platforms for each region, leading to a fragmented ecosystem that is hard to maintain. Over time, this lack of centralization makes rolling out global updates slow and expensive, ultimately limiting scalability and agility.

[TBD] SOLUTIONS

## Launching New Brands

::card{title="Next: Tooling and Concepts" icon="tabler:number-3-small" }

#description
TODO
Expand Down
2 changes: 1 addition & 1 deletion docs/content/guides/6.multistore/1.introduction/_dir.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
title: Introduction
sidebarRoot: true
navigation:
icon: tabler:brand-nextjs
icon: tabler:number-1-small
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
title: Tooling and concepts
sidebarRoot: true
navigation:
icon: tabler:brand-react-native
icon: tabler:number-2-small
2 changes: 1 addition & 1 deletion docs/content/guides/6.multistore/3.patterns/_dir.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
title: Patterns
sidebarRoot: true
navigation:
icon: tabler:brand-nuxt
icon: tabler:number-3-small
2 changes: 1 addition & 1 deletion docs/content/guides/_dir.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
title: Guides
sidebarRoot: true
sidebarRoot: false
navigation:
icon: ri:code-s-slash-fill
Loading