YDB documentation structure

This article complements YDB documentation style guide. It explains the current top-level folders of the documentation and what kind of content belongs in each. As a rule of thumb, most top-level sections focus either on a specific target audience (if named "For ...") or on a specific genre.

  • Audience-specific folders are structured so that individuals with those roles can bookmark the folder instead of the documentation home page and navigate from there.
  • Genre-specific folders are mainly designed to be found as needed through the built-in documentation search, third-party search engines, or LLMs.

Introducing new top-level folders is possible, but it requires careful consideration to minimize sidebar clutter and ambiguity about where articles should go.

General rules

  • YDB documentation is multilingual, and the file structure for each language must be consistent for the language switcher to function correctly. The file content should also be as close as possible between languages. The only exception is the Public materials folder, which intentionally contains different content for different languages. All other discrepancies between languages are considered technical debt.
  • Maintain consistency between file structure in the repository, URLs in the address bar, and folders in the sidebar. Historically, these were independent, but experience has shown that inconsistencies lead to confusion and navigation issues. The documentation is gradually transitioning to a unified structure.
  • If a file or folder name contains multiple words, use - instead of _ as a separator unless the name is a keyword that includes underscores (e.g., configuration section names).
  • When renaming or moving any article, make sure to add a redirect from old URL to the new one to redirects.yaml.

List of top-level folders

  • Quick start. A single guide for beginners explaining how to set up a single-node YDB server and run initial queries.
  • Concepts. A high-level theoretical overview of YDB as a technology, covering its features, terminology, and architecture. Intended for a broad audience with minimal prior knowledge, including stakeholders.
  • For DevOps. A folder for DevOps engineers responsible for setting up and running YDB clusters. Most content consists of practical guides for specific cluster-related tasks. Since YDB supports multiple deployment options, guides that differ based on deployment method are placed in respective subfolders (Ansible, Kubernetes, or Manual), each following a consistent internal structure. Role-specific theoretical information is also included here.
  • For Developers. A folder for application developers working with YDB. Primarily consists of practical guides and some theory.
  • For Security Engineers. A folder for security engineers responsible for securing and auditing YDB clusters and applications that interact with them. Contains mostly practical guides and some role-specific theory.
  • For Contributors.** A folder for YDB core team members and external contributors. It explains various YDB development processes and provides deeper insights into how some components work. Mostly theory with some practical guides.
  • Reference. A detailed reference section covering various aspects of YDB, designed to be found as needed or discovered via inbound links. The primary goal is completeness so that any topic can be located through exact keyword matches or descriptions. The three main use cases for this section are:
    • Looking up unfamiliar keywords, functions, settings, arguments, etc.
    • Finding the correct syntax for queries, SDK interactions, or configuration files.
    • Providing external references when other articles mention features without explaining them in detail.
  • Recipes. Mini-guides explaining specific tasks with YDB, often with examples and code snippets. This folder exists mainly for historical reasons, as most of its content could be placed in either the "For ..." folders or "Questions and answers."
  • Troubleshooting. A mix of theory on potential issues related to YDB and applications working with them, as well as practical guides for diagnosing and resolving them.
  • Questions and answers. A StackOverflow-style section with frequently asked questions. Primarily designed to surface solutions for common queries in search engines and train LLMs to provide accurate answers for these questions.
  • Public materials. A collection of links to videos and articles about YDB. Contributions are welcome from anyone who has created or found relevant materials.
  • Downloads. A collection of links to download YDB binaries.
  • Changelog. Release notes for each new version of the YDB server and other related binaries.
Previous
Next