docs: Restructure documentation hierarchy

Author: timonback

docs/configuration/_category_.json

@@ -0,0 +1,7 @@
+{
+  "label": "Configuration",
+  "position": 30,
+  "link": {
+    "type": "doc", "id": "configuration"
+  }
+}

docs/configuration.md docs/configuration/configuration.mddocs/configuration.md renamed to docs/configuration/configuration.md

@@ -9,15 +9,6 @@ import CodeConfigurationAsyncApiDocket from '!!raw-loader!./snippets/_configurat
 
 # Configuration
 
-## Activating
-
-Springwolf is actived automatically as soon as one of the available plugin dependencies (e.g. `springwolf-kafka`)
-is added to the application classpath. 
-
-
-
-## Springwolf configuration
-
 There are 2 ways to configure springwolf:
 
 1. `application.properties`, which is simple and should suit most use-cases
@@ -34,6 +25,8 @@ There are 2 ways to configure springwolf:
   </TabItem>
 </Tabs>
 
+## Properties
+
 ### basePackage (required)
 
 It is recommended to structure the project such that all consumers and producers (classes containing listener/producer methods) are in the same package - it is not mandatory, and if they are scattered across multiple packages, just provide the highest in hierarchy package that contains all of them.

docs/documenting-consumers.md …s/configuration/documenting-consumers.mddocs/documenting-consumers.md renamed to docs/configuration/documenting-consumers.md docs/documenting-consumers.md renamed to docs/configuration/documenting-consumers.md

@@ -2,7 +2,7 @@
 sidebar_position: 60
 ---
 
-# Documenting Consumers
+# Consumers
 
 Springwolf comes with build-in support to auto-detect listeners of supported protocols.
 

docs/documenting-producers.md …s/configuration/documenting-producers.mddocs/documenting-producers.md renamed to docs/configuration/documenting-producers.md docs/documenting-producers.md renamed to docs/configuration/documenting-producers.md

@@ -2,7 +2,7 @@
 sidebar_position: 64
 ---
 
-# Documenting Producers
+# Producers
 
 Unlike consumers which are defined declaratively with an annotation, producers are defined imperatively, and there is no implementation uniform enough so that metadata can be picked up automatically.
 

docs/documenting-schemas.md docs/configuration/documenting-schemas.mddocs/documenting-schemas.md renamed to docs/configuration/documenting-schemas.md

@@ -8,7 +8,7 @@ import CodeBlock from '@theme/CodeBlock';
 import CodeSchemaGroovy from '!!raw-loader!./snippets/_schema_groovy.md';
 import CodeSchemaMaven from '!!raw-loader!./snippets/_schema_maven.md';
 
-# Documenting Schemas
+# Schemas
 
 Under the hood springwolf relies on swagger-core `ModelConverters`.
 

…nippets/_configuration_asyncApiDocket.md …nippets/_configuration_asyncApiDocket.mddocs/snippets/_configuration_asyncApiDocket.md renamed to docs/configuration/snippets/_configuration_asyncApiDocket.md docs/snippets/_configuration_asyncApiDocket.md renamed to docs/configuration/snippets/_configuration_asyncApiDocket.md

@@ -39,7 +39,7 @@ If not, whether
 Publishing messages from the UI is disabled by default due to security concerns.
 Springwolf does not offer authentication nor authorization, anyone can publish messages to (production) channels.
 
-Check the [configuration](configuration.md) to enable this feature.
+Check the [configuration](configuration/configuration.md) to enable this feature.
 
 Spring Security allows to limit access to authorized users.