docs(forms): fix links in signal forms guides and use docs-pill-row links for next steps

This commit is contained in:
galmi 2025-11-20 15:17:40 +01:00 committed by Pawel Kozlowski
parent 313454bf17
commit 726dfad9db
5 changed files with 34 additions and 19 deletions

View file

@ -422,7 +422,9 @@ accountForm = form(this.accountModel, schemaPath => {
This guide covered building custom controls that integrate with Signal Forms. Related guides explore other aspects of Signal Forms:
- [Form Models guide](guide/forms/signals/models) - Creating and updating form models
<!-- TODO: Uncomment when guides are available -->
<!-- - [Field State Management guide](guide/forms/signals/field-state-management) - Using form state signals -->
<!-- - [Validation guide](guide/forms/signals/validation) - Adding validation to your forms -->
<docs-pill-row>
<docs-pill href="guide/forms/signals/models" title="Form models" />
<docs-pill href="guide/forms/signals/field-state-management" title="Field state management" />
<docs-pill href="guide/forms/signals/validation" title="Validation" />
<!-- <docs-pill href="guide/forms/signals/arrays" title="Working with Arrays" /> -->
</docs-pill-row>

View file

@ -74,7 +74,7 @@ These signals enable you to build responsive form user experiences that react to
Validation state signals tell you whether a field is valid and what errors it contains.
NOTE: This guide focuses on **using** validation state in your templates and logic (such as reading `valid()`, `invalid()`, `errors()` to display feedback). For information on **defining** validation rules and creating custom validators, see the Validation guide (coming soon).
NOTE: This guide focuses on **using** validation state in your templates and logic (such as reading `valid()`, `invalid()`, `errors()` to display feedback). For information on **defining** validation rules and creating custom validators, see the [Validation guide](guide/forms/signals/validation).
### Checking validity
@ -689,7 +689,12 @@ Checking both `touched()` and validation state ensures styles only appear after
## Next steps
Here are other related guides on Signal Forms:
This guide covered validation and availability status handling, interaction tracking and field state propagation. Related guides explore other aspects of Signal Forms:
- [Form Models guide](guide/forms/signals/models) - Creating models and updating values
- Validation guide - Defining validation rules and custom validators (coming soon)
<!-- TODO: UNCOMMENT WHEN THE GUIDES ARE AVAILABLE -->
<docs-pill-row>
<docs-pill href="guide/forms/signals/models" title="Form models" />
<docs-pill href="guide/forms/signals/validation" title="Validation" />
<docs-pill href="guide/forms/signals/custom-controls" title="Custom controls" />
<!-- <docs-pill href="guide/forms/signals/arrays" title="Working with Arrays" /> -->
</docs-pill-row>

View file

@ -526,11 +526,14 @@ async loadExistingUser() {
For forms that always start with existing data, you might wait to render the form until data loads in order to avoid a flash of empty fields.
<!-- TODO: UNCOMMENT WHEN THE GUIDES ARE AVAILABLE -->
<!-- ## Next steps
## Next steps
This guide covered creating models and updating values. Related guides explore other aspects of Signal Forms:
<!-- TODO: UNCOMMENT WHEN THE GUIDES ARE AVAILABLE -->
<docs-pill-row>
<docs-pill href="guide/forms/signals/field-state-management" title="Field State Management" />
<docs-pill href="guide/forms/signals/field-state-management" title="Field state management" />
<docs-pill href="guide/forms/signals/validation" title="Validation" />
<docs-pill href="guide/forms/signals/arrays" title="Working with Arrays" />
</docs-pill-row> -->
<docs-pill href="guide/forms/signals/custom-controls" title="Custom controls" />
<!-- <docs-pill href="guide/forms/signals/arrays" title="Working with Arrays" /> -->
</docs-pill-row>

View file

@ -45,15 +45,16 @@ The `Field` directive must be imported into any component that binds form fields
})
```
<!-- TODO: UNCOMMENT SECTION BELOW WHEN AVAILABLE -->
<!-- ## Next steps
## Next steps
To learn more about how Signal Forms work, check out the following guides:
<!-- TODO: UNCOMMENT SECTION BELOW WHEN AVAILABLE -->
<docs-pill-row>
<docs-pill href="essentials/signal-forms" title="Signal forms essentials" />
<docs-pill href="guide/forms/signals/models" title="Form models" />
<docs-pill href="guide/forms/signals/field-state-management" title="Field state management" />
<docs-pill href="guide/forms/signals/validation" title="Validation" />
<docs-pill href="guide/forms/signals/custom-controls" title="Custom controls" />
</docs-pill-row> -->
<!-- <docs-pill href="guide/forms/signals/arrays" title="Working with Arrays" /> -->
</docs-pill-row>

View file

@ -624,6 +624,10 @@ The `valid()` signal returns `false` while validation is pending, even if there
This guide covered creating and applying validation rules. Related guides explore other aspects of Signal Forms:
- [Form Models guide](guide/forms/signals/models) - Creating and updating form models
<!-- TODO: Uncomment when Field State Management guide is published -->
<!-- - [Field State Management guide](guide/forms/signals/field-state-management) - Using validation state in templates and displaying errors -->
<!-- TODO: UNCOMMENT WHEN THE GUIDES ARE AVAILABLE -->
<docs-pill-row>
<docs-pill href="guide/forms/signals/field-state-management" title="Field state management" />
<docs-pill href="guide/forms/signals/models" title="Form models" />
<docs-pill href="guide/forms/signals/custom-controls" title="Custom controls" />
<!-- <docs-pill href="guide/forms/signals/arrays" title="Working with Arrays" /> -->
</docs-pill-row>