[update] update info for new methods

Author: AlexKlimenkov

data/api/gantt_adjusttaskheightforbaselines.md

@@ -1,21 +1,24 @@
 adjustTaskHeightForBaselines
 =============
 
+@short: adjusts the task's row height for proper display of baseline elements
 
-@todo:
-	check the autogenerated stub
-
-@short:
-	
-
-@params:
-
-
-
-
+@params: 
+- task (*object*) - the task object whose `row_height` will be adjusted
 
 @example:
+const task = gantt.getTask(taskId);
+gantt.adjustTaskHeightForBaselines(task);
+gantt.render();
 
-@template:	api_method
+@template: api_method
 @descr:
+This method modifies the [`row_height`](desktop/resizing_rows.md) value of the provided task to ensure correct display of baseline elements. 
+
+Typically, there is no need to call this method directly. It is necessary only when you dynamically modify the display settings of the [gantt.config.baselines](api/gantt_baselines_config.md) config.
+
+@relatedapi:
+api/gantt_baselines_config.md
 
+@relatedsample:
+04_customization/15_baselines.html

data/api/gantt_baseline_text_template.md

@@ -1,18 +1,27 @@
 baseline_text
 =============
 
-@todo:
-	check the autogenerated stub
+@short: specifies the text displayed inside the baseline element
 
-
-@short:
-	
-
-@type:
+@params:
+- **task** (*Task*) - the task object associated with the baseline
+- **baseline** (*object*) - the baseline object
+- **index** (*number*) - the index of the baseline in the task's baselines array
 
 @example:
+gantt.templates.baseline_text = function(task, baseline, index) {
+    return "Baseline #" + (index + 1);
+};
+
+@template: api_template
+@returns:
+- **text** (*string*) - the HTML content to be injected as the innerHTML of the baseline element. The default template returns an empty string.
 
-@template:	api_template
 @descr:
 
 
+@relatedapi:
+api/gantt_baselines_config.md
+
+@relatedsample:
+04_customization/15_baselines.html

data/api/gantt_baselines_config.md

@@ -1,18 +1,37 @@
 baselines
 =============
 
-@todo:
-	check the autogenerated stub
+@short: configures the functionality of baselines in the Gantt chart
 
+@type: object | boolean
 
-@short:
-	
 
-@type: 
 @example:
-
-
-@template:	api_config
+gantt.config.baselines = {
+  datastore: "baselines",
+  render_mode: false,
+  dataprocessor_baselines: false,
+  row_height: 16,
+  bar_height: 8
+};
+gantt.init("gantt_here");
+
+@template: api_config
 @descr:
-
-
+This config defines how baselines are handled and displayed in the Gantt chart. It can be set as an object to customize the display or as a boolean to enable or disable the feature. The object configuration contains the following properties:
+
+- **datastore** (*string*) - the name of the datastore used for storing baseline entries. For related functionality, see the `getDatastore` method.
+- **render_mode** (*boolean | string*) - determines how baselines are displayed:
+  - `false` - baselines are not shown.
+  - `"taskRow"` - baselines are displayed in the same row as the task bar.
+  - `"separateRow"` - baselines are shown in a separate subrow, expanding the task row height.
+  - `"individualRow"` - each baseline is displayed in its own subrow beneath the task.
+- **dataprocessor_baselines** (*boolean*) - specifies whether baseline updates trigger the DataProcessor as individual entries.
+- **row_height** (*number*) - defines the height of the subrow for baselines, applicable only when `render_mode` is set to `"separateRow"` or `"individualRow"`.
+- **bar_height** (*number*) - sets the height of the baseline bar.
+
+@relatedapi:
+api/gantt_getdatastore.md
+
+@relatedsample:
+04_customization/15_baselines.html

data/api/gantt_deadlines_config.md

@@ -1,18 +1,17 @@
 deadlines
 =============
 
-@todo:
-	check the autogenerated stub
+@short: enables or disables the display of deadline elements for tasks
 
-
-@short:
-	
-
-@type: 
+@type: boolean
+@default: true
 @example:
+gantt.config.deadlines = true;
+gantt.init("gantt_here");
 
-
-@template:	api_config
+@template: api_config
 @descr:
+This config enables or disables the display of deadline elements for tasks. If enabled, Gantt will check the `task.deadline` property, and if it contains a valid date, the deadline element will be displayed in the timeline.
 
-
+@relatedsample:
+04_customization/14_deadline.html

data/api/gantt_link_radius_config.md

@@ -1,18 +1,18 @@
 link_radius
 =============
 
-@todo:
-	check the autogenerated stub
+@short: sets the radius for rounding corners of link lines in the timeline
 
-
-@short:
-	
-
-@type: 
+@default: 4
+@type: number
 @example:
+gantt.config.link_radius = 6;
+gantt.init("gantt_here");
 
-
-@template:	api_config
+@template: api_config
 @descr:
+The property defines the radius for rounding the corners of link lines in the timeline. If the value is less than or equal to 1, rounding is disabled. If a link segment's length is not sufficient for the specified radius, rounding will not be applied to that segment.
 
-
+@relatedapi:
+api/gantt_link_line_width_config.md
+api/gantt_link_arrow_size_config.md

data/api/gantt_onafterselect_event.md

@@ -1,14 +1,20 @@
 Manually Scheduled Summary Tasks
 ===============================
 
-There is a possibility to schedule summary tasks manually. This feature serves to outline project phases before all subtasks are detailed, 
+There is a possibility to schedule [projects](desktop/task_types.md) (summary tasks) manually. This feature serves to outline project phases before all subtasks are detailed, 
  providing a framework for your project timeline. 
 
 By default, summary tasks automatically calculate their dates based on the earliest start and latest end dates of their subtasks. 
 You can also set fixed start and end dates for summary tasks independently of their subtasks. As a result, the Gantt chart will display both the fixed duration 
 and the duration derived from subtasks.
 
-To activate this feature for a summary task, set the api/gantt_auto_scheduling_config.md property to *false*. The fixed dates are stored in **task.start_date** and 
+{{sample
+ 04_customization/25_project_dates.html
+}}
+
+To activate this feature for a summary task, set the api/gantt_auto_scheduling_config.md property to *false*. 
+
+The fixed dates are stored in **task.start_date** and 
 **task.end_date**, while the computed dates from subtasks are available in **task.$auto_start_date** and **task.$auto_end_date**.
 
 ~~~js
@@ -20,7 +26,7 @@ gantt.parse({
       type: "project",
       start_date: "2025-05-01 00:00:00",
       duration: 15,
-      auto_scheduling: false
+      auto_scheduling: false /* ! */
     },
     // ...
   ],

data/desktop/custom_projects_dates.md

@@ -44,6 +44,20 @@ The returned stack is an array of the undo user actions. Each user action contai
 - **_value_** - (*object*) the changed task/link object 
 - **_oldValue_** - (*object*) the task/link object before changes
 
+###setUndoStack() / setRedoStack()
+
+- <span class=submethod>**setUndoStack (stack: UndoRedoAction[]) **</span> - sets the stack of stored undo user actions
+
+~~~js
+gantt.ext.undo.setUndoStack(stack);
+~~~
+
+- <span class=submethod>**setRedoStack (stack: UndoRedoAction[]) **</span> - sets the stack of stored redo user actions
+
+~~~js
+gantt.ext.undo.setRedoStack(stack);
+~~~
+
 ###clearUndoStack() / clearRedoStack()
 
 - <span class=submethod>**clearUndoStack (): void**</span> - clears the stack of stored undo commands

data/desktop/undo_ext.md

@@ -10,6 +10,7 @@ Start
 		<li><a href="desktop/custom_skins.md">Skins customization with CSS variables</a></li>  
         <li><a href="desktop/skins.md#darkskin">New Dark skin</a></li>      
         <li><a href="desktop/baselines.md">Built-in support for Baselines</a></li>    
+        <li><a href="desktop/custom_projects_dates.md">Manually Scheduled Projects</a></li>    
 	</ul>
 
     <p class='action_buttons'>

data/index.md

@@ -28,7 +28,7 @@ The v9.0 update introduces several breaking changes.
 
 ### Skins switched to CSS variables
 
-CSS skins (themes) have been completely reworked and now utilize CSS variables. While the HTML structure of the component and CSS class names have mostly remained unchanged, CSS styles written for older versions of the Gantt are likely no longer effective with v9.0.
+CSS skins (themes) have been completely reworked and now utilize CSS variables. While the HTML structure of the component and CSS class names have mostly remained unchanged, CSS styles written for older versions of the Gantt may no longer work as intended with v9.0.
 
 For example, the following style was used to color tasks depending on their priority:
 
@@ -95,7 +95,7 @@ Starting from v9.0, the same effect is achieved with the following style:
 Check the available variables on the desktop/custom_skins.md page.
 
 {{note
-Migration will require the rewriting of existing CSS to achieve the required design.
+Migration will likely require updating of existing CSS to achieve the required design.
 }}
 
 ### Single CSS file