Skip to content

Conversation

dhtclk
Copy link
Collaborator

@dhtclk dhtclk commented Aug 26, 2025

Summary

Adding doc_type to frontmatter of docs to enable diataxis categorization to be utilized for search and general organization.

Checklist

@dhtclk dhtclk requested review from a team as code owners August 26, 2025 22:03
Copy link

vercel bot commented Aug 26, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
clickhouse-docs Ready Ready Preview Comment Sep 19, 2025 7:36pm
clickhouse-docs-jp Building Building Preview Comment Sep 19, 2025 7:36pm
2 Skipped Deployments
Project Deployment Preview Comments Updated (UTC)
clickhouse-docs-ru Ignored Ignored Preview Sep 19, 2025 7:36pm
clickhouse-docs-zh Ignored Ignored Preview Sep 19, 2025 7:36pm

Copy link
Member

@Blargian Blargian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Please expand the front-matter check to require a category. It's no good adding if in 6 months all new pages don't have it. I need to do the same for the keyword tagging.

  • I'd ask to please go through and check manually as well. Just a 10 minute scan through these and I can see many incorrectly tagged pages e.g. docs/cloud/changelogs/24_06.md tagged as explanation but docs/cloud/changelogs/24_08.md is tagged as reference.

  • Let's have categories for landing page, changelog, they seem like distinct docs. Anything else you can think of that feels like a distinct category?

  • The difference between tutorial and how-to guide applied to ClickHouse docs is not clear to me (even after reading https://diataxis.fr/tutorials-how-to/). I wonder if just guide doesn't make more sense for our docs. We can always further refine with time. If you agree, just do a search and replace through the files to fix. Index.md files should be landing pages by convention.

sidebar_position: 2
sidebar_label: '2025'
title: '2025 Changelog'
doc_type: 'reference'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
doc_type: 'reference'
doc_type: 'changelog'

@@ -1,5 +1,6 @@
---
sidebar_label: Tabs Sample
doc_type: 'how-to'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can delete this file honestly

title: 'FAQ'
slug: /about-us/faq
description: 'Landing page'
doc_type: 'reference'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
doc_type: 'reference'
doc_type: 'landing page'

description: 'Understand what makes ClickHouse stand apart from other database management systems'
title: 'Distinctive Features of ClickHouse'
keywords: ['compression', 'secondary-indexes','column-oriented']
doc_type: 'reference'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
doc_type: 'reference'
doc_type: 'explanation'

slug: /about
title: 'About ClickHouse'
description: 'Landing page for About ClickHouse'
doc_type: 'reference'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
doc_type: 'reference'
doc_type: 'landing page'

description: 'Page describing when to use JSON'
keywords: ['JSON']
show_related_blogs: true
doc_type: 'reference'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
doc_type: 'reference'
doc_type: 'how-to'

title: 'Overview'
hide_title: true
description: 'Landing page for Best Practices section in ClickHouse'
doc_type: 'reference'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
doc_type: 'reference'
doc_type: 'landing page'

@Blargian
Copy link
Member

@dhtclk the remaining two files are getting flagged because they're autogenerated files. You'll need to check the SQL query here:

description: ''This section contains descriptions of server settings i.e settings
which cannot be changed at the session or query level.''
keywords: [''global server settings'']
sidebar_label: ''Server Settings''
sidebar_position: 57
slug: /operations/server-configuration-parameters/settings
title: ''Server Settings''
and here:
'---
title: ''Session Settings''
sidebar_label: ''Session Settings''
slug: /operations/settings/settings
toc_max_heading_level: 2
description: ''Settings which are found in the ``system.settings`` table.''
. This is from back in medieval times before the invention of <!--AUTOGENERATED_BEGIN--><!--AUTOGENERATED_END-->

@dhtclk dhtclk merged commit cba9548 into main Sep 19, 2025
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants