Update docs

Author: malczuuu

docs/01-problem4j-core/_category_.json

@@ -1,12 +1,8 @@
 ---
-sidebar_position: 1
+sidebar_position: 2
 ---
 
-# Setting Up & Configuration
-
-Setting up dependencies for using Problem4J Core library.
-
-## Dependency
+# Problem4J Core
 
 Add library as dependency to Maven or Gradle. See the actual versions on [Maven Central][maven-central]. **Java 8** or
 higher is required to use this library.

…-core/01-setting-up-and-configuration.md docs/02-problem4j-core.mddocs/01-problem4j-core/01-setting-up-and-configuration.md renamed to docs/02-problem4j-core.md docs/01-problem4j-core/01-setting-up-and-configuration.md renamed to docs/02-problem4j-core.md

@@ -0,0 +1,92 @@
+---
+sidebar_position: 1
+---
+
+# Problem4J & Spring Boot
+
+The premier integration of Problem4J with Spring Boot.
+
+## Getting Started
+
+```xml
+<dependencies>
+    <dependency>
+        <groupId>io.github.problem4j</groupId>
+        <artifactId>problem4j-spring-webmvc</artifactId>
+        <version>2.2.0</version>
+    </dependency>
+</dependencies>
+```
+
+```kt
+dependencies {
+    implementation("io.github.problem4j:problem4j-spring-webmvc:2.2.0")
+}
+```
+
+Integration with Spring Boot is very straightforward. By adding the library as a dependency to your project, you get
+auto-configuration for Spring WebFlux and Spring WebMVC. This means that no additional configuration is required to
+start using Problem4J in your application. You can throw `ProblemException` or any exception annotated with
+`@ProblemMapping` from your controllers and they will be properly handled by the library.
+
+Various Spring Boot internal exceptions are also mapped to `Problem` instances, so you can be sure that any exception
+thrown from your application will be handled and returned in a consistent format.
+
+```java
+@RestController
+public class HelloController {
+
+    @GetMapping("/hello")
+    public String hello() {
+        throw new ProblemException(Problem.of("Hello Error", 400, "something went wrong with /hello endpoint"));
+    }
+}
+```
+
+The most prominent build-in exceptions that are mapped to `Problem` instances include:
+
+- various validation errors,
+- missing request parameters,
+- type mismatches,
+- unsupported media types,
+- binding between request parameters and method arguments,
+- and many more.
+
+Format for all these exceptions aims to encapsulate all internal details of the framework used by the application.
+
+---
+
+To peek, log or debug exceptions handled by the library, you can implement `AdviceWebMvcInspector` interface. This
+interface provide a single method that is called whenever an exception is handled by the library. You can use this
+method to log the exception or perform any other custom logic.
+
+For WebFlux, use `AdviceWebFluxInspector` interface instead, which declares `ServerWebExchange` argument instead of
+`WebRequest`.
+
+```java
+@Component
+public class LoggingInspector implements AdviceWebMvcInspector {
+
+  private static final Logger log = LoggerFactory.getLogger(LoggingInspector.class);
+
+  @Override
+  public void inspect(
+      ProblemContext context,
+      Problem problem,
+      Exception ex,
+      HttpHeaders headers,
+      HttpStatusCode status,
+      WebRequest request) { // AdviceWebFluxInspector declares ServerWebExchange argument
+    log.info(
+        "Handled [status={} title={}]: exception={}",
+        status.value(),
+        problem.getTitle(),
+        ex.getClass().getSimpleName());
+  }
+}
+```
+
+---
+
+And with this, you have a basic setup of Problem4J with Spring Boot. You can now start throwing `ProblemException` from
+your controllers and they will be properly handled and returned in a consistent format.

docs/05-tutorials/01-problem4j-and-spring-boot.md

@@ -2,17 +2,37 @@
 sidebar_position: 2
 ---
 
-# Using it from scratch
-
-An example of setting up with an actual HTTP server.
-
-The primary integration provided by this library orbits around Spring Boot. However, the Problem4J libraries are fully
-featured to work in any environment.
-
-## Integration example for Javalin
+# Problem4J & Javalin
+
+The example integration of Problem4J with Javalin.
+
+Even though Problem4J is primarily focused on Spring Boot, it can be easily integrated with any Java application, as
+long as you can catch exceptions and convert them to `Problem` instances. This page demonstrates how to do this with
+[Javalin][javalin], a lightweight web framework for Java and Kotlin.
+
+## Getting Started
+
+```xml
+<dependencies>
+    <dependency>
+        <groupId>io.github.problem4j</groupId>
+        <artifactId>problem4j-core</artifactId>
+        <version>1.4.1</version>
+    </dependency>
+    <dependency>
+        <groupId>io.github.problem4j</groupId>
+        <artifactId>problem4j-jackson3</artifactId>
+        <version>1.4.1</version>
+    </dependency>
+</dependencies>
+```
 
-This chapter is a quick introduction to using Problem4J in a non-Spring Java application, using [Javalin][javalin]
-library for HTTP server functionality.
+```kt
+dependencies {
+    implementation("io.github.problem4j:problem4j-core:1.4.1")
+    implementation("io.github.problem4j:problem4j-jackson3:1.4.1")
+}
+```
 
 Note that this example also assumes, for JSON serialization, that you use Jackson (`JsonMapper`) in either v2 or v3 and
 the compatible [Problem4J Jackson](../problem4j-jackson) module.

…oblem4j-core/02-using-it-from-scratch.md …05-tutorials/02-problem4j-and-javalin.mddocs/01-problem4j-core/02-using-it-from-scratch.md renamed to docs/05-tutorials/02-problem4j-and-javalin.md docs/01-problem4j-core/02-using-it-from-scratch.md renamed to docs/05-tutorials/02-problem4j-and-javalin.md

@@ -0,0 +1,8 @@
+{
+  "label": "Tutorials",
+  "position": 5,
+  "link": {
+    "type": "generated-index",
+    "description": "Tutorials for learning about Problem4J - setting up and getting started."
+  }
+}