diff --git a/README.md b/README.md
index b2b8780..fa5e0ba 100644
--- a/README.md
+++ b/README.md
@@ -74,6 +74,14 @@ automatically preparing the codebase to support them without requiring any manua
Imagine you've developed (or planning to develop) an e-commerce app and need to sell it to countless customers. To achieve this, your **e-commerce** codebase must be dynamic enough to accommodate essential changes, such as the app name, identifier, icon, theme, version, base URL, and custom configurations—like whether to enable or disable specific features—and more. This is
illustrated in the diagram below:
+
+
+
+
+
+
+
Solara addresses this challenge by introducing a centralized brand management system, enabling you to generate an infinite number of apps efficiently, as illustrated below:
+
+
+
+
+
+
+
This centralized approach not only simplifies brand management but also enhances the flexibility of your codebase, allowing you to serve a diverse customer base with ease.
@@ -187,7 +204,13 @@ Solara offers powerful tools for managing your brands.
The Solara Management Tools Diagram below illustrates these tools:
#### Solara Management Tools Diagram
+
+
+
+
+
+
> For the detailed guidance, please refer to [Brand Management](https://github.com/Solara-Toolkit/Solara/wiki/Brand-Management).
@@ -241,6 +265,13 @@ Refer to the image below for a visual guide:
The `solara` directory contains all the essential files required for Solara. Below is its structure:
+
+
+
+
+
+
+
> For comprehensive details, check
> the [Brand Configuration](https://github.com/Solara-Kit/Solara/wiki/Brand-Configuration).
@@ -288,6 +320,13 @@ See the diagram below
#### Brand Structure Diagram
+
+
+
+
+
+
+
---
@@ -317,6 +357,13 @@ illustrating this process:
#### Brand Switching Diagram
+
+
+
+
+
+
+
## The Flow of Brand Switching Operation
@@ -340,6 +388,13 @@ by the diagram below:
#### Brand Switching Flow Diagram
+
+
+
+
+
+
+
This diagram illustrates the sequential flow from preparing the codebase to generating code and finally deploying
resources. Each phase builds upon the previous one, leading to a smooth transition for managing brand configurations.
@@ -395,7 +451,7 @@ Solara deploys resources and generated code into specific directories within the
-
+
@@ -460,6 +516,13 @@ brand-specific settings.
The diagram below illustrates how the `brand_config.json` is generated for each platform, ensuring that all necessary
configurations are appropriately formatted and accessible.
+
+
+
+
+
+
+
1. **Central Configuration File**
- **`BRAND_KEY/shared/brand_config.json`**: This is the main configuration file that includes all customizable