docs: prepare 1.12.0 release

Author: timonback

docs/faq.md

@@ -100,18 +100,23 @@ Be sure to enable fully qualified names ([`use-fqn`](configuration/configuration
 
 Spring Security allows to limit access to authorized users.
 
-### Consumers are detected multiple times (with different payloads)
+### Classes have fully qualified names (`io.springwolf.package.ClassName`)
 
-When Springwolf finds multiple consumers/producers for the same channel/topic, these are merged together.
-This is expected, as there are use-cases where different payloads are sent via the same channel/topic.
-
-Springwolf uses on scanners to find all consumer and producers in your application.
-Most likely two scanners found your consumer/producer each.
-See [configuration](configuration/configuration.mdx) to disable scanners.
+Disable the [fully qualified class name (FQN) option (`springwolf.use-fqn=false`)](configuration/configuration.mdx).
 
 ### Only one of multiple classes with the same name (different package) is detected
 
-Enable the fully qualified class name (FQN) option (`springwolf.use-fqn=true`) so that Springwolf uses the FQN internally.
+Enable the [fully qualified class name (FQN) option (`springwolf.use-fqn=true`)](configuration/configuration.mdx).
+
+### Springwolf interferes with OpenAPI documentation
+
+Springwolf uses `swagger-core` to analyze classes, which is used by some OpenAPI libraries like `springdoc-openapi`.
+`swagger-core` configuration is partly global and can't be isolated.
+
+Options:
+
+1. Use the same settings in Springwolf and the other library (including the [fully qualified class name (FQN) option (`springwolf.use-fqn=false`)](configuration/configuration.mdx)).
+2. Don't run Springwolf and the other library at the same time, for example by generating the documentation at build time.
 
 ### Generic types (List) don't contain item properties
 
@@ -133,40 +138,25 @@ class ListWrapper extends ArrayList<String> {}
 public void sendMessage(ListWrapper<String> msg) {}
 ```
 
-## Release Notes / Migration Guide / Updating / Upgrading
-
-Releases are managed in [GitHub Releases](https://github.com/springwolf/springwolf-core/releases),
-which feature noteworthy changes, the full changelog and notes on how to migrate.
-
-Since each release has a git _tag_, the [Springwolf examples for each plugin](https://github.com/springwolf/springwolf-core/blob/master/springwolf-examples) showcase the use of Springwolf for any previous version.
-
-### How to migrate from Springwolf 0.18.0 to 1.0.0
-
-See [Release 1.0.0](https://github.com/springwolf/springwolf-core/releases/tag/v1.0.0).
-
-### How to migrate from the deprecated `AsyncApiDocket` bean to Spring properties
-
-See [Issue #445](https://github.com/springwolf/springwolf-core/issues/445).
-
-### Is Spring Boot 2.X supported
-
-You can use an older version of Springwolf, which is build to support Spring Boot 2.X.
-However, these versions don't get any updates.
+### Consumers are detected multiple times (with different payloads)
 
-Last versions to support Spring Boot 2.X:
+When Springwolf finds multiple consumers/producers for the same channel/topic, these are merged together.
+This is expected, as there are use-cases where different payloads are sent via the same channel/topic.
 
-- `springwolf-amqp:0.6.0`
-- `springwolf-cloud-stream:0.1.0`
-- `springwolf-core:0.6.0`
-- `springwolf-kafka:0.10.0`
-- `springwolf-ui:0.6.0`
+Springwolf uses on scanners to find all consumer and producers in your application.
+Most likely two scanners found your consumer/producer each.
+See [configuration](configuration/configuration.mdx) to disable scanners.
 
 ## Usage Patterns
 
 ### How to access the generated documentation within java
 
 Use the `AsyncApiService` to access the generated documentation.
 
+### How to customize the generated documentation
+
+See the [customization page](configuration/customizing.md)
+
 ### How to generate the documentation at build time
 
 #### With Gradle
@@ -190,3 +180,31 @@ from the given `apiDocsUrl` and store it in the `outputDir` and with the given `
 
 If your application is unable to start up with the `bootRun` task, see if [customBootRun](https://github.com/springdoc/springdoc-openapi-gradle-plugin#customization)
 properties can help you.
+
+## Release Notes / Migration Guide / Updating / Upgrading
+
+Releases are managed in [GitHub Releases](https://github.com/springwolf/springwolf-core/releases),
+which feature noteworthy changes, the full changelog and notes on how to migrate.
+
+Since each release has a git _tag_, the [Springwolf examples for each plugin](https://github.com/springwolf/springwolf-core/blob/master/springwolf-examples) showcase the use of Springwolf for any previous version.
+
+### How to migrate from Springwolf 0.18.0 to 1.0.0
+
+See [Release 1.0.0](https://github.com/springwolf/springwolf-core/releases/tag/v1.0.0).
+
+### How to migrate from the deprecated `AsyncApiDocket` bean to Spring properties
+
+See [Issue #445](https://github.com/springwolf/springwolf-core/issues/445).
+
+### Is Spring Boot 2.X supported
+
+You can use an older version of Springwolf, which is build to support Spring Boot 2.X.
+However, these versions don't get any updates.
+
+Last versions to support Spring Boot 2.X:
+
+- `springwolf-amqp:0.6.0`
+- `springwolf-cloud-stream:0.1.0`
+- `springwolf-core:0.6.0`
+- `springwolf-kafka:0.10.0`
+- `springwolf-ui:0.6.0`

docs/add-ons.mdx renamed to docs/introduction/add-ons.mdx

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 50
+sidebar_position: 20
 ---
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';