Describe the problem that you experienced
The landing page frames most of the tradeoffs/nuance in forms as template vs reactive forms. Signal forms are condensed to a singular sentence: "TIP: If you're looking for the new Signal Forms, check out our essential Signal Forms guide!"
Enter the URL of the topic with the problem
https://angular.dev/guide/forms
Describe what you were looking for in the documentation
I would assume that these days, the Overview would more likely be one of the following
- A balance of all three. Like the signal forms subpage comparing all three form APIs: https://angular.dev/guide/forms/signals/comparison. In fact, IMO that page could stand in for the bulk of the existing Overview.
- Signal forms first with template/reactive forms given a brief overview, and then relevant links to their respective sections. Like the following:
Describe the actions that led you to experience the problem
Going to the forms main section from the root of the docs
Describe what you want to experience that would fix the problem
IMO the signal forms comparison vs reactive/template page copy could be the new forms Overview page. And to combine both my points above from "Describe what you were looking for in the documentation", I would say that the Overview should be a mix of both points: the comparison page but signal forms first, and then links to relevant pages for the legacy forms APIs and to the existing Overview copy as its own non-default forms overview page.
Describe the problem that you experienced
The landing page frames most of the tradeoffs/nuance in forms as template vs reactive forms. Signal forms are condensed to a singular sentence: "TIP: If you're looking for the new Signal Forms, check out our essential Signal Forms guide!"
Enter the URL of the topic with the problem
https://angular.dev/guide/forms
Describe what you were looking for in the documentation
I would assume that these days, the Overview would more likely be one of the following
Describe the actions that led you to experience the problem
Going to the forms main section from the root of the docs
Describe what you want to experience that would fix the problem
IMO the signal forms comparison vs reactive/template page copy could be the new forms Overview page. And to combine both my points above from "Describe what you were looking for in the documentation", I would say that the Overview should be a mix of both points: the comparison page but signal forms first, and then links to relevant pages for the legacy forms APIs and to the existing Overview copy as its own non-default forms overview page.