docs: added templates updates for version 1.2.0-beta.7 (#128)

Author: dieppa

docs/get-started/gradle-plugin.md

@@ -63,6 +63,10 @@ flamingock {
 | Method | Description |
 |--------|-------------|
 | `community()` | Enables Community edition (adds BOM and core library) |
+| `sql()` | Adds SQL template and target system support |
+| `mongodb()` | Adds MongoDB sync template and target system support |
+| `dynamodb()` | Adds DynamoDB target system support |
+| `couchbase()` | Adds Couchbase target system support |
 | `springboot()` | Adds Spring Boot integration and test support |
 | `graalvm()` | Adds GraalVM native image support |
 | `mongock()` | Enables seamless migration from Mongock — imports audit log, detects legacy change units, and executes pending ones |
@@ -86,6 +90,38 @@ implementation("io.flamingock:flamingock-community")
 testImplementation("io.flamingock:flamingock-test-support")
 ```
 
+### sql()
+
+```kotlin
+implementation("io.flamingock:flamingock-sql-template")
+implementation("io.flamingock:flamingock-sql-targetsystem")
+```
+
+### mongodb()
+
+```kotlin
+implementation("io.flamingock:flamingock-mongodb-sync-template")
+implementation("io.flamingock:flamingock-mongodb-sync-targetsystem")
+```
+
+When `springboot()` is also enabled:
+
+```kotlin
+implementation("io.flamingock:flamingock-mongodb-springdata-targetsystem")
+```
+
+### dynamodb()
+
+```kotlin
+implementation("io.flamingock:flamingock-dynamodb-targetsystem")
+```
+
+### couchbase()
+
+```kotlin
+implementation("io.flamingock:flamingock-couchbase-targetsystem")
+```
+
 ### springboot()
 
 ```kotlin

docs/templates/create-your-own-template.md

@@ -17,20 +17,20 @@ While official Flamingock templates are experimental, you can already build and
 
 ## Dependency
 
-Creating a template requires the `flamingock-core-api` artifact on the classpath. This dependency is transitively included by the core Flamingock library, so you only need to declare it explicitly when the template lives in its own dedicated module (e.g., a reusable template library):
+Creating a template requires the `flamingock-template-api` artifact on the classpath. This dependency is transitively included by the core Flamingock library, so you only need to declare it explicitly when the template lives in its own dedicated module (e.g., a reusable template library):
 
 <Tabs groupId="gradle_maven">
   <TabItem value="gradle" label="Gradle">
 ```kotlin
 implementation(platform("io.flamingock:flamingock-community-bom:$version"))
-implementation("io.flamingock:flamingock-core-api")
+implementation("io.flamingock:flamingock-template-api")
 ```
   </TabItem>
   <TabItem value="maven" label="Maven">
 ```xml
 <dependency>
     <groupId>io.flamingock</groupId>
-    <artifactId>flamingock-core-api</artifactId>
+    <artifactId>flamingock-template-api</artifactId>
 </dependency>
 ```
   </TabItem>

docs/templates/mongodb-template.md

@@ -55,19 +55,20 @@ This single YAML file replaces what would typically require a Java class with an
 <Tabs groupId="gradle_maven">
   <TabItem value="gradle" label="Gradle">
 ```kotlin
-import io.flamingock.gradle.FlamingockTemplate.MONGODB
-
 flamingock {
     //...
-    templates(MONGODB)
+    mongodb()
 }
 ```
   </TabItem>
   <TabItem value="maven" label="Maven">
+
+Requires the [Flamingock BOM](../get-started/quick-start.md) in your `<dependencyManagement>` section:
+
 ```xml
 <dependency>
     <groupId>io.flamingock</groupId>
-    <artifactId>flamingock-java-template-mongodb</artifactId>
+    <artifactId>flamingock-mongodb-template</artifactId>
 </dependency>
 ```
   </TabItem>

docs/templates/sql-template.md

@@ -36,19 +36,20 @@ rollback: "DROP TABLE users;"
 <Tabs groupId="gradle_maven">
   <TabItem value="gradle" label="Gradle">
 ```kotlin
-import io.flamingock.gradle.FlamingockTemplate.SQL
-
 flamingock {
     //...
-    templates(SQL)
+    sql()
 }
 ```
   </TabItem>
   <TabItem value="maven" label="Maven">
+
+Requires the [Flamingock BOM](../get-started/quick-start.md) in your `<dependencyManagement>` section:
+
 ```xml
 <dependency>
     <groupId>io.flamingock</groupId>
-    <artifactId>flamingock-java-template-sql</artifactId>
+    <artifactId>flamingock-sql-template</artifactId>
 </dependency>
 ```
   </TabItem>

docs/templates/templates-how-to-use.md

@@ -15,31 +15,50 @@ Using a Flamingock Template is straightforward. Here's an example of how you can
 This section uses the **SQL Template** as example.
 :::
 
-## Step 1: Add the Template dependency
+## Step 1: Add the template dependency
 
-Ensure your **Flamingock Template** dependency is included in your project. Example of using `sql-template`:
+How you set up the dependency depends on where the template comes from.
+
+### Official Flamingock templates
+
+Official templates are included in the Flamingock Gradle plugin and the BOM, so no version management is needed. For example, to use the SQL Template:
 
 <Tabs groupId="gradle_maven">
   <TabItem value="gradle" label="Gradle">
 ```kotlin
-import io.flamingock.gradle.FlamingockTemplate.SQL
-
 flamingock {
     //...
-    templates(SQL)
+    sql()
 }
 ```
   </TabItem>
   <TabItem value="maven" label="Maven">
+
+Requires the [Flamingock BOM](../get-started/quick-start.md) in your `<dependencyManagement>` section. Then add the template dependency without a version:
+
 ```xml
 <dependency>
     <groupId>io.flamingock</groupId>
-    <artifactId>flamingock-java-template-sql</artifactId>
+    <artifactId>flamingock-sql-template</artifactId>
 </dependency>
 ```
   </TabItem>
 </Tabs>
 
+Each official template has its own plugin function (`sql()`, `mongodb()`, etc.) and BOM-managed artifact. See the individual template reference pages for the exact setup.
+
+### Third-party or community templates
+
+For templates published by third parties, add them as a standard dependency:
+
+```kotlin
+implementation("com.example:custom-template:1.0.0")
+```
+
+### In-project templates
+
+If the template is defined within your own project, no additional dependency is needed — Flamingock discovers it automatically via [ServiceLoader registration](./create-your-own-template.md#3-register-the-template-with-serviceloader).
+
 ## Step 2: Create the change file
 
 Template-based changes are defined in **YAML files** placed inside your application's resources directory. Each file represents a single change.