Merge pull request #904 from keboola/devin/AJDA-2544-1775068701

docs: rename 'Data Apps' to 'Apps' throughout documentation [AJDA-2544]

Author: zubednarova

_data/navigation.yml

@@ -168,12 +168,12 @@ items:
             title: UA and GA4 Comparison
 
   - url: /data-apps/
-    title: Data Apps
+    title: Apps
     items:
       - url: /data-apps/streamlit/
-        title: Streamlit Data Apps
+        title: Streamlit Apps
       - url: /data-apps/python-js/
-        title: Python/JS Data Apps
+        title: Python/JS Apps
       - url: /data-apps/authentication/
         title: Authentication
         items:

_data/telemetry_tables.yml

@@ -254,7 +254,7 @@ tables:
 
   - id: kbc_data_app_workspace
     mode: project
-    description: "This table lists runs of [data apps](/data-apps/) and their consumption metrics."
+    description: "This table lists runs of [apps](/data-apps/) and their consumption metrics."
     is_full_load: false
     note: "A value of `0` in `data_app_runtime_hours`,`time_credits_used` or `billed_credits_used` means a correction was made. The row couldn't be removed due to incremental loads, so the original value was set to zero."
     columns:
@@ -263,7 +263,7 @@ tables:
         description: "Identifier of the workspace active window (between starting and pausing the sandbox)"
         example: "`10910_kbc-eu-central-1_8c9e68ac-3a40-4aea-a62c-34ef37d12a5a`"
       - name: kbc_data_app_workspace_id
-        description: "Data app workspace identifier"
+        description: "App workspace identifier"
         example: "`10910_kbc-eu-central-1`"
       - name: kbc_project_id
         fk: kbc_project
@@ -295,10 +295,10 @@ tables:
         description: "Hostname of the workspace"
         example: "`https://hello-world-759519.hub.north-europe.azure.keboola.com`"
       - name: data_app_runtime_hours
-        description: "Runtime of the data app workspace on the particular date in hours"
+        description: "Runtime of the app workspace on the particular date in hours"
         example: "`2.413333`"
       - name: backend_size
-        description: "Size of the data app backend"
+        description: "Size of the app backend"
         example: "`Small`"
       - name: time_credits_used
         description: "Number of time credits consumed by the workspace on the particular date"
@@ -801,7 +801,7 @@ tables:
     mode: project
     description: "This table shows aggregated values for all metrics that may be included in the contract, such as consumed credits, data in storage, and the number of users. This combines data from different data sources (tables), making it useful for providing an overview of consumption."
     is_full_load: false
-    note: "A `0` value for **Data Apps** or **Data Science Sandbox** in `usage_breakdown` means a correction was made. The row couldn't be removed due to incremental loads, so the original value was set to zero."
+    note: "A `0` value for **Apps** or **Data Science Sandbox** in `usage_breakdown` means a correction was made. The row couldn't be removed due to incremental loads, so the original value was set to zero."
     org_mode_note: "`organization_value` and `company_value` are available in **Organization** mode only. You need data for all projects."
     usage_breakdown:
       - name: "Applications"
@@ -1653,7 +1653,7 @@ tables:
         example: "`orchestration trigger`"
       - name: kbc_data_app_id
         fk: kbc_data_app
-        description: "Foreign key to the Keboola data app"
+        description: "Foreign key to the Keboola app"
         example: "`123_kbc-us-east-1_keboola.data-apps-945672`"
 
   - id: kbc_table_metadata
@@ -2167,28 +2167,28 @@ tables:
 
   - id: kbc_data_app
     mode: activity_center
-    description: "This table lists the [data apps](/data-apps/)."
+    description: "This table lists the [apps](/data-apps/)."
     is_full_load: false
     columns:
       - name: kbc_data_app_id
         pk: true
-        description: "Unique identifier for the data application"
+        description: "Unique identifier for the application"
         example: "`123_kbc-us-east-1_keboola.data-apps-945672`"
       - name: kbc_project_id
         fk: kbc_project
         description: "Foreign key to the Keboola project"
         example: "`580_kbc-us-east-1`"
       - name: data_app_created
-        description: "Datetime when the data app was created"
+        description: "Datetime when the app was created"
         example: "`2023-05-14 12:30:45`"
       - name: data_app_id_num
-        description: "Numerical ID for the data application"
+        description: "Numerical ID for the application"
         example: "`945672`"
       - name: kbc_data_app_name
-        description: "Human-readable name of the data app"
+        description: "Human-readable name of the app"
         example: "`Customer Data Loader`"
       - name: kbc_data_app_url
-        description: "URL link to access the data application"
+        description: "URL link to access the application"
         example: "`https://1191546783.hub.keboola.com`"
       - name: kbc_component_id
         description: "Identifier of the component"
@@ -2201,7 +2201,7 @@ tables:
         description: "Foreign key to the Keboola component configuration"
         example: "`123_kbc-us-east-1_keboola.data-apps_1191549426`"
       - name: kbc_data_app_is_deleted
-        description: "Boolean flag indicating whether the data application has been deleted"
+        description: "Boolean flag indicating whether the application has been deleted"
         example: "`false`"
 
   - id: kbc_data_app_params_event
@@ -2211,18 +2211,18 @@ tables:
     columns:
       - name: kbc_data_app_event_id
         pk: true
-        description: "Unique identifier for the event created by the data app"
+        description: "Unique identifier for the event created by the app"
         example: "`123557345_kbc-us-east-1`"
       - name: kbc_project_id
         fk: kbc_project
         description: "Foreign key to the Keboola project"
         example: "`580_kbc-us-east-1`"
       - name: kbc_data_app_id
         fk: kbc_data_app
-        description: "Foreign key to the Keboola data app"
+        description: "Foreign key to the Keboola app"
         example: "`123_kbc-us-east-1_keboola.data-apps-945672`"
       - name: data_app_id_num
-        description: "Numerical ID for the data application"
+        description: "Numerical ID for the application"
         example: "`945672`"
       - name: event_created_at
         description: "Datetime when the event was created"
@@ -2286,7 +2286,7 @@ relationships:
     type: one-to-many
   - from: kbc_project
     to: kbc_data_app_workspace
-    label: "has data app workspaces"
+    label: "has app workspaces"
     type: one-to-many
   - from: kbc_project
     to: kbc_data_science_sandbox
@@ -2418,11 +2418,11 @@ relationships:
     type: one-to-many
   - from: kbc_project
     to: kbc_data_app
-    label: "has data apps"
+    label: "has apps"
     type: one-to-many
   - from: kbc_project
     to: kbc_data_app_params_event
-    label: "has data app events"
+    label: "has app events"
     type: one-to-many
 
   # Branch relationships
@@ -2494,7 +2494,7 @@ relationships:
     type: one-to-many
   - from: kbc_component_configuration
     to: kbc_data_app
-    label: "has data app"
+    label: "has app"
     type: one-to-many
 
   # Flow phase -> task
@@ -2607,7 +2607,7 @@ relationships:
     label: "has events"
     type: one-to-many
 
-  # Data app relationships
+  # App relationships
   - from: kbc_data_app
     to: kbc_data_app_params_event
     label: "has events"

data-apps/authentication/index.md

@@ -11,9 +11,9 @@ redirect_from:
 
 ## Overview
 
-Once a data app is deployed, its URL is publicly available! We recommend using one of the built-in authentication methods described below to protect your app.
+Once an app is deployed, its URL is publicly available! We recommend using one of the built-in authentication methods described below to protect your app.
 
-Keboola provides several built-in authentication methods to control who can access your data apps. Choose the method that best fits your security requirements.
+Keboola provides several built-in authentication methods to control who can access your apps. Choose the method that best fits your security requirements.
 
 {: .image-popup}
 ![Authentication options](/data-apps/authentication/authentication.png)
@@ -44,7 +44,7 @@ If you enter an app with OIDC, you will be asked to select an `Authentication Pr
 
 ## GitHub Authentication
 
-Restrict access to your data app using GitHub OAuth. Users authenticate via their GitHub account, and you can optionally restrict access to specific organizations, teams, repositories, or individual users.
+Restrict access to your app using GitHub OAuth. Users authenticate via their GitHub account, and you can optionally restrict access to specific organizations, teams, repositories, or individual users.
 
 ### Required Fields
 
@@ -69,15 +69,15 @@ Restrict access to your data app using GitHub OAuth. Users authenticate via thei
 1. Go to your GitHub account **Settings > Developer Settings > OAuth Apps** and create a new OAuth App.
 2. Set the **Authorization callback URL** to: `https://<dataAppId>.hub.<keboolaConnectionHost>/_proxy/callback` (e.g., `https://my-app-12345678.hub.north-europe.azure.keboola.com/_proxy/callback`).
 3. Copy the **Client ID** and **Client Secret** from the created OAuth App.
-4. In your Keboola Data App configuration, select **GitHub** as the authentication method.
+4. In your Keboola app configuration, select **GitHub** as the authentication method.
 5. Paste the **Client ID** and **Client Secret**.
 6. Optionally configure organization, team, repository, or allowed users restrictions.
 7. If you use organization, team, or repository restrictions with a private organization, provide an **Access Token** with `read:org` scope.
 8. Save and redeploy your app.
 
 ## GitLab Authentication
 
-Restrict access to your data app using GitLab OAuth. Users authenticate via their GitLab account, and you can optionally restrict access by groups, projects, or roles.
+Restrict access to your app using GitLab OAuth. Users authenticate via their GitLab account, and you can optionally restrict access by groups, projects, or roles.
 
 ### Required Fields
 
@@ -101,14 +101,14 @@ Restrict access to your data app using GitLab OAuth. Users authenticate via thei
 2. Set the **Redirect URI** to: `https://<dataAppId>.hub.<keboolaConnectionHost>/_proxy/callback` (e.g., `https://my-app-12345678.hub.north-europe.azure.keboola.com/_proxy/callback`).
 3. Ensure the `openid`, `profile`, and `email` scopes are selected. If you use group or project restrictions, also select `read_api`.
 4. Copy the **Application ID** and **Secret**.
-5. In your Keboola Data App configuration, select **GitLab** as the authentication method.
+5. In your Keboola app configuration, select **GitLab** as the authentication method.
 6. Paste the **Client ID**, **Client Secret**, and **GitLab Instance URL**.
 7. Optionally configure groups, projects, or allowed roles restrictions.
 8. Save and redeploy your app.
 
 ## JumpCloud Authentication
 
-Restrict access to your data app using JumpCloud OIDC. Users authenticate via their JumpCloud account, and you can optionally restrict access by roles.
+Restrict access to your app using JumpCloud OIDC. Users authenticate via their JumpCloud account, and you can optionally restrict access by roles.
 
 ### Required Fields
 
@@ -131,7 +131,7 @@ Restrict access to your data app using JumpCloud OIDC. Users authenticate via th
 2. Configure the application as an **OIDC** application.
 3. Set the **Redirect URI** to: `https://<dataAppId>.hub.<keboolaConnectionHost>/_proxy/callback` (e.g., `https://my-app-12345678.hub.north-europe.azure.keboola.com/_proxy/callback`).
 4. Copy the **Client ID** and **Client Secret** from the SSO tab.
-5. In your Keboola Data App configuration, select **JumpCloud** as the authentication method.
+5. In your Keboola app configuration, select **JumpCloud** as the authentication method.
 6. Paste the **Client ID**, **Client Secret**, **Issuer URL**, and **Logout URL**.
 7. Optionally configure allowed roles to restrict access.
 8. Save and redeploy your app.
@@ -146,4 +146,4 @@ https://<dataAppId>.hub.<keboolaConnectionHost>/_proxy/callback
 
 For example: `https://my-app-12345678.hub.north-europe.azure.keboola.com/_proxy/callback`
 
-You can find your app's full URL after the first deployment in the Data App configuration.
+You can find your app's full URL after the first deployment in the app configuration.

data-apps/backend-versions/index.md

@@ -8,7 +8,7 @@ redirect_from:
 * TOC
 {:toc}
 
-When deploying a data app, you can select a **backend version** from a dropdown in the deployment wizard.
+When deploying an app, you can select a **backend version** from a dropdown in the deployment wizard.
 Each backend version defines the runtime environment your app runs in, including the Python version, Streamlit version,
 and a set of pre-installed packages.
 
@@ -24,7 +24,7 @@ For example: `1.15.2 - Python 3.13 + Streamlit 1.51`
 
 This means:
 
-- **Backend version** (`1.15.2`): The release version of the base Docker image that powers your data app. Newer backend versions may include updated pre-installed packages, bug fixes, and infrastructure improvements.
+- **Backend version** (`1.15.2`): The release version of the base Docker image that powers your app. Newer backend versions may include updated pre-installed packages, bug fixes, and infrastructure improvements.
 - **Python version** (`3.13`): The version of the Python interpreter. Different Python versions offer different language features and performance characteristics.
 - **Streamlit version** (`1.51`): The version of the [Streamlit](https://streamlit.io/) framework used to run your app.
 

data-apps/general-design-guide/index.md

@@ -1,5 +1,5 @@
 ---
-title: Data Apps General Design Guide
+title: Apps General Design Guide
 permalink: /data-apps/general-design-guide/
 redirect_from:
   - /components/data-apps/general-design-guide/
@@ -8,13 +8,13 @@ redirect_from:
 * TOC
 {:toc}
 
-This guide will help you quickly create a user-friendly data app in Keboola. We cover essentials like theming, headers, storage integration, 
+This guide will help you quickly create a user-friendly app in Keboola. We cover essentials like theming, headers, storage integration, 
 and more to streamline your setup. With clear, step-by-step instructions, you'll be able to build an intuitive, visually appealing app. 
 
 ## Theming
 There are two options for setting theming:
 
-1. **Keboola Data Apps Interface:** Choose from predefined or custom themes directly in the Keboola interface. See more in [the documentation](/data-apps/#theming).
+1. **Keboola Apps Interface:** Choose from predefined or custom themes directly in the Keboola interface. See more in [the documentation](/data-apps/#theming).
 2. **Configuration File:** Use the settings in the `config.toml` file, located in the `.streamlit` folder.
 
 {: .image-popup}