.default})
-
- .default})
-
-
-
-### Copying API Endpoint
-
-Click the copy button beside the endpoint URL to use it in your application's REST calls.
-
-.default})
-
-
-### Creating a New API Key
-
-.default})
to launch the configuration dialog. Then, follow the detailed property guidelines outlined in the table below to complete your setup.
- .default})
- .default})
- .default})
reveals the API key in the interface and includes a copy button .default})
, enabling easy duplication of the API key for use in configuring your application or services..default})
removes the key upon confirmation, safeguarding against unintended deletions..default})
opens a configuration dialog for modifying the API key's details..default})
-
+
+
+
+### Creating a New API Key
+
+ button to open the API key configuration dialog. Define properties such as the key’s description, type, assigned role, expiration date, and allowed hosts.
+
+
+
+
+
+### API Management Table
+
+In the API management section, each key includes options to:
+
+ reveals the API key in the interface and includes a copy button , enabling easy duplication of the API key for use in configuring your application or services. removes the key upon confirmation, safeguarding against unintended deletions. opens a configuration dialog for modifying the API key's details.
+ .default})
+
+### Next Invoice
+
+The **Next Invoice** section displays the amount and date of your next scheduled payment, with the option to view a detailed breakdown.
+
+.default})
+ .default})
+
+
+### Subscription Overview
+
+This section provides the status and cycle of your subscription, along with the associated payment method.
+
+.default})
+ .default})
opens a dialog box where you can update the card details, including:
+
+
+.default})
+ .default})
+
+.default})
button redirects you to a detailed invoice page where you can:
+ .default})
+ .default})
button directs you to the [Subscription Page](#subscription-page), where you can manage services and environments, including upgrading or deleting environments.
+
+
+## Subscription Page
+
+The **Subscription Page** is designed for managing environment-specific services and associated costs. It allows you to upgrade, delete, or add environments, providing detailed control over the resources allocated to each environment.
+
+### Environment Overview
+
+The **Environment Overview** section lists all environments with details of their configurations and associated costs.
+
+.default})
+
+Clicking on an environment card reveals detailed configurations and associated costs for the environment:
+
+- **Qodly Power**: Displays the computing resources (CPU and memory) assigned to the environment, along with the monthly cost.
+- **Extra Storage**: Shows any additional storage allocated to the environment.
+- **Internet Outbound Data Transfer Pack**: Indicates the bandwidth included for outbound data transfers.
+- **Backup Service**: Displays if the database backup option is enabled.
+
+.default})
+
+
+### Add Environment
+
+The **Add Environment** .default})
button enables the creation of new environments. Users can:
+
+- Add multiple environments in one session.
+
+- Customize each environment with specific computing power, storage, bandwidth, and additional services.
+
+- Review configuration summaries and total costs before finalizing.
+
+- Either submit .default})
all configured environments or discard .default})
the entire session.
+
+ .default})
+
+
+:::tip
+The configuration options for each environment in this section are the same as those in the [Step 3: Configure Application Details](./myApps.md#step-3-configure-application-details) section when creating a new app for the first time. Each added environment requires independent configuration, including options for:
+:::
+
+
+### View Environment
+
+The **View Environment** .default})
button opens the [selected environment’s overview page](./environmentsOverview.md) for further details and monitoring.
+
+### Upgrading an Environment
+
+The **Upgrade** .default})
button opens a configuration panel where you can adjust the resources allocated to a specific environment, enhancing its capabilities based on your project needs.
+
+:::tip
+The current configuration settings for the environment are pre-selected by default, making it easy to adjust specific elements as needed.
+:::
+
+The upgrade panel includes the Environment Configuration options, consistent with the settings available in the [Step 3: Configure Application Details section](./myApps.md#environment-configuration) during initial app creation. Changes can be applied by clicking "Save Changes" .default})
or discarded by selecting Cancel .default})
.
+
+.default})
+
+:::tip
+Billing adjustments are prorated for the remaining duration of the current billing cycle, as displayed in the summary panel to the right.
+:::
+
+:::info
+If the Database Backup Service was enabled during the initial creation of the environment, it remains locked and cannot be deselected in the upgrade configuration.
+:::
+
+### Deleting an Environment
+
+The **Delete** .default})
button removes the selected environment (except Development) after confirmation:
+
+.default})
+ .default})
+
+## Console Homepage
+
+The Console homepage displays an organized list of your applications, grouped by type:
+
+- [**Sandbox**](./sandbox.md): Appears as a separate section, with a single entry (since each user is limited to one Sandbox at a time).
+.default})
+
+- [**My Apps**](./myApps.md): Lists all applications you’ve created, including any paid applications or clones of the Sandbox.
+.default})
+
+- **Shared Applications**: Lists applications owned by other users that have been shared with you. Access permissions vary based on the owner’s settings, allowing you to collaborate with some limitations.
+.default})
+
+
+Each application is displayed with key details:
+
+- **Name**: The name assigned to the application.
+
+- **Environments**: The number of environments associated with the app (e.g., Development, Staging, Production).
+
+- **Created At**: The date and time when the application was created.
+
+- **Status**: The current state of the app (e.g., Created, Running, or Inactive).
+
+- **Actions**: Quick-access management actions that vary slightly depending on the type of application.
+
+
+## Managing Applications
+
+Each application, whether Sandbox, My Apps, or Shared Applications, provides a set of actions that you can access directly from the Console homepage. These actions include:
+
+| Action | Sandbox | My Apps | Shared Applications |
+|---------|---------|---------|---------------------|
+| **Clone** | Cloning converts the Sandbox into a fully functional paid application with additional features and no Sandbox limitations. | Cloning duplicates the configuration and code of the paid application (excluding data) to create a new project based on the same codebase. | Not Available. |
+| **Users** | Allows you to add users for collaborative testing, but with Sandbox limitations. | Allows adding users with various roles (e.g., developer, tester, admin) for full project collaboration. | Not Available. |
+| **Delete** | Permanently deletes the Sandbox. | Permanently deletes the paid application. | Not Available. |
+| **Wake Up** | Available for the Sandbox when it enters Sleep Mode after inactivity. | Not Available. | Not Available.|
+
+
+## Application Overview Details
+
+The **Overview Page** in the Console provides a summary of essential information for any application, including Sandbox, paid applications, or Shared Applications. This is the first screen you see upon accessing an application in the Console, giving you a quick snapshot of its current status, resources, and recent activities. Here’s a breakdown of each section:
+.default})
+
+
+### Instance Information
+
+The top section of the Overview page displays key metrics and the status of your application’s environment, helping you monitor its health and resource usage:
+.default})
+
+- **Refresh button**: The .default})
button to refresh the information about the environment.
+
+- **Instance**: Shows the current state of the application instance.
+
+ - **RUNNING**: The instance is active and operational.
+
+ - **PENDING**: The instance is being set up and has not fully started yet.
+
+ - **OFFLINE**: The instance is unavailable or has been shut down.
+
+
+- **Server**: Indicates the server’s current status.
+
+ - **ONLINE**: The server is accessible and fully operational.
+
+ - **OFFLINE**: The server is not accessible.
+
+- **Disk**: Displays the percentage of disk storage currently in use, providing a quick overview of your storage consumption. This metric helps you manage and adjust storage resources as needed.
+
+
+- **Memory**: Shows the memory utilization percentage of your application. Monitoring memory usage ensures that your application has sufficient resources to operate smoothly.
+
+
+- **Outbound**: Tracks the data consumption of your application, listing both the current usage and the allocated limit (e.g., 94/1024MB). Exceeding your bandwidth limit can lead to additional charges or a throttling of data transfers.
+
+ :::info Edit Alert Button
+ .default})
+ .default})
+ .default})
+ .default})
+
+:::info
+Qodly Studio is only accessible in the development environment. Other environments, such as staging or production, do not offer access to Qodly Studio and are primarily intended for testing, showcasing, or final user deployment.
+:::
+
+
+## Qodly Account Management
+
+The account management section in Qodly provides users with functionalities to manage their personal account details, view invoices for applications, and securely log out of the platform.
+
+### Account Dropdown Menu
+
+Located in the top-right corner of the Qodly interface, the **Account Dropdown Menu** provides three options:
+
+.default})
+ .default})
+
+This section provides two main actions:
+
+1. **Update Account Details**: Clicking on **Update Account Details** opens a form where users can update their:
+
+ .default})
+ .default})
+ .default})
\ No newline at end of file
diff --git a/docs/cloud/dataManagement.md b/docs/cloud/dataManagement.md
new file mode 100644
index 0000000000..9497d66bd9
--- /dev/null
+++ b/docs/cloud/dataManagement.md
@@ -0,0 +1,79 @@
+---
+id: dataManagement
+title: Data Management
+---
+
+import Column from '@site/src/components/Column'
+
+## Overview
+
+The **Data** tab provides essential tools for managing and monitoring backups within your application's environment. This feature allows you to schedule regular backups, view backup history, and monitor backup activities. Note that the **Data** tab and backup functionalities are only available with a subscription.
+
+## Subscription Requirement
+
+- If you are viewing a shared application, you’ll see a message prompting you to ask the app owner to upgrade the application for backup access.
+
+- For owned applications without an active subscription, the tab will display an option to **Upgrade subscription**, allowing you to unlock the backup features directly.
+
+## Data Administration
+
+The **Data Administration** section includes settings for managing the backup frequency and viewing details about the latest backup.
+
+- **Frequency**: Displays the current backup schedule, such as daily or weekly, including the specific time (GMT) when backups are performed. This frequency can be set according to your data protection requirements.
+
+- **Last Backup**: Shows the date and time of the most recent backup, ensuring you can keep track of the latest data preservation point.
+
+
+There are additional actions available to help you manage your backups effectively:
+
+- **Refresh**: Updates the displayed information to reflect any recent changes to backup settings or the last backup.
+
+- **Settings (gear icon)**: Opens a dialog where you can configure the backup frequency and other backup-related settings.
+
+
+## Configuring Backup Frequency
+
+To adjust the backup frequency:
+
+1. Click the **Settings** (gear) icon within the **Backup Info** section.
+
+2. Set the desired frequency (e.g., daily, weekly) and specify the time for the backup to occur.
+
+3. Click **Save** to confirm your changes.
+
+This configuration ensures that your application data is periodically backed up based on the schedule that best fits your operational needs.
+
+
+## Backup History
+
+The **Backup History** section provides a log of all completed backups, allowing you to review each backup's details and status.
+
+- **Time**: Displays the exact timestamp of each backup event.
+
+- **Type**: Indicates the type of backup (e.g., full backup or incremental backup).
+
+- **Size**: Shows the size of the backup, helping you manage storage usage.
+
+- **Qodly Version**: Reflects the application version at the time of backup, allowing for version tracking.
+
+- **Release**: Displays the release associated with the backup, if applicable.
+
+- **Status**: Displays the verification status of each backup. Backup verification involves checking data integrity, which may include verifying records and/or indexes to ensure that data can be restored accurately.
+
+
+Each backup entry provides essential actions to manage your backups efficiently:
+
+- **Download**: Available for each backup entry, allowing you to download a copy of the backup for offline storage or testing.
+
+- **Restore**: Allows you to restore the application to the state captured in the backup. Note that this action should be used with caution as it will revert your data to the specified backup point.
+
+
+## Activity Log
+
+At the bottom of the **Data** tab, the **Activity** section tracks recent actions related to data management and backup settings.
+
+- **Set Backup Frequency**: Logs changes to the backup frequency, including the user who made the change and the specific schedule set.
+
+- **Create Backup**: Records each instance of a manual or scheduled backup, showing the timestamp and user involved.
+
+This log helps maintain an audit trail for data management activities, providing transparency and accountability for any changes to backup configurations or data state.
\ No newline at end of file
diff --git a/docs/cloud/deployment.md b/docs/cloud/deployment.md
deleted file mode 100644
index c2e2016297..0000000000
--- a/docs/cloud/deployment.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-id: deployment
-title: Release Management and Deployment
----
-
-Managing releases and deployments involves a unique approach that links releases between different environments, such as development and staging. This behavior is designed to ensure the integrity and consistency of your deployment pipeline but may lead to specific constraints when it comes to deleting releases.
-
-## Creating a Release in Development
-
-When initiating a **release** within the **development** environment, it begins as a standalone release that has not yet been pushed to any other environment. The steps involved include:
-
-1. Navigate to the **Deploy** tab.
-
-2. Click on the .default})
button, where you can provide a title and a brief description for the release.
-
-
-
-:::info
-During this phase, you have the freedom to delete .default})
this release as needed.
-.default})
-This is particularly useful for cases where a release in development may have issues or requires modifications before being promoted to other environments.
-:::
-
-
-## Release Deployment
-
-To commence the deployment of a release, simply click on the deployment icon .default})
positioned adjacent to the release in question.
-
-
-
-.default})
to a subsequent environment, such as the staging phase, deletion of the release is no longer an available option. This restriction is evident through the icon .default})
next to the release, which signifies the inability to remove it from either the **development** or **staging** environments.
-
-.default})
-
-.default})
-
-- Alternatively, you can click on the left-side tabs to manage your apps individually for each environment:
-
- .default})
-
-## Stop or restart Qodly Server
-
-Useful for resetting server memory.
-
-.default})
-
-## Open Qodly Studio
-
-You can directly access your application in Qodly Studio in two ways:
-
-- By clicking the **Studio** button on the Overview page
-
- .default})
-
-- Or, by clicking the "Studio URL" in the **General** tab for the current environment.
-
- .default})
-
-## Monitor Resources
-
-Access the **Metrics** tab of an environment to monitor its resources.
-
-.default})
-
-## Update Qodly Server
-
-Click the cloud icon to update your Qodly Server with the latest provided by the Qodly Platform.
-
-.default})
-
-## Invite Developers and Users
-
-In the **Team** tab, view the list of registered developers and users. Invite users by clicking the **Add user** button and providing their details, including "First Name", "Last Name", "Email Address", and "Profile" (a [role defined in Qodly Studio](../studio/roles/rolesPrivilegesOverview.md)).
-
-.default})
-
-## Schedule and Restore Backups
-
-.default})
-
-## Preview Your App
-
-Click the **Preview URL** in the Application Access area to open your application's [home page](../studio/settings.md#start-page).
-
-.default})
-
-## Add Custom Domain
-
-Per app, you can add a domain for validation (details provided by QCMC).
-
-
+:::
## Access Files via SFTP
-
### Overview
For every environment, you can access your files on the server using the **Secure File Transfer Protocol** (SFTP). This is achieved by clicking the **Access files** button.
diff --git a/docs/cloud/getStarted.md b/docs/cloud/getStarted.md
deleted file mode 100644
index 34e456aca3..0000000000
--- a/docs/cloud/getStarted.md
+++ /dev/null
@@ -1,72 +0,0 @@
----
-id: getStarted
-title: Qodly Applications
----
-
-
-## Application Overview
-
-The Qodly Cloud Management Console (QCMC) is the portal from which you can manage all your Qodly applications.
-
-After [logging in to your Qodly account](../concepts/quickstart.md), the QCMC presents an organized display of your Qodly applications on a single page.
-
-
-Your Qodly applications fall into three categories:
-
-- **Sandbox**: This serves as a trial application where you can freely explore Qodly's features and experiment. Please note that the Sandbox is accessible only in the [development environment](../cloud/getStarted#environments-and-services).
-- **Applications**: This section lists all applications you've created, excluding the Sandbox.
-- **Shared Applications**: Here, you'll find applications developed by other collaborators and shared with you through invitations.
-
-.default})
-
-## Environments and services
-
-For each application, the [Qodly Server](../concepts/platform.md#qodly-server) is deployed across three distinct instances, referred to as environments:
-
-- **Development**: This environment is ideal for developers to create, design, and enhance their Qodly applications.
-- **Staging**: In this environment, developers, product managers, or quality teams can thoroughly test application features in a configuration that closely simulates the production environment.
-- **Production**: The production environment is where users can access and utilize your finalized application.
-
-
-Each environment offers a unique set of services:
-
-||Development|Staging|Production|
-|---|---|---|---|
-|Access to Qodly Studio|X|||
-|Invite developers|X|||
-|Invite users||X|X|
-|Data Backup and Restore|||X|
-|Updates|X|X|X|
-
-
-
-## Cloning Applications
-
-Rather than starting from scratch, you have the option to clone any existing application and kickstart a new project based on the same codebase.
-
-To initiate application cloning, locate the desired application in the Apps list and click the **Clone** button:
-
-.default})
-
-The cloning process duplicates all your code, except data and resources.
-
-
-## Sleep Mode for Sandbox Applications
-
-Sandbox environments benefit from an automatic Sleep Mode feature, intended to enhance resource efficiency.
-
-The Sleep Mode feature is based upon the following principles:
-
-- **Automatic Sleep Activation**: If your sandbox's Studio is not accessed for a continuous period of 7 days, it will automatically enter Sleep Mode. This is part of our strategy to optimize resource usage.
-
-- **Easy Reactivation**: You can easily wake your sandbox from Sleep Mode during your next login, resuming your work seamlessly.
-
-Entering and waking up from sleep mode is automatically handled by the Qodly Cloud. You are notified by messages on screen when accessing the QCMC.
-
-:::important Important Notice - Deletion Policy
-
-If the sandbox is not reactivated within 3 months, it will be subject to permanent deletion.
-You will receive an email notification before any action is taken, ensuring you're informed at every step.
-We believe this feature will not only improve our system's efficiency but also encourage more active engagement with your sandbox projects.
-
-:::
diff --git a/docs/cloud/img/+Environment.png b/docs/cloud/img/+Environment.png
new file mode 100644
index 0000000000..2398ef6878
Binary files /dev/null and b/docs/cloud/img/+Environment.png differ
diff --git a/docs/cloud/img/GeneralActivity.png b/docs/cloud/img/GeneralActivity.png
new file mode 100644
index 0000000000..260a8d7cb0
Binary files /dev/null and b/docs/cloud/img/GeneralActivity.png differ
diff --git a/docs/cloud/img/GeneralApplicationAccess.png b/docs/cloud/img/GeneralApplicationAccess.png
new file mode 100644
index 0000000000..5133b7c0e6
Binary files /dev/null and b/docs/cloud/img/GeneralApplicationAccess.png differ
diff --git a/docs/cloud/img/GeneralApplicationAccessAuthenticated.png b/docs/cloud/img/GeneralApplicationAccessAuthenticated.png
new file mode 100644
index 0000000000..bfe1228626
Binary files /dev/null and b/docs/cloud/img/GeneralApplicationAccessAuthenticated.png differ
diff --git a/docs/cloud/img/GeneralApplicationAccessCustomDomain.png b/docs/cloud/img/GeneralApplicationAccessCustomDomain.png
new file mode 100644
index 0000000000..4b6db3daba
Binary files /dev/null and b/docs/cloud/img/GeneralApplicationAccessCustomDomain.png differ
diff --git a/docs/cloud/img/GeneralApplicationAccessCustomDomain2.png b/docs/cloud/img/GeneralApplicationAccessCustomDomain2.png
new file mode 100644
index 0000000000..9f6084bf18
Binary files /dev/null and b/docs/cloud/img/GeneralApplicationAccessCustomDomain2.png differ
diff --git a/docs/cloud/img/GeneralApplicationAccessCustomDomain3.png b/docs/cloud/img/GeneralApplicationAccessCustomDomain3.png
new file mode 100644
index 0000000000..c6a6bf0524
Binary files /dev/null and b/docs/cloud/img/GeneralApplicationAccessCustomDomain3.png differ
diff --git a/docs/cloud/img/GeneralApplicationAccessPublic.png b/docs/cloud/img/GeneralApplicationAccessPublic.png
new file mode 100644
index 0000000000..349f5f217b
Binary files /dev/null and b/docs/cloud/img/GeneralApplicationAccessPublic.png differ
diff --git a/docs/cloud/img/GeneralApplicationAccessStudio.png b/docs/cloud/img/GeneralApplicationAccessStudio.png
new file mode 100644
index 0000000000..da29336440
Binary files /dev/null and b/docs/cloud/img/GeneralApplicationAccessStudio.png differ
diff --git a/docs/cloud/img/GeneralEnvironmentInfo.png b/docs/cloud/img/GeneralEnvironmentInfo.png
new file mode 100644
index 0000000000..aaea0de633
Binary files /dev/null and b/docs/cloud/img/GeneralEnvironmentInfo.png differ
diff --git a/docs/cloud/img/GeneralEnvironmentInfoServer.png b/docs/cloud/img/GeneralEnvironmentInfoServer.png
new file mode 100644
index 0000000000..93e172b99e
Binary files /dev/null and b/docs/cloud/img/GeneralEnvironmentInfoServer.png differ
diff --git a/docs/cloud/img/GeneralEnvironmentInfoUsage.png b/docs/cloud/img/GeneralEnvironmentInfoUsage.png
new file mode 100644
index 0000000000..5655eeb6bb
Binary files /dev/null and b/docs/cloud/img/GeneralEnvironmentInfoUsage.png differ
diff --git a/docs/cloud/img/GeneralEnvironmentInfoUsers.png b/docs/cloud/img/GeneralEnvironmentInfoUsers.png
new file mode 100644
index 0000000000..e296cd4f48
Binary files /dev/null and b/docs/cloud/img/GeneralEnvironmentInfoUsers.png differ
diff --git a/docs/cloud/img/accountDropdown.png b/docs/cloud/img/accountDropdown.png
new file mode 100644
index 0000000000..6641d37dda
Binary files /dev/null and b/docs/cloud/img/accountDropdown.png differ
diff --git a/docs/cloud/img/activityHistory.png b/docs/cloud/img/activityHistory.png
new file mode 100644
index 0000000000..f5568bcfdb
Binary files /dev/null and b/docs/cloud/img/activityHistory.png differ
diff --git a/docs/cloud/img/addUser1.png b/docs/cloud/img/addUser1.png
new file mode 100644
index 0000000000..c5d417bc54
Binary files /dev/null and b/docs/cloud/img/addUser1.png differ
diff --git a/docs/cloud/img/addUser2.png b/docs/cloud/img/addUser2.png
new file mode 100644
index 0000000000..9cef8b3cdd
Binary files /dev/null and b/docs/cloud/img/addUser2.png differ
diff --git a/docs/cloud/img/addUser3.png b/docs/cloud/img/addUser3.png
new file mode 100644
index 0000000000..f6f3dc2f26
Binary files /dev/null and b/docs/cloud/img/addUser3.png differ
diff --git a/docs/cloud/img/addUser4.png b/docs/cloud/img/addUser4.png
new file mode 100644
index 0000000000..1b3c1b7ef0
Binary files /dev/null and b/docs/cloud/img/addUser4.png differ
diff --git a/docs/cloud/img/addUser5.png b/docs/cloud/img/addUser5.png
new file mode 100644
index 0000000000..361fc4d8c7
Binary files /dev/null and b/docs/cloud/img/addUser5.png differ
diff --git a/docs/cloud/img/addUser6.png b/docs/cloud/img/addUser6.png
new file mode 100644
index 0000000000..9aac91347d
Binary files /dev/null and b/docs/cloud/img/addUser6.png differ
diff --git a/docs/cloud/img/addUserToEnvironement1.png b/docs/cloud/img/addUserToEnvironement1.png
new file mode 100644
index 0000000000..98378886be
Binary files /dev/null and b/docs/cloud/img/addUserToEnvironement1.png differ
diff --git a/docs/cloud/img/app1.2.png b/docs/cloud/img/app1.2.png
deleted file mode 100644
index f9d6c61ff2..0000000000
Binary files a/docs/cloud/img/app1.2.png and /dev/null differ
diff --git a/docs/cloud/img/app1.png b/docs/cloud/img/app1.png
deleted file mode 100644
index d42e871274..0000000000
Binary files a/docs/cloud/img/app1.png and /dev/null differ
diff --git a/docs/cloud/img/app2.png b/docs/cloud/img/app2.png
deleted file mode 100644
index 9cc1ea32b5..0000000000
Binary files a/docs/cloud/img/app2.png and /dev/null differ
diff --git a/docs/cloud/img/applicationOverview.png b/docs/cloud/img/applicationOverview.png
new file mode 100644
index 0000000000..732a1bd757
Binary files /dev/null and b/docs/cloud/img/applicationOverview.png differ
diff --git a/docs/cloud/img/backup.png b/docs/cloud/img/backup.png
deleted file mode 100644
index 99828983be..0000000000
Binary files a/docs/cloud/img/backup.png and /dev/null differ
diff --git a/docs/cloud/img/billingChangePayement.png b/docs/cloud/img/billingChangePayement.png
new file mode 100644
index 0000000000..0d45ba0329
Binary files /dev/null and b/docs/cloud/img/billingChangePayement.png differ
diff --git a/docs/cloud/img/billingChangePayement2.png b/docs/cloud/img/billingChangePayement2.png
new file mode 100644
index 0000000000..2aff457241
Binary files /dev/null and b/docs/cloud/img/billingChangePayement2.png differ
diff --git a/docs/cloud/img/billingDownloadInvoice.png b/docs/cloud/img/billingDownloadInvoice.png
new file mode 100644
index 0000000000..0f40c7aca4
Binary files /dev/null and b/docs/cloud/img/billingDownloadInvoice.png differ
diff --git a/docs/cloud/img/billingDownloadInvoice2.png b/docs/cloud/img/billingDownloadInvoice2.png
new file mode 100644
index 0000000000..dc4a08fc37
Binary files /dev/null and b/docs/cloud/img/billingDownloadInvoice2.png differ
diff --git a/docs/cloud/img/billingInvoices.png b/docs/cloud/img/billingInvoices.png
new file mode 100644
index 0000000000..7b6689755f
Binary files /dev/null and b/docs/cloud/img/billingInvoices.png differ
diff --git a/docs/cloud/img/billingManageSubscription.png b/docs/cloud/img/billingManageSubscription.png
new file mode 100644
index 0000000000..2ef3b4892d
Binary files /dev/null and b/docs/cloud/img/billingManageSubscription.png differ
diff --git a/docs/cloud/img/billingNextInvoice.png b/docs/cloud/img/billingNextInvoice.png
new file mode 100644
index 0000000000..c01973ffde
Binary files /dev/null and b/docs/cloud/img/billingNextInvoice.png differ
diff --git a/docs/cloud/img/billingNextInvoiceDetails.png b/docs/cloud/img/billingNextInvoiceDetails.png
new file mode 100644
index 0000000000..ac9a2e31f6
Binary files /dev/null and b/docs/cloud/img/billingNextInvoiceDetails.png differ
diff --git a/docs/cloud/img/billingOverview.png b/docs/cloud/img/billingOverview.png
new file mode 100644
index 0000000000..60a16b1660
Binary files /dev/null and b/docs/cloud/img/billingOverview.png differ
diff --git a/docs/cloud/img/billingSubscriptionOverview.png b/docs/cloud/img/billingSubscriptionOverview.png
new file mode 100644
index 0000000000..f88240f5fd
Binary files /dev/null and b/docs/cloud/img/billingSubscriptionOverview.png differ
diff --git a/docs/cloud/img/cancel.png b/docs/cloud/img/cancel.png
new file mode 100644
index 0000000000..827ae854b9
Binary files /dev/null and b/docs/cloud/img/cancel.png differ
diff --git a/docs/cloud/img/changePassword.png b/docs/cloud/img/changePassword.png
new file mode 100644
index 0000000000..a92fe46acc
Binary files /dev/null and b/docs/cloud/img/changePassword.png differ
diff --git a/docs/cloud/img/clone.png b/docs/cloud/img/clone.png
deleted file mode 100644
index 0cd712f11b..0000000000
Binary files a/docs/cloud/img/clone.png and /dev/null differ
diff --git a/docs/cloud/img/configureAddEnvironment.png b/docs/cloud/img/configureAddEnvironment.png
new file mode 100644
index 0000000000..174831c561
Binary files /dev/null and b/docs/cloud/img/configureAddEnvironment.png differ
diff --git a/docs/cloud/img/configureAdditionalEnvironment.png b/docs/cloud/img/configureAdditionalEnvironment.png
new file mode 100644
index 0000000000..db85258492
Binary files /dev/null and b/docs/cloud/img/configureAdditionalEnvironment.png differ
diff --git a/docs/cloud/img/configureDevelopmentEnvironment.png b/docs/cloud/img/configureDevelopmentEnvironment.png
new file mode 100644
index 0000000000..5b2f9dee3d
Binary files /dev/null and b/docs/cloud/img/configureDevelopmentEnvironment.png differ
diff --git a/docs/cloud/img/configureGeneralInfo.png b/docs/cloud/img/configureGeneralInfo.png
new file mode 100644
index 0000000000..4c5f10a430
Binary files /dev/null and b/docs/cloud/img/configureGeneralInfo.png differ
diff --git a/docs/cloud/img/configureSummary.png b/docs/cloud/img/configureSummary.png
new file mode 100644
index 0000000000..c3f6aa9b80
Binary files /dev/null and b/docs/cloud/img/configureSummary.png differ
diff --git a/docs/cloud/img/console.png b/docs/cloud/img/console.png
deleted file mode 100644
index 50c9c7ccb7..0000000000
Binary files a/docs/cloud/img/console.png and /dev/null differ
diff --git a/docs/cloud/img/consoleMyApps.png b/docs/cloud/img/consoleMyApps.png
new file mode 100644
index 0000000000..a7fe6bee16
Binary files /dev/null and b/docs/cloud/img/consoleMyApps.png differ
diff --git a/docs/cloud/img/consoleOverview.png b/docs/cloud/img/consoleOverview.png
new file mode 100644
index 0000000000..be27face1e
Binary files /dev/null and b/docs/cloud/img/consoleOverview.png differ
diff --git a/docs/cloud/img/consoleSandbox.png b/docs/cloud/img/consoleSandbox.png
new file mode 100644
index 0000000000..55f3969444
Binary files /dev/null and b/docs/cloud/img/consoleSandbox.png differ
diff --git a/docs/cloud/img/consoleSharedApplications.png b/docs/cloud/img/consoleSharedApplications.png
new file mode 100644
index 0000000000..70bc4d5217
Binary files /dev/null and b/docs/cloud/img/consoleSharedApplications.png differ
diff --git a/docs/cloud/img/declinePayement.png b/docs/cloud/img/declinePayement.png
new file mode 100644
index 0000000000..615dd3aa16
Binary files /dev/null and b/docs/cloud/img/declinePayement.png differ
diff --git a/docs/cloud/img/delete.png b/docs/cloud/img/delete.png
new file mode 100644
index 0000000000..432202ffa4
Binary files /dev/null and b/docs/cloud/img/delete.png differ
diff --git a/docs/cloud/img/deleteUser.png b/docs/cloud/img/deleteUser.png
new file mode 100644
index 0000000000..213133fb84
Binary files /dev/null and b/docs/cloud/img/deleteUser.png differ
diff --git a/docs/cloud/img/discard.png b/docs/cloud/img/discard.png
new file mode 100644
index 0000000000..e70d4ae3f6
Binary files /dev/null and b/docs/cloud/img/discard.png differ
diff --git a/docs/cloud/img/edit.png b/docs/cloud/img/edit.png
new file mode 100644
index 0000000000..cab57a155f
Binary files /dev/null and b/docs/cloud/img/edit.png differ
diff --git a/docs/cloud/img/editAlert.png b/docs/cloud/img/editAlert.png
new file mode 100644
index 0000000000..3257c20bb9
Binary files /dev/null and b/docs/cloud/img/editAlert.png differ
diff --git a/docs/cloud/img/editUser1.png b/docs/cloud/img/editUser1.png
new file mode 100644
index 0000000000..df0802f90d
Binary files /dev/null and b/docs/cloud/img/editUser1.png differ
diff --git a/docs/cloud/img/environementUserList.png b/docs/cloud/img/environementUserList.png
new file mode 100644
index 0000000000..b37f404d09
Binary files /dev/null and b/docs/cloud/img/environementUserList.png differ
diff --git a/docs/cloud/img/environments.png b/docs/cloud/img/environments.png
new file mode 100644
index 0000000000..bc83867feb
Binary files /dev/null and b/docs/cloud/img/environments.png differ
diff --git a/docs/cloud/img/expand.png b/docs/cloud/img/expand.png
new file mode 100644
index 0000000000..fe96ae8c61
Binary files /dev/null and b/docs/cloud/img/expand.png differ
diff --git a/docs/cloud/img/instanceInformation.png b/docs/cloud/img/instanceInformation.png
new file mode 100644
index 0000000000..cc4817bcb6
Binary files /dev/null and b/docs/cloud/img/instanceInformation.png differ
diff --git a/docs/cloud/img/invitationsAwaitingResponse.png b/docs/cloud/img/invitationsAwaitingResponse.png
new file mode 100644
index 0000000000..80aaf20bd2
Binary files /dev/null and b/docs/cloud/img/invitationsAwaitingResponse.png differ
diff --git a/docs/cloud/img/invite1.png b/docs/cloud/img/invite1.png
deleted file mode 100644
index 62ed8436e9..0000000000
Binary files a/docs/cloud/img/invite1.png and /dev/null differ
diff --git a/docs/cloud/img/invoices.png b/docs/cloud/img/invoices.png
new file mode 100644
index 0000000000..1551907b33
Binary files /dev/null and b/docs/cloud/img/invoices.png differ
diff --git a/docs/cloud/img/metrics.png b/docs/cloud/img/metrics.png
deleted file mode 100644
index 461c836310..0000000000
Binary files a/docs/cloud/img/metrics.png and /dev/null differ
diff --git a/docs/cloud/img/myAccount.png b/docs/cloud/img/myAccount.png
new file mode 100644
index 0000000000..adf52d89d9
Binary files /dev/null and b/docs/cloud/img/myAccount.png differ
diff --git a/docs/cloud/img/newApp.png b/docs/cloud/img/newApp.png
new file mode 100644
index 0000000000..0c31a92f0e
Binary files /dev/null and b/docs/cloud/img/newApp.png differ
diff --git a/docs/cloud/img/newSandbox.png b/docs/cloud/img/newSandbox.png
new file mode 100644
index 0000000000..0ca6ecdcbb
Binary files /dev/null and b/docs/cloud/img/newSandbox.png differ
diff --git a/docs/cloud/img/openStudio.png b/docs/cloud/img/openStudio.png
new file mode 100644
index 0000000000..0de0f584a1
Binary files /dev/null and b/docs/cloud/img/openStudio.png differ
diff --git a/docs/cloud/img/payOnYourOwn.png b/docs/cloud/img/payOnYourOwn.png
new file mode 100644
index 0000000000..18ecd93e4a
Binary files /dev/null and b/docs/cloud/img/payOnYourOwn.png differ
diff --git a/docs/cloud/img/preview.png b/docs/cloud/img/preview.png
deleted file mode 100644
index 0b6670be50..0000000000
Binary files a/docs/cloud/img/preview.png and /dev/null differ
diff --git a/docs/cloud/img/publish.png b/docs/cloud/img/publish.png
deleted file mode 100644
index 0848482882..0000000000
Binary files a/docs/cloud/img/publish.png and /dev/null differ
diff --git a/docs/cloud/img/refresh.png b/docs/cloud/img/refresh.png
new file mode 100644
index 0000000000..1f7d10e0cb
Binary files /dev/null and b/docs/cloud/img/refresh.png differ
diff --git a/docs/cloud/img/removeUser.png b/docs/cloud/img/removeUser.png
new file mode 100644
index 0000000000..56bab4beb7
Binary files /dev/null and b/docs/cloud/img/removeUser.png differ
diff --git a/docs/cloud/img/removeUserfromEnvironments.png b/docs/cloud/img/removeUserfromEnvironments.png
new file mode 100644
index 0000000000..467169ad76
Binary files /dev/null and b/docs/cloud/img/removeUserfromEnvironments.png differ
diff --git a/docs/cloud/img/saveChanges.png b/docs/cloud/img/saveChanges.png
new file mode 100644
index 0000000000..4e7bfb48ff
Binary files /dev/null and b/docs/cloud/img/saveChanges.png differ
diff --git a/docs/cloud/img/studio1.png b/docs/cloud/img/studio1.png
deleted file mode 100644
index d654b23cb3..0000000000
Binary files a/docs/cloud/img/studio1.png and /dev/null differ
diff --git a/docs/cloud/img/studio2.png b/docs/cloud/img/studio2.png
deleted file mode 100644
index f5ab841db3..0000000000
Binary files a/docs/cloud/img/studio2.png and /dev/null differ
diff --git a/docs/cloud/img/submit.png b/docs/cloud/img/submit.png
new file mode 100644
index 0000000000..f6613a648d
Binary files /dev/null and b/docs/cloud/img/submit.png differ
diff --git a/docs/cloud/img/subscriptionAddEnvironement.png b/docs/cloud/img/subscriptionAddEnvironement.png
new file mode 100644
index 0000000000..439085500d
Binary files /dev/null and b/docs/cloud/img/subscriptionAddEnvironement.png differ
diff --git a/docs/cloud/img/subscriptionAddEnvironement2.png b/docs/cloud/img/subscriptionAddEnvironement2.png
new file mode 100644
index 0000000000..b85bc74be8
Binary files /dev/null and b/docs/cloud/img/subscriptionAddEnvironement2.png differ
diff --git a/docs/cloud/img/subscriptionDelete.png b/docs/cloud/img/subscriptionDelete.png
new file mode 100644
index 0000000000..28bc4bcff7
Binary files /dev/null and b/docs/cloud/img/subscriptionDelete.png differ
diff --git a/docs/cloud/img/subscriptionDelete2.png b/docs/cloud/img/subscriptionDelete2.png
new file mode 100644
index 0000000000..d18ea90181
Binary files /dev/null and b/docs/cloud/img/subscriptionDelete2.png differ
diff --git a/docs/cloud/img/subscriptionOpen.png b/docs/cloud/img/subscriptionOpen.png
new file mode 100644
index 0000000000..9d68a623c0
Binary files /dev/null and b/docs/cloud/img/subscriptionOpen.png differ
diff --git a/docs/cloud/img/subscriptionOverview.png b/docs/cloud/img/subscriptionOverview.png
new file mode 100644
index 0000000000..ba9b0a1059
Binary files /dev/null and b/docs/cloud/img/subscriptionOverview.png differ
diff --git a/docs/cloud/img/subscriptionOverview2.png b/docs/cloud/img/subscriptionOverview2.png
new file mode 100644
index 0000000000..4f44f5825a
Binary files /dev/null and b/docs/cloud/img/subscriptionOverview2.png differ
diff --git a/docs/cloud/img/subscriptionUpgrade.png b/docs/cloud/img/subscriptionUpgrade.png
new file mode 100644
index 0000000000..6562177a16
Binary files /dev/null and b/docs/cloud/img/subscriptionUpgrade.png differ
diff --git a/docs/cloud/img/subscriptionUpgradePanel.png b/docs/cloud/img/subscriptionUpgradePanel.png
new file mode 100644
index 0000000000..1fbf90e42d
Binary files /dev/null and b/docs/cloud/img/subscriptionUpgradePanel.png differ
diff --git a/docs/cloud/img/templateMoreInfo.png b/docs/cloud/img/templateMoreInfo.png
new file mode 100644
index 0000000000..3eb84fedd0
Binary files /dev/null and b/docs/cloud/img/templateMoreInfo.png differ
diff --git a/docs/cloud/img/templates.png b/docs/cloud/img/templates.png
new file mode 100644
index 0000000000..2cc371120a
Binary files /dev/null and b/docs/cloud/img/templates.png differ
diff --git a/docs/cloud/img/transferOwnership.png b/docs/cloud/img/transferOwnership.png
new file mode 100644
index 0000000000..204f3836fe
Binary files /dev/null and b/docs/cloud/img/transferOwnership.png differ
diff --git a/docs/cloud/img/transferOwnership2.png b/docs/cloud/img/transferOwnership2.png
new file mode 100644
index 0000000000..0a9e922bdc
Binary files /dev/null and b/docs/cloud/img/transferOwnership2.png differ
diff --git a/docs/cloud/img/update.png b/docs/cloud/img/update.png
deleted file mode 100644
index 6efd8c763d..0000000000
Binary files a/docs/cloud/img/update.png and /dev/null differ
diff --git a/docs/cloud/img/updateAccount.png b/docs/cloud/img/updateAccount.png
new file mode 100644
index 0000000000..506ac9bbc3
Binary files /dev/null and b/docs/cloud/img/updateAccount.png differ
diff --git a/docs/cloud/img/upgradeToLatestVersion.png b/docs/cloud/img/upgradeToLatestVersion.png
new file mode 100644
index 0000000000..023a2a47d4
Binary files /dev/null and b/docs/cloud/img/upgradeToLatestVersion.png differ
diff --git a/docs/cloud/img/userCard.png b/docs/cloud/img/userCard.png
new file mode 100644
index 0000000000..401284bbf4
Binary files /dev/null and b/docs/cloud/img/userCard.png differ
diff --git a/docs/cloud/img/userList.png b/docs/cloud/img/userList.png
new file mode 100644
index 0000000000..a576a807db
Binary files /dev/null and b/docs/cloud/img/userList.png differ
diff --git a/docs/cloud/myApps.md b/docs/cloud/myApps.md
new file mode 100644
index 0000000000..115d70bc7c
--- /dev/null
+++ b/docs/cloud/myApps.md
@@ -0,0 +1,178 @@
+---
+id: myApps
+title: My Apps
+---
+
+import Column from '@site/src/components/Column'
+
+## Overview
+
+The **My Apps** area is where you can manage all the applications you’ve created in Qodly, including paid applications and any cloned from the Sandbox environment. This area provides access to essential management options, configuration settings, and monitoring tools, enabling you to control every aspect of your applications.
+
+
+## Creating a New Application
+
+To create an app in the Console, follow the steps below, using the provided screenshots for guidance. Each step includes specific details on the configuration options available during setup.
+
+### Step 1: Navigate to "My Apps"
+
+.default})
+ .default})
+
+2. **Blank Template**: If you prefer a completely custom setup without any pre-built code, select the Blank Template.
+
+3. **More Info**: Click **More Info** under a template to view additional details, such as images, a description, author information, and the supported language.
+.default})
+
+4. Once you’ve chosen a template, click **Create** to proceed.
+
+
+### Step 3: Configure Application Details
+
+You’ll now enter the **Application Configuration** page, where you’ll provide essential information and allocate resources for your new app, like:
+
+- **Application Name**: Enter a unique name for your application. This name will be visible in the Console and can be updated later if needed.
+- **Field**: Select the global domain or purpose of your application (e.g., "E-commerce" or "Project Management").
+- **Description**: Provide a short description of your app’s purpose to help identify it within the Console.
+- **Tags**: Add tags to categorize your app. This feature is useful for organizing and searching for applications. To add a tag, type it in and press **Enter**.
+
+ .default})
+
+#### Environment Configuration
+
+The next section allows you to configure resources for each environment associated with the app. By default, only the **Development Environment** is available.
+
+1. **Qodly Power**: Choose the required computing power for your environment. Options vary by memory and CPU configurations (e.g., Power 1 with 2 GB memory and 2 CPU, Power 2 with 4 GB memory and 2 CPU).
+2. **Storage**: By default, you receive 100 GB of free storage. Additional storage can be added based on the anticipated needs of your app.
+3. **Backup**: Enable the backup feature if needed. By default, backups are not available but can be purchased as an add-on based on the storage size.
+4. **Network**: Configure the data transferred over the network. The default allocation is 1 GB, with options to add more data if your application requires it.
+
+ .default})
+
+
+.default})
+ .default})
+
+.default})
+ .default})
+
+
+- **Option 2: Transfer Ownership**: Invite someone else to take responsibility for the app's subscription.
+ .default}){kind=spacer}
+
+
+#### Option 1: Pay on Your Own:
+
+If you decide to cover the application expenses yourself, you will be guided through a billing and payment process:
+
+- **Billing Details Page**: This page allows you to enter or update the billing details required for the subscription. Once your information is complete and verified, click Proceed to Payment to move to the next step.
+
+- **Secure Payment Page**: On this page, you will securely enter your payment details to finalize the subscription. Once all details are complete, click Submit to process your payment.
+
+
+#### Option 2: Transfer Ownership:
+
+If someone else will be responsible for the payment, you can transfer ownership of the application to them. Here’s how this process works:
+
+- Enter the email of the person who will pay for the subscription.
+ .default}){kind=spacer}
+
+:::info
+The system ensures you cannot send the invitation to your own email address, displaying an error if attempted.
+:::
+
+- Once the invitation is sent, the app is moved to the Invitations Awaiting Response section until the recipient accepts the invitation.
+ .default})
+
+:::info Invitations Awaiting Response
+This section displays all pending invitations for transferring app ownership. For each invitation, the following actions are available:
+
+- Resend Invitation: Re-send the request to the recipient.
+
+- Cancel Invitation: Remove the request if no longer needed.
+:::
+
+
+- The invited individual will receive an email with a link to accept the ownership transfer. Once they accept:
+
+ - They will gain full ownership of the application.
+
+ - They will proceed to fill out their billing details and complete the payment.
+
+
+:::info Decline Payment
+
+.default})
+ .default})
+
+
+## Creating a Release in Development
+
+When creating a **release** in the **development** environment, it initially exists as an independent release that hasn’t yet been pushed to other environments. The steps to create a release include:
+
+1. Go to the **Deploy** tab.
+
+2. Click on the button, then provide a title and a brief description for the release.
+
+
+
+:::info
+At this stage, you can freely delete the release if needed.
+
+This flexibility is useful when a release in development has issues or requires modifications before it is promoted to other environments.
+:::
+
+
+## Deploying a Release
+
+To deploy a release, simply click on the deployment icon next to the release you wish to deploy.
+
+
+
+ to a subsequent environment, such as **staging**, it can no longer be deleted. This restriction is indicated by the icon beside the release, signifying that it cannot be removed from the **development** or **staging** environments.
+
+
+
+.default})
+
+#### 1. **Usage**:
+
+.default})
+ .default})
+ .default})
+ .default})
+
+#### 1. **Studio URL**:
+
+.default})
+ .default})
+ .default})
+ .default})
+
+.default})
+ .default})
+ .default})
+ .default})
+
+
+ 2. **Blank Template**: If you prefer a completely custom setup without any pre-built code, select the Blank Template.
+
+ 3. **More Info**: Click **More Info** under a template to view additional details, such as images, a description, author information, and the supported language.
+
+
+ 4. Once you’ve chosen a template, click **Create** to proceed.
+
+Once created, you’ll see an overview of your Sandbox in the cosole homepage.
+
+
+## Sleep Mode
+
+To optimize resource usage, the Sandbox utilize an automatic Sleep Mode feature, which helps conserve resources when the environment is inactive:
+
+- **Automatic Sleep Mode**: If the Sandbox remains inactive for more than 7 days, it will automatically enter Sleep Mode.
+
+- **Manual Wake Up**: You can reactivate the Sandbox by clicking the `Wake Up` button, making it operational immediately. Each manual wake-up action is documented in the Activity log, including the time and user information.
+
+- **Notifications**: Qodly sends email notifications to inform you when your Sandbox enters or exits Sleep Mode.
+
+
+## Deletion Policy
+
+If a Sandbox environment remains inactive for an extended period, Qodly may permanently delete it according to the following policy:
+
+- **3-Month Inactivity Threshold**: If the Sandbox is not reactivated within 3 months, it will be permanently deleted.
+
+- **Notification Prior to Deletion**: Before deletion, Qodly will send an email notification, giving you an opportunity to save any necessary data or take other actions.
+
diff --git a/docs/cloud/userAccountManagement.md b/docs/cloud/userAccountManagement.md
new file mode 100644
index 0000000000..05f0819b86
--- /dev/null
+++ b/docs/cloud/userAccountManagement.md
@@ -0,0 +1,399 @@
+---
+id: userAccountManagement
+title: User Management
+---
+
+import Column from '@site/src/components/Column'
+
+## Overview
+
+Qodly provides a robust user management system with two distinct interfaces:
+
+
+| Interface | Purpose | Key Features | Access |
+|-----------------|-------------------|---------------------------|------------------------------------------|
+| Users Page | Centralized app-wide user management. | - Add new users or assign existing users to environments..default})
+3. Fill in the following details:
+.default})
+ .default})
+
+:::tip Environment-Specific Assignment
+The added user is automatically visible in the Team Tab of the assigned environments, maintaining consistency between the Users Page and environment-specific views. Changes to user details made in either interface are synchronized.
+:::
+
+
+### Edit User Details
+
+Editing a user's details in the Users Page is environment-specific, meaning you must update their information individually for each environment they are assigned to. Follow these steps to make changes:
+
+.default})
the user card to reveal their assigned environments..default})
button next to the specific environment where the user is assigned..default})
+ .default})
+ .default})
button located on the user card.
+ .default})
+ the user card to view all the environments they are assigned to..default})
button next to the specific environment where the user is assigned.
+ .default})
+ .default})
button located on the user card.
+ .default})
+ .default})
+3. In the dialog, select one of the following options:
+
+ .default})
+ .default})
+ .default})
+
+These users will also appear in the Users Page with a tag representing the environment to which they were assigned.
+:::
+
+
+### Edit User Details
+
+Editing a user’s details in the Team Tab is specific to the environment where the user is assigned. Any changes made are applicable only for that particular environment.
+
+ button next to the user..default})
+
+ button next to the specific user.
+
+ .default})
-
-2. Copy the verification code from your email and click **Confirm account**.
-
- .default})
-
-3. Provide additional information to complete your profile:
-
- .default})
-
-4. Click **Submit** to access the Qodly Cloud Management Console.
-
-
-## Step 2: Set Up Your Sandbox and Environment
-
-1. Choose a Template to create your sandbox application. Two options are available:
-
- - **Create a sandbox from scratch**: Begin with an empty sandbox and follow the **Welcome Tour** within Qodly Studio. Select the Blank app template.
- - **Create a sandbox from a sample**: Start with a sample application containing code and data for reference.
- .default})
-
-
-2. The sandbox environment will be prepared automatically. This process takes just a few seconds.
-
- .default})
-
-
-## Step 3: Navigate Qodly Studio and Begin the Welcome Tour
-
-With the environment ready, it's time to access Qodly Studio and follow the Welcome Tour.
-
-
-1. Click the **Studio** button located on the right side of your application line:
-
- .default})
-
-2. Click **Next** to start the Welcome Tour within Qodly Studio!
-
- .default})
-
- .default})
-
- :::
-
-Data button on the Studio home page: Data button on Qodly Studio home page: Data button in the header bar: .default})
+You can delete and reinstall it as needed. The only limitation is one sandbox per user.
2. The development environment of your sandbox application is automatically prepared. This step takes just a few seconds.
@@ -44,7 +57,7 @@ The application name is automatically generated for sandbox applications.
:::
-## Step 3: Navigate Qodly Studio and Begin the Welcome Tour
+## Navigate Qodly Studio and Begin the Welcome Tour
With the development environment ready, it's time to access Qodly Studio and follow the Welcome Tour.
@@ -74,6 +87,9 @@ With the development environment ready, it's time to access Qodly Studio and fol
Methods or Classes. New + tab and opt for either Methods or Classes..default})
+1. Click the Debug button located in Qodly Studio toolbar.
2. If the debug session starts successfully, a green bullet will appear on the button label. .default})
@@ -43,7 +43,7 @@ Verify that the method or function with the breakpoint is saved and not in [draf
If you wish to stop a debug session, follow these steps:
-1. Click the **Debug** button in the Studio toolbar while a debug session is active.
+1. Click the **Debug** button in Qodly Studio toolbar while a debug session is active.
2. A warning dialog box will prompt you to confirm whether you want to detach the debugger, effectively closing the debug session attached to your browser. You will have several options:
diff --git a/docs/studio/model/attributes.md b/docs/studio/model/attributes.md
index ff58d6cd59..ba024eadac 100644
--- a/docs/studio/model/attributes.md
+++ b/docs/studio/model/attributes.md
@@ -21,7 +21,7 @@ You can view and modify a few of the attribute’s properties when you select or
- a name in _italics_ indicates a not exposed attribute
- **Primary Key**: Indicates the primary key attribute for the datastore class. This attribute is mandatory, you can rename it but not delete it.
- **Type Icon**: Displays the datastore entity type as an icon.
-- **Type**: Attribute type that you can change by double-clicking on it to render the area enterable. An attribute type can be [scalar](../../concepts/platform.md#data-types) or based upon a [relation](#create-a-relation-attribute), in which case it can be of the _classNameEntity_ or _classNameSelection_ type.
+- **Type**: Attribute type that you can change by double-clicking on it to render the area enterable. An attribute type can be [scalar](#data-types) or based upon a [relation](#create-a-relation-attribute), in which case it can be of the _classNameEntity_ or _classNameSelection_ type.
All attributes of a datastore class are also listed in the [Outline area](model-editor-interface#outline) of the model editor.
@@ -41,7 +41,7 @@ There are several categories of attributes in Qodly:
Indicates an alias attribute.
- **Calculated**: A [calculated attribute](#calculated-attributes) does not store information; instead, it determines its value based on other values from the same entity or from other entities, attributes or datastore class methods. .default})
Indicates a calculated attribute.
-The data type list contains [predefined data types](../../concepts/platform.md#qodly-database) as well as datastore classes and entity selections (in bold), and relation attributes if some have already been defined:
+The data type list contains [predefined data types](#data-types) as well as datastore classes and entity selections (in bold), and relation attributes if some have already been defined:
.default})
@@ -63,9 +63,27 @@ To create a storage attribute:
2. Give a [name](#attribute-name) to the attribute.
3. Select a predefined data type from the list and press **Enter**.
-:::info
-The **Qodly database** supports [an extended set of data types](../../concepts/platform.md#data-types).
-:::
+
+### Data types
+
+The following table lists all available Qodly Database storage (*aka* scalar) data types and how they are handled in the [QodlyScript language](../../language/basics/lang-data-types.md):
+
+|Data Types |Language support|Description|
+|---|----|---|
+|Text|`string` |A sequence of characters up to 2 GB|
+|String |`string` |A sequence of characters with properties|
+|UUID|-|Universally Unique Identifier: a 16-bytes (128 bits) number containing 32 hexadecimal characters|
+|Date|`date` |If the **Date only** property is selected for this attribute type, the date value will include only the "MM/DD/YYYY" format (e.g., "10/05/2023"). Otherwise, the date value including the time, stored in UTC. The date is expressed in the following format: YYYY-MM-DDTHH:MM:ss.SSSZ (e.g., "2023-10-05T23:00:00.000Z" for October 5, 2023 in the Central European Timezone). SSS represents the milliseconds, which can be between 0 to 999. |
+|Duration|`time` |A time value which is stored as a duration between two dates |
+|Bool|`boolean`|A Boolean value: either true or false.|
+|Byte|-|A sequence of 8 bits.|
+|Word|-|A 16-bit signed integer. Range: -32,767 to 32,768|
+|Number|`real`|A numeric value, can be a Real or a Long. Range: ±1.7e±308 (real), -2^31 to (2^31)-1 (long)|
+|Long|`real`|An integer number, greater than or equal to a standard number. Range: -2,147,483,648 to 2,147,483,647 |
+|Object|`object`|Object containing any kind of property/value pairs, including collections. This data type can be indexed. Functions and recursive references are not supported|
+|Image|`picture` |A path to an image file or an actual image. |
+|Blob|`blob` or `object` |Binary Large Object stored as a scalar value or a `4D.Blob` object |
+
## Create a relation attribute
diff --git a/docs/studio/model/model-editor-interface.md b/docs/studio/model/model-editor-interface.md
index 1bcc78054f..8cc77308a7 100644
--- a/docs/studio/model/model-editor-interface.md
+++ b/docs/studio/model/model-editor-interface.md
@@ -14,7 +14,7 @@ The Data Model Editor in Qodly enables you to create and modify the **model** fo
### ORDA Concepts
-In Qodly, each datastore class can have attributes that store or calculate data, or refer to data in other datastore classes (relation attributes). You can also create functions to interact with the data in your model, following the ORDA concepts.
+In Qodly, each datastore class can have attributes that store or calculate data, or refer to data in other datastore classes (relation attributes). You can also create functions to interact with the data in your model, following the [ORDA concepts](../../orda/data-model.md#the-orda-concept).
### Permissions
diff --git a/docs/studio/overview.md b/docs/studio/overview.md
index d133f75820..62b8668343 100644
--- a/docs/studio/overview.md
+++ b/docs/studio/overview.md
@@ -6,7 +6,7 @@ title: Overview
Development in Qodly relies on the use of **Qodly Studio**, an innovative platform for creating business web applications. Our primary goal with **Qodly Studio** is to provide developers with a seamless, 100% web-based development experience. This platform empowers developers to:
- Design and modify data models that align with your business logic.
-- Effortlessly link data with [ORDA](../concepts/platform.md#the-orda-concept) dataclasses.
+- Effortlessly link data with [ORDA](../orda/data-model.md#the-orda-concept) dataclasses.
- Visually craft Pages by simply dragging and dropping components onto a canvas.
- Instantly preview web pages.
- Execute QodlyScript code directly within web events or qodlysource events.
@@ -31,10 +31,11 @@ Deployed Qodly applications are accessible on all popular web browsers, with no
## Accessing Qodly Studio
-Access to Qodly Studio is granted to developers once they complete a series of authentication steps to enter the Qodly Console, as outlined in the [Architecture chapter](../concepts/cloud.md). From the Development or Staging [environments](../cloud/getStarted.md#environments-and-services) within the Qodly Console, you can access your application instance in Qodly Studio by either:
+Access to Qodly Studio is granted to developers once they complete a series of authentication steps to enter the Qodly Cloud Management Console. From the Development or Staging [environment](../cloud/environmentsOverview.md) within the Qodly Console, you can access your application instance in Qodly Studio by either:
+
+- Clicking on the [Studio](../cloud/consoleOverview#accessing-the-studio) button on the Overview page.
+- Clicking on the [Studio URL](../cloud/resourceMonitoring#1-studio-url) in the General tab for the environment.
-- Clicking on the [Studio](../cloud/application-management#open-qodly-studio) button on the Overview page.
-- Clicking on the [Studio URL](../cloud/application-management#open-qodly-studio) in the General tab for the open environment.
diff --git a/docs/studio/pageLoaders/components/checkbox.md b/docs/studio/pageLoaders/components/checkbox.md
index 6f9adcb593..bda36cf42c 100644
--- a/docs/studio/pageLoaders/components/checkbox.md
+++ b/docs/studio/pageLoaders/components/checkbox.md
@@ -6,7 +6,6 @@ import Column from '@site/src/components/Column'
The **Checkbox** component is a UI element designed for binary selections. It consists of a small box that can be checked (selected) or unchecked (deselected) by the user.
-
:::info
The **Checkbox** component contains an embedded **Checkbox Input** and a **Label** element. This is of great importance as configuring the **Checkbox** component may require adjusting properties within the embedded elements. This applies to the visual style, triggers, and actions as they may differ.
@@ -115,152 +114,128 @@ Interacting with user input data is straightforward. When you bind a qodlysource
Subsequently, you can utilize this input value in various ways, such as within a standard action to initiate a search with matching attribute values.
-## Customizing Checkbox Styles
+## Customizing CheckBox Styles
The **Checkbox** component offers additional customization options through CSS, providing control over the appearance of checkbox elements.
-### Understanding Checkbox CSS Classes
+### Component-Specific Classes
+
+The following CSS classes are applied to various elements within the **CheckBox** component, defining their layout, style, and behavior. Each class can be customized to adjust the look and functionality of specific parts of the component.
+
+| **Class Name** | **Applies To** | **Description** |
+|------------------------------|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------|
+| `chakra-checkbox` | CheckBox wrapper | Provides base styling for the CheckBox wrapper, including layout and positioning. |
+| `chakra-checkbox__input` | Checkbox input | Applies default styling for the actual checkbox input element, usually hidden to allow the control to display instead. |
+| `chakra-checkbox__control` | Checkbox control indicator | Styles the visible checkbox control, which represents the checked or unchecked state of the component. |
+| `fd-label` | Label element | Styles the CheckBox label, including font size, color, and positioning relative to the checkbox input. |
-The Checkbox component supports various CSS classes that enable customization of the checkbox container, label, outline, and checkmark area. Below is a list of the supported CSS classes and their corresponding elements.
-| **Class Name** | **Applies To** | **Description** |
-|------------------|-------------------------------|--------------------------------------------|
-| `.chakra-checkbox` | The outline of the checkbox component | Applies styles to the outline of the checkbox component.|
-| `.chakra-checkbox__control` | The embedded checkmark area | Customizes the chechmark area within the checkbox element. |
+### Component-Specific Tags
-### Custom styling examples
+The following HTML tags make up the structure of the **CheckBox** component. Each tag can be styled to adjust its appearance, alignment, and user interaction.
-The following examples demonstrate how to customize the appearance of the Checkbox component.
+| **Tag Name** | **Applies To** | **Description** |
+|--------------|-----------------------------|----------------------------------------------------------------------------------------------------------------------------|
+| `` | Checkbox input field | The main checkbox where users select or deselect options. Styling the input affects borders, padding, and position, influencing how it appears alongside the label text. |
-#### Example 1 - Rounded Silver Outline
-This example customizes the outline of the checkbox component by using a rounded border in silver and a background color in white for contrast.
+### Example 1 - Overall CheckBox Style
+
+The `self .chakra-checkbox` selector targets the main CheckBox container, allowing customization of size, cursor behavior, and shadow effects.
-{`self {
- padding: 10px;
- width: 150px;
- box-shadow: 4px 4px 10px rgba(215, 218, 225, 0.9), 4px 4px 10px rgba(221, 221, 232, 0.9), 4px 4px 10px rgba(240, 240, 244, 0.9), 4px 4px 10px rgba(227, 227, 234, 0.9);
- font-family: 'Times New Roman', Times, serif;
- border-radius: 10px;
-}
+{`/* Main CheckBox container styling */
self .chakra-checkbox{
- background-color:white;
- margin-left: 60px;
- border-radius: 20px;
- border-color:silver;
- border-width: 3px;
-}
-` }
+ width: 2.8rem;
+ height: 2.8rem;
+ cursor: pointer;
+ border-radius: .5rem;
+ box-shadow: .3rem .3rem .6rem #c8d0e7, -.2rem -.2rem .5rem #FFFFFF;
+}`}
.default})
+ src={require('./img/checkbox__style1.png').default} style={{ borderRadius: '6px', display: 'block', margin: '0 auto' }}/>
-{`self {
- padding: 10px;
- width: 150px;
- box-shadow: 4px 4px 10px rgba(215, 218, 225, 0.9), 4px 4px 10px rgba(221, 221, 232, 0.9), 4px 4px 10px rgba(240, 240, 244, 0.9), 4px 4px 10px rgba(227, 227, 234, 0.9);
- font-family: 'Times New Roman', Times, serif;
- border-radius: 10px;
-}
+{`/* Check mark control styling */
self .chakra-checkbox__control{
- background-color:white;
- box-shadow: 4px 4px 10px rgba(215, 218, 225, 0.9), 4px 4px 10px rgba(221, 221, 232, 0.9), 4px 4px 10px rgba(240, 240, 244, 0.9), 4px 4px 10px rgba(227, 227, 234, 0.9);
- border-radius: 10px;
- border-color: silver;
- margin-left: 70px;
-}
-` }
+ font-size: 80%;
+ font-weight: 700;
+ color: #9baacf;
+ transition: .3s ease;
+ border: 0;
+ width: 100%;
+ height: 100%;
+}`}
.default})
+ src={require('./img/checkbox__style2.png').default} style={{ borderRadius: '6px', display: 'block', margin: '0 auto' }}/>
-{`self {
- padding: 10px;
- width: 150px;
- box-shadow: 4px 4px 10px rgba(215, 218, 225, 0.9), 4px 4px 10px rgba(221, 221, 232, 0.9), 4px 4px 10px rgba(240, 240, 244, 0.9), 4px 4px 10px rgba(227, 227, 234, 0.9);
- font-family: 'Times New Roman', Times, serif;
- border-radius: 10px;
-}
-self .chakra-checkbox__control:hover{
- background-color:grey;
- box-shadow: 4px 4px 10px rgba(215, 218, 225, 0.9), 4px 4px 10px rgba(221, 221, 232, 0.9), 4px 4px 10px rgba(240, 240, 244, 0.9), 4px 4px 10px rgba(227, 227, 234, 0.9);
- border-radius: 10px;
+{`/* Checked state styling */
+self .chakra-checkbox__control[data-checked]{
+ background: transparent;
+ box-shadow: inset .2rem .2rem .5rem #c8d0e7, inset -.2rem -.2rem .5rem #FFFFFF !important;
+ color: #6d5dfc;
}`}
.default})
+ src={require('./img/checkbox__style3.png').default} style={{ borderRadius: '6px', display: 'block', margin: '0 auto' }}/>
-{`
-self {
- padding: 10px;
- width: 150px;
- box-shadow: 4px 4px 10px rgba(215, 218, 225, 0.9), 4px 4px 10px rgba(221, 221, 232, 0.9), 4px 4px 10px rgba(240, 240, 244, 0.9), 4px 4px 10px rgba(227, 227, 234, 0.9);
- font-family: 'Times New Roman', Times, serif;
- border-radius: 10px;
-}
-self .chakra-checkbox__control[data-checked]{
- color:white;
- background-color:rgb(63, 17, 103);
- margin: 5px 5px 5px 5px;
- border-radius: 10px;
+{`/* Checked state styling */
+self .chakra-checkbox__control[data-checked]:hover{
+ color: white;
+ box-shadow: inset .2rem .2rem 1rem #5b0eeb, inset -.2rem -.2rem 1rem #8abdff !important;
}`}
.default})
+ src={require('./img/checkbox__style4.png').default} style={{ borderRadius: '6px', display: 'block', margin: '0 auto' }}/>
-
+
{`/* Create the empty stars */
self::before {
- content: "\\2606 \\2606 \\2606 \\2606 \\2606"; /* Unicode representation of empty star */
- color: #ccc;
+ content: "\\2606 \\2606 \\2606 \\2606 \\2606"; /* Unicode representation of empty star */
+ color: #ccc;
}
/* Hide the slider but keep functionality */
-self .fd-slidercontainer{
- position: absolute !important;
- opacity: 0;
- width: 130px;
- padding: 0;
+self .fd-slidercontainer {
+ position: absolute !important;
+ opacity: 0;
+ width: 130px;
+ padding: 0;
}
/* Fill the stars based on the 'aria-valuenow' attribute */
-self:has([aria-valuenow="1"])::before{
- content: "\\2605 \\2606 \\2606 \\2606 \\2606";
- color: #6d5dfc;
+self:has([aria-valuenow="1"])::before {
+ content: "\\2605 \\2606 \\2606 \\2606 \\2606";
+ color: #6d5dfc;
}
-self:has([aria-valuenow="2"])::before{
- content: "\\2605 \\2605 \\2606 \\2606 \\2606";
- color: #6d5dfc;
+self:has([aria-valuenow="2"])::before {
+ content: "\\2605 \\2605 \\2606 \\2606 \\2606";
+ color: #6d5dfc;
}
-self:has([aria-valuenow="3"])::before{
- content: "\\2605 \\2605 \\2605 \\2606 \\2606";
- color: #6d5dfc;
+self:has([aria-valuenow="3"])::before {
+ content: "\\2605 \\2605 \\2605 \\2606 \\2606";
+ color: #6d5dfc;
}
-self:has([aria-valuenow="4"])::before{
- content: "\\2605 \\2605 \\2605 \\2605 \\2606";
- color: #6d5dfc;
+self:has([aria-valuenow="4"])::before {
+ content: "\\2605 \\2605 \\2605 \\2605 \\2606";
+ color: #6d5dfc;
}
-self:has([aria-valuenow="5"])::before{
- content: "\\2605 \\2605 \\2605 \\2605 \\2605";
- color: #6d5dfc;
+self:has([aria-valuenow="5"])::before {
+ content: "\\2605 \\2605 \\2605 \\2605 \\2605";
+ color: #6d5dfc;
}`}
diff --git a/docs/studio/pageLoaders/components/textinput.md b/docs/studio/pageLoaders/components/textinput.md
index 8ec9cdb902..88f70ce507 100644
--- a/docs/studio/pageLoaders/components/textinput.md
+++ b/docs/studio/pageLoaders/components/textinput.md
@@ -321,12 +321,12 @@ self {
box-shadow: inset .2rem .2rem .5rem #c8d0e7, inset -.2rem -.2rem .5rem #FFFFFF;
background: none;
font-family: inherit;
- padding-left: 1.4rem;
+ padding-left: 1.4rem;
}
/* Input tag styling*/
self input{
- color: #9a8ff8;
- border: 0 !important;
+ color: #9a8ff8;
+ border: 0 !important;
}
/* Layout adjustment to display the first child element as a flex container */
self > :first-child{
diff --git a/docs/studio/pageLoaders/states/nonConditionalState.md b/docs/studio/pageLoaders/states/nonConditionalState.md
index 0dbb3f7221..1c50cb804f 100644
--- a/docs/studio/pageLoaders/states/nonConditionalState.md
+++ b/docs/studio/pageLoaders/states/nonConditionalState.md
@@ -244,7 +244,7 @@ To prevent any confusion between the editable and base states, the `Preview` but
:::info
-Remember that when previewing in the studio, you are on the WebAdmin port, so no privilege restrictions are applied (even if you have [Conditional states](./conditionalState.md) that reference privileges).
+Remember that when previewing in Qodly Studio, you are on the WebAdmin port, so no privilege restrictions are applied (even if you have [Conditional states](./conditionalState.md) that reference privileges).
:::
diff --git a/docs/studio/rendering.md b/docs/studio/rendering.md
index f3854eaf0f..aeec9ab5cb 100644
--- a/docs/studio/rendering.md
+++ b/docs/studio/rendering.md
@@ -23,7 +23,7 @@ In the case of Qodly Studio, rendering takes a different path compared to conven
- **Rendering Trigger**: Accessing the Page directly in a web browser is not an option. Instead, the Page is "**rendered**" when users initiate the rendering process, which can be done in one of two ways:
- - **Preview in the Studio**: Users have the option to [preview the Page within the Qodly Studio interface](#preview-in-the-studio).
+ - **Preview in Qodly Studio**: Users have the option to [preview the Page within Qodly Studio interface](#preview-in-the-studio).
- **Dedicated Browser Tab**: Alternatively, users can opt to [render the Page in a separate browser tab](#preview-in-a-browser-window).
@@ -48,7 +48,7 @@ Crucially, each Page is assigned a **unique URL** on the Qodly Web server. These
## Data Flow and Server Architecture
-The flow of data within the Qodly Studio ecosystem is carefully orchestrated, ensuring a seamless rendering experience:
+The flow of data within Qodly Studio ecosystem is carefully orchestrated, ensuring a seamless rendering experience:
.default})
@@ -61,18 +61,18 @@ The flow of data within the Qodly Studio ecosystem is carefully orchestrated, en
## Page Rendering Options
-Rendering a Page in Qodly Studio provides versatile control and accessibility. You can preview it in the Studio or a separate browser window, but It's important to note that:
+Rendering a Page in Qodly Studio provides versatile control and accessibility. You can preview it in Qodly Studio or a separate browser window, but It's important to note that:
:::info
Database resource access control depends on the chosen rendering method.
:::
-### Preview in the Studio
+### Preview in Qodly Studio
.default})
from the Explorer or the toolbar:
@@ -48,7 +48,7 @@ Show/hide helper tip icons .default})
+
Enables selection of a Page to serve as the application’s start page. This chosen Page will automatically render in the following situations:
- When the **Preview** button is clicked in the Page Editor, the Page opens in a new tab.
-- When the **Preview URL** area in the Qodly Cloud dashboard is clicked, the Page is displayed.
+- When the **Authenticated URL** area in the Qodly Cloud console is clicked, the Page is displayed.
### Default Display Mode
diff --git a/docusaurus.config.js b/docusaurus.config.js
index 9b62fb27c2..f37848e0c3 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -98,13 +98,13 @@ const config = {
alt: 'Qodly',
//src: 'img/qodly-logo-dark.svg',
//srcDark: 'img/qodly-logo-white.svg',
- src: 'img/Qodly-beta-D.png',
- srcDark: 'img/Qodly-beta-W.png',
+ src: 'img/qodly-light-version.svg',
+ srcDark: 'img/qodly-dark-version.svg',
},
items: [
{
type: 'doc',
- docId: 'concepts/quickstart',
+ docId: 'get-started/quickstart',
position: 'left',
label: 'Getting Started',
},
@@ -112,7 +112,7 @@ const config = {
type: 'doc',
docId: 'cloud/getStarted',
position: 'left',
- label: 'Dashboard',
+ label: 'console',
},*/
{
type: 'doc',
@@ -122,16 +122,10 @@ const config = {
},
{
type: 'doc',
- docId: 'cloud/getStarted',
+ docId: 'cloud/consoleOverview',
position: 'left',
label: 'Run & Manage',
},
- {
- type: 'doc',
- docId: 'concepts/platform',
- position: 'left',
- label: 'Architecture',
- },
{
type: 'doc',
docId: 'api/overview',
@@ -176,7 +170,7 @@ const config = {
},
{
label: "Release Notes",
- to: "notes/v1.0.0-beta.6",
+ to: "notes/1.0.0-beta.6",
},
],
},
diff --git a/package-lock.json b/package-lock.json
index 01991d1e8b..bb5eb5ddae 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -4463,9 +4463,9 @@
}
},
"node_modules/caniuse-lite": {
- "version": "1.0.30001542",
- "resolved": "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001542.tgz",
- "integrity": "sha512-UrtAXVcj1mvPBFQ4sKd38daP8dEcXXr5sQe6QNNinaPd0iA/cxg9/l3VrSdL73jgw5sKyuQ6jNgiKO12W3SsVA==",
+ "version": "1.0.30001680",
+ "resolved": "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001680.tgz",
+ "integrity": "sha512-rPQy70G6AGUMnbwS1z6Xg+RkHYPAi18ihs47GH0jcxIG7wArmPgY3XbS2sRdBbxJljp3thdT8BIqv9ccCypiPA==",
"funding": [
{
"type": "opencollective",
@@ -4479,7 +4479,8 @@
"type": "github",
"url": "https://github.com/sponsors/ai"
}
- ]
+ ],
+ "license": "CC-BY-4.0"
},
"node_modules/ccount": {
"version": "1.1.0",
@@ -16391,9 +16392,9 @@
}
},
"caniuse-lite": {
- "version": "1.0.30001542",
- "resolved": "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001542.tgz",
- "integrity": "sha512-UrtAXVcj1mvPBFQ4sKd38daP8dEcXXr5sQe6QNNinaPd0iA/cxg9/l3VrSdL73jgw5sKyuQ6jNgiKO12W3SsVA=="
+ "version": "1.0.30001680",
+ "resolved": "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001680.tgz",
+ "integrity": "sha512-rPQy70G6AGUMnbwS1z6Xg+RkHYPAi18ihs47GH0jcxIG7wArmPgY3XbS2sRdBbxJljp3thdT8BIqv9ccCypiPA=="
},
"ccount": {
"version": "1.1.0",
diff --git a/sidebars.js b/sidebars.js
index c8450d4b8c..16d96b5659 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -42,8 +42,46 @@ const sidebars = {
GetStarted: [
{
type: 'doc',
- id: 'concepts/quickstart',
- label: "Quickstart"
+ id: 'get-started/quickstart'
+ },
+ {
+ type: 'doc',
+ id: 'get-started/first-app'
+ },{
+ type: 'doc',
+ id: 'get-started/test-debug'
+ },
+ {
+ type: 'doc',
+ id: 'get-started/deployment'
+ },
+ {
+ type: 'doc',
+ id: 'get-started/data-management'
+ },
+ {
+ type: 'doc',
+ id: 'get-started/support'
+ },
+ {
+ type: 'doc',
+ id: 'get-started/updates'
+ },
+ {
+ type: 'doc',
+ id: 'get-started/community'
+ },
+ {
+ type: 'doc',
+ id: 'get-started/subscriptions'
+ },
+ {
+ type: 'doc',
+ id: 'get-started/payments'
+ },
+ {
+ type: 'doc',
+ id: 'get-started/refunds'
},
],
Develop: [
@@ -157,7 +195,10 @@ const sidebars = {
{
type: 'category',
label: 'Programming Guide',
- items: ['orda/data-model', 'orda/data', 'orda/queries',
+ items: [ 'orda/data-model',
+ 'orda/data',
+ 'orda/queries',
+ 'orda/sessions',
],
},
{
@@ -268,7 +309,6 @@ const sidebars = {
'language/commands/delayProcess',
'language/commands/deleteString',
'language/commands/ds',
- 'language/commands/equalPictures',
'language/commands/exp',
'language/commands/false',
'language/commands/file',
@@ -412,40 +452,30 @@ const sidebars = {
],
Run: [
+ 'cloud/consoleOverview',
{
- type: "doc",
- id: "cloud/getStarted",
- label: "Qodly Applications",
- },
- {
- type: "doc",
- id: "cloud/application-management",
- label: "Application Management",
- },
- {
- type: "doc",
- id: "cloud/api-key",
- label: "API Keys",
+ type: 'category',
+ label: 'Applications',
+ items: [
+ 'cloud/sandbox',
+ 'cloud/myApps',
+ ],
},
{
- type: "doc",
- id: "cloud/deployment",
- label: "Release Management and Deployment",
+ type: 'category',
+ label: 'Environments',
+ items: [
+ 'cloud/environmentsOverview',
+ 'cloud/resourceMonitoring',
+ 'cloud/apiKeys',
+ 'cloud/dataManagement',
+ 'cloud/deployManagement',
+ ],
},
+ 'cloud/billingSubscriptionManagement',
+ 'cloud/userAccountManagement',
],
- Architecture: [
- {
- type: 'doc',
- id: 'concepts/platform',
- label: "Platform Overview"
- },
- {
- type: 'doc',
- id: 'concepts/cloud',
- label: "Cloud Architecture"
- },
- ],
ReactComponent: [
{
type: 'doc',
@@ -535,13 +565,13 @@ const sidebars = {
label: 'Qodly Releases',
collapsed: false,
items: [
-
- 'notes/v1.0.0-beta.6',
- 'notes/v1.0.0-beta.5',
- 'notes/v1.0.0-beta.4',
- 'notes/v1.0.0-beta.3',
- 'notes/v1.0.0-beta.2',
- 'notes/v1.0.0-beta.1'
+ 'notes/1.0.0-beta.6',
+ 'notes/1.0.0-beta.5',
+ 'notes/1.0.0-beta.4',
+ 'notes/1.0.0-beta.3',
+ 'notes/1.0.0-beta.2',
+ 'notes/1.0.0-beta.1',
+ 'notes/1.0.0-beta.0'
],
},
],
diff --git a/src/components/HomepageFeatures/index.js b/src/components/HomepageFeatures/index.js
index d2e463e3d7..bf1d7ed6c5 100644
--- a/src/components/HomepageFeatures/index.js
+++ b/src/components/HomepageFeatures/index.js
@@ -14,7 +14,7 @@ const FeatureList = [
the application building world!
),
- link: "concepts/quickstart"
+ link: "get-started/quickstart"
},
{
title: 'Develop',
@@ -33,21 +33,21 @@ const FeatureList = [
description: (
<>
Launch and monitor your Qodly applications using a
- comprehensive console in our cloud infrastructure.
+ full-featured console in our cloud infrastructure.
),
- link: "cloud/getStarted"
+ link: "cloud/consoleOverview"
},
{
- title: 'Architecture',
- Svg: require('@site/static/img/q-architecture.svg').default,
+ title: 'REST API',
+ Svg: require('@site/static/img/q-dev.svg').default,
description: (
<>
- Explore the Qodly architecture, technologies,
- and main concepts.
+ Access your data from other applications
+ using the highly secured, comprehensive Qodly REST API.
),
- link: "concepts/platform"
+ link: "api/overview"
},
{
title: 'Custom Components',
diff --git a/src/pages/index.js b/src/pages/index.js
index 491a51876a..78c55f59c9 100644
--- a/src/pages/index.js
+++ b/src/pages/index.js
@@ -18,7 +18,7 @@ function HomepageHeader() {