> For the complete documentation index, see [llms.txt](https://ng-girls.gitbook.io/todo-list-tutorial/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ng-girls.gitbook.io/todo-list-tutorial/more-workshops/forms_intro.md). # Forms As you've probably noticed, there is always more than one way to implement a solution for a feature. This is what makes programming exciting and code open to collaboration and discussion. Today you will learn another approach to handle data-entry tasks- forms. Angular supports **template-driven** and **reactive** forms to help developers work with a form's input elements. Each form type has its advantages and disadvantages so it's good to understand the differences and why you use one type over another. Please take a moment to read about Angular forms from [angular.io](https://angular.io/guide/forms-overview). If you are already familiar with **template-driven** and **reactive** forms in Angular, we recommend refreshing your memory so that we can all approach the next steps in the tutorial on the same footing. Please feel free to take the time you need to familiarize yourself with Angular forms and make notes as necessary. Mentors are happy to answer any questions. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://ng-girls.gitbook.io/todo-list-tutorial/more-workshops/forms_intro.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.