docs: reorganize Android SDK docs and merge modules into overview section

Author: dzienisz

android-sdk/about.mdx

@@ -7,7 +7,6 @@ description: Overview of Tolgee Mobile SDK with Over‑the‑Air (OTA) localizat
 
 import SystemCard from '@site/src/component/SystemCard';
 import FeatureGrid from '@site/src/component/FeatureGrid';
-import Tolgee from '@site/src/component/Tolgee';
 
 # Tolgee Mobile SDK
 
@@ -17,9 +16,15 @@ For managing static translations in your repository, consider using the [Tolgee
 
 ## Overview
 
-Tolgee Mobile SDK for **Android** and **Compose Multiplatform** lets you localize Kotlin-based applications with **dynamic content delivery**, providing translations dynamically without needing to publish new app versions.
+Tolgee Mobile SDK for **Android** and **Compose Multiplatform** lets you localize Kotlin-based applications with **dynamic content delivery**, adapting content to user behavior, preferences, and device data.
 
-**Supports Over‑the‑Air (OTA)** translation updates, seamless integration with **Android Views**, **Jetpack Compose**, **Compose Multiplatform**, and **static translation fallbacks**.
+**Supports Over‑the‑Air (OTA)** translation updates, providing translations dynamically **without needing to publish new app versions**.
+
+The platform works offline with **caching**, **fallbacks**, **device-aware resource selection**, and **preloading** of critical namespaces for a smooth user experience. Tolgee **keeps UX consistent** by updating the UI automatically in response to locale changes, resulting in **fewer untranslated or mismatched strings**.
+
+:::info
+Tolgee gives you multiple hosting options: Cloud CDN (Cloud or self‑hosting) or your own CDN.
+:::
 
 ## Features
 
@@ -50,6 +55,22 @@ Tolgee Mobile SDK for **Android** and **Compose Multiplatform** lets you localiz
   }
 ]} />
 
+
+## Modules
+
+Tolgee Mobile SDK is split into modules so you only add what you need.
+
+### When to use which module
+- **Core**
+  - Use with traditional Android Views or any non-Compose UI.
+  - Provides content delivery (CDN), key lookup, formatting (Sprintf/ICU), caching.
+  - Start here if you don't use Jetpack Compose.
+- **Compose**
+  - Use with Jetpack Compose or Compose Multiplatform.
+  - Adds localized composables and helpers (e.g., stringResource, pluralStringResource).
+  - Requires core transitively.
+
+
 ## Demo apps
 
 ### 📱 Android Views Demo

android-sdk/get-started.mdx

@@ -18,61 +18,55 @@ Follow these steps to integrate Tolgee into your Android project and start local
     title="Quickstart"
     emoji="📦"
     description="Set up dependencies and network security configuration"
-    links={[
-      { href: "./quickstart", label: "Quickstart Guide", color: "blue" }
-    ]}
-  />
-  
-  <SystemCard
-    title="Modules Overview"
-    emoji="🔧"
-    description="Choose between Core and Compose modules for your project"
-    links={[
-      { href: "./modules", label: "Modules Guide", color: "green" }
-    ]}
+    links={[{ href: './quickstart', label: 'Quickstart Guide', color: 'blue' }]}
   />
 </div>
 
 ## Integration Path
 
-1. **[Quickstart](./quickstart)** - Add Tolgee SDK to your project
-2. **[Modules Overview](./modules)** - Understand Core vs Compose modules
-3. **Choose your implementation** (see cards below)
-4. **[Production Setup](./production)** - Configure for production deployment
+### 1. **[Quickstart](./quickstart)** - Add Tolgee SDK to your project
 
-## Choose Your Implementation
+### 2. **Choose your implementation**
 
 <div className="grid grid-cols-1 md:grid-cols-2 lg:grid-cols-3 gap-4 my-6">
   <SystemCard
     title="Jetpack Compose"
     emoji="🚀"
     description="Modern declarative UI with reactive translations"
     links={[
-      { href: "/android-sdk/jetpack", label: "Overview", color: "blue" },
-      { href: "/android-sdk/jetpack/installation", label: "Installation", color: "green" },
-      { href: "/android-sdk/jetpack/usage", label: "Usage", color: "orange" }
+      { href: '/android-sdk/jetpack', label: 'Overview', color: 'blue' },
+      {
+        href: '/android-sdk/jetpack/installation',
+        label: 'Installation',
+        color: 'green',
+      },
+      { href: '/android-sdk/jetpack/usage', label: 'Usage', color: 'orange' },
     ]}
   />
-  
+
   <SystemCard
     title="Android Views"
     emoji="📱"
     description="Traditional Android UI with dynamic translations"
-    links={[
-      { href: "./usage", label: "Usage Guide", color: "purple" }
-    ]}
+    links={[{ href: './usage', label: 'Usage Guide', color: 'purple' }]}
   />
-  
+
   <SystemCard
     title="CLI Integration"
     emoji="⚡"
     description="Generate and manage <strong>static translations</strong>"
     links={[
-      { href: "/tolgee-cli/installation", label: "Tolgee CLI", color: "cyan" }
+      { href: '/tolgee-cli/installation', label: 'Tolgee CLI', color: 'cyan' },
     ]}
   />
 </div>
 
+### 3. **[Production guide](./production)** - Configure for production deployment
+
+:::warning
+The Gradle compiler plugin is not released yet and is not part of the current installation options.
+:::
+
 ## What You'll Achieve
 
 After completing the setup, your app will have:
@@ -90,9 +84,7 @@ After completing the setup, your app will have:
     title="Production Guide"
     emoji="🚀"
     description="Over‑the‑Air (OTA) updates, caching, formatting, and testing for production apps"
-    links={[
-      { href: "./production", label: "Production Setup", color: "blue" }
-    ]}
+    links={[{ href: './production', label: 'Production Setup', color: 'blue' }]}
   />
 </div>
 

android-sdk/jetpack/installation.mdx

@@ -161,5 +161,5 @@ If you have a different integration setup (for example, using tolgee-cli and bun
 ## Next steps
 
 - Learn how to use translations in Compose: [`Usage`](./usage.mdx)
-- Not sure which module to use? See [`Modules overview`](../modules.mdx)
+- Not sure which module to use? See [`Modules overview`](../about.mdx)
 - Having issues? Check [`Troubleshooting`](./troubleshooting.mdx)

android-sdk/modules.mdx

@@ -1,6 +1,6 @@
 ---
 id: quickstart
-title: Quickstart
+title: Quickstart (Core Module)
 description: Quick start guide for Tolgee Mobile SDK with Core module (traditional Android Views)
 ---
 
@@ -15,21 +15,21 @@ For managing static translations, we recommend using [Tolgee CLI](https://github
     <div className="flex items-center gap-3">
       <span className="text-2xl">📱</span>
       <div>
-        <h4 className="text-lg font-semibold mb-1 text-blue-800 dark:text-blue-200">Android API Level</h4>
+      <h4 className="text-lg font-semibold mb-1 text-blue-800 dark:text-blue-200">Android API Level</h4>
         <p className="text-sm text-blue-700 dark:text-blue-300 mb-0">Minimum <a href="https://developer.android.com/guide/topics/manifest/uses-sdk-element#ApiLevels" className="text-blue-600 dark:text-blue-400 hover:underline">API Level 21+</a> (Android 5.0 and above)</p>
       </div>
     </div>
   </div>
 </div>
 
-# Quickstart (Core Module)
+# Quickstart
 
 This guide shows you how to integrate Tolgee Mobile SDK using the **Core module** for traditional Android Views.
 
 The **Core module** is a Kotlin Multiplatform library that provides runtime support for Tolgee translations in your app. With Tolgee, you can update your translations **over-the-air** without releasing a new app version.
 
 :::info
-Using **Version Catalog** is recommended to keep your versions aligned, especially in bigger projects. This provides **readability, centralization, and consistency**. 
+Using **Version Catalog** is recommended to keep your versions aligned, especially in bigger projects. This provides **readability, centralization, and consistency**.
 :::
 
 :::note
@@ -38,34 +38,34 @@ To build configuration examples use Kotlin DSL (build.gradle.kts). Groovy DSL ma
 
 1. Add dependency (Core):
 
- In `gradle/libs.versions.toml` <u>add an alias for Tolgee library</u>.
+In `gradle/libs.versions.toml` <u>add an alias for Tolgee library</u>.
 
-   ```toml
-   # gradle/libs.versions.toml
-   [libraries]
-   tolgee = { group = "io.tolgee.mobile-kotlin-sdk", name = "core", version.ref = "tolgee" }
-   ```
+```toml
+# gradle/libs.versions.toml
+[libraries]
+tolgee = { group = "io.tolgee.mobile-kotlin-sdk", name = "core", version.ref = "tolgee" }
+```
 
-Then, in `build.gradle.kts`, <u>use the created alias</u>. 
+Then, in `build.gradle.kts`, <u>use the created alias</u>.
 
-   ```kotlin
-   // build.gradle.kts (module)
-   dependencies {
-       implementation(libs.tolgee)
-   }
-   ```
+```kotlin
+// build.gradle.kts (module)
+dependencies {
+    implementation(libs.tolgee)
+}
+```
 
 For **smaller projects** you can also add dependency directly (the old way).
 
-   ```kotlin
-   // build.gradle.kts 
-   dependencies {
-       implementation("io.tolgee.mobile-kotlin-sdk:core:tolgee")
-   }
-   ```
+```kotlin
+// build.gradle.kts
+dependencies {
+    implementation("io.tolgee.mobile-kotlin-sdk:core:tolgee")
+}
+```
 
 :::note
-If you use **Jetpack Compose**, see the Compose variant: [Jetpack Quickstart](/android-sdk/jetpack/installation)
+If you use **Jetpack Compose**, see the Compose variant: [Jetpack Compose -> Quickstart](/android-sdk/jetpack/installation)
 :::
 
 2. (If needed) Ensure repositories include Maven Central:
@@ -75,12 +75,14 @@ If you use **Jetpack Compose**, see the Compose variant: [Jetpack Quickstart](/a
 pluginManagement { repositories { gradlePluginPortal(); google(); mavenCentral() } }
 dependencyResolutionManagement { repositories { google(); mavenCentral() } }
 ```
+
 To use the library, **you need to have proper repositories configured** in your project.
 Otherwise an error like:
 
 ```text
 Could not find io.tolgee.mobile-kotlin-sdk:core
 ```
+
 might pop up.
 Make sure **Maven Central** is set up properly so the dependency can be resolved.
 
@@ -106,7 +108,7 @@ Add network security config to your `AndroidManifest.xml`:
 </application>
 ```
 
-:::note
+:::info
 Allowing `tolgee.io` and `tolg.ee` domains is required when using Tolgee Cloud CDN. If you only access your own self-hosted CDN, include your domain(s) accordingly.
 :::
 
@@ -130,13 +132,14 @@ class MyApplication : Application() {
 
 When your app boots up, Tolgee is globally initialized. The translations are downloaded from CDN and cached locally. Other parts of your app (such as activities and fragments) can now use Tolgee without additional configuration.
 
-***Make sure that your app knows where to download translations***:
+**_Make sure that your app knows where to download translations_**:
 
 For your app to download translation files, you need to provide a CDN URL prefix specific to your project. This prefix points to the catalog that contains your app’s translations.
 
 ### How to get your CDN URL prefix (Content Delivery):
+
 1. Open Tolgee Platform → your Project → Developer settings → Content Delivery.
-2. Copy the full CDN URL prefix. 
+2. Copy the full CDN URL prefix.
 3. You can use different prefixes per environment (dev/staging/prod).
 
 ### Optional: Verify connectivity locally:
@@ -145,31 +148,29 @@ For your app to download translation files, you need to provide a CDN URL prefix
 curl -I "https://cdn.tolg.ee/your-cdn-url-prefix/en.json"
 ```
 
-You should receive a 200 response. 
+You should receive a 200 response.
 If you get 403 (Forbidden) or 404 (Not found), double‑check the prefix.
 
 :::tip
 Dynamic updates without republishing
 :::
 
-To receive fresh translations without needing to publish new app versions, wrap the base context in your Activities.
-This way, APIs like getString() will use Tolgee dynamically.
+To receive **fresh translations without needing to publish new app versions**, wrap the base context in your Activities.
+This way, APIs like getString will use Tolgee **dynamically**.
 
-- With wrapped context → fresh translations from the Tolgee CDN will be provided automatically.
+- **With wrapped context** → fresh translations from the Tolgee CDN will be provided automatically.
 
-- Without wrapped context → only the translations already bundled or previously cached will be available.
+- **Without wrapped context** → only the translations already bundled or previously cached will be available.
 
-See the step-by-step guide in Usage.
+**See the step-by-step guide in Usage.**
 
-:::note
+:::info
 If you have a different integration setup (for example, using tolgee-cli and bundling JSON translation files in assets), the initialization may look different.
 :::
 
-
 ## Next steps
 
-- Not sure which artifact to use? See [`Modules overview`](./modules.mdx)
+- Not sure which artifact to use? See ['overview`](./about.mdx)
 - Learn how to fetch and render translations in Views: [`Usage`](./usage.mdx)
 - Using Compose? Start here: [`Jetpack Installation`](./jetpack/installation.mdx)
 - Having issues? Check [`Troubleshooting`](./troubleshooting.mdx)
-

android-sdk/quickstart.mdx

@@ -3,7 +3,6 @@ module.exports = {
     'about',
     'get-started',
     'quickstart',
-    'modules',
     'usage',
     {
       type: 'category',