[DOP-27545] fix title

Author: Anna Mikhaylova

mddocs/changelog.md

@@ -1,17 +1,3 @@
 # Changelog { #changelog }
 
-- [0.3.3 [UNRELEASED] (2025-09-30)][DRAFT]
-- [0.3.2 (2026-03-05)][0.3.2]
-- [0.3.1 (2026-01-15)][0.3.1]
-- [0.3.0 (2025-12-18)][0.3.0]
-- [0.2.5 (2025-10-10)][0.2.5]
-- [0.2.4 (2025-07-09)][0.2.4]
-- [0.2.3 (2025-04-11)][0.2.3]
-- [0.2.2 (2025-04-11)][0.2.2]
-- [0.2.1 (2025-04-07)][0.2.1]
-- [0.2.0 (2025-04-04)][0.2.0]
-- [0.1.5 (2024-04-22)][0.1.5]
-- [0.1.4 (2024-04-15)][0.1.4]
-- [0.1.3 (2024-04-15)][0.1.3]
-- [0.1.2 (2024-04-15)][0.1.2]
-- [0.1.1 (2024-03-29)][0.1.1]
+!include(../../changelog/index.md)

mddocs/changelog/0.3.0.md

@@ -62,8 +62,7 @@ auth:
 
 ### Example config.yml
 
-```yaml
-config.yml:
+```yaml title="config.yml"
 worker:
   spark_session_default_config:
   spark.master: local

mddocs/reference/frontend/configuration.md

@@ -2,10 +2,11 @@
 
 ## API url
 
-SyncMaster UI requires REST API to be accessible from browser. API url is set up using environment variable:
+SyncMaster UI requires REST API to be accessible from browser. API url is set up using config file:
 
-```bash
-SYNCMASTER__UI__API_BROWSER_URL=http://localhost:8000
+```yaml title="config.yml"
+ui:
+   api_browser_url: http://localhost:8000
 ```
 
 If both REST API and frontend are served on the same domain (e.g. through Nginx reverse proxy), for example:
@@ -15,6 +16,18 @@ If both REST API and frontend are served on the same domain (e.g. through Nginx
 
 Then you can use relative path:
 
-```bash
-SYNCMASTER__UI__API_BROWSER_URL=/api
+```yaml title="config.yml"
+ui:
+   api_browser_url: /api
+```
+
+## Auth provider
+
+By default, SyncMaster UI shows login page with username & password fields, designed for [server-auth-dummy][server-auth-dummy].
+To show a login page for [keycloak-auth-provider][keycloak-auth-provider], you should set config option:
+
+```yaml title="config.yml"
+ui:
+   auth_provider: keycloakAuthProvider
+   # auth_provider: dummyAuthProvider
 ```

mddocs/reference/server/configuration/debug.md

@@ -54,7 +54,7 @@ This is done by adding a specific filter to logging settings:
 
 ### `config.yml`
 
-```yaml
+```yaml title="config.yml"
 logging:
     filters:
         correlation_id:

mddocs/reference/server/manage_superusers_cli.md

@@ -9,17 +9,17 @@ There are two ways to manage users:
 
   Usernames can be passed via config file:
 
-  ```yaml title="config.yml"
-      superusers:
-        - user1
-        - user2
-  ```
+```yaml title="config.yml"
+superusers:
+  - user1
+  - user2
+```
 
   Or via environment variable:
 
-  ```bash
-    export 'SYNCMASTER__SUPERUSERS=["user1", "user2"]'
-  ```
+```bash
+export 'SYNCMASTER__SUPERUSERS=["user1", "user2"]'
+```
 
 - manual via CLI:
 <!-- TODO: fix docstring extraction -->

mddocs/reference/worker/create_spark_session.md

@@ -8,7 +8,7 @@ By default, SparkSession is created with ``spark.master: local``, including all
 
 It is possible to alter default [Spark Session configuration](https://spark.apache.org/docs/latest/configuration.html)_ worker settings:
 
-```yaml
+```yaml title="config.yaml"
 worker:
     spark_session_default_config:
         spark.master: local
@@ -20,7 +20,7 @@ worker:
 
 For example, to use SyncMaster on Spark-on-K8s, you can use worker image for Spark executor containers:
 
-```yaml
+```yaml title="config.yaml"
 worker:
     spark_session_default_config:
         spark.master: k8s://https://kubernetes.default.svc
@@ -41,7 +41,7 @@ worker:
 
 It is also possible to use custom function which returns ``SparkSession`` object:
 
-```yaml
+```yaml title="config.yaml"
 worker:
     create_spark_session_function: my_worker.spark.create_custom_spark_session
 ```
@@ -60,8 +60,8 @@ def create_custom_spark_session(
     target: ConnectionDTO,
     settings: WorkerSettings,
 ) -> SparkSession:
-# any custom code returning SparkSession object
-return SparkSession.builde.config(...).getOrCreate()
+    # any custom code returning SparkSession object
+      return SparkSession.builde.config(...).getOrCreate()
 ```
 
 Module with custom function should be placed into the same Docker image or Python virtual environment used by SyncMaster worker.

mddocs/reference/worker/log_url.md

@@ -6,7 +6,7 @@ This log URL might point to an Elastic instance or another logging tool such as
 The log URL is generated based on a template configured in the configuration.
 The configuration parameter is:
 
-```yaml
+```yaml title="config.yaml"
     worker:
         log_url_template: https://grafana.example.com?correlation_id={{ correlation_id }}&run_id={{ run.id }}
 ```