📝 (docs): enhance field map documentation with structured sections

Add structured sections such as "Samples" and "Metadata" to the
field-calculation-map and field-clear-map documentation. Introduce
class-description and class-options for better content organization.
Remove unnecessary horizontal rules for cleaner formatting.

These changes improve the readability and usability of the
documentation by providing clear, organized sections and examples,
making it easier for users to understand and implement the field maps.

Author: MrHinsh

docs/content/docs/reference/field-maps/field-calculation-map/index.md

@@ -15,6 +15,9 @@ date: 2025-06-24T12:07:31Z
 discussionId: 2756
 ---
 
+{{< class-description >}}
+
+
 ## Purpose and Use Cases
 
 This map is typically used when:
@@ -24,7 +27,6 @@ This map is typically used when:
 - You wish to **assign weights** to different numeric fields and store a computed score
 - Your source project uses **different naming or units**, and you want to normalise during migration
 
----
 
 ## Options
 
@@ -47,15 +49,13 @@ The [NCalc](https://github.com/ncalc/ncalc) engine supports:
 
 This multiplies the values of the two fields `Custom.EstimatedHours` and `Custom.HourlyRate`.
 
----
 
 ## Behaviour and Execution
 
 - The field map executes during **work item migration** and **before saving** to the target.
 - It applies to the **latest revision** only unless otherwise configured.
 - The calculated value **overwrites** any existing value in `targetField`.
 
----
 
 ## Field Resolution Rules
 
@@ -64,7 +64,6 @@ This multiplies the values of the two fields `Custom.EstimatedHours` and `Custom
 - If a referenced field is missing or null, the expression evaluation may fail.
 - Non-numeric fields will cause an evaluation error.
 
----
 
 ## Practices
 
@@ -73,12 +72,29 @@ This multiplies the values of the two fields `Custom.EstimatedHours` and `Custom
 - Always **test with a sample dataset** using `run-local` before production use.
 - Use `ApplyTo` to limit the map to only relevant work item types.
 
----
 
 ## Limitations
 
 - Only works with **numeric** source fields.
 - Errors during evaluation are **not recoverable** mid-run unless caught at validation.
 - Does **not support cross-work-item calculations**.
 
----
+
+
+## Samples
+
+### Sample
+
+{{< class-sample sample="sample" >}}
+
+### Defaults
+
+{{< class-sample sample="defaults" >}}
+
+### Classic
+
+{{< class-sample sample="classic" >}}
+
+## Metadata
+
+{{< class-metadata >}}

docs/content/docs/reference/field-maps/field-clear-map/index.md

@@ -10,11 +10,11 @@ aliases:
 - /learn/azure-devops-migration-tools/Reference/FieldMaps/FieldClearMap/index.md
 date: 2025-06-24T12:07:31Z
 discussionId: 2791
-
 ---
-The **FieldClearMap** is used to explicitly clear a field value on migrated work items by setting the target field to `null`. This is especially useful for sanitising or removing unwanted metadata, calculated fields, or legacy data that should not be carried into the target system.
 
----
+{{< class-description >}}
+
+The **FieldClearMap** is used to explicitly clear a field value on migrated work items by setting the target field to `null`. This is especially useful for sanitising or removing unwanted metadata, calculated fields, or legacy data that should not be carried into the target system.
 
 ## Purpose and Use Cases
 
@@ -24,7 +24,9 @@ This map is typically used when:
 - You're migrating to a system where a field is **no longer in use** or **read-only**.
 - A field value causes validation errors in the target and should be reset.
 
----
+## Options
+
+{{< class-options >}}
 
 ## Behaviour
 
@@ -33,7 +35,6 @@ This map is typically used when:
 - Only affects the latest revision unless the processor is configured to rewrite history.
 - Will silently **overwrite** any existing value in that field on the target.
 
----
 
 ## Practices
 
@@ -42,12 +43,27 @@ This map is typically used when:
 - Combine with `ApplyTo` to limit field clearing to specific types where the field is present.
 - Be cautious when clearing **system fields**; not all fields accept `null` values.
 
----
-
 ## Limitations
 
 - Does not validate whether the field actually exists on the target.
 - If `targetField` is a **required field** in the target process, this may cause a validation error.
 - Does not support conditional clearing; the field is always cleared if this map applies.
 
----
+
+## Samples
+
+### Sample
+
+{{< class-sample sample="sample" >}}
+
+### Defaults
+
+{{< class-sample sample="defaults" >}}
+
+### Classic
+
+{{< class-sample sample="classic" >}}
+
+## Metadata
+
+{{< class-metadata >}}