Update docs structure

.gitignore

@@ -76,6 +76,6 @@ locale/*
 
 # tntcxx submodule
 
-/doc/how-to/getting_started_cxx.rst
-/doc/how-to/_includes
-/doc/book/connectors/cxx/
+/doc/getting_started_cxx.rst
+/doc/_includes
+/doc/connector/cxx/

build_submodules.sh

@@ -28,12 +28,13 @@ mv -fv "${luatest_dest}/index.rst" "${luatest_dest}/_includes/"
 
 # Tarantool C++ connector
 tntcxx_root="${project_root}/modules/tntcxx"
-tntcxx_howto_dest="${project_root}/doc/how-to"
-tntcxx_api_dest="${project_root}/doc/book/connectors"
+tntcxx_howto_dest="${project_root}/doc/connector"
+tntcxx_api_dest="${project_root}/doc/connector"
 
 # Copy Tarantool C++ connector docs to the right places
 mkdir -p "${tntcxx_api_dest}/cxx/"
-mkdir -p "${tntcxx_howto_dest}/_includes"
-cp -rfv "${tntcxx_root}/doc/tntcxx_getting_started.rst" "${tntcxx_howto_dest}/getting_started_cxx.rst"
-cp -rfv "${tntcxx_root}/examples/" "${tntcxx_howto_dest}/_includes/examples/"
+mkdir -p "${tntcxx_howto_dest}/cxx/"
+mkdir -p "${tntcxx_howto_dest}/cxx/_includes/"
+cp -rfv "${tntcxx_root}/doc/tntcxx_getting_started.rst" "${tntcxx_howto_dest}/cxx/"
+cp -rfv "${tntcxx_root}/examples/" "${tntcxx_howto_dest}/cxx/_includes/examples/"
 cp -rfv "${tntcxx_root}/doc/tntcxx_api.rst" "${tntcxx_api_dest}/cxx/"

doc/enterprise/flight_recorder.rst → doc/admin/flight_recorder.rst

@@ -3,10 +3,14 @@
 Flight recorder
 ===============
 
+..  admonition:: Enterprise Edition
+    :class: fact
+
+    The flight recorder is available in the `Enterprise Edition <https://www.tarantool.io/compare/>`_ only.
+
 **Example on GitHub**: `flightrec <https://github.com/tarantool/doc/tree/latest/doc/code_snippets/snippets/config/instances.enabled/flightrec>`_
 
-The flight recorder available in the Enterprise Edition is an event collection tool that
-gathers various information about a working Tarantool instance, such as:
+The flight recorder is an event collection tool that gathers various information about a working Tarantool instance, such as:
 
 *   logs
 *   metrics
@@ -49,8 +53,8 @@ Tarantool continues writing to the existing ``current.ttfr`` file after restart.
 
 .. _enterprise-flight-recorder_configure:
 
-Configure a flight recorder
----------------------------
+Configure the flight recorder
+-----------------------------
 
 When the flight recorder is enabled, you can set the options related to :ref:`logging <cfg_logging-log>`,
 :ref:`metrics <metrics-reference>`, and storing the :ref:`request and response <internals-requests_responses>` data.

doc/book/admin/index.rst → doc/admin/index.rst

@@ -22,23 +22,21 @@ utilities:
 This chapter includes the following sections:
 
 .. toctree::
-   :maxdepth: 2
+   :maxdepth: 1
    :numbered: 0
 
-   instance_config
-   start_stop_instance
    modules
    logs
    security
    access_control
-   vshard_admin
    replication/index
    server_introspection
    daemon_supervision
    disaster_recovery
    backups
    upgrades
-   os_notes
    bug_reports
-   troubleshoot
+   flight_recorder
    monitoring
+   os_notes
+   troubleshoot

doc/book/admin/logs.rst → doc/admin/logs.rst

@@ -74,9 +74,6 @@ program.
 There is also the built-in function :ref:`log.rotate() <log-rotate>`, which you
 can call on an instance to reopen its log file after rotation.
 
-To learn about log rotation in the deprecated ``tarantoolctl`` utility,
-check its :ref:`documentation <tarantoolctl-log-rotation>`.
-
 
 .. _admin-logs-destination:
 

doc/book/admin/monitoring/metrics_reference.rst → doc/admin/monitoring/metrics_reference.rst

@@ -847,10 +847,10 @@ Saved tuples are divided into 3 categories: ``used``, ``read_view``, ``tracking`
 
 Each category has two metrics:
 
-- ``retained`` tuples - they are no longer in the index, but MVCC does not allow them to be removed.
-- ``stories`` - MVCC is based on the story mechanism, almost every tuple has a story.
-This is a separate metric because even the tuples that are in the index can have a story.
-So ``stories`` and ``retained`` need to be measured separately.
+-   ``retained`` tuples - they are no longer in the index, but MVCC does not allow them to be removed.
+-   ``stories`` - MVCC is based on the story mechanism, almost every tuple has a story.
+    This is a separate metric because even the tuples that are in the index can have a story.
+    So ``stories`` and ``retained`` need to be measured separately.
 
 ..  container:: table
 

doc/book/admin/os_notes.rst → doc/admin/os_notes.rst

@@ -38,12 +38,3 @@ Checking that it works:
 
     $ /etc/init.d/your_service_name start
     $ tail -f -n 100 /var/log/tarantool/your_service_name.log
-
-
-.. _admin-os_notes-freebsd:
-
-FreeBSD
--------
-
-To learn about specifics of using the deprecated ``tarantoolctl`` utility on FreeBSD,
-check its :ref:`documentation <tarantoolctl-freebsd>`.

doc/book/admin/replication/repl_monitoring.rst → doc/admin/replication/repl_monitoring.rst

@@ -7,7 +7,7 @@ To learn what instances belong to the replica set and obtain statistics for all
 these instances, execute a :ref:`box.info.replication <box_info_replication>` request.
 The output below shows the replication status for a replica set containing one :ref:`master and two replicas <replication-master_replica_bootstrap>`:
 
-..  include:: /how-to/replication/repl_bootstrap.rst
+..  include:: /platform/replication/replication_tutorials/repl_bootstrap.rst
     :start-after: box_info_replication_manual_leader_start
     :end-before: box_info_replication_manual_leader_end
 

doc/book/admin/replication/repl_recover.rst → doc/admin/replication/repl_recover.rst

@@ -43,7 +43,7 @@ hardware or network failure, or due to a programming bug.
 
 The master's upstream status is reported as ``disconnected`` when executing :ref:`box.info.replication <replication-monitoring>` on a replica:
 
-..  include:: /how-to/replication/repl_bootstrap_auto.rst
+..  include:: /platform/replication/replication_tutorials/repl_bootstrap_auto.rst
     :start-after: box_info_replication_auto_leader_disconnected_start
     :end-before: box_info_replication_auto_leader_disconnected_end
 

doc/alternate_build_master.rst

@@ -11,12 +11,10 @@
 
     overview_index
     getting_started/index
-    how-to/index
-    concepts/index
-    CRUD operations <reference/reference_lua/box_space>
-    book/admin/index
-    book/connectors
-    enterprise/index
+    platform/index
+    tooling/index
+    admin/index
+    connector/index
     reference/index
     contributing/index
     release/index