cleanup

Author: tymondesigns

docs/docs.json

@@ -64,7 +64,6 @@
                         "group": "Validation",
                         "pages": [
                             "json-schema/validation/data-validation",
-                            "json-schema/validation/error-handling",
                             "json-schema/validation/version-features"
                         ]
                     }

docs/json-schema/advanced/conditional-validation.mdx

@@ -628,22 +628,3 @@ $complexSchema = Schema::object('complex_validation')
     Different validation rules for different API versions or client types.
   </Card>
 </CardGroup>
-
-## Next Steps
-
-<CardGroup cols={2}>
-  <Card
-    title="Schema Definitions"
-    icon="bookmark"
-    href="/advanced/definitions-refs"
-  >
-    Learn to create reusable schema components for complex conditional logic
-  </Card>
-  <Card
-    title="Dependent Schemas"
-    icon="link"
-    href="/advanced/dependent-schemas"
-  >
-    Explore property-dependent validation in modern JSON Schema versions
-  </Card>
-</CardGroup>

docs/json-schema/advanced/definitions-refs.mdx

@@ -443,7 +443,7 @@ $ecommerceApiSchema = Schema::object('ecommerce_api')
   <Card title="Maintainability" icon="wrench">
     Update shared schemas in one place and have changes propagate throughout your API.
   </Card>
-  <Card title="Consistency" icon="circle-check">
+  <Card title="Consistency" icon="shield-check">
     Ensure consistent validation rules across different parts of your application.
   </Card>
   <Card title="Modularity" icon="boxes">
@@ -539,22 +539,3 @@ $schema->addDefinition(
     Reuse field validation patterns across different forms and input structures.
   </Card>
 </CardGroup>
-
-## Next Steps
-
-<CardGroup cols={2}>
-  <Card
-    title="Conditional Validation"
-    icon="code-branch"
-    href="/advanced/conditional-validation"
-  >
-    Learn how to use definitions with conditional validation logic
-  </Card>
-  <Card
-    title="Code Generation"
-    icon="code"
-    href="/code-generation/from-classes"
-  >
-    Generate schemas with definitions from PHP classes
-  </Card>
-</CardGroup>

docs/json-schema/advanced/dependent-schemas.mdx

@@ -563,22 +563,3 @@ $schema->dependentSchemas([
     Profile settings where enabled features require additional information.
   </Card>
 </CardGroup>
-
-## Next Steps
-
-<CardGroup cols={2}>
-  <Card
-    title="Pattern Properties"
-    icon="regex"
-    href="/advanced/pattern-properties"
-  >
-    Learn about regex-based property validation patterns
-  </Card>
-  <Card
-    title="Conditional Validation"
-    icon="code-branch"
-    href="/advanced/conditional-validation"
-  >
-    Master if/then/else and other conditional validation techniques
-  </Card>
-</CardGroup>

docs/json-schema/advanced/pattern-properties.mdx

@@ -489,22 +489,3 @@ $schema->patternProperties([
     Allow users to define custom fields that follow specific naming rules.
   </Card>
 </CardGroup>
-
-## Next Steps
-
-<CardGroup cols={2}>
-  <Card
-    title="Object Schema"
-    icon="cube"
-    href="/schema-types/object"
-  >
-    Learn more about object validation and additional properties
-  </Card>
-  <Card
-    title="Code Generation"
-    icon="code"
-    href="/code-generation/from-classes"
-  >
-    Generate schemas with pattern properties from PHP classes
-  </Card>
-</CardGroup>

docs/json-schema/advanced/string-formats.mdx

@@ -211,22 +211,3 @@ $userProfileSchema->isValid($validProfile); // true
     Validate formatted data during import processes with appropriate type checking.
   </Card>
 </CardGroup>
-
-## Next Steps
-
-<CardGroup cols={2}>
-  <Card
-    title="String Schema"
-    icon="text"
-    href="/schema-types/string"
-  >
-    Learn more about string validation and pattern matching
-  </Card>
-  <Card
-    title="Validation Guide"
-    icon="check-circle"
-    href="/validation/data-validation"
-  >
-    Master data validation techniques and error handling
-  </Card>
-</CardGroup>

docs/json-schema/advanced/unevaluated-properties.mdx

@@ -423,22 +423,3 @@ $schema = Schema::object('strict_user', SchemaVersion::Draft_2019_09)
     Validate data during migration with strict control over allowed properties and transformations.
   </Card>
 </CardGroup>
-
-## Next Steps
-
-<CardGroup cols={2}>
-  <Card
-    title="Dependent Schemas"
-    icon="link"
-    href="/advanced/dependent-schemas"
-  >
-    Learn about property-dependent validation in modern JSON Schema
-  </Card>
-  <Card
-    title="Version Features"
-    icon="code-branch"
-    href="/validation/version-features"
-  >
-    Understand JSON Schema version compatibility and feature support
-  </Card>
-</CardGroup>

docs/json-schema/code-generation/from-classes.mdx

@@ -512,22 +512,3 @@ Validation rules like minLength, pattern, format are not extracted from docblock
     Generate schemas for application configuration classes.
   </Card>
 </CardGroup>
-
-## Next Steps
-
-<CardGroup cols={2}>
-  <Card
-    title="From Closures"
-    icon="code"
-    href="/code-generation/from-closures"
-  >
-    Learn to generate schemas from function signatures
-  </Card>
-  <Card
-    title="From Enums"
-    icon="list-ul"
-    href="/code-generation/from-enums"
-  >
-    Generate validation schemas from PHP enums
-  </Card>
-</CardGroup>

docs/json-schema/code-generation/from-closures.mdx

@@ -466,29 +466,10 @@ function handleUserStuff($data, $action, $options = []) {}
   <Card title="Form Processing" icon="file-text">
     Create client-side validation from server-side form processing functions.
   </Card>
-  <Card title="Data Pipeline" icon="stream">
+  <Card title="Data Pipeline" icon="workflow">
     Validate data transformations and processing steps in data pipelines.
   </Card>
   <Card title="Configuration" icon="cog">
     Generate validation for configuration and setup functions.
   </Card>
 </CardGroup>
-
-## Next Steps
-
-<CardGroup cols={2}>
-  <Card
-    title="From Enums"
-    icon="list-ul"
-    href="/code-generation/from-enums"
-  >
-    Generate validation schemas from PHP enums
-  </Card>
-  <Card
-    title="From JSON Schema"
-    icon="file-code"
-    href="/code-generation/from-json"
-  >
-    Import and work with existing JSON Schema definitions
-  </Card>
-</CardGroup>

docs/json-schema/code-generation/from-enums.mdx

@@ -628,29 +628,10 @@ try {
   <Card title="Configuration" icon="cog">
     Ensure application configuration uses only valid environment and option values.
   </Card>
-  <Card title="State Management" icon="state-machine">
+  <Card title="State Management" icon="workflow">
     Validate state transitions and status changes in business workflows.
   </Card>
   <Card title="Form Validation" icon="file-text">
     Generate client-side validation and form options from backend enums.
   </Card>
 </CardGroup>
-
-## Next Steps
-
-<CardGroup cols={2}>
-  <Card
-    title="From JSON Schema"
-    icon="file-code"
-    href="/code-generation/from-json"
-  >
-    Import and work with existing JSON Schema definitions
-  </Card>
-  <Card
-    title="Data Validation"
-    icon="check-circle"
-    href="/validation/data-validation"
-  >
-    Learn advanced validation techniques for enum values
-  </Card>
-</CardGroup>