Merge branch 'main' of https://github.com/ClickHouse/clickhouse-docs into autogen_arithmetic_functions

Author: Blargian

contribute/style-guide.md

@@ -376,3 +376,20 @@ logic might fail.
 1. Keep version strings in consistent formats for predictable results.
 
 2. Use simplified version parameters in URLs (e.g., `v08` instead of `v0.8.x`).
+
+## Related blog component
+
+Pages can show a "Related blogs" component which displays recent blogs which are
+related to the keywords or title of the document.
+
+If you would like to show it on a page, add the following property to the 
+front matter:
+
+```yaml
+---
+show_related_blogs: true
+---
+```
+
+This will show it on the page, assuming there is a matching blog. If there is no
+match then it remains hidden.

docs/about-us/distinctive-features.md

@@ -4,6 +4,7 @@ sidebar_label: 'Why is ClickHouse unique?'
 sidebar_position: 50
 description: 'Understand what makes ClickHouse stand apart from other database management systems'
 title: 'Distinctive Features of ClickHouse'
+keywords: ['compression', 'secondary-indexes','column-oriented']
 ---
 
 # Distinctive Features of ClickHouse

docs/best-practices/avoid_mutations.md

@@ -1,9 +1,10 @@
 ---
 slug: /best-practices/avoid-mutations
 sidebar_position: 10
-sidebar_label: 'Avoid Mutations'
-title: 'Avoid Mutations'
+sidebar_label: 'Avoid mutations'
+title: 'Avoid mutations'
 description: 'Page describing why to avoid mutations in ClickHouse'
+keywords: ['mutations']
 ---
 
 import Content from '@site/docs/best-practices/_snippets/_avoid_mutations.md';

docs/best-practices/avoid_optimize_final.md

@@ -2,8 +2,9 @@
 slug: /best-practices/avoid-optimize-final
 sidebar_position: 10
 sidebar_label: 'Avoid Optimize Final'
-title: 'Avoid Optimize Final'
-description: 'Page describing why to avoid Optimize Final in ClickHouse'
+title: 'Avoid OPTIMIZE FINAL'
+description: 'Page describing why you should avoid the OPTIMIZE FINAL clause in ClickHouse'
+keywords: ['avoid OPTIMIZE FINAL', 'background merges']
 ---
 
 import Content from '@site/docs/best-practices/_snippets/_avoid_optimize_final.md';

docs/best-practices/choosing_a_primary_key.md

@@ -4,6 +4,8 @@ sidebar_position: 10
 sidebar_label: 'Choosing a Primary Key'
 title: 'Choosing a Primary Key'
 description: 'Page describing how to choose a primary key in ClickHouse'
+keywords: ['primary key']
+show_related_blogs: true
 ---
 
 import Image from '@theme/IdealImage';

docs/best-practices/json_type.md

@@ -4,6 +4,8 @@ sidebar_position: 10
 sidebar_label: 'Using JSON'
 title: 'Use JSON where appropriate'
 description: 'Page describing when to use JSON'
+keywords: ['JSON']
+show_related_blogs: true
 ---
 
 ClickHouse now offers a native JSON column type designed for semi-structured and dynamic data. It's important to clarify that **this is a column type, not a data format**—you can insert JSON into ClickHouse as a string or via supported formats like [JSONEachRow](/docs/interfaces/formats/JSONEachRow), but that does not imply using the JSON column type. Users should only use the JSON type when the structure of their data is dynamic, not when they simply happen to store JSON.

docs/best-practices/minimize_optimize_joins.md

@@ -2,15 +2,15 @@
 slug: /best-practices/minimize-optimize-joins
 sidebar_position: 10
 sidebar_label: 'Minimize and Optimize JOINs'
-title: 'Minimize and Optimize JOINs'
+title: 'Minimize and optimize JOINs'
 description: 'Page describing best practices for JOINs'
+keywords: ['JOIN', 'Parallel Hash JOIN']
+show_related_blogs: true
 ---
 
 import Image from '@theme/IdealImage';
 import joins from '@site/static/images/bestpractices/joins-speed-memory.png';
 
-
-
 ClickHouse supports a wide variety of JOIN types and algorithms, and JOIN performance has improved significantly in recent releases. However, JOINs are inherently more expensive than querying from a single, denormalized table. Denormalization shifts computational work from query time to insert or pre-processing time, which often results in significantly lower latency at runtime. For real-time or latency-sensitive analytical queries, **denormalization is strongly recommended**.
 
 In general, denormalize when:

docs/best-practices/partitioning_keys.mdx

@@ -4,6 +4,7 @@ sidebar_position: 10
 sidebar_label: 'Choosing a Partitioning Key'
 title: 'Choosing a Partitioning Key'
 description: 'Page describing how to choose a partitioning key'
+keywords: ['partitioning key']
 ---
 
 import Image from '@theme/IdealImage';

docs/best-practices/select_data_type.md

@@ -1,9 +1,10 @@
 ---
 slug: /best-practices/select-data-types
 sidebar_position: 10
-sidebar_label: 'Select Data Types'
-title: 'Select Data Types'
+sidebar_label: 'Selecting data Types'
+title: 'Selecting data Types'
 description: 'Page describing how to choose data types in ClickHouse'
+keywords: ['data types']
 ---
 
 import NullableColumns from '@site/docs/best-practices/_snippets/_avoid_nullable_columns.md';

docs/best-practices/selecting_an_insert_strategy.md

@@ -1,9 +1,11 @@
 ---
 slug: /best-practices/selecting-an-insert-strategy
 sidebar_position: 10
-sidebar_label: 'Selecting an Insert Strategy'
-title: 'Selecting an Insert Strategy'
+sidebar_label: 'Selecting an insert strategy'
+title: 'Selecting an insert strategy'
 description: 'Page describing how to choose an insert strategy in ClickHouse'
+keywords: ['INSERT', 'asynchronous inserts', 'compression', 'batch inserts']
+show_related_blogs: true
 ---
 
 import Image from '@theme/IdealImage';