Skip to content

docs: introduce Signal Forms in the forms overview - #71896

Open
erkamyaman wants to merge 1 commit into
angular:mainfrom
erkamyaman:docs-add-signal-forms-to-forms-overview
Open

erkamyaman wants to merge 1 commit into
angular:mainfrom
erkamyaman:docs-add-signal-forms-to-forms-overview

Conversation

@erkamyaman

Copy link
Copy Markdown
Contributor

@JeanMeche 's note on #71383 said the forms overview "needs a rewrite" and should push Signal Forms more heavily now that they are stable (@publicApi 22.0). This is a first, scoped step. The intro now lists three approaches and says Signal Forms work best in new applications, with reactive forms still a solid choice (both are the existing wording of the Signal Forms overview). The comparison table gets a Signal Forms row, and Next steps gets a Signal Forms pill row. The detailed reactive versus template-driven comparison is unchanged.

The overview described only reactive and template-driven forms, with a
single tip pointing at Signal Forms. Now that Signal Forms are stable,
present them as the third approach: say they work best in new
applications, add them to the comparison table, and add them to the next
steps, while keeping the reactive and template-driven comparison.
@angular-robot angular-robot Bot added the area: docs Related to the documentation label Nov 9, 2026
@ngbot ngbot Bot added this to the Backlog milestone Nov 9, 2026
@pullapprove
pullapprove Bot requested a review from MarkTechson November 9, 2026 19:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: docs Related to the documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant