wip

Author: TizianoT

sqlite-cloud/platform/analyzer.mdx

@@ -12,16 +12,19 @@ import applyAnalyzer from '@docs-website-assets/introduction/video/dashboard_ana
 
 The Analyzer panel is a powerful tool that collects and categorizes all the queries executed on your cluster based on their execution time. It allows for intelligent and proactive analysis, and provides recommendations on which indexes to use to optimize frequently used queries.
 
-<VideoPlayer src={enableAnalyzer} />
+---
 
-By default, the Analyzer is turned off to avoid a small performance penalty. However, you can enable it by accessing the Settings button and setting the `query_analyzer_enabled` flag to 1, then pressing Save. You can also adjust the `query_analyzer_threshold` flag to set the minimum threshold query time (in milliseconds) that triggers a query to be included in the Analyzer. If the default value is too low, it's recommended to increase it to avoid having too many queries included in the panel.
+## Getting Started
 
+By default, the Analyzer is turned off to avoid a small performance penalty. However, you can enable it by accessing the Settings button and setting the `query_analyzer_enabled` flag to 1, then pressing Save. You can also adjust the `query_analyzer_threshold` flag to set the minimum threshold query time (in milliseconds) that triggers a query to be included in the Analyzer. If the default value is too low, it's recommended to increase it to avoid having too many queries included in the panel.
+<VideoPlayer src={enableAnalyzer} />
 
 
+----
 ## Testing the Analyzer
+To test the Analyzer, we can go to the `Studio -> chinook.sqlite -> SQL Console` section and perform a query that filters the non-indexed Composer column of the Track table with the following statement: `SELECT * FROM Tracks WHERE Composer = 'AC/DC'`;
 <VideoPlayer src={applyAnalyzer} />
 
-To test the Analyzer, we can go to the `Studio -> chinook.sqlite -> SQL Console` section and perform a query that filters the non-indexed Composer column of the Track table with the following statement: `SELECT * FROM Tracks WHERE Composer = 'AC/DC'`;
 
 
 Once we have executed this query, we can go back to the Analyzer panel and see that it has been successfully analyzed by the **nxidiwbuhz** node. 

sqlite-cloud/platform/backups.mdx

@@ -10,11 +10,12 @@ import VideoPlayer from '@commons-components/Video/VideoPlayer.astro';
 import enableDisableBackup from '@docs-website-assets/introduction/video/dashboard_enable_disable_backup.mp4';
 import restoreBackup from '@docs-website-assets/introduction/video/dashboard_restore_backup.mp4';
 
-## Overview
 Backups provide a robust solution for mitigating data loss and resolving data corruption issues. Backups are available for databases in all [Dev, Pro and Startup](https://www.sqlitecloud.io/pricing) projects.
 
 SQLite Cloud creates a full snapshot backup of your data once a day, and stores incremental changes once per second, on commodity object storage.
 
+---- 
+
 ## Features
 
 #### Automated Backups
@@ -24,13 +25,16 @@ SQLite Cloud creates a full snapshot backup of your data once a day, and stores
 - **Easy Restoration Process**: Restoring from a backup automatically overwrites the existing database, seamlessly reverting it to the desired state without additional configuration.
 - **Consistency and Reliability**: After restoration, the database functions as it did at the chosen point in time, ensuring operational continuity.
 
+
+---
+
 ## Getting Started
 Setting up and managing backups in SQLite Cloud is designed to be straightforward, allowing you to implement robust data protection strategies effortlessly.
 
 <VideoPlayer src={enableDisableBackup} />
 
-
-### Restoring from a Backup
+---
+## Restoring from a Backup
 
 Click on a backup to begin the restore process. Select Yes to confirm the restoration, and your database will be restored to the selected point in time.
 

sqlite-cloud/platform/edge-functions.mdx

@@ -18,6 +18,8 @@ Edge functions can be called remotely over HTTP or Websockets via API, or trigge
 
 Turning on linearizable reads ensures strong consistency, but may introduce some latency. When eventual consistency is sufficient, we recommend leaving linearizable reads off.
 
+---
+
 ## Getting Started
 
 Use the **Edge Functions panel**  to effortlessly create, deploy, and test Edge Functions directly in the SQLite Cloud dashboard.  
@@ -67,6 +69,7 @@ Edge functions can be called via HTTP GET and POST methods. You can pass additio
 - Query parameters: Accessible via `request.params`
 - Request body: Accessible via `request.data`
 
+---
 
 ## Guides
 ### Interacting with your Database
@@ -102,6 +105,9 @@ You can also add environment variables in the UI by navigating to the "Environme
 ### Handling Errors
 In case of error we return an HTTP error code and a JSON with the error message. Manually throwing an error in your code results in a 500 response. You may also return an error. 
 
+
+--- 
+
 ## Examples
 
 ### Assigning and Notifying a Support Rep on User Sign up

sqlite-cloud/platform/offsync.mdx

@@ -11,14 +11,15 @@ import enableSync from '@docs-website-assets/introduction/video/dashboard_sqlite
 import connectionUrlSync from '@docs-website-assets/introduction/video/dashboard_sync_connection_url.mp4';
 import devicesSync from '@docs-website-assets/introduction/video/dashboard_sync_devices.mp4';
 
-
-
 import Callout from "@commons-components/Information/Callout.astro";
 
 OffSync is a powerful SQLite Cloud feature that enables true **local-first** data synchronization for your applications. Powered by the [SQLite Sync](https://github.com/sqliteai/sqlite-sync) extension, it allows you to build robust, offline-capable applications where data is stored and processed on edge devices and seamlessly synchronized with a central SQLite Cloud database.
 
 This architecture is ideal for mobile apps, IoT devices, and any application requiring high availability and low latency, even with intermittent network connectivity. By leveraging Conflict-free Replicated Data Types (CRDTs), OffSync ensures that changes made offline are merged automatically and without conflicts when the device reconnects.
 
+
+---
+
 ## How It Works
 
 OffSync extends standard SQLite tables with built-in support for offline work and automatic synchronization. This allows multiple devices to operate independently and then seamlessly merge their changes.
@@ -29,26 +30,29 @@ OffSync extends standard SQLite tables with built-in support for offline work an
 
 When combined with [Row-Level Security (RLS)](/docs/rls), OffSync allows you to build secure, multi-tenant applications where each user's data is safely isolated, both on the edge and in the cloud.
 
+
+--- 
+
 ## Configuring OffSync
 
 You can enable and manage OffSync for your databases directly from the SQLite Cloud dashboard.  
 Below are the main steps:
 
-### 1. Enable Tables for Synchronization
+### Enable Tables for Synchronization
 From the **Sync Tables** tab, select which tables in your database you want to keep synchronized.  
 Once enabled, all changes to those tables will automatically sync with connected devices.
 
 <VideoPlayer src={enableSync} />
 
 
-### 2. Get the Connection String
+### Get the Connection String
 In the **Configuration** tab, copy the connection string.  
 Use this in your application to initialize OffSync and connect your local SQLite database with SQLite Cloud.
 
 <VideoPlayer src={connectionUrlSync} />
 
 
-### 3. Manage Connected Devices
+### Manage Connected Devices
 In the **Devices** tab, you can view all devices currently connected to your database.  
 Here you can check their sync status and remove devices if needed.
 

sqlite-cloud/platform/rls.mdx

@@ -10,8 +10,6 @@ import VideoPlayer from '@commons-components/Video/VideoPlayer.astro';
 import rlsEnable from '@docs-website-assets/introduction/video/dashboard_rls_enable.mp4';
 import rlsTest from '@docs-website-assets/introduction/video/dashboard_rls_test.mp4';
 
-
-
 import Callout from "@commons-components/Information/Callout.astro";
 
 Row-Level Security (RLS) allows you to define fine-grained access control policies that determine which rows in a table a user can access. This ensures that users can only view or modify data they are authorized to see, enhancing data security and privacy.
@@ -24,6 +22,8 @@ RLS is a powerful feature for building secure, multi-tenant applications. When c
 
 This architecture simplifies development by allowing your application to interact with a local database while SQLite Cloud [OffSync](/docs/offsync) transparently handles the synchronization with a central database. RLS ensures that each user's data is securely isolated during this process. The centralized database can then be used for powerful business analytics and reporting across all tenants, without compromising individual data privacy.
 
+---
+
 ## Policy Enforcement
 
 RLS in SQLite Cloud operates based on the following principles:
@@ -40,6 +40,8 @@ To make data accessible to token-authenticated users, you must both enable RLS f
 
 Otherwise, they will be blocked from accessing any rows.
 
+---
+
 ## Configuring RLS
 
 You can configure RLS policies for your databases through the SQLite Cloud dashboard.
@@ -62,7 +64,31 @@ You can configure RLS policies for your databases through the SQLite Cloud dashb
     The SQL expressions can be any valid SQLite expression that returns a boolean value. You can use built-in SQLite functions, and even custom functions to define your policies.
     </Callout>
 
+### User Information Functions
+
+To help you create dynamic RLS policies, SQLite Cloud provides two functions to retrieve information about the current authenticated user:
+
+- `auth_userid()`: Returns the `userid` of the current token-authenticated user.
+- `auth_json()`: Returns a JSON object with all the details of the current token-authenticated user, including `user_id`, `name`, `attributes`, `created_at`, and `expires_at`.
+
+These functions are particularly useful for creating policies that are based on user attributes.
+
+For more information on Access Tokens, see the [Access Tokens documentation](/docs/access-tokens). The API Documentation for the Access Tokens API can be found in the Weblite section in the [Dashboard](https://dashboard.sqlitecloud.io/).
+
+### OLD and NEW References
+
+Your RLS policies for `INSERT`, `UPDATE`, and `DELETE` operations can reference column values as they are being changed. This is done using the special `OLD.column` and `NEW.column` identifiers. Their availability and meaning depend on the operation being performed:
+
+| Operation | `OLD.column` Reference | `NEW.column` Reference |
+| :--- | :--- | :--- |
+| `INSERT` | Not available | The value for the new row. |
+| `UPDATE` | The value of the row *before* the update. | The value of the row *after* the update. |
+| `DELETE` | The value of the row being deleted. | Not available |
+
+---
+
 ## Testing RLS
+
 <VideoPlayer src={rlsTest} />
 
 To verify that your Row-Level Security (RLS) policies work as expected, you can use the **Test RLS** feature in the dashboard:
@@ -87,26 +113,10 @@ To verify that your Row-Level Security (RLS) policies work as expected, you can
    - By switching back to **Database Studio**, you can see all rows in the table without RLS filters.  
    - This allows you to compare the filtered view (via token) with the complete dataset and confirm that your policies are correctly enforced.
 
-### User Information Functions
 
-To help you create dynamic RLS policies, SQLite Cloud provides two functions to retrieve information about the current authenticated user:
 
-- `auth_userid()`: Returns the `userid` of the current token-authenticated user.
-- `auth_json()`: Returns a JSON object with all the details of the current token-authenticated user, including `user_id`, `name`, `attributes`, `created_at`, and `expires_at`.
-
-These functions are particularly useful for creating policies that are based on user attributes.
-
-For more information on Access Tokens, see the [Access Tokens documentation](/docs/access-tokens). The API Documentation for the Access Tokens API can be found in the Weblite section in the [Dashboard](https://dashboard.sqlitecloud.io/).
 
-### OLD and NEW References
-
-Your RLS policies for `INSERT`, `UPDATE`, and `DELETE` operations can reference column values as they are being changed. This is done using the special `OLD.column` and `NEW.column` identifiers. Their availability and meaning depend on the operation being performed:
-
-| Operation | `OLD.column` Reference | `NEW.column` Reference |
-| :--- | :--- | :--- |
-| `INSERT` | Not available | The value for the new row. |
-| `UPDATE` | The value of the row *before* the update. | The value of the row *after* the update. |
-| `DELETE` | The value of the row being deleted. | Not available |
+---
 
 ## Example
 
@@ -245,7 +255,10 @@ OLD.status <> 'paid'
 **Explanation:**
 This policy uses the `OLD` reference to check the value of the `status` column *before* the update is applied. If the status is already `'paid'`, the condition `OLD.status <> 'paid'` will be false, and the `UPDATE` operation will be denied. This effectively makes paid invoices read-only.
 
-### Advanced: RLS and SQLite Sync
+
+--- 
+
+## Advanced: RLS and SQLite Sync
 
 When using RLS in conjunction with [SQLite Sync](https://github.com/sqliteai/sqlite-sync), it's important to understand how they interact. The Sync protocol applies changes on a column-by-column basis, which can affect how `INSERT` and `UPDATE` policies are evaluated.
 

sqlite-cloud/platform/security.mdx

@@ -15,6 +15,8 @@ To add new users to your cluster, simply click on the **Create User** button.
 
 Once a user is successfully created, you can assign one or more roles to them to determine their level of access to the system.
 
+---
+
 ## Roles
 In SQLite Cloud, a role is a set of permissions that allows a user to perform specific actions on a particular resource, such as a database or table. Users can have multiple roles, which determine their access to the system.
 
@@ -29,7 +31,7 @@ There are two types of roles in SQLite Cloud:
 
 ![Dashboard Roles](@docs-website-assets/introduction/dashboard_roles.png)
 
-## Built-in roles
+### Built-in roles
 import Callout from "@commons-components/Information/Callout.astro"; 
 
 SQLite Cloud offers a comprehensive system of built-in roles designed to provide essential privileges within a database framework. These roles can be assigned using the [GRANT ROLE](https://docs.sqlitecloud.io/docs/role-commands) command, and custom roles can be created with the [CREATE ROLE](https://docs.sqlitecloud.io/docs/role-commands) command. Privileges represent fundamental operations that can be executed on specific databases or tables and can be granted, revoked, or assigned to specific roles.

sqlite-cloud/platform/webhooks.mdx

@@ -11,6 +11,10 @@ import webhooksEdgeFunction from '@docs-website-assets/introduction/video/dashbo
 
 **Webhooks** are HTTP callbacks that allow your applications to receive real-time notifications when specific events occur. In the context of SQLite Cloud, webhooks make it easy to build reactive systems by automatically sending notifications when data changes happen within your databases.
 
+
+---
+
+
 ## Real-Time Notifications for Database Writes
 
 
@@ -20,7 +24,7 @@ For example, you can configure SQLite Cloud to notify a [webhook.site](https://w
 
 <VideoPlayer src={webhooksUrl} />
 
-
+---
 
 ## Change Data Capture
 
@@ -64,12 +68,15 @@ This enables seamless integration with logging systems, monitoring dashboards, o
 * **data** – The values corresponding to the affected row(s).
 * **webhook** – Metadata about the webhook itself, including its unique `id`, target `action` (URL or Edge Function), and configuration `options`.
 
+---
+
 ## Security
 
 Upon creation, each webhook is assigned a **secret key** used to verify the authenticity of incoming requests.
 
 ![Dashboard Projects](@docs-website-assets/introduction/dashboard_webhook_secret.png)
 
+---
 
 ## Trigger Edge Functions