From 7cb4183f5830bac086769b60e3b3a06c385350f1 Mon Sep 17 00:00:00 2001 From: George Wilde Date: Fri, 21 Sep 2018 21:31:59 +0100 Subject: [PATCH] docs(forms): change headings (#25900) Remove "Form" sub-heading & move intro to template-driven form heading. PR Close #25900 --- aio/content/guide/forms.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/aio/content/guide/forms.md b/aio/content/guide/forms.md index 8302539399..0ee0384347 100644 --- a/aio/content/guide/forms.md +++ b/aio/content/guide/forms.md @@ -1,5 +1,4 @@ # Template-driven forms -#### Forms Forms are the mainstay of business applications. You use forms to log in, submit a help request, place an order, book a flight, @@ -8,6 +7,8 @@ schedule a meeting, and perform countless other data-entry tasks. In developing a form, it's important to create a data-entry experience that guides the user efficiently and effectively through the workflow. +#### Introduction to Template-driven forms + Developing forms requires design skills (which are out of scope for this page), as well as framework support for *two-way data binding, change tracking, validation, and error handling*, which you'll learn about on this page. @@ -25,8 +26,6 @@ You can run the in Stackblitz and download the cod {@a template-driven} -#### Template-driven forms - You can build forms by writing templates in the Angular [template syntax](guide/template-syntax) with the form-specific directives and techniques described in this page.