Move content to correct sections for generated summary

Signed-off-by: Danil Grigorev <[email protected]>

docs/book/src/01_user/00.md

@@ -0,0 +1,3 @@
+# User guide
+
+This section contains quick start and concepts relevant to a new operator user.

docs/book/src/user/quick-start.md → docs/book/src/01_user/02_quick-start.md

@@ -2,6 +2,8 @@
 
 This is a quickstart guide for getting Cluster API Operator up and running on your Kubernetes cluster.
 
+For more detailed information, please refer to the full documentation.
+
 ## Prerequisites
 
 - [Running Kubernetes cluster](https://cluster-api.sigs.k8s.io/user/quick-start#install-andor-configure-a-kubernetes-cluster).
@@ -25,42 +27,47 @@ kubectl create secret generic "${CREDENTIALS_SECRET_NAME}" --from-literal=AWS_B6
 
 ### Installing Cluster API Operator
 
-#### Method 1: Apply Manifests from Release Assets
-
-Before installing the Cluster API Operator this way, you must first ensure that cert-manager is installed, as the operator does not manage cert-manager installations. To install cert-manager, run the following command:
-
-```bash
-kubectl apply -f https://github.com/jetstack/cert-manager/releases/latest/download/cert-manager.yaml
-```
-
-Wait for cert-manager to be ready before proceeding.
-
-After cert-manager is successfully installed, you can install the Cluster API operator directly by applying the latest release assets:
+Add helm repository:
 
 ```bash
-kubectl apply -f https://github.com/kubernetes-sigs/cluster-api-operator/releases/latest/download/operator-components.yaml
+helm repo add capi-operator https://kubernetes-sigs.github.io/cluster-api-operator
+helm repo update
 ```
 
-#### Method 2: Use Helm Charts
-
-Alternatively, you can install the Cluster API operator using Helm charts:
+Deploy Cluster API components with docker provider using a single command during operator installation
 
 ```bash
-helm repo add capi-operator https://kubernetes-sigs.github.io/cluster-api-operator
-helm repo update
-helm install capi-operator capi-operator/cluster-api-operator --create-namespace -n capi-operator-system
+helm install capi-operator capi-operator/cluster-api-operator --create-namespace -n capi-operator-system --set infrastructure=docker --set cert-manager.enabled=true --set configSecret.name=${CREDENTIALS_SECRET_NAME} --set configSecret.namespace=${CREDENTIALS_SECRET_NAMESPACE}  --wait --timeout 90s
 ```
 
-##### Installing cert-manager using Helm chart
+Docker provider can be replaced by any provider supported by [clusterctl](https://cluster-api.sigs.k8s.io/reference/providers.html#infrastructure).
 
-CAPI operator Helm chart supports provisioning of cert-manager as a dependency. It is disabled by default, but you can enable it with `--set cert-manager.enabled=true` option to `helm install` command or inside of `cert-manager` section in [values.yaml](https://github.com/kubernetes-sigs/cluster-api-operator/blob/main/hack/charts/cluster-api-operator/values.yaml) file. Additionally you can define other [parameters](https://artifacthub.io/packages/helm/cert-manager/cert-manager#configuration) provided by the cert-manager chart.
+Other options for installing Cluster API Operator are described in [installation documentation](../02_installation/).
+
+# Example API Usage
 
-##### Installing providers using Helm chart
+Deploy latest version of core Cluster API components:
 
-Deploy Cluster API components with docker provider using a single command during operator installation:
+```yaml
+apiVersion: operator.cluster.x-k8s.io/v1alpha2
+kind: CoreProvider
+metadata:
+  name: cluster-api
+  namespace: capi-system
 
-```bash
-helm install capi-operator capi-operator/cluster-api-operator --create-namespace -n capi-operator-system --set infrastructure=docker --set cert-manager.enabled=true --set configSecret.name=${CREDENTIALS_SECRET_NAME} --set configSecret.namespace=${CREDENTIALS_SECRET_NAMESPACE}  --wait --timeout 90s
 ```
 
-Docker provider can be replaced by any provider supported by [clusterctl](https://cluster-api.sigs.k8s.io/reference/providers.html#infrastructure).
+Deploy Cluster API AWS provider with specific version, custom manager options and flags:
+
+```yaml
+---
+apiVersion: operator.cluster.x-k8s.io/v1alpha2
+kind: InfrastructureProvider
+metadata:
+ name: aws
+ namespace: capa-system
+spec:
+ version: v2.1.4
+ configSecret:
+   name: aws-variables
+```

docs/book/src/03_topics/01_capi-providers-lifecycle/00.md

@@ -0,0 +1,7 @@
+# Cluster API Provider Lifecycle
+
+This section contains lifecycle operations a user can perform on a provider manifest, such as:
+- Install
+- Upgrade
+- Modify
+- Delete

docs/book/src/03_topics/02_configuration/00.md

@@ -0,0 +1,3 @@
+# Configuration
+
+This section contains a list of frequent configuration tasks for CAPI Operator providers.

docs/book/src/topics/configuration/examples-of-api-usage.md → docs/book/src/03_topics/02_configuration/03_examples-of-api-usage.md

@@ -106,7 +106,7 @@ spec:
 
 5. As an admin, I would like to use the default fetch configurations by simply specifying the expected Cluster API provider names such as `aws`, `vsphere`, `azure`, `kubeadm`, `talos`, or `cluster-api` instead of having to explicitly specify the fetch configuration. In the example below, since we are using 'vsphere' as the name of the InfrastructureProvider the operator will fetch it's configuration from `url: https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/releases` by default.
 
-See more examples in the [air-gapped environment section](#air-gapped-environment)
+See more examples in the [air-gapped environment section](./01_air-gapped-environtment.md)
 
 ```yaml
 ---

docs/book/src/topics/configuration/configuration.md → docs/book/src/03_topics/02_configuration/05_provider-spec-configuration.md

@@ -1,6 +1,4 @@
-# Configuration
-
-## Provider Spec
+# Provider Spec
 
 1. `ProviderSpec`: desired state of the Provider, consisting of:
    - Version (string): provider version (e.g., "v0.1.0")

docs/book/src/03_topics/03_basic-cluster-api-provider-installation/00.md

@@ -0,0 +1,3 @@
+# Basic Cluster API provider installation
+
+This section provides an example to a CAPZ provider installation.

docs/book/src/04_developer/00.md

@@ -0,0 +1,6 @@
+# Developer
+
+This section contains regular developer tasks, such as:
+- Release
+- Development guide
+- Migration guide

docs/book/src/05_reference/00.md

@@ -0,0 +1,8 @@
+# Reference
+
+- [API reference](./01_api_reference.md)
+- [Glossary](./02_glossary.md)
+- [Code of Conduct](./03_code-of-conduct.md)
+- [Contributing](./04_contributing.md)
+- [CI Jobs](./05_ci-jobs.md)
+- [Providers](./06_providers.md)

docs/book/src/05_reference/03_code-of-conduct.md

@@ -0,0 +1,3 @@
+# Code of Conduct
+
+{{#include ../../../../code-of-conduct.md}}

docs/book/src/05_reference/04_contributing.md

@@ -0,0 +1,3 @@
+# Contributing
+
+{{#include ../../../../CONTRIBUTING.md}}

docs/book/src/SUMMARY.md

@@ -1,30 +0,0 @@
-# Summary
-
-[Introduction](./introduction.md)
-[Quick Start](./user/quick-start.md)
-- [Installation](./installation/installation.md)
-    - [Using plugin](./installation/plugin-installation.md)
-    - [Using Manifests from Release Assets](./installation/manifest-installation.md)
-    - [Using Helm Charts](./installation/helm-chart-installation.md)
-[Concepts](./user/concepts.md)
-- [Topics](./topics/topics.md)
-    - [Cluster API Provider Lifecycle](./topics/capi-provides-lifecycle.md)
-        - [Installing a Provider](./topics/installing-provider.md)
-        - [Upgrading a Provider](./topics/upgrading-provider.md)
-        - [Modifying a Provider](./topics/modifying-provider.md)
-        - [Deleting a Provider](./topics/deleting-provider.md)
-    - [Basic Cluster API Provider Installation](./topics/basic-capi-provider-installation.md)
-        - [Installing the CoreProvider](./topics/installing-core-provider.md)
-        - [Installing Azure Infrastructure Provider](./topics/installing-capz.md)
-        - [Deleting providers](./topics/deleting-providers.md)
-    - [Air-gapped Environment](./topics/air-gapped-environtment.md)
-    - [Injecting additional manifests](./topics/injecting-additional-manifests.md)
-- [Developer Guide](./developer/guide.md)
-    - [Releasing](./developer/release.md)
-    - [Version migration](./developer/v1alpha1-to-v1alpha2.md)
-- [Reference](./reference/reference.md)
-    - [API Reference](./reference/api_reference.md)
-    - [Glossary](./reference/glossary.md)
-    - [Code of Conduct](./code-of-conduct.md)
-    - [Contributing](./CONTRIBUTING.md)
-    - [CI Jobs](./reference/ci-jobs.md)